D2 · Adaptation: labelers and verdicts
Collect the communities’ answers
D2 brings back two kinds of answer: each original lead’s account of its community in the model’s terms, and independent readers’ judgments about how well the model fits. It checks that those answers arrived intact before interpreting their implications.
Where this stage starts
D1 has prepared and fixed the tasks. The adaptation handler resumes each matching community lead with its original conversation and files. Separate readers receive the verdict packets. The aggregator’s check leg opens after these jobs have returned their files.
What the leads, readers and aggregator do
Each community lead rewrites its local account using the population model. It records where the model applies, where it needs detail or a condition, where the community contradicts it, and where a new idea may be needed. Each claim needs evidence from that community. A community needing no adaptation still submits an explicit answer; silence is a missing return.
Two independent readers also judge whether the model accounts for the community, accounts for it with something left over, fails to account for it, or cannot be judged from the evidence. Their reasons and disagreements remain visible. The lead’s own assessment sits beside these verdicts and does not replace them.
The ingestion tools check model versions, identifiers, citations, required fields and completeness. The handler can return a failed response for repair. The aggregator then inspects the report and a seeded sample of ten local accounts: do they describe how those communities organized, or merely repeat the population model?
These checks establish whether a return can be read and traced. They do not decide that a proposed correction is scientifically warranted. A high disagreement rate or a large number of exceptions is something to report, not a reason to adjust answers until the numbers look better.
What the next stage receives
D3 receives the accepted adaptation records, both verdicts, local accounts and explicit gaps. It can now assess the substance of corrections. D2 leaves that adjudication to D3 rather than mixing collection with judgment.
What the output files contain
Open a file group for its purpose. These are descriptions of the stage’s outputs. Markdown files hold prose; JSONL files hold one structured record per line.
The adaptation ledgeradaptations.jsonl
adaptations.jsonl collects validated return lines with
their evidence and model version. “Validated” here means that the
required structural checks passed, not that the aggregator has accepted
the claim.
The independent judgmentsverdicts-D.jsonl
verdicts-D.jsonl preserves the readers’ fit judgments
and reasons beside the leads’ assessments. It makes disagreement visible
instead of reducing two readings to a vote.
The local accounts and comparison tablerooms/<sub>/model-D.md, verdict-D, _views/rooms-x-elements.tsv
rooms/<sub>/model-D.md holds each returned local
account, with its verdict-D record alongside.
_views/rooms-x-elements.tsv arranges communities against
model elements so D3 can inspect all evidence concerning one claim
together.
What arrived, failed or remains missingingest-D.md, notes-D2.md, RUN.json, run_manifest.json, handback-D2.md
ingest-D.md reports accepted lines, failed rules and
missing communities. notes-D2.md records the sample checks
and substantive cautions. RUN.json records return counts;
run_manifest.json records the models used.
handback-D2.md carries defects and unresolved operational
matters forward.
Full stage description
Read the complete technical card for exact tasks, reading boundaries, checks and closing rules. The explanation above is a guide; the card holds the instructions.
How the stage is divided into legs
D2a: check. Repeats: no. Interview point: -.
Changes recorded for this run
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.
Source versions and hashes identify the exact technical documents reproduced here.