Design 47 R3d, the terminal-free fix: no step on design 47's path needs the operator's terminal.
issue 1317: a seat held once whose holder on record is assigned nowhere passes to its only claimant, with a hand act by the controller counted as a decision, not a repair; no pass when an assignment read fails; none written on the merge gate's throwaway composition (ADR 0449 §4).
issue 1314: a failed delivery plan raises plan-failed (warning) with Retry when plans retry would run, otherwise no action and the refusal's words; it ends when the plan leaves failed or 7 days after its last change (ADR 0449 §1-§2, ADR 0451 §3).
issue 1315: the asker words and performs Retry (plans retry), and asks again when a retried plan fails again (ADR 0449 §1-§2).
issue 1316: a refused answer to a plan's ask is told on the operator channel; an answer whose outcome is unknown is told as not known (ADR 0449 §3).
issue 1328: plans retry refuses a failed plan that a newer done plan of its repository and branch has passed, reading every later plan (ADR 0451 §1-§2).
What the operator sees on delivery: the failed delivery plans of the last 7 days raise plan-failed at once; on 2026-10-19 four of them (mesh-catalog #340, #313, mesh-controller #336, mesh-catalog #266) were passed by newer deliveries, so their notices carry no button and need nothing.
Tries before this pull request: 12db1d37, 7b83aaa9, f1775281 and 7f23c537 (build-1792446557334894303), all passed. Review: three rounds, the last one's single required change confirmed at the head.
Reviewed-by: review-no-terminal@shanks at 7f23c537cc
Design 47 R3d, the terminal-free fix: no step on design 47's path needs the operator's terminal.
- issue 1317: a seat held once whose holder on record is assigned nowhere passes to its only claimant, with a hand act by the controller counted as a decision, not a repair; no pass when an assignment read fails; none written on the merge gate's throwaway composition (ADR 0449 §4).
- issue 1314: a failed delivery plan raises `plan-failed` (warning) with Retry when `plans retry` would run, otherwise no action and the refusal's words; it ends when the plan leaves failed or 7 days after its last change (ADR 0449 §1-§2, ADR 0451 §3).
- issue 1315: the asker words and performs Retry (`plans retry`), and asks again when a retried plan fails again (ADR 0449 §1-§2).
- issue 1316: a refused answer to a plan's ask is told on the operator channel; an answer whose outcome is unknown is told as not known (ADR 0449 §3).
- issue 1328: `plans retry` refuses a failed plan that a newer done plan of its repository and branch has passed, reading every later plan (ADR 0451 §1-§2).
What the operator sees on delivery: the failed delivery plans of the last 7 days raise `plan-failed` at once; on 2026-10-19 four of them (mesh-catalog #340, #313, mesh-controller #336, mesh-catalog #266) were passed by newer deliveries, so their notices carry no button and need nothing.
Tries before this pull request: 12db1d37, 7b83aaa9, f1775281 and 7f23c537 (build-1792446557334894303), all passed. Review: three rounds, the last one's single required change confirmed at the head.
Reviewed-by: review-no-terminal@shanks at 7f23c537ccedd6ef196a1122c66be51c77d15da5
mesh/merge-gate head 7f23c537cced merged into trunk 1f708e2d8d72 — pass: builds build-agent, mesh-controller → ace, g14, novox, shanks; no bus step; every …
Deliverynovox/mesh-controller@7f23c537cced — delivered since 2026-10-19T22:56:06Z
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
Transitions
2026-10-19 21:55 (new) → proposed (announced): novox/mesh-controller#402's head announced
2026-10-19 22:04 proposed → checked (checked): a verdict names this commit and the trunk's head as its trunk commit
2026-10-19 22:04 checked → ready (accepted): the gate passed or warned, and the repository's own check did not fail
2026-10-19 22:33 ready → proposed (trunk moved): out of date: judged against trunk caa3fc8995, the trunk is now 1f708e2d8d72; judged again on a recheck or when it is merged
2026-10-19 22:44 proposed → checked (checked): a verdict names this commit and the trunk's head as its trunk commit
2026-10-19 22:44 checked → ready (accepted): the gate passed or warned, and the repository's own check did not fail
2026-10-19 22:49 ready → published (merged): on the trunk its modules follow: merged there, and its walk opened — or nothing for a walk to move
2026-10-19 22:49 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-19 22:56 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@7f23c537cced` — **delivered** since 2026-10-19T22:56:06Z
**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
**Transitions**
- 2026-10-19 21:55 (new) → proposed (announced): novox/mesh-controller#402's head announced
- 2026-10-19 22:04 proposed → checked (checked): a verdict names this commit and the trunk's head as its trunk commit
- 2026-10-19 22:04 checked → ready (accepted): the gate passed or warned, and the repository's own check did not fail
- 2026-10-19 22:33 ready → proposed (trunk moved): out of date: judged against trunk caa3fc899501, the trunk is now 1f708e2d8d72; judged again on a recheck or when it is merged
- 2026-10-19 22:44 proposed → checked (checked): a verdict names this commit and the trunk's head as its trunk commit
- 2026-10-19 22:44 checked → ready (accepted): the gate passed or warned, and the repository's own check did not fail
- 2026-10-19 22:49 ready → published (merged): on the trunk its modules follow: merged there, and its walk opened — or nothing for a walk to move
- 2026-10-19 22:49 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-19 22:56 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 7f23c537
Judged: head 7f23c537cced merged into trunk caa3fc899501; read beside it: mesh-catalog 954f84ea19b5, mesh-controller-main caa3fc899501, mesh-host 2474bf28330f, 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/asker_retry_integration_test.go, cmd/mesh-controller/asker_test.go, cmd/mesh-controller/plan_failed_test.go, cmd/mesh-controller/queue_test.go, cmd/mesh-controller/seat_pass_test.go, cmd/mesh-controller/signals_test.go, internal/catalogue/seat_pass_test.go, internal/inventory/holdings_test.go
Run by the build seat on shanks as build-1792446997268221218 (builds --log build-1792446997268221218).
Merge check at 7f23c537
Judged: head 7f23c537cced merged into trunk 1f708e2d8d72; read beside it: mesh-catalog 954f84ea19b5, mesh-controller-main 1f708e2d8d72, mesh-host 2474bf28330f, 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/asker_retry_integration_test.go, cmd/mesh-controller/asker_test.go, cmd/mesh-controller/plan_failed_test.go, cmd/mesh-controller/queue_test.go, cmd/mesh-controller/seat_pass_test.go, cmd/mesh-controller/signals_test.go, internal/catalogue/seat_pass_test.go, internal/inventory/holdings_test.go
Run by the build seat on ace as build-1792449196335150776 (builds --log build-1792449196335150776).
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.
Design 47 R3d, the terminal-free fix: no step on design 47's path needs the operator's terminal.
plan-failed(warning) with Retry whenplans retrywould run, otherwise no action and the refusal's words; it ends when the plan leaves failed or 7 days after its last change (ADR 0449 §1-§2, ADR 0451 §3).plans retry), and asks again when a retried plan fails again (ADR 0449 §1-§2).plans retryrefuses a failed plan that a newer done plan of its repository and branch has passed, reading every later plan (ADR 0451 §1-§2).What the operator sees on delivery: the failed delivery plans of the last 7 days raise
plan-failedat once; on 2026-10-19 four of them (mesh-catalog #340, #313, mesh-controller #336, mesh-catalog #266) were passed by newer deliveries, so their notices carry no button and need nothing.Tries before this pull request:
12db1d37,7b83aaa9,f1775281and7f23c537(build-1792446557334894303), all passed. Review: three rounds, the last one's single required change confirmed at the head.Reviewed-by: review-no-terminal@shanks at
7f23c537ccDelivery
novox/mesh-controller@7f23c537cced— delivered since 2026-10-19T22:56:06ZDelivery plan — builds build-agent, mesh-controller → ace, g14, novox, shanks; no bus step
Machines
Transitions
caa3fc8995, the trunk is now 1f708e2d8d72; judged again on a recheck or when it is mergedThe commit's note under
refs/notes/mesh-plankeeps every transition:git log --notes=mesh-plan.Merge check at
7f23c537Judged: head
7f23c537ccedmerged into trunkcaa3fc899501; read beside it: mesh-catalog954f84ea19b5, mesh-controller-maincaa3fc899501, mesh-host2474bf28330f, 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 shanks as
build-1792446997268221218(builds --log build-1792446997268221218).Merge check at
7f23c537Judged: head
7f23c537ccedmerged into trunk1f708e2d8d72; read beside it: mesh-catalog954f84ea19b5, mesh-controller-main1f708e2d8d72, mesh-host2474bf28330f, 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-1792449196335150776(builds --log build-1792449196335150776).