- Validator budget 15 to 30: recording verdicts in pieces for 100 Checks used all 15 calls in one attempt. - Plans record three runs on 2026-10-08: case 02 completed at 100% with no Revision in 24 minutes; case 03 completed at 100% with two Revisions of the design in 40 minutes; case 04 (interactive) ended with warnings at 75%, on two router faults: a reply that echoes the question is read as a change request, and the router loops at the Revision limit. Neither is fixed here. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
1.3 KiB
1.3 KiB
Step 23 — Implementation Detail
Built on 2026-10-08.
verdict_putrecords 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_readreturns what is recorded.submit_deliverableattaches the recorded verdicts asverdicts.jsonwhen none is passed. Passing the file still works.- 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.
- The validator's model timeout is 300 seconds (
models.timeout_secondsinproviders/gcp.yaml); it had the default 180. agents/validator.mdtells 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).