The operator asked (2026-10-10) for severity and what an issue needs to be estimated by the judgement that already reads the backlog, and for dependencies between issues (an issue workable only once what it waits for is delivered). Complexity was asked and withdrawn as a research topic; it is left out.
ADR 0279: fields severity (critical/major/minor), needs (none/decision/operator), suggested-owner, delivered, triage; link kind depends-on (cycle refused; get shows needed-by); verbs: open takes severity/needs, new set, list filters severity/needs/ready. Ready = every dependency wontfix, or resolved with every pull request its fixed-by names delivered (from mesh-delivery.transition, and checks once at the move to resolved); an issue made ready gains a note and the event ready. The judgement of ADR 0278 becomes the triage: second question always asked; fills only empty values, notes a disagreement, adds links never removes; groom backfills, dry run first. Store: optional keys of one KV JSON value, no schema, so no migration.
ADR 0278: dated note that its mechanism moved to 0279.
To-be 53: §1, §2, §3, §7, new §10, What it leaves out.
Glossary: triage, ready.
Checks run locally: records, index, cycle, words (with the catalogue) pass. Code: mesh-catalog PR (feat/mesh-issues-triage), naming this decision.
The operator asked (2026-10-10) for severity and what an issue needs to be estimated by the judgement that already reads the backlog, and for dependencies between issues (an issue workable only once what it waits for is delivered). Complexity was asked and withdrawn as a research topic; it is left out.
- ADR 0279: fields `severity` (critical/major/minor), `needs` (none/decision/operator), `suggested-owner`, `delivered`, `triage`; link kind `depends-on` (cycle refused; `get` shows needed-by); verbs: `open` takes severity/needs, new `set`, `list` filters severity/needs/ready. Ready = every dependency wontfix, or resolved with every pull request its fixed-by names delivered (from `mesh-delivery.transition`, and `checks` once at the move to resolved); an issue made ready gains a note and the event `ready`. The judgement of ADR 0278 becomes the **triage**: second question always asked; fills only empty values, notes a disagreement, adds links never removes; `groom` backfills, dry run first. Store: optional keys of one KV JSON value, no schema, so no migration.
- ADR 0278: dated note that its mechanism moved to 0279.
- To-be 53: §1, §2, §3, §7, new §10, What it leaves out.
- Glossary: **triage**, **ready**.
Checks run locally: records, index, cycle, words (with the catalogue) pass. Code: mesh-catalog PR (feat/mesh-issues-triage), naming this decision.
The operator asked for severity and what an issue needs to be estimated by the
judgement that already reads the backlog, and for dependencies between issues,
an issue being workable only once what it waits for is on the machines.
Deliverynovox/hq@d5aecc7a313a — delivered since 2026-10-10T16:00:52Z
Delivery plan — builds nothing: the change touches no module of the mesh's graph
Transitions
2026-10-10 15:55 (new) → proposed (announced): novox/hq#285's head announced
2026-10-10 15:56 proposed → checked (checked): the verdict names this commit
2026-10-10 15:56 checked → ready (accepted): the gate passed or warned, and the repository's own check did not fail
2026-10-10 16:00 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 16:00 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@d5aecc7a313a` — **delivered** since 2026-10-10T16:00:52Z
**Delivery plan** — builds nothing: the change touches no module of the mesh's graph
**Transitions**
- 2026-10-10 15:55 (new) → proposed (announced): novox/hq#285's head announced
- 2026-10-10 15:56 proposed → checked (checked): the verdict names this commit
- 2026-10-10 15:56 checked → ready (accepted): the gate passed or warned, and the repository's own check did not fail
- 2026-10-10 16:00 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 16:00 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.
The operator asked (2026-10-10) for severity and what an issue needs to be estimated by the judgement that already reads the backlog, and for dependencies between issues (an issue workable only once what it waits for is delivered). Complexity was asked and withdrawn as a research topic; it is left out.
severity(critical/major/minor),needs(none/decision/operator),suggested-owner,delivered,triage; link kinddepends-on(cycle refused;getshows needed-by); verbs:opentakes severity/needs, newset,listfilters severity/needs/ready. Ready = every dependency wontfix, or resolved with every pull request its fixed-by names delivered (frommesh-delivery.transition, andchecksonce at the move to resolved); an issue made ready gains a note and the eventready. The judgement of ADR 0278 becomes the triage: second question always asked; fills only empty values, notes a disagreement, adds links never removes;groombackfills, dry run first. Store: optional keys of one KV JSON value, no schema, so no migration.Checks run locally: records, index, cycle, words (with the catalogue) pass. Code: mesh-catalog PR (feat/mesh-issues-triage), naming this decision.
Delivery
novox/hq@d5aecc7a313a— delivered since 2026-10-10T16:00:52ZDelivery 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.