Research 042: the mesh keeps its own issues #267

2026-10-10T00:58:47Z

mesh-admin commented

2026-10-10 00:58:47 +00:00

Opens research 042 (status: active) for the operator's ask of 2026-10-10: an issue tracker on the bus that hands out numbers atomically and takes in the current issues. Do not merge without review.

Measured: 357 issue folders on main (283 resolved, 1 wontfix, 45 located, 27 open, 1 diagnosing), 1.9 MiB in all; 31 commits on main mention a renumbering; one open PR (#250) still carries the old number in its branch; 5 of 10 open conditions are healer-wanted.
First slice proposed: a Go module issues on one mesh seat, state in a bucket per ADR 0201, events per ADR 0041, verbs open/get/list/move/note/link/import; move enforces today's cycle rules at the write. Atomic numbering needs compare-and-set in the state interface, which the SDK (v0.1.9) does not offer.
Truth: recommended split: the tracker holds number, status and links; hq keeps a folder only for design/governance issues, pointing at the tracker by number. Needs a decision superseding parts of ADR 0019 and 0080 at graduation.
hits (the operator's reference) studied: same statuses and fields as ours, ops-log stream + KV projection, CAS counter. Recommended: build our own on its model; its Sustainable Use License limits distribution, it creates its own bus resources (against ADR 0201 §3), and its words clash with the glossary.
Five open questions for the operator in 01-findings.md section 7.

Checks run locally: records.py, index.py, cycle.py, words.py pass (sh merge-check.sh).

Opens research 042 (status: active) for the operator's ask of 2026-10-10: an issue tracker on the bus that hands out numbers atomically and takes in the current issues. Do not merge without review. - **Measured:** 357 issue folders on main (283 resolved, 1 wontfix, 45 located, 27 open, 1 diagnosing), 1.9 MiB in all; 31 commits on main mention a renumbering; one open PR (#250) still carries the old number in its branch; 5 of 10 open conditions are `healer-wanted`. - **First slice proposed:** a Go module `issues` on one mesh seat, state in a bucket per ADR 0201, events per ADR 0041, verbs open/get/list/move/note/link/import; `move` enforces today's cycle rules at the write. Atomic numbering needs compare-and-set in the state interface, which the SDK (v0.1.9) does not offer. - **Truth:** recommended split: the tracker holds number, status and links; hq keeps a folder only for design/governance issues, pointing at the tracker by number. Needs a decision superseding parts of ADR 0019 and 0080 at graduation. - **hits** (the operator's reference) studied: same statuses and fields as ours, ops-log stream + KV projection, CAS counter. Recommended: build our own on its model; its Sustainable Use License limits distribution, it creates its own bus resources (against ADR 0201 §3), and its words clash with the glossary. - Five open questions for the operator in 01-findings.md section 7. Checks run locally: records.py, index.py, cycle.py, words.py pass (`sh merge-check.sh`).

mesh-admin added 1 commit 2026-10-10 00:58:47 +00:00

Research 042: the mesh keeps its own issues

mesh/merge-gate pass: the change touches no module of the mesh's graph

Details

mesh/repo-check pass: its merge-check.sh passed

Details

mesh/delivery delivered

Details

028f3b6ae5

Opens the effort the operator asked for on 2026-10-10: an issues module on the bus that hands out
numbers atomically, so agents stop colliding on them, and takes in the 357 issue folders. Findings
cover the first slice, where the truth lives, the import, conditions, views, and hits as a model.

mesh-admin commented

2026-10-10 00:58:59 +00:00

Delivery novox/hq@028f3b6ae5c5 — delivered since 2026-10-10T01:02:53Z

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

Transitions

2026-10-10 00:58 (new) → proposed (announced): novox/hq#267's head announced
2026-10-10 00:59 proposed → checked (checked): the verdict names this commit
2026-10-10 00:59 checked → ready (accepted): the gate passed or warned, and the repository's own check did not fail
2026-10-10 01:02 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 01:02 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.

**Delivery** `novox/hq@028f3b6ae5c5` — **delivered** since 2026-10-10T01:02:53Z **Delivery plan** — builds nothing: the change touches no module of the mesh's graph **Transitions** - 2026-10-10 00:58 (new) → proposed (announced): novox/hq#267's head announced - 2026-10-10 00:59 proposed → checked (checked): the verdict names this commit - 2026-10-10 00:59 checked → ready (accepted): the gate passed or warned, and the repository's own check did not fail - 2026-10-10 01:02 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 01:02 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-admin merged commit 014554ce9b into main

2026-10-10 01:02:23 +00:00

mesh-admin deleted branch research/042-the-mesh-keeps-its-own-issues

2026-10-10 01:02:24 +00:00

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: novox/hq#267