ADR 0278, to-be 53 §9: the issue tracker checks every new issue for a duplicate #281

Merged
mesh-admin merged 3 commits from decisions/0278-the-issue-tracker-checks-each-new-issue-for-a-duplicate into main 2026-10-10 15:22:34 +00:00
Contributor

The operator asked (2026-10-10) for a tool that consolidates duplicate issues, and better, one that runs when an issue is opened.

  • ADR 0278: the tracker consumes its own opened event; two judgements (a shortlist by titles, a verdict on the reports) by the agent module's new claude_code_judge, which runs the agent with no tools, in safe mode, under the node's licence, within 25 s. A certain duplicate: the newer issue is linked duplicates, its report kept as a note on the older one, moved to wontfix "duplicate of N". Related or not certain: relates-to and notes. None: a note. Never the older issue, never a resolved one; once per issue; a failed judgement leaves one note and ends in max-deliveries. The backlog: verb groom, a dry run kept in state, applied on confirm.
  • To-be 53: §1 parts, §2 verb groom, §7 check row, §8 slice 3 note, new §9.
  • Glossary: duplicate check.

Checks run locally: records, index, cycle, words (with the catalogue) all pass. Code follows in mesh-catalog, naming this decision.

The operator asked (2026-10-10) for a tool that consolidates duplicate issues, and better, one that runs when an issue is opened. - ADR 0278: the tracker consumes its own `opened` event; two judgements (a shortlist by titles, a verdict on the reports) by the agent module's new `claude_code_judge`, which runs the agent with no tools, in safe mode, under the node's licence, within 25 s. A certain duplicate: the newer issue is linked `duplicates`, its report kept as a note on the older one, moved to `wontfix` "duplicate of N". Related or not certain: `relates-to` and notes. None: a note. Never the older issue, never a resolved one; once per issue; a failed judgement leaves one note and ends in `max-deliveries`. The backlog: verb `groom`, a dry run kept in state, applied on `confirm`. - To-be 53: §1 parts, §2 verb `groom`, §7 check row, §8 slice 3 note, new §9. - Glossary: **duplicate check**. Checks run locally: records, index, cycle, words (with the catalogue) all pass. Code follows in mesh-catalog, naming this decision.
mesh-admin added 1 commit 2026-10-10 15:04:37 +00:00
ADR 0278, to-be 53 §9: the issue tracker checks every new issue for a duplicate
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
cf3065c660
The operator asked for duplicates to be consolidated, and better, when an issue is
opened rather than on a schedule. A judgement needs a model, and the mesh had no
channel for one; the agent module answers one question with no tools, under the
node's licence, and the tracker acts only on a clear duplicate, closing the newer
issue and keeping its report on the older one.
Author
Contributor

Delivery novox/hq@5f2f52001888 — delivered since 2026-10-10T15:22:46Z

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

Transitions

  • 2026-10-10 15:21 (new) → proposed (announced): novox/hq#281's head announced
  • 2026-10-10 15:22 proposed → checked (checked): the verdict names this commit
  • 2026-10-10 15:22 checked → ready (accepted): the gate passed or warned, and the repository's own check did not fail
  • 2026-10-10 15:22 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 15:22 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@5f2f52001888` — **delivered** since 2026-10-10T15:22:46Z **Delivery plan** — builds nothing: the change touches no module of the mesh's graph **Transitions** - 2026-10-10 15:21 (new) → proposed (announced): novox/hq#281's head announced - 2026-10-10 15:22 proposed → checked (checked): the verdict names this commit - 2026-10-10 15:22 checked → ready (accepted): the gate passed or warned, and the repository's own check did not fail - 2026-10-10 15:22 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 15:22 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:20:03 +00:00
ADR 0278: the check as a whole takes up to a minute, kept alive by the tool runner (issue 387); one judgement at a time
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
f89c2c350d
Review found the two questions together exceed the consumer's ack wait, which the
tool runner did not extend; the record says so and names the fix it waits on.
jschoubben added 1 commit 2026-10-10 15:21:41 +00:00
ADR 0278: the check's worst case is under the tool runner's two minutes, not one
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
5f2f520018
mesh-admin merged commit d82dde3dca into main 2026-10-10 15:22:34 +00:00
mesh-admin deleted branch decisions/0278-the-issue-tracker-checks-each-new-issue-for-a-duplicate 2026-10-10 15:22:35 +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#281