To-be 53 names ADR 0300: the issue tracker's record is a log of operations #317

Merged
mesh-admin merged 1 commits from design/53-adr-0300-home into main 2026-10-11 18:41:56 +00:00
Contributor

ADR 0300 (accepted in the knowledge base on 2026-10-11, proposed from g14 as the tracker's half of ADR 0297) named no home, so the knowledge base's whole-set rule fails ("ADR 0300 is accepted and nothing cites it"). That keeps mesh-knowledge unhealthy on novox and fails the rollout gate of every mesh-knowledge change, mesh-catalog #222 (issue 508) and #219 (issue 497) among them. To-be 53 is the issue tracker's design, so it names ADR 0300 among its decisions and states it in a short section; the record gets this design as its home by a progressive insight in the knowledge base. Nothing ADR 0300 decides changes. merge-check.sh passes. Issue 504 asks the knowledge base to refuse acceptance without a home.

ADR 0300 (accepted in the knowledge base on 2026-10-11, proposed from g14 as the tracker's half of ADR 0297) named no home, so the knowledge base's whole-set rule fails ("ADR 0300 is accepted and nothing cites it"). That keeps mesh-knowledge unhealthy on novox and fails the rollout gate of every mesh-knowledge change, mesh-catalog #222 (issue 508) and #219 (issue 497) among them. To-be 53 is the issue tracker's design, so it names ADR 0300 among its decisions and states it in a short section; the record gets this design as its home by a progressive insight in the knowledge base. Nothing ADR 0300 decides changes. `merge-check.sh` passes. Issue 504 asks the knowledge base to refuse acceptance without a home.
mesh-admin added 1 commit 2026-10-11 18:38:04 +00:00
Give ADR 0300 its place in to-be 53: the tracker's record is a log of operations (issue 508)
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
f95f758c87
ADR 0300 was accepted with no home, so the knowledge base's whole-set rule fails and holds every rollout of mesh-knowledge.
Author
Contributor

Delivery novox/hq@f95f758c87a5 — delivered since 2026-10-11T18:42:08Z

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

Transitions

  • 2026-10-11 18:38 (new) → proposed (announced): novox/hq#317's head announced
  • 2026-10-11 18:39 proposed → checked (checked): the verdict names this commit
  • 2026-10-11 18:39 checked → ready (accepted): the gate passed or warned, and the repository's own check did not fail
  • 2026-10-11 18:42 ready → published (merged): on the trunk its modules follow: merged there, and its walk opened — or nothing for a walk to move
  • 2026-10-11 18:42 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@f95f758c87a5` — **delivered** since 2026-10-11T18:42:08Z **Delivery plan** — builds nothing: the change touches no module of the mesh's graph **Transitions** - 2026-10-11 18:38 (new) → proposed (announced): novox/hq#317's head announced - 2026-10-11 18:39 proposed → checked (checked): the verdict names this commit - 2026-10-11 18:39 checked → ready (accepted): the gate passed or warned, and the repository's own check did not fail - 2026-10-11 18:42 ready → published (merged): on the trunk its modules follow: merged there, and its walk opened — or nothing for a walk to move - 2026-10-11 18:42 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 4336fdfb11 into main 2026-10-11 18:41:56 +00:00
mesh-admin deleted branch design/53-adr-0300-home 2026-10-11 18:41:56 +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#317