# `FLEET.md`

The fan-out to readers, the figures, and the return.

## What it holds

**§1 The fan-out**: fleets at B2 to C1 as hands, at R = 2 readers per item; the pilot, fleet, adjudication and revision steps and the files each writes; the three legs of every fleet stage, with the operator's `fleet.py` as the dispatch; the 50 KB packet ceiling. **§2 The figures**: one definition each for fidelity, agreement, gold fidelity, transmission after revision, stability, the position curve and transmission, and "Fidelity is primary and agreement secondary." **§3 The return, D1 to D3**: the handoff folder, the labelers in Codex, `ingest.py`, and the verdict fleet with its criterion (`composes`, `composes-with-residue`, `does-not-compose`, `cannot-tell`).

## Who writes it, and when

Written with the instrument. `build.sh` copies it to the root at build; AGENT.md says it "comes with the fleet stages".

## Why it exists

Contract §4: seven stages send work to readers who are not the analyst, and no reader runs on the analyst's model or in its session. FLEET says what the figures license: they bound "whether the written instrument decides, never whether it is right."

## Where

[FLEET.md](../../../aggregator/runs/claude-v43-1/00_GIVE-THE-AGENT/FLEET.md); source [aggregator/instrument/FLEET.md](../../../aggregator/instrument/FLEET.md).

Checked against: FLEET.md, CONTRACT-aggregator.md §4, AGENT.md, harness/build.sh.