oosnow/mctd-opd-cache

MCTD optional OPD annotation snapshots

Consistent SQLite backups of the existing ALFWorld, ScienceWorld, PlanCraft and EB-Habitat teacher-output stores. They retain outputs regardless of success, with separate trajectory_outcomes labels where available. Missing outcome labels mean unknown, not success. Publication does not re-label these entries.

Environment	Output records	Outcome records
ALFWorld	275,140	243,700
ScienceWorld	15,246	15,246
PlanCraft	3,248	3,248
EB-Habitat	39,938	0

Outputs and outcomes are not necessarily one-to-one. The same context may have multiple results and episode outcomes. SQLite quick_check, SHA-256 and archive inventories are checked during export. Use the exact manifest counts if a newer revision differs from this card.

python scripts/download_resources.py --environment all --with-cache

Reuse contract

These caches preserve original namespace/context/payload keys, provenance, quality flags and outcomes. Historical path or model-contract differences can prevent cache hits on another machine. Only compatible entries may be reused; this snapshot does not promise that every historical output will hit, and the download does not rekey incompatible E+C supervision.

Duplicate static-success indexes are deliberately omitted: the existing training code rebuilds them from the teacher dataset in oosnow/mctd-data. These caches are optional acceleration inputs, not success-only SFT data. Keep the algorithm's outcome-aware reuse and reward-weighting rules.

Model management labels are not proof of the actual generator. Preserve the original backend provenance; multiple teacher and scorer runs are represented. The files contain no model weights, API credentials or training optimizer state. Environment-derived/generated material remains subject to applicable upstream/provider terms; this card does not establish a new blanket license.

The Habitat snapshot (eb-habitat-20260909.tar.gz) has no separate trajectory outcome records. These entries are unknown-outcome outputs, not successful or failed trajectory labels. They must not bypass outcome-aware reuse rules. Successful static trajectories are distributed separately in mctd-data.