neulab / neulab/agent-data-protocol
Audit: align sample stages and complete trajectories
Open
@neubig is already working on this.
Since Jul 14, 2026.
- Dominant language
- Python
- Stars
- 193
- Forks
- 17
- PR merge metrics
- No merged PRs in 30d
Description
Dataset quality audit category: Sample alignment and completeness issues
The May 2026 dataset audit found 27 issues in this class:
sample_alignment: 15trajectory_completeness: 8sample_representativeness: 4
Problem
Some datasets do not keep the same records across sample_raw.json, sample_std.json, and sample_sft.json, while others produce trajectories that end mid-action or combine multiple independent tasks into one trajectory. This makes examples hard to inspect, regenerate, and trust.
Examples
android_in_the_wild: stage counts do not match;sample_raw.jsonhas 3 records, butsample_std.jsonandsample_sft.jsonhave 1.go-browse-wa: stage counts do not match;sample_raw.jsonhas 100 records, butsample_std.jsonandsample_sft.jsonhave 5.nemotron_terminal_corpus: stage counts do not match;sample_raw.jsonhas 5 records, butsample_std.jsonandsample_sft.jsonhave 4.androidcontrol: standardized ids (0,20,40) do not match SFT ids (androidcontrol-0,androidcontrol-1,androidcontrol-2).CharlieDreemur_OpenManus-RL: three of five standardized trajectories end on anapi_actionsuch asperform_actionor a weather API call without a following observation or final answer.agenttuning_os: a second task is appended after a completed first task, making one ADP trajectory contain multiple independent OS problems.
Suggested work
- Add or strengthen tests requiring sample stage counts and ids to align across raw, standardized, and SFT files.
- Ensure converters preserve the same record order through the pipeline.
- Avoid dropping raw records silently during standardization or SFT conversion; if filtering is intentional, document and encode it deterministically.
- Require trajectories to end with a plausible terminal state, final answer, or documented reason for truncation.
- Split multiple independent tasks into separate trajectories where appropriate.
- Keep representative samples small but broad enough to cover important action/observation edge cases.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Assessment
This issue has not been assessed yet.