Datasetpublic

thebajajra/muse-trajectory-annotations

MUSE trajectory annotations Judge annotations of coding-agent trajectories. Subset: commit-hook Event-sequence annotations of 7,593 transcript windows drawn from 433 complete trajectories of a coding agent working on a git pre-commit-hook task (E1). For each window the judge identifies the earliest concrete workaround opportunity, the earliest rejection of a workaround (labelled normative / instrumental / mixed / unclear), and the earliest later adoption, with… See the full description on the dataset page: https://huggingface.co/datasets/thebajajra/muse-trajectory-annotations.

sourceHugging Faceupdated 28d agoView on Hugging Face

0likes68downloads

Dataset Card

MUSE trajectory annotations

Judge annotations of coding-agent trajectories.

Subset: `commit-hook`

Event-sequence annotations of 7,593 transcript windows drawn from 433 complete trajectories of a coding agent working on a git pre-commit-hook task (E1). For each window the judge identifies the earliest concrete workaround opportunity, the earliest rejection of a workaround (labelled normative / instrumental / mixed / unclear), and the earliest later adoption, with quoted evidence.

—Judge: glm-5.3 (z.ai), thinking enabled, temperature 0.0. Most windows annotated at reasoning_effort: high; the first 114 at max (ids listed in commit-hook/run_metadata.json).
—Record shape: window_id (joins back to the source trajectories), payload (labels conforming to the frozen role schema), parser_failed, attempts (1-3 draws), reasoning_chars, error. Windows that never parsed are kept with parser_failed: true so denominators stay honest.
—Families W1-W9 refer to the study's workaround taxonomy; turn indices are absolute turn numbers in the source trajectory.
—One file per shard: commit-hook/results_shard_000.jsonl ... _007.jsonl, ~1,000 windows each. run_metadata.json records judge settings and the deviations from the study manifest.