ADR 0275 and to-be 53: the mesh numbers and tracks its issues in a module of its own #270

Merged
mesh-admin merged 1 commits from decisions/the-mesh-keeps-its-own-issues into main 2026-10-10 10:34:52 +00:00
Contributor

Graduates research 042 (the mesh keeps its own issues).

  • ADR 0275 (accepted, 2026-10-10, deciders: jochen). The operator delegated the five open questions; each is decided as the research recommended: (1) the tracker holds every issue's number and status, hq keeps a folder only for a design or governance issue under the tracker's number; (2) our own Go module issues on hits's model, no hits code; (3) decision and research numbers from the tracker in slice 2; (4) the word stays issue, module issues, the issue tracker; (5) conditions linked only, the controller opens issues by itself only after slice 4 ran a week. Rejected options recorded.
  • To-be 53 — The issue tracker (designed): slice 1 in detail (seat issue-tracker on the control-node, verbs open/get/list/move/note/link, buckets issues and counters declared per ADR 0201, counter by compare-and-set via new runtime create/update state verbs, one event per change, cycle rules at the write, caller from the bus credential). Slices 2-5 listed with what the operator sees.
  • Acceptance: an agent opens an issue and gets the next number; two agents opening at the same moment never get the same one.
  • Research 042 closed (graduated, became: both).
  • Glossary: issue widened, issue tracker added; ticketing system / ticket system retired (hq). Bare ticket goes to Homonyms instead of a Not: line, because ADR 0258 and to-be 46 already use answer ticket for an answer's one-time token; retiring the bare word would fail words.py on to-be 46 and issue 360. words-allowed: research 042's overview kept (it records the operator's ask).

Checks run locally: cycle, records, index, words, merge-check.sh all pass.

Graduates research 042 (the mesh keeps its own issues). - **ADR 0275** (accepted, 2026-10-10, deciders: jochen). The operator delegated the five open questions; each is decided as the research recommended: (1) the tracker holds every issue's number and status, hq keeps a folder only for a design or governance issue under the tracker's number; (2) our own Go module `issues` on hits's model, no hits code; (3) decision and research numbers from the tracker in slice 2; (4) the word stays *issue*, module `issues`, the *issue tracker*; (5) conditions linked only, the controller opens issues by itself only after slice 4 ran a week. Rejected options recorded. - **To-be 53 — The issue tracker** (designed): slice 1 in detail (seat `issue-tracker` on the control-node, verbs open/get/list/move/note/link, buckets `issues` and `counters` declared per ADR 0201, counter by compare-and-set via new runtime `create`/`update` state verbs, one event per change, cycle rules at the write, caller from the bus credential). Slices 2-5 listed with what the operator sees. - Acceptance: an agent opens an issue and gets the next number; two agents opening at the same moment never get the same one. - Research 042 closed (`graduated`, `became:` both). - Glossary: *issue* widened, *issue tracker* added; *ticketing system* / *ticket system* retired (hq). Bare *ticket* goes to Homonyms instead of a Not: line, because ADR 0258 and to-be 46 already use *answer ticket* for an answer's one-time token; retiring the bare word would fail words.py on to-be 46 and issue 360. words-allowed: research 042's overview kept (it records the operator's ask). Checks run locally: cycle, records, index, words, merge-check.sh all pass.
mesh-admin added 1 commit 2026-10-10 10:31:46 +00:00
Graduate research 042 into ADR 0275 and to-be 53, so issue numbers stop colliding
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
015ff1adfb
Numbers taken by reading a repository many branches write at once collide;
one counter in a module of the mesh's own, advanced by compare-and-set,
ends that at the source. The operator delegated the five open questions
on 2026-10-10; each is decided as the research recommended. The glossary
gains the issue tracker, retires "ticketing system" and lists ticket as a
homonym, since ADR 0258 already uses it for an answer's one-time token.
Author
Contributor

Delivery novox/hq@015ff1adfbe9 — delivered since 2026-10-10T10:35:17Z

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

Transitions

  • 2026-10-10 10:31 (new) → proposed (announced): novox/hq#270's head announced
  • 2026-10-10 10:32 proposed → checked (checked): the verdict names this commit
  • 2026-10-10 10:32 checked → ready (accepted): the gate passed or warned, and the repository's own check did not fail
  • 2026-10-10 10:35 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 10:35 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@015ff1adfbe9` — **delivered** since 2026-10-10T10:35:17Z **Delivery plan** — builds nothing: the change touches no module of the mesh's graph **Transitions** - 2026-10-10 10:31 (new) → proposed (announced): novox/hq#270's head announced - 2026-10-10 10:32 proposed → checked (checked): the verdict names this commit - 2026-10-10 10:32 checked → ready (accepted): the gate passed or warned, and the repository's own check did not fail - 2026-10-10 10:35 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 10:35 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 9395c752cc into main 2026-10-10 10:34:52 +00:00
mesh-admin deleted branch decisions/the-mesh-keeps-its-own-issues 2026-10-10 10:34:52 +00:00
Sign in to join this conversation.
No Reviewers
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: novox/hq#270