D2: Adaptation: labelers and verdicts
Ask the original community leads what the model explains and misses.
This is a reading key. The linked contract and card hold the rules.
Reading order
- Contract, method, standing instructions.
- Your recorded platform: Claude or Codex.
- Full D2 card, then the run's head, diary and handler deliveries as that card prescribes.
Inputs and permitted reading
Use the full card's startup packet and reading boundaries. Do not use files from later stages merely because this repository contains them. Historical interviews use the files in their selected bundle.
Outputs, quoted from the card
adaptations.jsonl (ingested, validated);
verdicts-D.jsonl; ingest-D.md;
_views/rooms-x-elements.tsv (generated);
rooms/<sub>/model-D.md and verdict-D
copied from the drops; notes-D2.md; the D2 counts in
RUN.json; a run_manifest.json entry for the
labelers' model and the readers' model; handback-D2.md.
Legs
D2a: check. Repeats: no. Interview point: -.
Checks and handback
The stage card governs its checks. The handler and leg controller govern opening, close, pause and recovery. Do not infer permission to start from this page. Keep notes and the head current; the conversation and filesystem must match at any resumable close.
Published record
Status: finished, 1 recorded closed legs. This
describes source publication c070d990be88, not live
state.
Historical instructions and settings
Study-specific settings: the 15 October decision specified a 5.6 resume followed by a 6.1 return. Native D2 turns checked for all 14 shared communities use GPT-6.1 Sol, medium. Their run.json files retain resumed_with=5.6; that field is not the model of those answer turns. On 21 October the D3 re-check was assigned GPT-6.1 Sol, medium. Its return records name 6.1 and the same D2 sessions, but omit effort. This website review did not inspect every D3 native turn or all 705 D2 histories. See the historical context for decision rows and per-community fork evidence.
Historical context and evidence.