Issue 1121: after milestone 5 moved 8,599 build records onto the bus under bare ids with whole manifests inside, every build lookup read the whole bucket; a delivery plan's send of build-agent never finished while holding the plans and novox's declaration, and every act and the status waited behind it.
Builds under <module>.build.<id>, requests req.<id>, id.<id>; pointers newest, worked, held, commit.<sha>, source.<reuse key> move only to a newer build and are hints, repaired when wrong (ADR 0427).
Manifests once each in the same bucket under manifest.sha256-<hex>: no new bucket, no new grant.
The old keys are laid out once at start, idempotently, with progress every 1,000 records; they stay and are not read.
The silent-clock calls a plan look makes while holding the plans are bounded (the vendored kv.Keys ignores its context).
Issue: 1121. Decision: ADR 0427.
Reviewed-by: reviewer-1121@shanks at a1cb2f344c86ef361b49b14fde557ca3bcfac394 (squashed to c7959153 with the identical tree)
Issue 1121: after milestone 5 moved 8,599 build records onto the bus under bare ids with whole manifests inside, every build lookup read the whole bucket; a delivery plan's send of build-agent never finished while holding the plans and novox's declaration, and every act and the status waited behind it.
- Builds under `<module>.build.<id>`, requests `req.<id>`, `id.<id>`; pointers `newest`, `worked`, `held`, `commit.<sha>`, `source.<reuse key>` move only to a newer build and are hints, repaired when wrong (ADR 0427).
- Manifests once each in the same bucket under `manifest.sha256-<hex>`: no new bucket, no new grant.
- The old keys are laid out once at start, idempotently, with progress every 1,000 records; they stay and are not read.
- The silent-clock calls a plan look makes while holding the plans are bounded (the vendored kv.Keys ignores its context).
Issue: 1121. Decision: ADR 0427.
Reviewed-by: reviewer-1121@shanks at a1cb2f344c86ef361b49b14fde557ca3bcfac394 (squashed to c7959153 with the identical tree)
mesh/merge-gate head c79591531575 merged into trunk aa02e7bf4e78 — pass: builds build-agent, mesh-controller → ace, g14, novox, shanks; no bus step; every …
Milestone 5 moved 8,599 build records onto the bus under bare build ids, each
carrying its module's whole manifest. Every build lookup then read the whole
bucket, and a delivery plan's send did that per module per machine while it
held the plans and the machine's declaration: the send of build-agent never
finished, and every other act and the status waited behind it.
Builds now live under <module>.build.<id> (requests under req.<id>, id.<id>
names a build's module), with pointer keys newest, worked, held,
commit.<sha> and source.<reuse key> that move only to a newer build and are
read as hints, repaired when wrong. Manifests are kept once in the same
bucket under manifest.sha256-<hex>, so no grant the running bus lacks is
needed. The old keys are laid out once at start, idempotently, and left
unread. The calls a plan look makes on the silent clocks while it holds the
plans are bounded, since the vendored kv.Keys ignores its context.
Deliverynovox/mesh-controller@c79591531575 — delivered since 2026-10-18T11:47:49Z
Delivery plan — builds build-agent, mesh-controller → ace, g14, novox, shanks; no bus step
tier 0: mesh-controller
tier 1: build-agent
ace: receives build-agent
g14: receives build-agent
novox: receives mesh-controller, build-agent
shanks: receives build-agent
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 build-agent is judged on its first machine
Machines
mesh-controller on every machine running it: sent
build-agent on every machine running it: sent
Transitions
2026-10-18 11:32 (new) → proposed (announced): novox/mesh-controller#380's head announced
2026-10-18 11:38 proposed → checked (checked): a verdict names this commit and the trunk's head as its trunk commit
2026-10-18 11:38 checked → ready (accepted): the gate passed or warned, and the repository's own check did not fail
2026-10-18 11:39 ready → published (merged): on the trunk its modules follow: merged there, and its walk opened — or nothing for a walk to move
2026-10-18 11:39 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-18 11:47 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@c79591531575` — **delivered** since 2026-10-18T11:47:49Z
**Delivery plan** — builds build-agent, mesh-controller → ace, g14, novox, shanks; no bus step
- tier 0: mesh-controller
- tier 1: build-agent
- ace: receives build-agent
- g14: receives build-agent
- novox: receives mesh-controller, build-agent
- shanks: receives build-agent
- 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 build-agent is judged on its first machine
**Machines**
- mesh-controller on every machine running it: sent
- build-agent on every machine running it: sent
**Transitions**
- 2026-10-18 11:32 (new) → proposed (announced): novox/mesh-controller#380's head announced
- 2026-10-18 11:38 proposed → checked (checked): a verdict names this commit and the trunk's head as its trunk commit
- 2026-10-18 11:38 checked → ready (accepted): the gate passed or warned, and the repository's own check did not fail
- 2026-10-18 11:39 ready → published (merged): on the trunk its modules follow: merged there, and its walk opened — or nothing for a walk to move
- 2026-10-18 11:39 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-18 11:47 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`.
Merge check at c7959153
Judged: head c79591531575 merged into trunk aa02e7bf4e78; read beside it: mesh-catalog 7f77ce663a9e, mesh-controller-main aa02e7bf4e78, mesh-host 6469e8238443, mesh-tools 7412c5b6c9c5
mesh/merge-gate: PASS — every machine composes with the change as it did without (4 of 4 compose) (modules: build-agent, mesh-controller)
mesh/repo-check: PASS — its merge-check.sh passed
Delivery plan — builds build-agent, mesh-controller → ace, g14, novox, shanks; no bus step
tier 0: mesh-controller
tier 1: build-agent
ace: receives build-agent
g14: receives build-agent
novox: receives mesh-controller, build-agent
shanks: receives build-agent
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 build-agent is judged on its first machine
read by no module's build: cmd/mesh-controller/plan_looks_test.go, internal/chain/keys_test.go, internal/inventory/builds_test.go, internal/inventory/chain_builds_layout_test.go, internal/inventory/chain_move_test.go
Run by the build seat on ace as build-1792323169669974256 (builds --log build-1792323169669974256).
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 1121: after milestone 5 moved 8,599 build records onto the bus under bare ids with whole manifests inside, every build lookup read the whole bucket; a delivery plan's send of build-agent never finished while holding the plans and novox's declaration, and every act and the status waited behind it.
<module>.build.<id>, requestsreq.<id>,id.<id>; pointersnewest,worked,held,commit.<sha>,source.<reuse key>move only to a newer build and are hints, repaired when wrong (ADR 0427).manifest.sha256-<hex>: no new bucket, no new grant.Issue: 1121. Decision: ADR 0427.
Reviewed-by: reviewer-1121@shanks at a1cb2f344c86ef361b49b14fde557ca3bcfac394 (squashed to
c7959153with the identical tree)Delivery
novox/mesh-controller@c79591531575— delivered since 2026-10-18T11:47:49ZDelivery plan — builds build-agent, mesh-controller → 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
c7959153Judged: head
c79591531575merged into trunkaa02e7bf4e78; read beside it: mesh-catalog7f77ce663a9e, mesh-controller-mainaa02e7bf4e78, 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)mesh/repo-check: PASS — its merge-check.sh passedDelivery plan — builds build-agent, mesh-controller → ace, g14, novox, shanks; no bus step
Run by the build seat on ace as
build-1792323169669974256(builds --log build-1792323169669974256).