- 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>
From the case 02 run cancelled at 66 minutes on 2026-10-07:
- The validator records verdicts a few Checks at a time (verdict_put) and
they are attached on submission. It timed out five times writing them in
one reply. Verdicts on the same code survive a run cut short; verdicts on
changed code are dropped. Its model timeout is 300 s.
- A schema review at submission, in code: every setting a Check names is
looked up on its Element's resource type, and an unknown resource type is
reported. Two Revisions in that run were for Checks no code could meet.
On the two designs that passed validation it raises 2 of 96 Checks, both
one metric name used as a value, so it is returned once and never blocks.
- Reviews run together; the Jev coverage review stays off.
Plans record both steps and the cancelled run.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>