/contract-delivery-kickoff — the session that sets the ceiling

One job: a contract is signed, work is about to start, and the first session decides how a fixed number of days gets spent. /tor-procurement wrote the ToR, selection-toolkit ran the award. This is what happens after signature.

Why this exists

A delivery contract does not fail loudly. It drifts. The first session walks an issue list, agrees to everything reasonable on it, and the overrun surfaces in month five when the last tranche has no days left. The reference run is the Abortion Dashboard Phase II session of 24 July 2026: 8 technical and 7 coordination days against 17 contracted components, done entirely by hand.

So the deliverable is the arithmetic. The prep brief and the agenda are how the arithmetic reaches the room. If you produce beautiful documents and no day budget, you have built nothing.

The rule that governs everything here

Nothing is invented. Every contracted day, every rate, every tranche comes from the contract or is reported as a gap for Ane to resolve. A day rate read off a similar contract is indistinguishable from a real one once it is in a cell, and the session commits money against it. read never fills a gap; build refuses while _gaps survives; validate_spec refuses a real hole afterwards, so deleting the gap list smuggles nothing through.

The five moves this encodes

All five are proven on the 24 July 2026 session. They are not style preferences; each one closes a way the session goes wrong.