ADR 0285: every condition's message says which issue tracks it and where it stands (issue 400) #299

Merged
mesh-admin merged 2 commits from feat/400-alert-names-its-issue into main 2026-10-10 20:12:38 +00:00
Contributor

Issue 400: the operator could not tell from a notification whether its cause was known, tracked and being fixed, or whether they had to act.

  • ADR 0285: an issue tracks a condition by the condition's exact key (link kind condition), set by whoever opens or works on the issue; the tracker answers which issues track which conditions through a new verb tracking; the router (messenger) asks it over the bus and says the tracking line in every message about a condition; "Nothing for you to do." becomes "Needs you: answer issue N." while an issue waits for the operator, and is left out while nobody works on any issue tracking it. The controller is not changed.
  • Amends to-be 53 (new § 12, verb table, slice 4) and to-be 45 § 5 (the message), playbook 03 step 1, the glossary (tracks, tracking line), and a dated pointer in ADR 0253.

Code: mesh-catalog (modules/mesh-issues and modules/messenger), one pull request.

Acceptance: a message whose condition an issue tracks says the issue's number and, in plain words, whether someone is working on it, its fix is on its way, or nobody is; a message with no issue says so.

Issue 400: the operator could not tell from a notification whether its cause was known, tracked and being fixed, or whether they had to act. - ADR 0285: an issue tracks a condition by the condition's exact key (link kind `condition`), set by whoever opens or works on the issue; the tracker answers which issues track which conditions through a new verb `tracking`; the router (messenger) asks it over the bus and says the tracking line in every message about a condition; "Nothing for you to do." becomes "Needs you: answer issue N." while an issue waits for the operator, and is left out while nobody works on any issue tracking it. The controller is not changed. - Amends to-be 53 (new § 12, verb table, slice 4) and to-be 45 § 5 (the message), playbook 03 step 1, the glossary (tracks, tracking line), and a dated pointer in ADR 0253. Code: mesh-catalog (modules/mesh-issues and modules/messenger), one pull request. Acceptance: a message whose condition an issue tracks says the issue's number and, in plain words, whether someone is working on it, its fix is on its way, or nobody is; a message with no issue says so.
Author
Contributor

Delivery novox/hq@8f995111605b — delivered since 2026-10-10T20:13:10Z

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

Group feat/400-alert-names-its-issue, in order: novox/hq@67036c5e15 → novox/mesh-catalog@12619ec140

  • composed together: pass — every machine composes with the change as it did without (4 of 4 compose)

Transitions

  • 2026-10-10 20:10 (new) → proposed (announced): novox/hq#299's head announced
  • 2026-10-10 20:10 proposed → checked (checked): the verdict names this commit
  • 2026-10-10 20:10 checked → ready (accepted): the gate passed or warned, and the repository's own check did not fail
  • 2026-10-10 20:13 ready → published (merged): on the trunk its modules follow: merged there, and its walk opened — or nothing for a walk to move
  • 2026-10-10 20:13 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@8f995111605b` — **delivered** since 2026-10-10T20:13:10Z **Delivery plan** — builds nothing: the change touches no module of the mesh's graph **Group** `feat/400-alert-names-its-issue`, in order: novox/hq@67036c5e15e3 → novox/mesh-catalog@12619ec140a0 - composed together: pass — every machine composes with the change as it did without (4 of 4 compose) **Transitions** - 2026-10-10 20:10 (new) → proposed (announced): novox/hq#299's head announced - 2026-10-10 20:10 proposed → checked (checked): the verdict names this commit - 2026-10-10 20:10 checked → ready (accepted): the gate passed or warned, and the repository's own check did not fail - 2026-10-10 20:13 ready → published (merged): on the trunk its modules follow: merged there, and its walk opened — or nothing for a walk to move - 2026-10-10 20:13 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 2 commits 2026-10-10 20:09:36 +00:00
The operator could not tell from a notification whether its cause was
known, tracked and being fixed. An issue tracks a condition by its key;
the tracker answers which issues track which conditions, and the router
says it in every message about the condition. Amends to-be 53 and 45,
playbook 03 and the glossary, and points ADR 0253 at the new line.
Check every rule of ADR 0285, point ADR 0253 at it under its verdict rule, and cite the pull requests
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
mesh/delivery-group group feat/400-alert-names-its-issue merged: every member is merged
8f99511160
Review of hq#299.
jschoubben force-pushed feat/400-alert-names-its-issue from 67036c5e15 to 8f99511160 2026-10-10 20:09:36 +00:00 Compare
mesh-admin merged commit 86715ee5c1 into main 2026-10-10 20:12:38 +00:00
mesh-admin deleted branch feat/400-alert-names-its-issue 2026-10-10 20:12:38 +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#299