D3 · Adaptation: adjudication
Decide what the return changes
D3 asks which community responses require a change to the model, which describe local variations, and which remain unresolved. It is the substantive review of the answers collected in D2.
Where this stage starts
D2 has supplied local accounts, adaptation lines, independent verdicts and a record of missing returns. The aggregator has the fixed model those communities answered. It examines responses by model element, so corrections concerning the same claim can be compared across communities.
What the aggregator does
For each proposed adaptation, the aggregator returns to its evidence and records a decision: accept it, modify it with a reason, reject it, or retain it as a supported local particular. Unsupported or unresolved claims remain pending. Original responses stay in the record.
Similar corrections from more than one community trigger a closer comparison. Repetition alone does not establish a shared mechanism. The aggregator must show that the evidence warrants the same change, condition or distinction. A claim supported only in one community can stay in that local account without becoming a new population-wide element.
The aggregator also investigates communities the model could not explain. Some organized in a way the model misses. Others fall outside its subject, or have too little evidence to judge. These are different limits and must not be combined into one failure score. Disputed verdicts and tentative claims from the field account receive explicit rulings too.
If the model changes, affected communities must see the revised version. The aggregator documents how they were identified; uncertain scope requires a return to all communities. The handler resumes their return leads, and revised accounts and verdicts are checked again. A small pilot cannot certify every affected account.
What the next stage receives
D4 receives one frozen model version and an adjudicated record of adaptations tied to it. Original fit, current local adequacy and shared corrections stay separate. The model cannot be frozen at a newer version than the one served to the affected communities.
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.
Decisions on each responseadjudications.jsonl, verdicts-D.jsonl, findings.jsonl
adjudications.jsonl records rulings and reasons while
preserving original lines. verdicts-D.jsonl retains reader
verdicts alongside later rulings. findings.jsonl records
claims changed or bounded by the return.
The revised model and coding trailmodel/, model/history.jsonl, tier_history.jsonl, scheme_v2.jsonl, assignments_final.jsonl
model/ holds the model; model/history.jsonl
records revisions. tier_history.jsonl records category
changes. Where categories change, scheme_v2.jsonl and
assignments_final.jsonl are rewritten to keep the evidence
ladder consistent.
Who was rechecked, and against whatrecheck-scope.json, handoff-D/recheck/, adaptations-recheck.jsonl, verdicts-recheck-D.jsonl
recheck-scope.json distinguishes affected and unaffected
communities with reasons. handoff-D/recheck/ contains the
revised tasks and model. adaptations-recheck.jsonl and
verdicts-recheck-D.jsonl preserve the new responses
alongside earlier ones.
Exceptions and limitsuncomposed-D.md, exception-report-D.md
uncomposed-D.md explains cases the model could not
account for. exception-report-D.md distinguishes shared
changes, local particulars and unresolved claims, rather than treating
all adaptations as failures.
The frozen result and handoffnotes-D3.md, handback-D3.md, out/_closes/model-D3.sha256
notes-D3.md explains what the recheck established and
what remains uncertain. handback-D3.md summarizes the
handoff. out/_closes/model-D3.sha256 identifies the exact
model version carried into the taxonomy.
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
D3a: element group. Repeats: yes. Interview point: -.D3b: recheck. Repeats: no. Interview point: -.D3c: freeze and re-read. Repeats: no. Interview point: end.
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. D3 closed at D3c on 24 October 2026 in source commit 0990f903d412. The baseline catalogue c070d990 predates that close. See the historical context for decision rows and per-community fork evidence.
Source versions and hashes identify the exact technical documents reproduced here.