r/place A fruit fly for organization science

B3 · Coding: fleet

Read the material independently, twice

B3 applies the shared scheme across the analysed communities. Two independent readers examine every local theme, making differences in interpretation visible before the aggregator settles them.

Where this stage starts

B2 has frozen the categories and tested their instructions. B3 receives that scheme and all the local themes, with the concepts and participants’ words beneath them. A “reader” is a separate model conversation. The collection of reader jobs is called the fleet.

What the aggregator and handler do

The aggregator prepares batches that keep each community together. A large community may require several files, but one reader receives all its parts. Its second reading goes to a different reader. The allocation connects communities and readers across batches, allowing the analysis to examine whether particular readers or batch contexts produce different answers.

Each reader gets the scheme and its assigned evidence. It can see the labels of the community’s other themes for context, but not another reader’s answers, the aggregator’s notes or the canvas outcome. It assigns themes from their underlying concepts rather than relying on a community coder’s label alone. If one category does not capture the material, multiple placements need reasons.

The handler runs the jobs separately. The aggregator then checks what returned: whether every required item was read twice, whether replies are complete, and whether all category references are valid. A missing or truncated reply is a delivery problem, not evidence that two readers disagree.

Reference items measure how closely readers follow the author’s intended distinctions. Further checks examine changes across a batch and variation among readers. These results reveal how consistently the instrument works. They cannot establish that the categories are the best explanation of organizing.

What the next stage receives

B4 receives both readings, their reasons, and a record of coverage and uncertainty. B3 preserves disagreement instead of resolving it by majority vote. B4 must return to the evidence to decide what each disagreement means.

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.

Who read whatbatches-B3.jsonl, RETURN-B3.md

batches-B3.jsonl records the allocation of communities, items and reference examples. The packet files built from it contain the actual material served. RETURN-B3.md specifies the reply format, so the served task can be compared with the answer.

The original placements and reconsiderationsassign_raw.jsonl, assign_pass2.jsonl

assign_raw.jsonl preserves the first placements that B4 will adjudicate. assign_pass2.jsonl records each reader’s reconsiderations after finishing its batch. The second pass measures changes within that reading context; it does not overwrite the first.

Material assigned to several categoriesmultiplacement_log.jsonl, multiplacement_register-B3.md

multiplacement_log.jsonl records why an item needs more than one placement. multiplacement_register-B3.md summarizes recurring combinations, which later stages inspect as possible overlaps or defects in the scheme.

Consistency, context and remaining problemsfidelity-B3.md, position-B3.md, agent_report-B3.md, notes-B3.md, run_manifest.json

fidelity-B3.md reports matching against reference answers. position-B3.md examines changes with position in a batch. agent_report-B3.md examines reader and context variation. notes-B3.md explains choices, reissues and limits; the run_manifest.json entry records models and settings.

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
  • B3a: build. Repeats: no. Interview point: -.
  • B3b: check. Repeats: no. Interview point: -.

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

Chat Online