# The fleet coder's contract (CONTRACT-fleet-coder.md)

What a coder does when it reads one slice of a branch-B room.

**What it holds**

What the fleet coder does (steps 1 to 3 on its slice, then a slice `case.md` and `notes.md`) and does not do (no themes, no counter-reading search, no verdict, no `emit.close()`). What it gets: `brief.md`, `timeline.md`, `lexicon.md`, its slice, and the openings of earlier threads still running, marked as context and never coded. The two edges of a slice, and the tags every episode ends with: `[closed]`, `[inherited]`, `[unresolved]`. The rule that a `coded` thread must keep a live code and that a large read exclusion needs its cited line. The outputs and the closing `close_run.py . --role fleet --preflight`.

**Who writes it, and when**

The instrument's author. `tools/fleet.py dispatch` copies it into each `fleet/batch_NN/`.

**Why it exists**

A slice starts and stops mid-week, so the coder "cannot see it begin"; the tags let "the case lead reassemble the week". The coder is "not given any other coder's codes, case or notes", and the two facts files are "facts, not readings".

**Where**

[CONTRACT-fleet-coder.v32.md](../../../coder/instrument/v32/CONTRACT-fleet-coder.v32.md); a copy in each `run/fleet/batch_NN/` of a room's run archive.

Checked against: CONTRACT-fleet-coder.v32.md, tools/fleet.py, CONTRACT-case-lead.v32.md