Proposed: ADR 0293, an ask the controller made is delivered again to its seat's worker (issue 334) #310

Merged
mesh-admin merged 2 commits from decisions/334-the-controllers-own-ask-is-delivered-again into main 2026-10-11 02:36:25 +00:00
Contributor

This proposes ADR 0293, status proposed. The operator decides. It supersedes in part ADR 0264 decision 4 (an ask a seat's worker gave up on can only be dropped).

  • Decided if accepted: the controller's own asks to the two build seats are delivered again on their own subject. The original is deleted from the work queue first, and only when the message at that sequence has the dead letter's subject and stored time. Nothing is delivered while the worker is off the bus. The copy carries Mesh-Delivered-Again and a de-duplication id. The asker stays truthful: build accepts do not name a caller, so ADR 0259 §3 is untouched. Every other ask stays drop-only, and no grant changes.
  • Options weighed: (a) all asks drop-only, which is the status quo; (b) this one; (c) granting the controller every declared seat's accept subjects, rejected because it would let the controller speak in any module's name.
  • Said plainly: a retry made after the two-minute de-duplication window (the bus default, since the seat queues set none) can build twice.
  • ADR 0264 gets the dated Superseded in part note under its heading. The note says decision 4 holds as written until 0293 is accepted.
  • Implemented by mesh-controller #219, which must not merge before this record is accepted. Issue 334 stays open afterwards for the other seats.

Checks: sh merge-check.sh (records, index, cycle, words with the catalogue's list) passes locally.

This proposes ADR 0293, status `proposed`. **The operator decides.** It supersedes in part ADR 0264 decision 4 (an ask a seat's worker gave up on can only be dropped). - **Decided if accepted:** the controller's own asks to the two build seats are delivered again on their own subject. The original is deleted from the work queue first, and only when the message at that sequence has the dead letter's subject and stored time. Nothing is delivered while the worker is off the bus. The copy carries `Mesh-Delivered-Again` and a de-duplication id. The asker stays truthful: build accepts do not name a caller, so ADR 0259 §3 is untouched. Every other ask stays drop-only, and no grant changes. - **Options weighed:** (a) all asks drop-only, which is the status quo; (b) this one; (c) granting the controller every declared seat's accept subjects, rejected because it would let the controller speak in any module's name. - **Said plainly:** a retry made after the two-minute de-duplication window (the bus default, since the seat queues set none) can build twice. - **ADR 0264** gets the dated *Superseded in part* note under its heading. The note says decision 4 holds as written until 0293 is accepted. - Implemented by mesh-controller #219, which must not merge before this record is accepted. Issue 334 stays open afterwards for the other seats. Checks: `sh merge-check.sh` (records, index, cycle, words with the catalogue's list) passes locally.
mesh-admin added 1 commit 2026-10-11 01:26:16 +00:00
Propose ADR 0293: the controller delivers its own given-up asks again (issue 334)
mesh/merge-gate pass: the change touches no module of the mesh's graph
mesh/repo-check pass: its merge-check.sh passed
mesh/delivery superseded: a newer head of the same pull request
ab947a8c1c
Author
Contributor

Delivery novox/hq@f9677dabead7 — delivered since 2026-10-11T02:36:34Z

Delivery plan — builds nothing: the change touches no module of the mesh's graph

Transitions

  • 2026-10-11 02:21 (new) → proposed (announced): novox/hq#310's head announced
  • 2026-10-11 02:23 proposed → checked (checked): the verdict names this commit
  • 2026-10-11 02:23 checked → ready (accepted): the gate passed or warned, and the repository's own check did not fail
  • 2026-10-11 02:36 ready → published (merged): on the trunk its modules follow: merged there, and its walk opened — or nothing for a walk to move
  • 2026-10-11 02:36 published → delivered (done): nothing for a walk to move

The commit's note under refs/notes/mesh-plan keeps every transition: git log --notes=mesh-plan.

<!-- mesh-delivery:view --> **Delivery** `novox/hq@f9677dabead7` — **delivered** since 2026-10-11T02:36:34Z **Delivery plan** — builds nothing: the change touches no module of the mesh's graph **Transitions** - 2026-10-11 02:21 (new) → proposed (announced): novox/hq#310's head announced - 2026-10-11 02:23 proposed → checked (checked): the verdict names this commit - 2026-10-11 02:23 checked → ready (accepted): the gate passed or warned, and the repository's own check did not fail - 2026-10-11 02:36 ready → published (merged): on the trunk its modules follow: merged there, and its walk opened — or nothing for a walk to move - 2026-10-11 02:36 published → delivered (done): nothing for a walk to move The commit's note under `refs/notes/mesh-plan` keeps every transition: `git log --notes=mesh-plan`.
jschoubben added 1 commit 2026-10-11 02:21:14 +00:00
Accept ADR 0293 on the operator's word, and give it its place in to-be 45 (issue 334)
mesh/merge-gate pass: the change touches no module of the mesh's graph
mesh/repo-check pass: its merge-check.sh passed
mesh/delivery delivered
f9677dabea
The operator chose 2026-10-11 to let the controller deliver its own given-up asks again; every other ask stays drop-only.
mesh-admin merged commit 331e8d0bbe into main 2026-10-11 02:36:25 +00:00
mesh-admin deleted branch decisions/334-the-controllers-own-ask-is-delivered-again 2026-10-11 02:36:25 +00:00
Sign in to join this conversation.
No Reviewers
2 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: novox/hq#310