Issue 1886 (critical): R4e's delivery plan plan-1792707174627079192 is stuck in tier 1: the controller takes modules only from referenced builder keys, and only R4e's own build modules (in that plan) write references. ADR 0522: until a running builder says in mesh-delivery-builder_instances that it writes references (§1), every plan asks build-agent as before R4e (§2); an open plan's module waiting on a key the running builder cannot reference is asked of build-agent at the next look, which is how the stuck plan recovers (§3); the builder and the three build modules are build-agent's own until R4g (§6). Group with mesh-delivery on the same branch.
Tests seen failing first: TestTheBuilderSaysReferencesOnlyWhenAnInstanceSaysTheWord, TestAWalkAsksBuildAgentWhileTheBuilderDoesNotSayItWritesReferences, TestASayNotReadLeavesTheModuleUnasked, TestBuildAgentIsAskedForAnyModuleWhileTheBuilderDoesNotSay, TestAnOpenWalkWaitingOnAnUnreferencedKeyIsAskedOfBuildAgent, TestAFailedKeyOfABuilderThatDoesNotSayFailsNoWalk, TestTheReferenceWritersAreAskedOfBuildAgentWhateverTheBuilderSays, TestTheAskGuardUsesTheSayTheWalkRead, TestTheSettleJudgesByTheSameSayAsTheAsk (bbadbb2a: the settle and the ask read one say; the merge check at 1414ed7f hung in a look that handed modules back and asked them again). No try could run (its checker is stuck in the same plan); mesh/repo-check runs the integration tests. Delivered once by hand (ADR 0522 §5, cause bootstrap-1886).
Issue 1886 (critical): R4e's delivery plan plan-1792707174627079192 is stuck in tier 1: the controller takes modules only from referenced builder keys, and only R4e's own build modules (in that plan) write references. ADR 0522: until a running builder says in mesh-delivery-builder_instances that it writes references (§1), every plan asks build-agent as before R4e (§2); an open plan's module waiting on a key the running builder cannot reference is asked of build-agent at the next look, which is how the stuck plan recovers (§3); the builder and the three build modules are build-agent's own until R4g (§6). Group with mesh-delivery on the same branch.
Tests seen failing first: TestTheBuilderSaysReferencesOnlyWhenAnInstanceSaysTheWord, TestAWalkAsksBuildAgentWhileTheBuilderDoesNotSayItWritesReferences, TestASayNotReadLeavesTheModuleUnasked, TestBuildAgentIsAskedForAnyModuleWhileTheBuilderDoesNotSay, TestAnOpenWalkWaitingOnAnUnreferencedKeyIsAskedOfBuildAgent, TestAFailedKeyOfABuilderThatDoesNotSayFailsNoWalk, TestTheReferenceWritersAreAskedOfBuildAgentWhateverTheBuilderSays, TestTheAskGuardUsesTheSayTheWalkRead, TestTheSettleJudgesByTheSameSayAsTheAsk (bbadbb2a: the settle and the ask read one say; the merge check at 1414ed7f hung in a look that handed modules back and asked them again). No try could run (its checker is stuck in the same plan); mesh/repo-check runs the integration tests. Delivered once by hand (ADR 0522 §5, cause bootstrap-1886).
Reviewed-by: review-1886@shanks at bbadbb2af0215284b9b87733858b87170d334de7
R4e's own delivery plan waited for ever in tier 1: the controller took every
module but build-agent's own from a referenced builder key, and only R4e's
builder and build modules, delivered by that same plan, write references.
The builder now says so in its bucket of instances; until it does, a walk asks
build-agent as before R4e, and an open walk waiting on a key the running
builder cannot reference is judged again at the next look.
They push and answer each reference, so a key they write themselves can never
carry their own delivery; until R4g build-agent delivers them as it does the
builder.
mesh-delivery-builder on every machine running it: sent
Transitions
2026-10-22 23:59 (new) → proposed (announced): novox/mesh-controller#442's head announced
2026-10-23 00:10 proposed → checked (checked): a verdict names this commit and the trunk's head as its trunk commit
2026-10-23 00:10 checked → ready (accepted): the gate passed or warned, and the repository's own check did not fail
2026-10-23 00: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-23 00:28 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-23 00:35 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@bbadbb2af021` — **delivered** since 2026-10-23T00:35:30Z
**Delivery plan** — builds mesh-controller → novox; no bus step
- tier 0: mesh-controller
- novox: receives mesh-controller
**Group** `fix/1886-builder-says-references`: novox/mesh-controller@bbadbb2af021, novox/mesh-delivery@9fad90ee890a
**Machines**
- mesh-delivery-builder on every machine running it: sent
**Transitions**
- 2026-10-22 23:59 (new) → proposed (announced): novox/mesh-controller#442's head announced
- 2026-10-23 00:10 proposed → checked (checked): a verdict names this commit and the trunk's head as its trunk commit
- 2026-10-23 00:10 checked → ready (accepted): the gate passed or warned, and the repository's own check did not fail
- 2026-10-23 00: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-23 00:28 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-23 00:35 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/merge-gate head bbadbb2af021 merged into trunk 289bbf68e4f9 — pass: builds mesh-controller → novox; no bus step; the change touches no module of the m…
The settle read the say from the builder's bucket while the ask read it through
builderSaysReferences; where they differed (a test's say against a bus with no
bucket) a module was handed back and taken from its key again at every turn,
and the look's loop never ended.
Merge check at bbadbb2a
Judged: head bbadbb2af021 merged into trunk 289bbf68e4f9; read beside it: mesh-catalog 89e15c7bcda6, mesh-controller-main 289bbf68e4f9, mesh-host 48c3e3834c69, mesh-tools e0fadc43d9dd
mesh/merge-gate: PASS — the change touches no module of the mesh's graph
mesh/repo-check: PASS — its merge-check.sh passed
Delivery plan — builds mesh-controller → novox; no bus step
tier 0: mesh-controller
novox: receives mesh-controller
read by no module's build: cmd/mesh-controller/builder_says_default_test.go, cmd/mesh-controller/builder_says_test.go, internal/builderkeys/says_integration_test.go, internal/builderkeys/says_test.go
Run by the build seat on ace as build-1792713568373168879 (builds --log build-1792713568373168879).
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 1886 (critical): R4e's delivery plan plan-1792707174627079192 is stuck in tier 1: the controller takes modules only from referenced builder keys, and only R4e's own build modules (in that plan) write references. ADR 0522: until a running builder says in mesh-delivery-builder_instances that it writes references (§1), every plan asks build-agent as before R4e (§2); an open plan's module waiting on a key the running builder cannot reference is asked of build-agent at the next look, which is how the stuck plan recovers (§3); the builder and the three build modules are build-agent's own until R4g (§6). Group with mesh-delivery on the same branch.
Tests seen failing first: TestTheBuilderSaysReferencesOnlyWhenAnInstanceSaysTheWord, TestAWalkAsksBuildAgentWhileTheBuilderDoesNotSayItWritesReferences, TestASayNotReadLeavesTheModuleUnasked, TestBuildAgentIsAskedForAnyModuleWhileTheBuilderDoesNotSay, TestAnOpenWalkWaitingOnAnUnreferencedKeyIsAskedOfBuildAgent, TestAFailedKeyOfABuilderThatDoesNotSayFailsNoWalk, TestTheReferenceWritersAreAskedOfBuildAgentWhateverTheBuilderSays, TestTheAskGuardUsesTheSayTheWalkRead, TestTheSettleJudgesByTheSameSayAsTheAsk (
bbadbb2a: the settle and the ask read one say; the merge check at1414ed7fhung in a look that handed modules back and asked them again). No try could run (its checker is stuck in the same plan); mesh/repo-check runs the integration tests. Delivered once by hand (ADR 0522 §5, cause bootstrap-1886).Reviewed-by: review-1886@shanks at
bbadbb2af0Delivery
novox/mesh-controller@bbadbb2af021— delivered since 2026-10-23T00:35:30ZDelivery plan — builds mesh-controller → novox; no bus step
Group
fix/1886-builder-says-references: novox/mesh-controller@bbadbb2af0, novox/mesh-delivery@9fad90ee89Machines
Transitions
The commit's note under
refs/notes/mesh-plankeeps every transition:git log --notes=mesh-plan.Merge check at
bbadbb2aJudged: head
bbadbb2af021merged into trunk289bbf68e4f9; read beside it: mesh-catalog89e15c7bcda6, mesh-controller-main289bbf68e4f9, mesh-host48c3e3834c69, mesh-toolse0fadc43d9ddmesh/merge-gate: PASS — the change touches no module of the mesh's graphmesh/repo-check: PASS — its merge-check.sh passedDelivery plan — builds mesh-controller → novox; no bus step
Run by the build seat on ace as
build-1792713568373168879(builds --log build-1792713568373168879).