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.
Deliverynovox/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`.
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.
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).Mesh-Delivered-Againand 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.Checks:
sh merge-check.sh(records, index, cycle, words with the catalogue's list) passes locally.Delivery
novox/hq@f9677dabead7— delivered since 2026-10-11T02:36:34ZDelivery plan — builds nothing: the change touches no module of the mesh's graph
Transitions
The commit's note under
refs/notes/mesh-plankeeps every transition:git log --notes=mesh-plan.