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.
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.
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.
Deliverynovox/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`.
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.
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 a tool that consolidates duplicate issues, and better, one that runs when an issue is opened.
openedevent; two judgements (a shortlist by titles, a verdict on the reports) by the agent module's newclaude_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 linkedduplicates, its report kept as a note on the older one, moved towontfix"duplicate of N". Related or not certain:relates-toand notes. None: a note. Never the older issue, never a resolved one; once per issue; a failed judgement leaves one note and ends inmax-deliveries. The backlog: verbgroom, a dry run kept in state, applied onconfirm.groom, §7 check row, §8 slice 3 note, new §9.Checks run locally: records, index, cycle, words (with the catalogue) all pass. Code follows in mesh-catalog, naming this decision.
Delivery
novox/hq@5f2f52001888— delivered since 2026-10-10T15:22:46ZDelivery 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.