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.
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`.
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.
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 400: the operator could not tell from a notification whether its cause was known, tracked and being fixed, or whether they had to act.
condition), set by whoever opens or works on the issue; the tracker answers which issues track which conditions through a new verbtracking; 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.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.
Delivery
novox/hq@8f995111605b— delivered since 2026-10-10T20:13:10ZDelivery 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@12619ec140Transitions
The commit's note under
refs/notes/mesh-plankeeps every transition:git log --notes=mesh-plan.67036c5e15to8f99511160