novox/hq
9
0
Fork 0
Code Issues Pull Requests 1 Releases Wiki Activity

ADR 0248: the decision index is generated when it is read, and never stored (issue 297) #182

Merged
mesh-admin merged 2 commits from decision/generated-decisions-index into main 2026-10-07 21:44:15 +00:00
Conversation 1 Commits 2 Files Changed 10
+204 -324
mesh-admin commented 2026-10-07 21:39:19 +00:00
Contributor
Copy Link
Copy Source

Fixes issue 297 (two open decisions always conflict), with fix A of its diagnosis, approved by the operator 2026-10-07.

  • ADR 0248 supersedes in part ADR 0019's paragraph "the index is written"; ADR 0019 carries a dated "Superseded in part" note.
  • 02-DECISIONS/README.md keeps its prose and writes only the six topics in reading order, one line each; the stored list and its markers are gone.
  • index.py now checks: the README writes a reading order, every record's topic is one of it, and the README stores no list (markers or a generated line). --print renders the list; --write is gone. It fails on the README of main before this change.
  • records.py reads its topics from the same README lines (one list of topics, not two).
  • hq-status skill, checks README and playbook 00 updated.
  • Issue 297 resolved; not a core issue (located in hq), so no replay is required by cycle.py. The report's own replay was run: two branches off this one each adding a record on the same topic merge with no conflict, and merge-check passes on each and on the merge.

Companion: novox/mesh-catalog#115 adds the records module's records_decisions.

records.py, index.py, cycle.py, words.py and sh merge-check.sh pass locally.

Fixes issue 297 (two open decisions always conflict), with fix A of its diagnosis, approved by the operator 2026-10-07. - **ADR 0248** supersedes in part ADR 0019's paragraph "the index is written"; ADR 0019 carries a dated "Superseded in part" note. - `02-DECISIONS/README.md` keeps its prose and writes only the six topics in reading order, one line each; the stored list and its markers are gone. - `index.py` now checks: the README writes a reading order, every record's topic is one of it, and the README stores no list (markers or a generated line). `--print` renders the list; `--write` is gone. It fails on the README of main before this change. - `records.py` reads its topics from the same README lines (one list of topics, not two). - `hq-status` skill, checks README and playbook 00 updated. - Issue 297 resolved; not a core issue (located in hq), so no replay is required by cycle.py. The report's own replay was run: two branches off this one each adding a record on the same topic merge with no conflict, and merge-check passes on each and on the merge. Companion: novox/mesh-catalog#115 adds the records module's `records_decisions`. records.py, index.py, cycle.py, words.py and `sh merge-check.sh` pass locally.
mesh-admin added 1 commit 2026-10-07 21:39:20 +00:00
ADR 0248: the decision index is generated when it is read, so two open decisions no longer conflict 55637ecb95
jschoubben added 1 commit 2026-10-07 21:39:32 +00:00
Issue 297: resolved by hq PR #182 and mesh-catalog PR #115
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
f4a76ca291
mesh-admin commented 2026-10-07 21:40:03 +00:00
Author
Contributor
Copy Link
Copy Source

Delivery novox/hq@f4a76ca29195 — delivered since 2026-10-07T21:44:35Z

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

Transitions

  • 2026-10-07 21:39 (new) → proposed (announced): novox/hq#182's head announced
  • 2026-10-07 21:40 proposed → checked (checked): the verdict names this commit
  • 2026-10-07 21:40 checked → ready (accepted): the gate passed or warned, and the repository's own check did not fail
  • 2026-10-07 21:44 ready → published (merged): on the trunk its modules follow: merged there, and its walk opened — or nothing for a walk to move
  • 2026-10-07 21:44 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@f4a76ca29195` — **delivered** since 2026-10-07T21:44:35Z **Delivery plan** — builds nothing: the change touches no module of the mesh's graph **Transitions** - 2026-10-07 21:39 (new) → proposed (announced): novox/hq#182's head announced - 2026-10-07 21:40 proposed → checked (checked): the verdict names this commit - 2026-10-07 21:40 checked → ready (accepted): the gate passed or warned, and the repository's own check did not fail - 2026-10-07 21:44 ready → published (merged): on the trunk its modules follow: merged there, and its walk opened — or nothing for a walk to move - 2026-10-07 21:44 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 ded2173308 into main 2026-10-07 21:44:15 +00:00
mesh-admin deleted branch decision/generated-decisions-index 2026-10-07 21:44:15 +00:00
Sign in to join this conversation.
Reviewers
No Reviewers
Labels
Clear labels
mesh/ready
Reviewed and ready: mesh-delivery merges at the marked head once its checks pass (hq ADR 0364)
No labels
Milestone
No items
No Milestone
Assignees
Clear assignees
agent-ace agent-g14 agent-novox agent-shanks jschoubben mesh-tools miel.truyen nox-agent
No Assignees
2 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: novox/hq#182