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>
4.2 KiB
status
| status |
|---|
| accepted |
A change request starts from a baseline Execution
A user's requirements change after an architecture has been delivered. They need to say what has changed, at a high level, and get the architecture updated, not rebuilt from nothing with no link to what was agreed before. Today that is impossible by design: every Execution starts clean, and a Session or Customer case only groups Executions. We decide that a caller may start an Execution as a Change request against a Baseline: a completed Execution of the same Customer case. The new Execution begins from the Baseline's approved Deliverables and the user's description of what has changed, and it delivers a full, updated set plus a statement of what changed and why.
This is the one, explicit exception to "every Execution starts clean". It is named by the caller, limited to the same Customer case, and recorded in the Execution's manifest. Nothing flows between Executions unless a Baseline is named.
How a Change request runs
- The user says what changed, in the Workflow request, at the same high level as an original request: "retention goes from 30 days to 7 years", "it must now also serve a second region". It becomes the next statement in the Customer case's Intent history.
- The agents work out the consequences. The requirements analyst revises the Baseline's requirements, keeping every id that still holds and marking each requirement added, changed or removed. Each later Specialist starts from the Baseline's version of its Deliverable and changes only what the changed requirements reach.
- The Requirements chain shows the reach. Because requirements, components, Elements and Checks carry ids (ADR-0005), a changed requirement leads to the Elements and Checks it touches. Everything it does not reach is carried over unchanged.
- The user approves the change, not the whole. Each Approval shows what was added, changed and removed against the Baseline.
- Validation covers every Check, carried over or new, so an unchanged part that a change has broken is still caught.
Decisions
Accepted by the owner on 2026-10-07, with each of these:
- A Change request is a new Execution, with its own id, Approvals and files. The Baseline is never modified, so every delivered version of a Customer case's architecture remains on record.
- The Baseline must be a completed Execution of the same Customer case. One case can never start from another's work.
- The output is complete, not a patch. A Change request delivers the full updated Deliverables and a change summary, so the latest Execution of a case always stands on its own.
- A Change request may itself be a Baseline, so a case's Executions form a line of versions.
Considered Options
- Reopen the completed Execution and revise its Deliverables in place: rejected. It destroys the record of what was delivered and approved, and an Execution that never ends cannot be audited.
- Start clean and ask the user to restate everything with the change included: rejected. It loses every decision and Approval already made, changes parts nobody asked to change, and gives no account of what differs.
- Carry context automatically within a Customer case: rejected. Hidden carry-over is what "starts clean" exists to prevent; the caller must choose the Baseline.
- Deliver only a diff of the Deliverables: rejected. The reader would have to assemble the current architecture from a chain of patches.
Consequences
- "Every Execution starts clean" becomes "every Execution starts clean unless the caller names a Baseline". The glossary entries for Execution, Session and Customer case change to say so, and gain Change request and Baseline.
- This depends on ADR-0005. Without ids along the Requirements chain there is nothing to trace a change through, and a Change request would be a rewrite with extra context.
- A Change request against a Baseline produced by older Skills is revised under the Skills loaded now; the change summary can therefore include changes the user did not ask for. They must be shown as such.
- Lesson candidates gain a strong signal: what users change after delivery.