ADR 0237 (next free across main and open PRs): the build seat runs the merge check; facts in the artifact store; the gate judges only what the change adds; a catalogue change is judged by the running controller (version skew); checks run with no container-runtime socket, mesh-lab replays (reviewed) with it; replays live where their incident is; a core issue resolves only with replay: or replay-none:; the tests' bus is a server per test at the mesh's release.
to-be 45: decisions, writers table §1 (+2 rows), S14 row, §9 'As built', Phase 5 'Built' record and 'Not yet'.
cycle.py: the replay rule for core issues opened from 2026-10-07 (failed on a probe issue before it passed); checks README and playbook 03 say it.
Issues 236, 262, 263, 266, 273 carry replay:.
Checks: records, cycle, index all pass. Role names only.
- ADR 0237 (next free across main and open PRs): the build seat runs the merge check; facts in the artifact store; the gate judges only what the change adds; a catalogue change is judged by the running controller (version skew); checks run with no container-runtime socket, mesh-lab replays (reviewed) with it; replays live where their incident is; a core issue resolves only with `replay:` or `replay-none:`; the tests' bus is a server per test at the mesh's release.
- to-be 45: decisions, writers table §1 (+2 rows), S14 row, §9 'As built', Phase 5 'Built' record and 'Not yet'.
- `cycle.py`: the replay rule for core issues opened from 2026-10-07 (failed on a probe issue before it passed); checks README and playbook 03 say it.
- Issues 236, 262, 263, 266, 273 carry `replay:`.
Checks: records, cycle, index all pass. Role names only.
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.
Deliverynovox/hq@ca8642366411 — held since 2026-10-06T23:05:28Z
Held for a person: merged without a passing check: only a person decides that it goes on — mesh-delivery.release with why lets it go on.
Delivery plan — builds nothing: the change touches no module of the mesh's graph
Transitions
2026-10-06 23:05 (new) → proposed (announced): novox/hq#152 merged; its head was not heard by this owner, so it is made from the forge's word
2026-10-06 23:05 proposed → held (merged-unchecked): merged without a passing check — a verdict known with it is taken first: only a person decides that it goes on
The commit's note under refs/notes/mesh-plan keeps every transition: git log --notes=mesh-plan.
<!-- mesh-delivery:view -->
**Delivery** `novox/hq@ca8642366411` — **held** since 2026-10-06T23:05:28Z
Held for a person: merged without a passing check: only a person decides that it goes on — `mesh-delivery.release` with why lets it go on.
**Delivery plan** — builds nothing: the change touches no module of the mesh's graph
**Transitions**
- 2026-10-06 23:05 (new) → proposed (announced): novox/hq#152 merged; its head was not heard by this owner, so it is made from the forge's word
- 2026-10-06 23:05 proposed → held (merged-unchecked): merged without a passing check — a verdict known with it is taken first: only a person decides that it goes on
The commit's note under `refs/notes/mesh-plan` keeps every transition: `git log --notes=mesh-plan`.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
replay:orreplay-none:; the tests' bus is a server per test at the mesh's release.cycle.py: the replay rule for core issues opened from 2026-10-07 (failed on a probe issue before it passed); checks README and playbook 03 say it.replay:.Checks: records, cycle, index all pass. Role names only.
Delivery
novox/hq@ca8642366411— held since 2026-10-06T23:05:28ZHeld for a person: merged without a passing check: only a person decides that it goes on —
mesh-delivery.releasewith why lets it go on.Delivery plan — builds nothing: the change touches no module of the mesh's graph
Transitions
The commit's note under
refs/notes/mesh-plankeeps every transition:git log --notes=mesh-plan.