# 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).