r/place A fruit fly for organization science

B4 · Coding: adjudication and freeze

Resolve placements by returning to evidence

B4 turns the independent readings into a reasoned set of placements. Its central question is not which reader wins, but what the source material warrants under the existing scheme.

Where this stage starts

B3 has returned two readings for each local theme. B4 compares these with each other and with the author’s earlier grouping. It also has the scheme, the underlying concepts and the reasons readers gave. Agreement between two readers can still differ from the author’s original interpretation.

What the aggregator does

The aggregator first distinguishes failed delivery from a real difference in interpretation. Then it examines disputed placements without using reader identity as a shortcut. It reads the evidence and asks whether the problem lies in ambiguous category rules, a theme that bundles several acts, a reader’s error, the author’s error, or material that truly belongs in more than one category.

An adjudication is a written decision with a reason. It can keep a reader’s answer, choose a category neither reader selected, retain several justified placements, or leave uncertainty explicit. The original answers remain in the record. Where local community coders themselves disagree about the case, both readings and the affected claims must be identified.

The aggregator does not rewrite the frozen scheme here. Keeping the rules fixed separates two questions: where this item belongs under the present rules, and whether the rules need changing. The second belongs to C1, which can inspect the whole pattern of problems.

Finally, fresh readers check samples of settled placements: a random sample and a sample of adjudicated items. Those results are reported separately. Agreement after the aggregator has settled disputes is not the original independent agreement rate and should not be presented as such.

What the next stage receives

C1 receives a complete placement record, the reasons behind disputed decisions, and evidence about which category boundaries failed. It can revise the scheme with a clear account of what prompted each change.

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 decisions and settled placementsdisagreements.jsonl, assign_final.jsonl, adjudication_report.md

disagreements.jsonl records each ruling, diagnosis and supporting evidence. assign_final.jsonl records the resulting placements under the current scheme. adjudication_report.md explains the overall pattern and what remains uncertain.

Author, reader and community coder differencestransmission-B4.md, coder_conflicts.jsonl

transmission-B4.md separates kinds of author-reader disagreement. coder_conflicts.jsonl records conflicts in the local coding, so a later claim does not hide incompatible readings of the same material.

The fresh checkRETURN-B4.md, reassign.jsonl, transmission-after-revision-B4.md

RETURN-B4.md tells new readers how to answer. reassign.jsonl preserves their placements for comparison with the settled record. transmission-after-revision-B4.md reports that comparison, including the separate samples; its filename does not mean B4 has rewritten the category scheme.

Decisions that need to travel forwardnotes-B4.md, run_manifest.json

notes-B4.md records methodological choices, remaining problems and matters for C1. The stage’s run_manifest.json entry records the reader setup. Together these let a reviewer distinguish a technical repair, a substantive judgment and a deferred scheme revision.

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
  • B4a: adjudicate packet. Repeats: yes. Interview point: -.
  • B4b: sample build. Repeats: no. Interview point: -.
  • B4c: check and final placements. Repeats: no. Interview point: end.
Changes recorded for this run

Historical instructions and settings

The three shared B4 checkpoints retain a stage-file copy that differs from the current canonical card. Decision row 96 introduced three-placement adjudication on 12 October. The 21:19Z delivery explicitly opens B4a-01 under that amended rule, and notes-B4 records its use. A further rule changed packet 4 at item 401; earlier affected rulings were revisited at B4a-05. The saved file hash alone does not describe these handler-delivered amendments. Saved card SHA-256: bb5cc6a5690643e43d2e8a600efb4c750fc499bf2c2abea6c90a94861f0e1357. Current canonical card SHA-256: 7fb68adfcd6a1dab15368728559d3eb3c91162c555a8a69b26a53571dfd16ebe.

Historical context and evidence.

Source versions and hashes identify the exact technical documents reproduced here.

Chat Online