Issue 1024, ADR 0422. The merge gate composes every machine with the node-engine's own validator, vendored here at mesh-host of 2026-10-15 (go.mod's replace). It refuses the unknown and knows keys that mesh-host #117 (delivered to ace, g14, novox, shanks at 18:22) added, so mesh-catalog #349 was refused on every machine: resource "xorg.config": a directory does not use "unknown", and it is set. Refused rather than ignored.
The pin moves to #117's merge, 6469e8238443; go mod vendor changes only vendor/.../internal/declaration/declaration.go (byte-equal to mesh-host at 6469e823) and modules.txt.
TestTheGateTakesADirectoryThatSaysHowItReacts fails on the old pin with the gate's exact refusal and passes on the new.
Playbook 07's exception for a new manifest word (a group is not yet judged by its own controller, design 47 milestone 3): this is merged and delivered first, on a branch of its own so it is not grouped with mesh-catalog #349 and hq #409 (feat/owned-paths), which wait for it; then #349 is rechecked. Replaces #371 (same tree, grouped by mistake). Reviewed (approve at 4e14375a; forge tree equals it).
Issue 1024, ADR 0422. The merge gate composes every machine with the node-engine's own validator, vendored here at mesh-host of 2026-10-15 (go.mod's replace). It refuses the `unknown` and `knows` keys that mesh-host #117 (delivered to ace, g14, novox, shanks at 18:22) added, so mesh-catalog #349 was refused on every machine: `resource "xorg.config": a directory does not use "unknown", and it is set. Refused rather than ignored`.
- The pin moves to #117's merge, 6469e8238443; `go mod vendor` changes only vendor/.../internal/declaration/declaration.go (byte-equal to mesh-host at 6469e823) and modules.txt.
- `TestTheGateTakesADirectoryThatSaysHowItReacts` fails on the old pin with the gate's exact refusal and passes on the new.
Playbook 07's exception for a new manifest word (a group is not yet judged by its own controller, design 47 milestone 3): this is merged and delivered first, on a branch of its own so it is not grouped with mesh-catalog #349 and hq #409 (`feat/owned-paths`), which wait for it; then #349 is rechecked. Replaces #371 (same tree, grouped by mistake). Reviewed (approve at 4e14375a; forge tree equals it).
The gate composes every machine with the node-engine's own validator, vendored at mesh-host of 2026-10-15, which refuses the `unknown` and `knows` keys mesh-host #117 added; every catalogue manifest using them was refused on every machine (mesh-catalog #349). The pin moves to #117's merge, 6469e8238443, delivered; only the declaration validator changes in vendor/. A test holds the gate to taking such a directory.
route-proxy provides route: its consumers are sent again after it
route-proxy keeps data (ADR 0233): what it holds is backed up before it moves
build-agent keeps data (ADR 0233): what it holds is backed up before it moves
grants step: if this changes what the bus's user list says (a new tool, subject or user), novox is sent that list alone, every build there kept, before route-proxy, build-agent is judged on its first machine
Machines
mesh-controller on every machine running it: sent
route-proxy on every machine running it: sent
build-agent on every machine running it: sent
Transitions
2026-10-17 16:44 (new) → proposed (announced): novox/mesh-controller#372's head announced
2026-10-17 16:51 proposed → checked (checked): a verdict names this commit and the trunk's head as its trunk commit
2026-10-17 16:51 checked → ready (accepted): the gate passed or warned, and the repository's own check did not fail
2026-10-17 17:10 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 17:10 published → delivering (go): its walk started: let go by this owner in its group's order, by a person, or on the controller's own path — not a failed walk that carried a later commit for it, after which it waits for a walk of its own commit
2026-10-17 17:15 delivering → delivered (done): its walk is done, carrying its own commit: every machine of its deploy plan passed, or was left as its policy says
The commit's note under refs/notes/mesh-plan keeps every transition: git log --notes=mesh-plan.
<!-- mesh-delivery:view -->
**Delivery** `novox/mesh-controller@34197afa0181` — **delivered** since 2026-10-17T17:15:26Z
**Delivery plan** — builds build-agent, mesh-controller, route-proxy → ace, g14, novox, shanks; no bus step
- tier 0: mesh-controller, route-proxy
- tier 1: build-agent
- ace: receives route-proxy, build-agent
- g14: receives build-agent
- novox: receives mesh-controller, route-proxy, build-agent
- shanks: receives build-agent
- route-proxy provides route: its consumers are sent again after it
- route-proxy keeps data (ADR 0233): what it holds is backed up before it moves
- build-agent keeps data (ADR 0233): what it holds is backed up before it moves
- grants step: if this changes what the bus's user list says (a new tool, subject or user), novox is sent that list alone, every build there kept, before route-proxy, build-agent is judged on its first machine
**Machines**
- mesh-controller on every machine running it: sent
- route-proxy on every machine running it: sent
- build-agent on every machine running it: sent
**Transitions**
- 2026-10-17 16:44 (new) → proposed (announced): novox/mesh-controller#372's head announced
- 2026-10-17 16:51 proposed → checked (checked): a verdict names this commit and the trunk's head as its trunk commit
- 2026-10-17 16:51 checked → ready (accepted): the gate passed or warned, and the repository's own check did not fail
- 2026-10-17 17:10 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 17:10 published → delivering (go): its walk started: let go by this owner in its group's order, by a person, or on the controller's own path — not a failed walk that carried a later commit for it, after which it waits for a walk of its own commit
- 2026-10-17 17:15 delivering → delivered (done): its walk is done, carrying its own commit: every machine of its deploy plan passed, or was left as its policy says
The commit's note under `refs/notes/mesh-plan` keeps every transition: `git log --notes=mesh-plan`.
route-proxy provides route: its consumers are sent again after it
route-proxy keeps data (ADR 0233): what it holds is backed up before it moves
build-agent keeps data (ADR 0233): what it holds is backed up before it moves
grants step: if this changes what the bus's user list says (a new tool, subject or user), novox is sent that list alone, every build there kept, before route-proxy, build-agent is judged on its first machine
read by no module's build: cmd/mesh-controller/owned_paths_test.go
Run by the build seat on ace as build-1792255440759744117 (builds --log build-1792255440759744117).
Reviewed by owned-paths-review@novox: Approved at 4e14375a (forge tree equal): the pin moves to the delivered mesh-host 6469e823, vendored validator byte-equal, a test holds the gate to taking unknown/knows; gate 4/4 and merge-check.sh green. Marked through mesh-delivery.mark-ready (novox/hq issue 913).
ready at 34197afa01819555d02ca8ed89c467db8ea9e365
Reviewed by owned-paths-review@novox: Approved at 4e14375a (forge tree equal): the pin moves to the delivered mesh-host 6469e823, vendored validator byte-equal, a test holds the gate to taking unknown/knows; gate 4/4 and merge-check.sh green. 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 1024, ADR 0422. The merge gate composes every machine with the node-engine's own validator, vendored here at mesh-host of 2026-10-15 (go.mod's replace). It refuses the
unknownandknowskeys that mesh-host #117 (delivered to ace, g14, novox, shanks at 18:22) added, so mesh-catalog #349 was refused on every machine:resource "xorg.config": a directory does not use "unknown", and it is set. Refused rather than ignored.go mod vendorchanges only vendor/.../internal/declaration/declaration.go (byte-equal to mesh-host at 6469e823) and modules.txt.TestTheGateTakesADirectoryThatSaysHowItReactsfails on the old pin with the gate's exact refusal and passes on the new.Playbook 07's exception for a new manifest word (a group is not yet judged by its own controller, design 47 milestone 3): this is merged and delivered first, on a branch of its own so it is not grouped with mesh-catalog #349 and hq #409 (
feat/owned-paths), which wait for it; then #349 is rechecked. Replaces #371 (same tree, grouped by mistake). Reviewed (approve at 4e14375a; forge tree equals it).Delivery
novox/mesh-controller@34197afa0181— delivered since 2026-10-17T17:15:26ZDelivery plan — builds build-agent, mesh-controller, route-proxy → ace, g14, novox, shanks; no bus step
Machines
Transitions
The commit's note under
refs/notes/mesh-plankeeps every transition:git log --notes=mesh-plan.Merge check at
34197afaJudged: head
34197afa0181merged into trunkc43772fd94eb; read beside it: mesh-catalog54b3ce503e79, mesh-controller-mainc43772fd94eb, mesh-host6469e8238443, mesh-tools7412c5b6c9c5mesh/merge-gate: PASS — every machine composes with the change as it did without (4 of 4 compose) (modules: build-agent, mesh-controller, route-proxy)mesh/repo-check: PASS — its merge-check.sh passedDelivery plan — builds build-agent, mesh-controller, route-proxy → ace, g14, novox, shanks; no bus step
Run by the build seat on ace as
build-1792255440759744117(builds --log build-1792255440759744117).ready at
34197afa01Reviewed by owned-paths-review@novox: Approved at 4e14375a (forge tree equal): the pin moves to the delivered mesh-host 6469e823, vendored validator byte-equal, a test holds the gate to taking unknown/knows; gate 4/4 and merge-check.sh green. Marked through mesh-delivery.mark-ready (novox/hq issue 913).