# Step 3 — Implementation Detail Built on 2026-10-09. 1. In a Change request every requirement in `requirements.json` carries a `change`: `unchanged`, `added`, `changed` or `removed`. Everything but `unchanged` carries a `reason`. 2. `check_requirement_changes` in `app/workflows/changes.py`, run by `check_submission` when the Deliverable has a Baseline, refuses: - a requirement with no `change`, or a change with no reason; - a Baseline requirement missing from the list (it must stay, marked `removed`); - a requirement marked `added` whose id the Baseline already has, or marked anything else whose id it does not; - a requirement marked `unchanged` whose text differs from the Baseline's; - a list in which nothing is added, changed or removed. 3. A removed requirement stays in the file as the record of what was dropped. `read_list` leaves it out, so nothing downstream is asked to serve or check it. 4. `agents/requirements-analyst.md` says how to mark each requirement and to add a `Changes` heading. With a user present the draft is confirmed before submission by the rule of iteration 4 step 27. Differs from the plan: the check that an `unchanged` requirement keeps its text was added. Without it a requirement could change quietly. Tests: `tests/execution/test_change_requests.py` "step 3" (6).