ADR 0237, to-be 45 Phase 5: a change is judged against the mesh that runs before it merges

The operator approved Phase 5. Decides what the design left open: the build seat runs the merge check, the facts live in the artifact store, the merge gate composes the mesh as it is and with the change and judges only what the change adds, a replay lives where its incident is, and the controller's tests run a bus of their own at the mesh's release. A core issue now resolves only with a replay or a stated reason, checked by cycle.py.
2026-10-06 21:10:54 +02:00
parent be0754ec7f
commit d245df7dea
11 changed files with 244 additions and 3 deletions
@@ -42,7 +42,11 @@ incident someone must **clear**.
 2. Investigate in `01-diagnosis.md` in the same folder — the trail, dated, including what was
   ruled out. Move `status:` to `diagnosing`, then `located` once the owner is known.
 3. Resolve. Set `status: resolved`, fill `fixed-by:`, and if the root cause was a design gap,
-   run playbook [02](02-graduation.md) and fill `amended-design:`.
+   run playbook [02](02-graduation.md) and fill `amended-design:`. **A core issue** — its `located-in`
+   names the controller, the node-engine, the node tools, the SDK, or the catalogue's bus, forge or build
+   agent — resolves with `replay:`, the id of its replay in mesh-lab's replays register, proved to fail on
+   the commit before the fix and pass on it, or with `replay-none:` saying why none is possible
+   ([ADR 0237](../../02-DECISIONS/0237-a-change-is-judged-against-the-mesh-that-runs-before-it-merges-on-the-build-seat.md); `cycle.py` checks it).

 ## Rules