Files
gcp_solution_architecture_a…/.agents/plans/iter-07-change-requests/steps/step-2.md
Jonathan Boniface 5ef434d00e 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>
2026-10-09 11:38:15 +01:00

1.7 KiB

Step 2 — Implementation Detail

Built on 2026-10-09.

  1. app/baseline.py: load_baseline(output_root, customer_case, execution_id) reads a Baseline from its files under the Customer case, through execution.json: its id, its request, the Baseline it was itself changed from, and every Deliverable with its attachments. It never needs the Baseline's checkpoint.
  2. It refuses, with BaselineError (a ValueError), an id that is not an Execution id, an Execution with no files in that case, one that belongs to another Customer case (without saying which), one whose manifest status is not completed, and a Change request with no Customer case.
  3. ExecutionEngine.start(baseline=...) loads the Baseline before the Execution's id is taken or its intent recorded, so a refusal leaves nothing behind. The loaded Baseline is in the state as baseline.
  4. record_intent puts the Baseline on the new statement in intent/history.json and in its NNN.md; execution.json records it too. An Execution started without one has "baseline": null in both.
  5. Callers: baseline in the /generate body and in the A2A message metadata. A bad Baseline is a 400 from /generate and a failed task over A2A.
  6. Intake (iteration 5 step 12) no longer starts a message read as a change. It answers with the latest completed Execution of the case and how to name it as the Baseline, and starts nothing; "new_request": true in the metadata says it is new work and skips the reading. A caller who names a Baseline is not read at all.

Differs from the plan: nothing.

Tests: tests/execution/test_change_requests.py "step 2" (10), tests/a2a/test_server.py (3), tests/execution/test_intake.py.