feat: Change requests against a Baseline (ADR-0006)
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>
This commit is contained in:
12
.agents/plans/iter-07-change-requests/steps/step-6.md
Normal file
12
.agents/plans/iter-07-change-requests/steps/step-6.md
Normal file
@@ -0,0 +1,12 @@
|
||||
# Step 6 — Implementation Detail
|
||||
|
||||
Built on 2026-10-09.
|
||||
|
||||
1. A Change request writes `changes.json` beside its Deliverables: the requirements' own account, then components, recommendations, Elements, Relationships and Checks added, changed and removed by id, and `unrequested`. `execution.json` names it under `changes` and names the Baseline.
|
||||
2. Every Deliverable is written in full, as for any Execution, so the latest Execution of a case stands on its own.
|
||||
3. `intent/history.json` lists each statement with its Baseline (step 2), so a case's Executions read as a line of versions.
|
||||
4. `agents/packager.md`: the guide's executive summary opens with what changed and why, and names unrequested changes separately.
|
||||
|
||||
Differs from the plan: `changes.json` records ids, and reasons for requirements only. The plan asked for a reason on every item; a reason for a changed Check is whichever changed requirement or recommendation is its source, which a reader can follow from the ids.
|
||||
|
||||
Tests: `tests/execution/test_change_requests.py` "step 6" (1).
|
||||
Reference in New Issue
Block a user