Issue 1051 (playbook 08). A lesson of feature owned-paths (issue 1024): the controller vendors the node-engine's declaration validator at a pinned commit, so a new key the node-engine checks is refused by the merge gate until the controller's pin moves (mesh-controller #372 did it); and a release that must merge before the catalogue's joins the catalogue's delivery group on the feature's branch name, so it is given a name of its own. Phase 0 step 1 points to the exception. records.py and words.py pass. Reviewed in two rounds (approve at 8b077a8).
Issue 1051 (playbook 08). A lesson of feature owned-paths (issue 1024): the controller vendors the node-engine's declaration validator at a pinned commit, so a new key the node-engine checks is refused by the merge gate until the controller's pin moves (mesh-controller #372 did it); and a release that must merge before the catalogue's joins the catalogue's delivery group on the feature's branch name, so it is given a name of its own. Phase 0 step 1 points to the exception. records.py and words.py pass. Reviewed in two rounds (approve at 8b077a8).
Feature owned-paths (issue 1024) planned no controller release for a new key on directory resources, though the controller judges every machine with the node-engine's vendored validator; and the controller's release, on the feature's branch name, joined the catalogue's delivery group and could not merge before it.
Deliverynovox/hq@dbc740649039 — delivered since 2026-10-17T18:28:26Z
Delivery plan — builds nothing: the change touches no module of the mesh's graph
Transitions
2026-10-17 18:19 (new) → proposed (announced): novox/hq#411's head announced
2026-10-17 18:27 proposed → checked (checked): a verdict names this commit and the trunk's head as its trunk commit
2026-10-17 18:27 checked → ready (accepted): the gate passed or warned, and the repository's own check did not fail
2026-10-17 18:28 ready → published (merged): on the trunk its modules follow: merged there, and its walk opened — or nothing for a walk to move
2026-10-17 18:28 published → delivered (done): nothing for a walk to move
The commit's note under refs/notes/mesh-plan keeps every transition: git log --notes=mesh-plan.
<!-- mesh-delivery:view -->
**Delivery** `novox/hq@dbc740649039` — **delivered** since 2026-10-17T18:28:26Z
**Delivery plan** — builds nothing: the change touches no module of the mesh's graph
**Transitions**
- 2026-10-17 18:19 (new) → proposed (announced): novox/hq#411's head announced
- 2026-10-17 18:27 proposed → checked (checked): a verdict names this commit and the trunk's head as its trunk commit
- 2026-10-17 18:27 checked → ready (accepted): the gate passed or warned, and the repository's own check did not fail
- 2026-10-17 18:28 ready → published (merged): on the trunk its modules follow: merged there, and its walk opened — or nothing for a walk to move
- 2026-10-17 18:28 published → delivered (done): nothing for a walk to move
The commit's note under `refs/notes/mesh-plan` keeps every transition: `git log --notes=mesh-plan`.
Reviewed by owned-paths-review@novox: Issue 1051's playbook 07 lesson, approved in round 2 at 8b077a8 (forge tree equal); records.py and words.py pass. Marked through mesh-delivery.mark-ready (novox/hq issue 913).
ready at dbc740649039cd758e141c97d93a78738f71c2b1
Reviewed by owned-paths-review@novox: Issue 1051's playbook 07 lesson, approved in round 2 at 8b077a8 (forge tree equal); records.py and words.py pass. Marked through mesh-delivery.mark-ready (novox/hq issue 913).
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.
Issue 1051 (playbook 08). A lesson of feature owned-paths (issue 1024): the controller vendors the node-engine's declaration validator at a pinned commit, so a new key the node-engine checks is refused by the merge gate until the controller's pin moves (mesh-controller #372 did it); and a release that must merge before the catalogue's joins the catalogue's delivery group on the feature's branch name, so it is given a name of its own. Phase 0 step 1 points to the exception. records.py and words.py pass. Reviewed in two rounds (approve at 8b077a8).
Delivery
novox/hq@dbc740649039— delivered since 2026-10-17T18:28:26ZDelivery 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.ready at
dbc7406490Reviewed by owned-paths-review@novox: Issue 1051's playbook 07 lesson, approved in round 2 at 8b077a8 (forge tree equal); records.py and words.py pass. Marked through mesh-delivery.mark-ready (novox/hq issue 913).