A caller restates a request to say how requirements have changed, naming a
completed Execution of the same Customer case as the Baseline.
- app/baseline.py reads a Baseline from its files and refuses one that
does not exist, did not complete or belongs to another case, before
anything runs or is recorded. A Baseline is never modified.
- Requirements carry a change (unchanged, added, changed, removed) and a
reason. Submission is refused when a Baseline requirement disappears, an
id is reused, or an unchanged requirement's text differs. A removed
requirement stays on record and asks nothing downstream.
- Each Specialist starts from its delivered version; the graph and the code
are its working copy, and the description is carried over when the
design's shape is the same.
- app/workflows/changes.py compares versions by id and traces what each
changed requirement reaches; anything else that changed is listed as
unrequested. Approvals show the change for their Phase, and changes.json
is written with the full Deliverables.
- Intake no longer starts a message read as a change: it names the
Execution to give as the Baseline.
- A fifth evaluation case runs a request and then a change to it, with
four checks that the change is recorded, reaches Checks, stays contained
and costs less than its Baseline.
Tested with scripted agents only; no Change request has run with real
models.
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>