hq no longer stores the list of decision records in 02-DECISIONS/README.md (hq ADR 0248, issue 297): a stored list made every two open decisions conflict. The list is generated when read.
This adds records_decisions {topic?}: the records by topic, in the reading order the README writes (one line per topic, 1. **Label** — topic: name. ...), each with number, title, path and status, at the commit the answer names. A record whose topic is not in the reading order is returned as unfiled; a README with no reading order, or an unknown topic, is refused with why.
Tested: a new test against a repository it makes; and by hand against the hq branch of the companion PR (233 records, 6 topics, none unfiled). sh merge-check.sh passes locally (no controller beside it, so the manifest step said NOT CHECKED).
hq no longer stores the list of decision records in 02-DECISIONS/README.md (hq ADR 0248, issue 297): a stored list made every two open decisions conflict. The list is generated when read.
This adds `records_decisions {topic?}`: the records by topic, in the reading order the README writes (one line per topic, `1. **Label** — `topic: name`. ...`), each with number, title, path and status, at the commit the answer names. A record whose topic is not in the reading order is returned as unfiled; a README with no reading order, or an unknown topic, is refused with why.
Tested: a new test against a repository it makes; and by hand against the hq branch of the companion PR (233 records, 6 topics, none unfiled). `sh merge-check.sh` passes locally (no controller beside it, so the manifest step said NOT CHECKED).
Companion: novox/hq decision/generated-decisions-index.
Deliverynovox/mesh-catalog@cb733d1b7cea — delivered since 2026-10-07T21:51:25Z
Delivery plan — builds records → novox; no bus step
tier 0: records
novox: receives records
records keeps data (ADR 0233): what it holds is backed up before it moves
Machines
systemd on ace: passed — healthy 3 times over 2m25s
records on novox: passed — healthy 3 times over 2m46s
systemd on novox: judging — carried by release-1791409555270590919
systemd on the rest running it: sent
records on the rest running it: sent
Transitions
2026-10-07 21:39 (new) → proposed (announced): novox/mesh-catalog#115's head announced
2026-10-07 21:41 proposed → checked (checked): the verdict names this commit
2026-10-07 21:41 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 → delivering (go): its walk started: let go by this owner in its group's order, by a person, or on the controller's own path
2026-10-07 21:51 delivering → delivered (done): its walk is done: every machine of its deploy plan passed, or was left as its policy says
The commit's note under refs/notes/mesh-plan keeps every transition: git log --notes=mesh-plan.
<!-- mesh-delivery:view -->
**Delivery** `novox/mesh-catalog@cb733d1b7cea` — **delivered** since 2026-10-07T21:51:25Z
**Delivery plan** — builds records → novox; no bus step
- tier 0: records
- novox: receives records
- records keeps data (ADR 0233): what it holds is backed up before it moves
**Machines**
- systemd on ace: passed — healthy 3 times over 2m25s
- records on novox: passed — healthy 3 times over 2m46s
- systemd on novox: judging — carried by release-1791409555270590919
- systemd on the rest running it: sent
- records on the rest running it: sent
**Transitions**
- 2026-10-07 21:39 (new) → proposed (announced): novox/mesh-catalog#115's head announced
- 2026-10-07 21:41 proposed → checked (checked): the verdict names this commit
- 2026-10-07 21:41 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 → delivering (go): its walk started: let go by this owner in its group's order, by a person, or on the controller's own path
- 2026-10-07 21:51 delivering → delivered (done): its walk is done: every machine of its deploy plan passed, or was left as its policy says
The commit's note under `refs/notes/mesh-plan` keeps every transition: `git log --notes=mesh-plan`.
mesh/merge-gate: PASS — every machine composes with the change as it did without (4 of 4 compose) (modules: records)
mesh/repo-check: PASS — its merge-check.sh passed
Delivery plan — builds records → novox; no bus step
tier 0: records
novox: receives records
records keeps data (ADR 0233): what it holds is backed up before it moves
Run by the build seat on ace as build-1791409160491366791 (builds --log build-1791409160491366791).
--- the gate: records
records: ok, 6 tool(s), keeps checkout (rebuildable)
long-running resources without health: 0
1 manifest(s) checked. Judged against the seats this binary carries; a claim on one of the mesh's own seats is judged fully at registration, and a seat declared by a module not given here reads as unknown. Identities judged on a 6-character machine name, against the bounds of the providers given here
judging 1 module(s) changed against 4 machine(s), as the snapshot of 2026-10-07T21:23:22Z says they run
composing every machine as the mesh is
the bus's user list leaves out 5 user(s) the mesh has minted no credential for: controller, node.f35, node.idt, node.ygcyr, node.yvbpsm. Each is a user that cannot connect until one is issued
the bus's user list leaves out 5 user(s) the mesh has minted no credential for: controller, node.f35, node.idt, node.ygcyr, node.yvbpsm. Each is a user that cannot connect until one is issued
composing every machine with the change
the bus's user list leaves out 5 user(s) the mesh has minted no credential for: controller, node.f35, node.idt, node.ygcyr, node.yvbpsm. Each is a user that cannot connect until one is issued
the bus's user list leaves out 5 user(s) the mesh has minted no credential for: controller, node.f35, node.idt, node.ygcyr, node.yvbpsm. Each is a user that cannot connect until one is issued
merge gate: PASS — every machine composes with the change as it did without (4 of 4 compose)
judged by controller development build against the facts of 2026-10-07T21:23:22Z
modules the change moves:
- records (changed)
machines:
- a machine (f35): composes
- holds mesh-dns-resolver (idt): composes
- holds git, holds mesh-artifact-store, holds mesh-broker, holds mesh-catalog, holds mesh-delivery, holds mesh-dns-resolver, holds mesh-store, holds mesh-vault, holds npm-package-registry, the control node, the hub (ygcyr): composes
- a machine (yvbpsm): composes
a merge would rebuild 1 module(s) in 1 tier(s): records
--- its merge-check.sh (go toolchain)
ok git.novox.be/novox/mesh-catalog/checks/words 0.002s
words: 12 retired words, none in the 28156 strings of 522 files
long-running resources without health: 70, as kept
testing modules/records
ok records/cmd/records 1.231s
**Merge check** at `cb733d1b`
- `mesh/merge-gate`: **PASS** — every machine composes with the change as it did without (4 of 4 compose) (modules: records)
- `mesh/repo-check`: **PASS** — its merge-check.sh passed
**Delivery plan** — builds records → novox; no bus step
- tier 0: records
- novox: receives records
- records keeps data (ADR 0233): what it holds is backed up before it moves
Run by the build seat on ace as `build-1791409160491366791` (`builds --log build-1791409160491366791`).
```
--- the gate: records
records: ok, 6 tool(s), keeps checkout (rebuildable)
long-running resources without health: 0
1 manifest(s) checked. Judged against the seats this binary carries; a claim on one of the mesh's own seats is judged fully at registration, and a seat declared by a module not given here reads as unknown. Identities judged on a 6-character machine name, against the bounds of the providers given here
judging 1 module(s) changed against 4 machine(s), as the snapshot of 2026-10-07T21:23:22Z says they run
composing every machine as the mesh is
the bus's user list leaves out 5 user(s) the mesh has minted no credential for: controller, node.f35, node.idt, node.ygcyr, node.yvbpsm. Each is a user that cannot connect until one is issued
the bus's user list leaves out 5 user(s) the mesh has minted no credential for: controller, node.f35, node.idt, node.ygcyr, node.yvbpsm. Each is a user that cannot connect until one is issued
composing every machine with the change
the bus's user list leaves out 5 user(s) the mesh has minted no credential for: controller, node.f35, node.idt, node.ygcyr, node.yvbpsm. Each is a user that cannot connect until one is issued
the bus's user list leaves out 5 user(s) the mesh has minted no credential for: controller, node.f35, node.idt, node.ygcyr, node.yvbpsm. Each is a user that cannot connect until one is issued
merge gate: PASS — every machine composes with the change as it did without (4 of 4 compose)
judged by controller development build against the facts of 2026-10-07T21:23:22Z
modules the change moves:
- records (changed)
machines:
- a machine (f35): composes
- holds mesh-dns-resolver (idt): composes
- holds git, holds mesh-artifact-store, holds mesh-broker, holds mesh-catalog, holds mesh-delivery, holds mesh-dns-resolver, holds mesh-store, holds mesh-vault, holds npm-package-registry, the control node, the hub (ygcyr): composes
- a machine (yvbpsm): composes
a merge would rebuild 1 module(s) in 1 tier(s): records
--- its merge-check.sh (go toolchain)
ok git.novox.be/novox/mesh-catalog/checks/words 0.002s
words: 12 retired words, none in the 28156 strings of 522 files
long-running resources without health: 70, as kept
testing modules/records
ok records/cmd/records 1.231s
```
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
hq no longer stores the list of decision records in 02-DECISIONS/README.md (hq ADR 0248, issue 297): a stored list made every two open decisions conflict. The list is generated when read.
This adds
records_decisions {topic?}: the records by topic, in the reading order the README writes (one line per topic,1. **Label** —topic: name. ...), each with number, title, path and status, at the commit the answer names. A record whose topic is not in the reading order is returned as unfiled; a README with no reading order, or an unknown topic, is refused with why.Tested: a new test against a repository it makes; and by hand against the hq branch of the companion PR (233 records, 6 topics, none unfiled).
sh merge-check.shpasses locally (no controller beside it, so the manifest step said NOT CHECKED).Companion: novox/hq decision/generated-decisions-index.
Delivery
novox/mesh-catalog@cb733d1b7cea— delivered since 2026-10-07T21:51:25ZDelivery plan — builds records → novox; no bus step
Machines
Transitions
The commit's note under
refs/notes/mesh-plankeeps every transition:git log --notes=mesh-plan.Merge check at
cb733d1bmesh/merge-gate: PASS — every machine composes with the change as it did without (4 of 4 compose) (modules: records)mesh/repo-check: PASS — its merge-check.sh passedDelivery plan — builds records → novox; no bus step
Run by the build seat on ace as
build-1791409160491366791(builds --log build-1791409160491366791).