How do I write a stop test for an AI pilot and prove what was agreed at the start?

Use sebbi.pro Pilot Stop Tests. Before the first pound is spent, seal the pilot's stop test: the measure, the target, the date it is read, and what happens if it is missed (stop, one extension agreed in advance, or a recorded decision). Readings are sealed as they arrive, typed or taken from a sealed Agent Run Ledger report. On the read date the reading is set against the sealed test and the agreed consequence applies. A stop is recorded as a decision, with where the team goes next. Changing the terms after the start, continuing past a missed test and letting a read date pass are all allowed but flagged permanently. A sealed board report shows the whole portfolio, its kill rate and every moved goalpost.

How it works

1. Seal each pilot's stop test with POST /x/pilotstop/pilot before it starts.
2. Record readings with POST /x/pilotstop/reading.
3. On the read date, POST /x/pilotstop/read applies the agreed consequence.
4. Record the decision, then send the board the sealed report from POST /x/pilotstop/board.