ADR 0279, to-be 53 §10: the issue tracker triages every new issue, and an issue is ready when what it depends on is delivered #285

Merged
mesh-admin merged 4 commits from decisions/0279-the-issue-tracker-triages-every-new-issue into main 2026-10-10 16:00:22 +00:00
Contributor

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.
mesh-admin added 2 commits 2026-10-10 15:49:51 +00:00
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.
ADR 0279: ready waits for the pull requests fixed-by names, not every entry
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
3e346e7cd7
Author
Contributor

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.

<!-- 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`.
jschoubben added 1 commit 2026-10-10 15:54:50 +00:00
jschoubben added 1 commit 2026-10-10 15:54:57 +00:00
ADR 0279: set says who set a value in its event; a value is changed, not cleared
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
d5aecc7a31
mesh-admin merged commit d836092329 into main 2026-10-10 16:00:22 +00:00
mesh-admin deleted branch decisions/0279-the-issue-tracker-triages-every-new-issue 2026-10-10 16:00:23 +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#285