# Step 23 — Implementation Detail Built on 2026-10-08. 1. `verdict_put` records verdicts a few Checks per call, replacing any already recorded for the same Check, and takes the dry-run's result and proposed additions. Each reply says how many Checks have a verdict and names those left. `verdict_read` returns what is recorded. 2. `submit_deliverable` attaches the recorded verdicts as `verdicts.json` when none is passed. Passing the file still works. 3. The verdicts are kept in the Deliverable's working memory with a mark of the code they were given on (a hash of the submitted deployment guidance's files). A later attempt on the same code carries on from them; on changed code they are dropped before any tool runs. 4. The validator's model timeout is 300 seconds (`models.timeout_seconds` in `providers/gcp.yaml`); it had the default 180. 5. `agents/validator.md` tells it to record as it goes, one Element's Checks at a time, and to submit with no attachments. Run on 2026-10-08 (case 02): no model timeout. The validator used all 15 of its tool calls on its first attempt, having recorded verdicts; the second attempt read them and submitted in 68 seconds. Its budget is now 30 (`agents/validator.md`). Tests: `tests/execution/test_validation_in_pieces.py`, "verdicts a few at a time" (7).