Playbook 03 takes an issue's number from the issue tracker #274

Merged
mesh-admin merged 1 commits from process/issue-numbers-from-the-tracker into main 2026-10-10 11:09:16 +00:00
Contributor

The issue tracker (ADR 0275, to-be 53) has been live since 2026-10-10. This brings hq's issue process in line with it.

  • Playbook 03 (00-META/process/03-issues.md): an issue's number comes from issue-tracker.open, never from reading main or open pull requests. A design or governance issue passes record: and gets the folder 04-ISSUES/NNN-<record>/ under the tracker's number. Every other issue lives wholly in the tracker (note, move, link). A folder-backed issue keeps its status in frontmatter until slice 3's import, and move refuses it until then (ADR 0275). The old renumbering rule becomes: a number never moves.
  • hq-new-issue skill: the same steps, using the tracker's real argument names (checked with mesh_describe).
  • Research 042 findings §1: a dated correction. The SDK's Go state interface had Create/Update (compare-and-set) since go/v0.1.10, and Increment was added in go/v0.1.12. I checked this against the SDK's tags.
  • To-be 53: code: now names mesh-catalog modules/mesh-issues and mesh-sdk. Status stays in-progress.

Local checks: cycle, records, index and words pass, and merge-check.sh passes.

The issue tracker (ADR 0275, to-be 53) has been live since 2026-10-10. This brings hq's issue process in line with it. - **Playbook 03** (`00-META/process/03-issues.md`): an issue's number comes from `issue-tracker.open`, never from reading `main` or open pull requests. A design or governance issue passes `record:` and gets the folder `04-ISSUES/NNN-<record>/` under the tracker's number. Every other issue lives wholly in the tracker (`note`, `move`, `link`). A folder-backed issue keeps its status in frontmatter until slice 3's import, and `move` refuses it until then (ADR 0275). The old renumbering rule becomes: a number never moves. - **hq-new-issue skill**: the same steps, using the tracker's real argument names (checked with `mesh_describe`). - **Research 042 findings §1**: a dated correction. The SDK's Go state interface had `Create`/`Update` (compare-and-set) since go/v0.1.10, and `Increment` was added in go/v0.1.12. I checked this against the SDK's tags. - **To-be 53**: `code:` now names `mesh-catalog modules/mesh-issues` and `mesh-sdk`. Status stays `in-progress`. Local checks: cycle, records, index and words pass, and `merge-check.sh` passes.
mesh-admin added 1 commit 2026-10-10 11:06:26 +00:00
Playbook 03 takes an issue's number from the issue tracker
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
beaeedca79
Issue numbers collided while each author read main and the open pull
requests; since 2026-10-10 the tracker (ADR 0275) hands them out. The
playbook and the hq-new-issue skill now open every issue there, keep a
folder only for a design or governance issue, and say where its status
lives until slice 3. Research 042's finding that the SDK had no
compare-and-set is corrected, and to-be 53 names the module's code.
Author
Contributor

Delivery novox/hq@beaeedca793c — delivered since 2026-10-10T11:09:24Z

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

Transitions

  • 2026-10-10 11:06 (new) → proposed (announced): novox/hq#274's head announced
  • 2026-10-10 11:07 proposed → checked (checked): the verdict names this commit
  • 2026-10-10 11:07 checked → ready (accepted): the gate passed or warned, and the repository's own check did not fail
  • 2026-10-10 11:09 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:09 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@beaeedca793c` — **delivered** since 2026-10-10T11:09:24Z **Delivery plan** — builds nothing: the change touches no module of the mesh's graph **Transitions** - 2026-10-10 11:06 (new) → proposed (announced): novox/hq#274's head announced - 2026-10-10 11:07 proposed → checked (checked): the verdict names this commit - 2026-10-10 11:07 checked → ready (accepted): the gate passed or warned, and the repository's own check did not fail - 2026-10-10 11:09 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:09 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 8af56cf2ae into main 2026-10-10 11:09:16 +00:00
mesh-admin deleted branch process/issue-numbers-from-the-tracker 2026-10-10 11:09:16 +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#274