Grant the genesis controller its buckets and cancelled sets (hq to-be 45 Phase 0, issue 269) #32

2026-10-06T01:03:54Z

mesh-admin commented

2026-10-06 01:03:54 +00:00

The installer's first user list must say what the controller derives (mesh-controller's TestTheInstallersFirstUserListIsWhatTheControllerWouldCompose reads this file from a sibling checkout).

The controller now composes publish grants for:

$KV.mesh-controller_calls.> and $KV.mesh-controller_hand-acts.> — its own buckets (hq to-be 45 §1, §6, §7);
$KV.SEAT_MESH_BUILD_MACHINE_cancelled.> and $KV.SEAT_NODE_BUILD_AGENT_cancelled.> — the work queues' cancelled sets, which it writes on cancel and could not (hq issue 269).

Only examples/foundation-first-node-nats.lock changes. go vet and go test ./... pass.

Merge order: this one first, then novox/mesh-controller's PR on the same branch name. mesh-controller's genesis-template test compares its composed grant with this file in both directions, so mesh-controller's main fails that test against this change until its own PR lands, and its PR fails against mesh-host's main until this one does. Land the two back to back.

The installer's first user list must say what the controller derives (mesh-controller's `TestTheInstallersFirstUserListIsWhatTheControllerWouldCompose` reads this file from a sibling checkout). The controller now composes publish grants for: - `$KV.mesh-controller_calls.>` and `$KV.mesh-controller_hand-acts.>` — its own buckets (hq to-be 45 §1, §6, §7); - `$KV.SEAT_MESH_BUILD_MACHINE_cancelled.>` and `$KV.SEAT_NODE_BUILD_AGENT_cancelled.>` — the work queues' cancelled sets, which it writes on `cancel` and could not (hq issue 269). Only `examples/foundation-first-node-nats.lock` changes. `go vet` and `go test ./...` pass. **Merge order:** this one first, then novox/mesh-controller's PR on the same branch name. mesh-controller's genesis-template test compares its composed grant with this file in both directions, so mesh-controller's main fails that test against this change until its own PR lands, and its PR fails against mesh-host's main until this one does. Land the two back to back.

mesh-admin added 2 commits 2026-10-06 01:03:54 +00:00

Grant the genesis controller its own buckets' subjects (hq to-be 45 Phase 0) a654fa768d

The controller keeps its calls and the hand-act log in two key-value buckets
of its own, and composes a grant to write them. The installer's first user
list must say what the controller derives, or the first controller writes
nothing until the broker's machine is pushed.

Grant the genesis controller its work queues' cancelled sets (hq issue 269) 1e463def6b

The controller now derives the cancelled sets' subjects; the installer's
first user list says the same, or a cancel on a new mesh times out.

mesh-admin referenced this pull request from novox/mesh-controller

2026-10-06 01:04:26 +00:00

Keep calls and hand acts on the bus, answer status at once, record durations (hq to-be 45 Phase 0) #78

mesh-admin referenced this pull request from novox/hq

2026-10-06 01:04:42 +00:00

To-be 45 in progress; issue 269: the controller cannot write a cancelled set #129

mesh-admin merged commit 93efe41dc9 into main

2026-10-06 07:13:39 +00:00

mesh-admin deleted branch feat/a-core-that-cannot-fail-silently-phase-0

2026-10-06 07:13:39 +00:00

mesh-admin commented

2026-10-06 23:10:44 +00:00

Delivery novox/mesh-host@93efe41dc9f3 — 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 mesh-host → ace, g14, novox, shanks; no bus step

tier 0: mesh-host
ace: receives mesh-host
g14: receives mesh-host
novox: receives mesh-host
shanks: receives mesh-host

Transitions

2026-10-06 23:05 (new) → proposed (announced): novox/mesh-host#32 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.

**Delivery** `novox/mesh-host@93efe41dc9f3` — **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 mesh-host → ace, g14, novox, shanks; no bus step - tier 0: mesh-host - ace: receives mesh-host - g14: receives mesh-host - novox: receives mesh-host - shanks: receives mesh-host **Transitions** - 2026-10-06 23:05 (new) → proposed (announced): novox/mesh-host#32 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`.

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: novox/mesh-host#32