ADR 0275, to-be 53: the issue tracker's module is mesh-issues, holding the seat issue-tracker #272

Merged
mesh-admin merged 1 commits from decisions/0275-the-issue-trackers-module-is-mesh-issues into main 2026-10-10 10:59:54 +00:00
Contributor

The operator named the module on 2026-10-10: mesh-issues (the mesh's own parts carry the mesh- prefix, like mesh-delivery and mesh-vault); the seat stays issue-tracker, the role, as operator-channel is held by messenger. Verbs: issue-tracker.open/get/list/move/note/link.

  • ADR 0275: a dated progressive insight (the decision stands): the module's name, and that compare-and-set state (create, update at a revision) was already in the runtime and SDK since ADR 0259; slice 1 added only the SDK's Increment (mesh-sdk #16, tag go/v0.1.12).
  • To-be 53: the module's name throughout, §4 says what exists and how the counter is started (once, by create at the number before the first); handed off per playbook 04: status: in-progress, code: [mesh-catalog, mesh-sdk].
  • Glossary: issue tracker is the role: seat issue-tracker, held by module mesh-issues.

The module itself: mesh-catalog PR (feat/the-issue-tracker). sh merge-check.sh passes locally.

The operator named the module on 2026-10-10: `mesh-issues` (the mesh's own parts carry the `mesh-` prefix, like mesh-delivery and mesh-vault); the seat stays `issue-tracker`, the role, as `operator-channel` is held by `messenger`. Verbs: `issue-tracker.open/get/list/move/note/link`. - **ADR 0275**: a dated progressive insight (the decision stands): the module's name, and that compare-and-set state (`create`, `update` at a revision) was already in the runtime and SDK since ADR 0259; slice 1 added only the SDK's `Increment` (mesh-sdk #16, tag go/v0.1.12). - **To-be 53**: the module's name throughout, §4 says what exists and how the counter is started (once, by `create` at the number before the first); handed off per playbook 04: `status: in-progress`, `code: [mesh-catalog, mesh-sdk]`. - **Glossary**: *issue tracker* is the role: seat `issue-tracker`, held by module `mesh-issues`. The module itself: mesh-catalog PR (feat/the-issue-tracker). `sh merge-check.sh` passes locally.
mesh-admin added 1 commit 2026-10-10 10:52:45 +00:00
ADR 0275, to-be 53: the issue tracker's module is mesh-issues, holding the seat issue-tracker
mesh/delivery delivered
mesh/merge-gate pass: the change touches no module of the mesh's graph
mesh/repo-check pass: its merge-check.sh passed
8d9eae7224
The operator named the module on 2026-10-10: the mesh's own parts carry the
mesh- prefix, and the seat is the role. A dated insight in ADR 0275 says so,
and that compare-and-set state was already in the runtime (ADR 0259): slice 1
added the SDK's Increment. To-be 53 and the glossary say the same, and the
design is handed to mesh-catalog and mesh-sdk (in progress).
Author
Contributor

Delivery novox/hq@8d9eae722487 — delivered since 2026-10-10T11:00:14Z

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

Transitions

  • 2026-10-10 10:53 (new) → proposed (announced): novox/hq#272's head announced
  • 2026-10-10 10:54 proposed → checked (checked): the verdict names this commit
  • 2026-10-10 10:54 checked → ready (accepted): the gate passed or warned, and the repository's own check did not fail
  • 2026-10-10 11: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 11: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@8d9eae722487` — **delivered** since 2026-10-10T11:00:14Z **Delivery plan** — builds nothing: the change touches no module of the mesh's graph **Transitions** - 2026-10-10 10:53 (new) → proposed (announced): novox/hq#272's head announced - 2026-10-10 10:54 proposed → checked (checked): the verdict names this commit - 2026-10-10 10:54 checked → ready (accepted): the gate passed or warned, and the repository's own check did not fail - 2026-10-10 11: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 11: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-admin merged commit cf529b567c into main 2026-10-10 10:59:54 +00:00
mesh-admin deleted branch decisions/0275-the-issue-trackers-module-is-mesh-issues 2026-10-10 10:59:54 +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#272