# Step 7 — Implementation Detail Built on 2026-10-09: the case and its checks. **The run is outstanding.** 1. A case may carry `change`, a statement of what has changed. The evaluation then runs the case's request to completion, pre-approved, and runs `change` as a Change request against it in the same Customer case. The Change request is what is scored. 2. `case-05-change-retention`: case 01's request, then "raw events must now be kept for 7 years instead of 30 days ... and must not be deletable during that time. Everything else stays as it is." 3. `score_change` adds four checks to the usual ones: - `change_is_recorded`: at least one requirement is marked added, changed or removed; - `changed_requirements_reach_checks`: each added or changed requirement is the source of a Check that was added or changed, and a removed one's Checks are gone; - `change_is_contained`: no more than two items, or a tenth of the Baseline's graph, changed without being reached; - `change_costs_less_than_baseline`: the Change request used fewer tokens than the Execution it changed. 4. The report records the Baseline's id, seconds and tokens. Acceptance criteria: not yet tested. The case needs two Executions, roughly an hour and $8 to $10. Tests: `tests/eval/test_scoring.py`, "a Change request stays contained" (5).