Case 04, the first interactive evaluation, stopped at 100 Orchestrator
turns on two router faults:
- A reply that quoted the agent's question back was judged on that question.
A reply now reaches the router with quoted questions and Q:/A: labels
removed, and the questions are given to the decider as background.
- At a Revision limit the reply was read as another change request for the
same Deliverable, and the refusal repeated. The user is now told once,
the reply is taken as the answer, that Deliverable is not reopened again,
and the Execution carries on with it as it stands.
- Any run that asks the user four times running with no work done in
between now ends with a warning.
The validator is told to confirm with the user in an interactive Execution.
Plans record the fixes and the rerun, which did not finish: both fixes
held, and a third fault appeared that is not fixed here. A scripted answer
restating a requirement, given to a draft-confirmation question, reopens
requirements.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
- 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>
After case 02 (completed at 100%, but with two Revisions of the Target
architecture for gaps validation found one pass at a time):
- A Deliverable stands while what it was written from is unchanged. The
architecture description is written from the Elements and Relationships,
so a Revision that only adds or rewords Checks no longer runs the describer.
- Non-functional requirements and recommendations list their conditions,
one entry per separate thing that must be true; submission requires them.
- A coverage review at submission (JEV_COVERAGE_REVIEW, off by default):
for each condition, Jev chooses which Check verifies it, or none. Asked as
one broad yes-or-no per requirement it could not tell a complete design
from one with known gaps; asked as a choice per condition it raised all
four known gaps of case 02 and nothing on the complete graph. An opt-in
live test (LIVE_JEV=1) repeats that.
- The validator is told to report every gap in its first pass.
Plans record the case 02 run and both forms of the review with figures.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Design is now approved before any infrastructure code is written (ADR-0005).
A new target-architect Specialist produces one graph of Elements,
Relationships and Checks; the diagram is rendered from it, deployment
guidance must account for every Check, and validation gives a verdict per
Check. Requirements, components, products and recommendations carry ids in
data files, and a submission with a gap in the Requirements chain is refused.
Also in this commit:
- Customer cases group Executions, with an intent history per case
- lesson candidates are captured when an Execution ends
- evaluation gains chain, verdict, judged and interactive checks, and
per-case thresholds
- Terraform providers are cached between checks
- the requirements analyst proposes defaults instead of asking
- the legacy-baseline case and the checks that only read it are removed
- ADR-0006 (Change requests) accepted; ADR-0004 and ADR-0007 proposed
- plans for iterations 4 to 7 under .agents/plans/
Unproven with a real model: no evaluation run has completed on this design.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>