Opens issue 281, status located, fixed by novox/mesh-controller PR #100.
A plan sent a wide tier to its first machine one module at a time, a whole declaration per module. The churn raised core-behind on the machine, and the gate failed the module it was judging for that machine-level condition. The rollback then read "what the machine ran before" after an earlier send of the same tier had already carried the new build there, so it searched for a predecessor of the very commit it failed. The fix sends a tier to each machine once, judges it with one gate, sorts machine-level conditions (named module / core settling / machine as a whole), and treats a send that changed nothing of a module as no verdict on its build.
Role names only. records.py, index.py and cycle.py pass. The core-issue replay: is still to come before resolution.
Opens issue 281, status `located`, fixed by novox/mesh-controller PR #100.
A plan sent a wide tier to its first machine one module at a time, a whole declaration per module. The churn raised `core-behind` on the machine, and the gate failed the module it was judging for that machine-level condition. The rollback then read "what the machine ran before" after an earlier send of the same tier had already carried the new build there, so it searched for a predecessor of the very commit it failed. The fix sends a tier to each machine once, judges it with one gate, sorts machine-level conditions (named module / core settling / machine as a whole), and treats a send that changed nothing of a module as no verdict on its build.
Role names only. `records.py`, `index.py` and `cycle.py` pass. The core-issue `replay:` is still to come before resolution.
Deliverynovox/hq@055550802096 — delivered since 2026-10-09T07:31:48Z
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#154's head announced
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
2026-10-09 07:31 held → delivered (done): merged, and nothing for a walk to move: builds nothing: the change touches no module of the mesh's graph
The commit's note under refs/notes/mesh-plan keeps every transition: git log --notes=mesh-plan.
<!-- mesh-delivery:view -->
**Delivery** `novox/hq@055550802096` — **delivered** since 2026-10-09T07:31:48Z
**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#154's head announced
- 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
- 2026-10-09 07:31 held → delivered (done): merged, and nothing for a walk to move: builds nothing: the change touches no module of the mesh's graph
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.
Opens issue 281, status
located, fixed by novox/mesh-controller PR #100.A plan sent a wide tier to its first machine one module at a time, a whole declaration per module. The churn raised
core-behindon the machine, and the gate failed the module it was judging for that machine-level condition. The rollback then read "what the machine ran before" after an earlier send of the same tier had already carried the new build there, so it searched for a predecessor of the very commit it failed. The fix sends a tier to each machine once, judges it with one gate, sorts machine-level conditions (named module / core settling / machine as a whole), and treats a send that changed nothing of a module as no verdict on its build.Role names only.
records.py,index.pyandcycle.pypass. The core-issuereplay:is still to come before resolution.Delivery
novox/hq@055550802096— delivered since 2026-10-09T07:31:48ZDelivery 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.