reconstructed (true/false, a field of its own), amended (days), research touches (a touches link where it names a decision, research effort, issue or design; text otherwise, in order), rests-on as its own typed link (no longer a cites). get serves them, plus any other frontmatter field under fields.
New link kinds rests-on (decision to decision, held to the rules extends is: per-record rests-on and whole-set rests-on-live) and touches (from a research effort). Design 55 §2's link table names neither; hq needs a progressive insight or amendment there.
Clauses: only from the Decision section's own top-level numbered list with bold leads, never after its first ### subsection (fences respected). Fixtures copied from hq at f08920199d25: ADR 0259, 0272, 0273, 0278, 0288 and also 0040 (0114 and 0148 are the same case; not copied). Each is queued for drafting.
No Decision section (11 records): queued for drafting from what it decides (all sections but preamble, consequences, references); above 48 KiB it is marked no Decision section ... it has no clauses, said by get.
Repair: import with refresh: true re-reads, at the commit, every held record whose every version was written by the import or a refresh (nothing pending) and writes it as a new version refreshed from hq at <commit>: <path>; ... had lost or misread <what>; a record changed since (drafted, accepted over, corrected) is never touched and its row says so; one found the same is left alone, so a second run changes nothing; dry-run lists per record what would change.
Over hq at f08920199d25 (terminal dry-run): written clauses 224 to 196, records to draft 226 to 245. Live, all eight misread records (0040, 0114, 0148, 0259, 0272, 0273, 0278, 0288) are at version 1, so refresh reaches them; the ~226 prose decisions already drafted are not refreshed, so their reconstructed/amended stay unserved in their fields map until a later change.
Tests (fail first on main: the fields do not exist; 0002's reconstructed stayed in Extra before the parse fix): every field held and served (memory + postgres); the six records' clauses; a subsection list and a fence; no-Decision-section drafting from the sections and the too-large mark; refresh over records written as the old import did: dry run writes nothing and names changes, real run repairs 12, skips the drafted 0085, second run changes nothing, a drafted record is later skipped. go test -race ./... ok; merge-check.sh ok.
Merge order: independent of #211 (a test merge of both passes go test -race); either order is fine.
Fixes hq issue 487.
**Held now**
- `reconstructed` (true/false, a field of its own), `amended` (days), research `touches` (a `touches` link where it names a decision, research effort, issue or design; text otherwise, in order), `rests-on` as its own typed link (no longer a `cites`). `get` serves them, plus any other frontmatter field under `fields`.
- New link kinds `rests-on` (decision to decision, held to the rules `extends` is: per-record `rests-on` and whole-set `rests-on-live`) and `touches` (from a research effort). **Design 55 §2's link table names neither; hq needs a progressive insight or amendment there.**
**Clauses**: only from the Decision section's own top-level numbered list with bold leads, never after its first `###` subsection (fences respected). Fixtures copied from hq at f08920199d25: ADR 0259, 0272, 0273, 0278, 0288 and also 0040 (0114 and 0148 are the same case; not copied). Each is queued for drafting.
**No Decision section** (11 records): queued for drafting from what it decides (all sections but preamble, consequences, references); above 48 KiB it is marked `no Decision section ... it has no clauses`, said by `get`.
**Repair**: `import` with `refresh: true` re-reads, at the commit, every held record whose every version was written by the import or a refresh (nothing pending) and writes it as a new version `refreshed from hq at <commit>: <path>; ... had lost or misread <what>`; a record changed since (drafted, accepted over, corrected) is never touched and its row says so; one found the same is left alone, so a second run changes nothing; dry-run lists per record what would change.
Over hq at f08920199d25 (terminal dry-run): written clauses 224 to 196, records to draft 226 to 245. Live, all eight misread records (0040, 0114, 0148, 0259, 0272, 0273, 0278, 0288) are at version 1, so refresh reaches them; the ~226 prose decisions already drafted are not refreshed, so their `reconstructed`/`amended` stay unserved in their fields map until a later change.
**Tests** (fail first on main: the fields do not exist; 0002's `reconstructed` stayed in Extra before the parse fix): every field held and served (memory + postgres); the six records' clauses; a subsection list and a fence; no-Decision-section drafting from the sections and the too-large mark; refresh over records written as the old import did: dry run writes nothing and names changes, real run repairs 12, skips the drafted 0085, second run changes nothing, a drafted record is later skipped. `go test -race ./...` ok; `merge-check.sh` ok.
Merge order: independent of #211 (a test merge of both passes `go test -race`); either order is fine.
The import at hq f0892019 lost reconstructed, amended and a research effort's touches, held rests-on only as a
citation, took eight records' clauses from a numbered list inside a ### subsection, and left the 11 records with
no Decision section clause-less with nothing queued. Each is held now; refresh repairs a record only the import
ever wrote, and never one changed since.
Deliverynovox/mesh-catalog@156fda4b33d3 — covered since 2026-10-11T11:02:39Z
Delivery plan — builds mesh-knowledge → novox; no bus step
tier 0: mesh-knowledge
novox: receives mesh-knowledge
Machines
mesh-issues on novox: passed — healthy 3 times over 3m44s
mesh-knowledge on novox: passed — judged with mesh-issues: healthy 3 times over 3m44s
records on novox: passed — judged with mesh-issues: healthy 3 times over 3m44s
mesh-issues on the rest running it: sent
mesh-knowledge on the rest running it: sent
records on the rest running it: sent
Transitions
2026-10-11 10:44 (new) → proposed (announced): novox/mesh-catalog#213's head announced
2026-10-11 10:48 proposed → checked (checked): the verdict names this commit
2026-10-11 10:48 checked → ready (accepted): the gate passed or warned, and the repository's own check did not fail
2026-10-11 10:57 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 10:57 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 — not a failed walk that carried a later commit for it, after which it waits for a walk of its own commit
2026-10-11 11:02 delivering → covered (covered): covered: a later merge that contains it was delivered: novox/mesh-catalog@1b7f79f761 (merged as 73367192 into main, walk plan-1791716118369094536)
The commit's note under refs/notes/mesh-plan keeps every transition: git log --notes=mesh-plan.
<!-- mesh-delivery:view -->
**Delivery** `novox/mesh-catalog@156fda4b33d3` — **covered** since 2026-10-11T11:02:39Z
**Delivery plan** — builds mesh-knowledge → novox; no bus step
- tier 0: mesh-knowledge
- novox: receives mesh-knowledge
**Machines**
- mesh-issues on novox: passed — healthy 3 times over 3m44s
- mesh-knowledge on novox: passed — judged with mesh-issues: healthy 3 times over 3m44s
- records on novox: passed — judged with mesh-issues: healthy 3 times over 3m44s
- mesh-issues on the rest running it: sent
- mesh-knowledge on the rest running it: sent
- records on the rest running it: sent
**Transitions**
- 2026-10-11 10:44 (new) → proposed (announced): novox/mesh-catalog#213's head announced
- 2026-10-11 10:48 proposed → checked (checked): the verdict names this commit
- 2026-10-11 10:48 checked → ready (accepted): the gate passed or warned, and the repository's own check did not fail
- 2026-10-11 10:57 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 10:57 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 — not a failed walk that carried a later commit for it, after which it waits for a walk of its own commit
- 2026-10-11 11:02 delivering → covered (covered): covered: a later merge that contains it was delivered: novox/mesh-catalog@1b7f79f76177 (merged as 73367192 into main, walk plan-1791716118369094536)
The commit's note under `refs/notes/mesh-plan` keeps every transition: `git log --notes=mesh-plan`.
Run by the build seat on shanks as build-1791714017803049228 (builds --log build-1791714017803049228).
--- the gate: mesh-knowledge
note: mesh-knowledge uses the seat "operator-channel", which no module declares and the mesh does not define among the manifests given; registration judges it against the whole catalogue, and passing the declaring module's manifest too judges it here
mesh-knowledge: ok, 1 tool(s), invokes seat:issue-tracker.reserve, claude-code.claude_code_judge, records.records_status, records.records_list, records.records_read, seat:operator-channel.notify, ready: keep by unit every 30s; watch by its tool knowledge_health every 1m0s
long-running resources without health: 0
files asking for a setting without saying whether it is trusted: 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 0 module(s) changed against 4 machine(s), as the snapshot of 2026-10-11T10:15:21Z 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-11T10:15:21Z
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): mesh-knowledge
notes:
- modules/mesh-knowledge/README.md, modules/mesh-knowledge/cmd/mesh-knowledge/fields_test.go, modules/mesh-knowledge/cmd/mesh-knowledge/kit_test.go, modules/mesh-knowledge/cmd/mesh-knowledge/testdata/hq-f0892019/01-RESEARCH/021-finding-a-tool-in-the-mesh/00-overview.md, modules/mesh-knowledge/cmd/mesh-knowledge/testdata/hq-f0892019/01-RESEARCH/030-backups-against-our-own-mistakes/00-overview.md, modules/mesh-knowledge/cmd/mesh-knowledge/testdata/hq-f0892019/01-RESEARCH/030-backups-against-our-own-mistakes/01-what-the-mesh-holds.md, modules/mesh-knowledge/cmd/mesh-knowledge/testdata/hq-f0892019/01-RESEARCH/030-backups-against-our-own-mistakes/02-options-and-proposal.md, modules/mesh-knowledge/cmd/mesh-knowledge/testdata/hq-f0892019/02-DECISIONS/0002-nodes-communicate-over-a-broker.md, modules/mesh-knowledge/cmd/mesh-knowledge/testdata/hq-f0892019/02-DECISIONS/0004-a-node-and-how-it-joins.md, modules/mesh-knowledge/cmd/mesh-knowledge/testdata/hq-f0892019/02-DECISIONS/0037-where-a-module-lives.md, modules/mesh-knowledge/cmd/mesh-knowledge/testdata/hq-f0892019/02-DECISIONS/0038-the-mesh-assigns-the-port.md, modules/mesh-knowledge/cmd/mesh-knowledge/testdata/hq-f0892019/02-DECISIONS/0040-what-a-module-is.md, modules/mesh-knowledge/cmd/mesh-knowledge/testdata/hq-f0892019/02-DECISIONS/0085-a-secret-is-a-provision.md, modules/mesh-knowledge/cmd/mesh-knowledge/testdata/hq-f0892019/02-DECISIONS/0259-an-ask-is-a-message-on-the-bus-any-channel-answers-it-and-the-asker-acts-on-a-warrant.md, modules/mesh-knowledge/cmd/mesh-knowledge/testdata/hq-f0892019/02-DECISIONS/0272-the-operator-reaches-the-controller-with-mesh-cli-on-every-node-and-a-node-is-the-terminal-only-where-no-agent-runs-as-its-operator.md, modules/mesh-knowledge/cmd/mesh-knowledge/testdata/hq-f0892019/02-DECISIONS/0273-the-agents-home-is-the-modules-and-the-operators-personal-rules-and-lessons-are-registered-through-it.md, modules/mesh-knowledge/cmd/mesh-knowledge/testdata/hq-f0892019/02-DECISIONS/0278-the-issue-tracker-checks-every-new-issue-for-a-duplicate-through-a-judgement-the-agent-makes-without-tools.md, modules/mesh-knowledge/cmd/mesh-knowledge/testdata/hq-f0892019/02-DECISIONS/0288-the-object-store-stays-on-the-maintained-fork-and-garage-is-chosen-only-after-the-consumers-s3-features-are-counted.md and modules/mesh-knowledge/cmd/mesh-knowledge/testdata/hq-f0892019/COMMIT read by no module's build, and rebuild nothing (issue 280)
--- its merge-check.sh (go toolchain)
ok git.novox.be/novox/mesh-catalog/checks/words 0.003s
words: 12 retired words and 70 daemons' lines, none in the 41546 strings of 672 files
ok git.novox.be/novox/mesh-catalog/checks/agenthome 0.012s
agent-home: no archive and no file written into under the agent's home
ok git.novox.be/novox/mesh-catalog/checks/paths 0.006s
paths: no module names another's state on its machine (3 known, listed to go)
long-running resources without health: 69, as kept
testing modules/mesh-knowledge
ok mesh-knowledge/cmd/mesh-knowledge 101.036s
--- its merge-check-typescript.sh (typescript toolchain)
**Merge check** at `1cc0ab36`
- `mesh/merge-gate`: **PASS** — every machine composes with the change as it did without (4 of 4 compose) (modules: mesh-knowledge)
- `mesh/repo-check`: **PASS** — its merge-check.sh passed, each part in its toolchain: merge-check.sh (go), merge-check-typescript.sh (typescript)
**Delivery plan** — builds mesh-knowledge → novox; no bus step
- tier 0: mesh-knowledge
- novox: receives mesh-knowledge
- read by no module's build: modules/mesh-knowledge/README.md, modules/mesh-knowledge/cmd/mesh-knowledge/fields_test.go, modules/mesh-knowledge/cmd/mesh-knowledge/kit_test.go, modules/mesh-knowledge/cmd/mesh-knowledge/testdata/hq-f0892019/01-RESEARCH/021-finding-a-tool-in-the-mesh/00-overview.md, modules/mesh-knowledge/cmd/mesh-knowledge/testdata/hq-f0892019/01-RESEARCH/030-backups-against-our-own-mistakes/00-overview.md, modules/mesh-knowledge/cmd/mesh-knowledge/testdata/hq-f0892019/01-RESEARCH/030-backups-against-our-own-mistakes/01-what-the-mesh-holds.md, modules/mesh-knowledge/cmd/mesh-knowledge/testdata/hq-f0892019/01-RESEARCH/030-backups-against-our-own-mistakes/02-options-and-proposal.md, modules/mesh-knowledge/cmd/mesh-knowledge/testdata/hq-f0892019/02-DECISIONS/0002-nodes-communicate-over-a-broker.md, modules/mesh-knowledge/cmd/mesh-knowledge/testdata/hq-f0892019/02-DECISIONS/0004-a-node-and-how-it-joins.md, modules/mesh-knowledge/cmd/mesh-knowledge/testdata/hq-f0892019/02-DECISIONS/0037-where-a-module-lives.md, modules/mesh-knowledge/cmd/mesh-knowledge/testdata/hq-f0892019/02-DECISIONS/0038-the-mesh-assigns-the-port.md, modules/mesh-knowledge/cmd/mesh-knowledge/testdata/hq-f0892019/02-DECISIONS/0040-what-a-module-is.md, modules/mesh-knowledge/cmd/mesh-knowledge/testdata/hq-f0892019/02-DECISIONS/0085-a-secret-is-a-provision.md, modules/mesh-knowledge/cmd/mesh-knowledge/testdata/hq-f0892019/02-DECISIONS/0259-an-ask-is-a-message-on-the-bus-any-channel-answers-it-and-the-asker-acts-on-a-warrant.md, modules/mesh-knowledge/cmd/mesh-knowledge/testdata/hq-f0892019/02-DECISIONS/0272-the-operator-reaches-the-controller-with-mesh-cli-on-every-node-and-a-node-is-the-terminal-only-where-no-agent-runs-as-its-operator.md, modules/mesh-knowledge/cmd/mesh-knowledge/testdata/hq-f0892019/02-DECISIONS/0273-the-agents-home-is-the-modules-and-the-operators-personal-rules-and-lessons-are-registered-through-it.md, modules/mesh-knowledge/cmd/mesh-knowledge/testdata/hq-f0892019/02-DECISIONS/0278-the-issue-tracker-checks-every-new-issue-for-a-duplicate-through-a-judgement-the-agent-makes-without-tools.md, modules/mesh-knowledge/cmd/mesh-knowledge/testdata/hq-f0892019/02-DECISIONS/0288-the-object-store-stays-on-the-maintained-fork-and-garage-is-chosen-only-after-the-consumers-s3-features-are-counted.md, modules/mesh-knowledge/cmd/mesh-knowledge/testdata/hq-f0892019/COMMIT
Run by the build seat on shanks as `build-1791714017803049228` (`builds --log build-1791714017803049228`).
```
--- the gate: mesh-knowledge
note: mesh-knowledge uses the seat "operator-channel", which no module declares and the mesh does not define among the manifests given; registration judges it against the whole catalogue, and passing the declaring module's manifest too judges it here
mesh-knowledge: ok, 1 tool(s), invokes seat:issue-tracker.reserve, claude-code.claude_code_judge, records.records_status, records.records_list, records.records_read, seat:operator-channel.notify, ready: keep by unit every 30s; watch by its tool knowledge_health every 1m0s
long-running resources without health: 0
files asking for a setting without saying whether it is trusted: 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 0 module(s) changed against 4 machine(s), as the snapshot of 2026-10-11T10:15:21Z 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-11T10:15:21Z
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): mesh-knowledge
notes:
- modules/mesh-knowledge/README.md, modules/mesh-knowledge/cmd/mesh-knowledge/fields_test.go, modules/mesh-knowledge/cmd/mesh-knowledge/kit_test.go, modules/mesh-knowledge/cmd/mesh-knowledge/testdata/hq-f0892019/01-RESEARCH/021-finding-a-tool-in-the-mesh/00-overview.md, modules/mesh-knowledge/cmd/mesh-knowledge/testdata/hq-f0892019/01-RESEARCH/030-backups-against-our-own-mistakes/00-overview.md, modules/mesh-knowledge/cmd/mesh-knowledge/testdata/hq-f0892019/01-RESEARCH/030-backups-against-our-own-mistakes/01-what-the-mesh-holds.md, modules/mesh-knowledge/cmd/mesh-knowledge/testdata/hq-f0892019/01-RESEARCH/030-backups-against-our-own-mistakes/02-options-and-proposal.md, modules/mesh-knowledge/cmd/mesh-knowledge/testdata/hq-f0892019/02-DECISIONS/0002-nodes-communicate-over-a-broker.md, modules/mesh-knowledge/cmd/mesh-knowledge/testdata/hq-f0892019/02-DECISIONS/0004-a-node-and-how-it-joins.md, modules/mesh-knowledge/cmd/mesh-knowledge/testdata/hq-f0892019/02-DECISIONS/0037-where-a-module-lives.md, modules/mesh-knowledge/cmd/mesh-knowledge/testdata/hq-f0892019/02-DECISIONS/0038-the-mesh-assigns-the-port.md, modules/mesh-knowledge/cmd/mesh-knowledge/testdata/hq-f0892019/02-DECISIONS/0040-what-a-module-is.md, modules/mesh-knowledge/cmd/mesh-knowledge/testdata/hq-f0892019/02-DECISIONS/0085-a-secret-is-a-provision.md, modules/mesh-knowledge/cmd/mesh-knowledge/testdata/hq-f0892019/02-DECISIONS/0259-an-ask-is-a-message-on-the-bus-any-channel-answers-it-and-the-asker-acts-on-a-warrant.md, modules/mesh-knowledge/cmd/mesh-knowledge/testdata/hq-f0892019/02-DECISIONS/0272-the-operator-reaches-the-controller-with-mesh-cli-on-every-node-and-a-node-is-the-terminal-only-where-no-agent-runs-as-its-operator.md, modules/mesh-knowledge/cmd/mesh-knowledge/testdata/hq-f0892019/02-DECISIONS/0273-the-agents-home-is-the-modules-and-the-operators-personal-rules-and-lessons-are-registered-through-it.md, modules/mesh-knowledge/cmd/mesh-knowledge/testdata/hq-f0892019/02-DECISIONS/0278-the-issue-tracker-checks-every-new-issue-for-a-duplicate-through-a-judgement-the-agent-makes-without-tools.md, modules/mesh-knowledge/cmd/mesh-knowledge/testdata/hq-f0892019/02-DECISIONS/0288-the-object-store-stays-on-the-maintained-fork-and-garage-is-chosen-only-after-the-consumers-s3-features-are-counted.md and modules/mesh-knowledge/cmd/mesh-knowledge/testdata/hq-f0892019/COMMIT read by no module's build, and rebuild nothing (issue 280)
--- its merge-check.sh (go toolchain)
ok git.novox.be/novox/mesh-catalog/checks/words 0.003s
words: 12 retired words and 70 daemons' lines, none in the 41546 strings of 672 files
ok git.novox.be/novox/mesh-catalog/checks/agenthome 0.012s
agent-home: no archive and no file written into under the agent's home
ok git.novox.be/novox/mesh-catalog/checks/paths 0.006s
paths: no module names another's state on its machine (3 known, listed to go)
long-running resources without health: 69, as kept
testing modules/mesh-knowledge
ok mesh-knowledge/cmd/mesh-knowledge 101.036s
--- its merge-check-typescript.sh (typescript toolchain)
```
mesh/delivery covered: a later merge that contains it was delivered: novox/mesh-catalog@1b7f79f76177 (merged as 73367192 into main, walk plan-17917161183…
Run by the build seat on shanks as build-1791715470091571643 (builds --log build-1791715470091571643).
--- the gate: mesh-knowledge
note: mesh-knowledge uses the seat "operator-channel", which no module declares and the mesh does not define among the manifests given; registration judges it against the whole catalogue, and passing the declaring module's manifest too judges it here
mesh-knowledge: ok, 1 tool(s), invokes seat:issue-tracker.reserve, claude-code.claude_code_judge, records.records_status, records.records_list, records.records_read, seat:operator-channel.notify, ready: keep by unit every 30s; watch by its tool knowledge_health every 1m0s
long-running resources without health: 0
files asking for a setting without saying whether it is trusted: 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 0 module(s) changed against 4 machine(s), as the snapshot of 2026-10-11T10:42:35Z 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-11T10:42:35Z
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): mesh-knowledge
notes:
- modules/mesh-knowledge/README.md, modules/mesh-knowledge/cmd/mesh-knowledge/fields_test.go, modules/mesh-knowledge/cmd/mesh-knowledge/kit_test.go, modules/mesh-knowledge/cmd/mesh-knowledge/testdata/hq-f0892019/01-RESEARCH/021-finding-a-tool-in-the-mesh/00-overview.md, modules/mesh-knowledge/cmd/mesh-knowledge/testdata/hq-f0892019/01-RESEARCH/030-backups-against-our-own-mistakes/00-overview.md, modules/mesh-knowledge/cmd/mesh-knowledge/testdata/hq-f0892019/01-RESEARCH/030-backups-against-our-own-mistakes/01-what-the-mesh-holds.md, modules/mesh-knowledge/cmd/mesh-knowledge/testdata/hq-f0892019/01-RESEARCH/030-backups-against-our-own-mistakes/02-options-and-proposal.md, modules/mesh-knowledge/cmd/mesh-knowledge/testdata/hq-f0892019/02-DECISIONS/0002-nodes-communicate-over-a-broker.md, modules/mesh-knowledge/cmd/mesh-knowledge/testdata/hq-f0892019/02-DECISIONS/0004-a-node-and-how-it-joins.md, modules/mesh-knowledge/cmd/mesh-knowledge/testdata/hq-f0892019/02-DECISIONS/0037-where-a-module-lives.md, modules/mesh-knowledge/cmd/mesh-knowledge/testdata/hq-f0892019/02-DECISIONS/0038-the-mesh-assigns-the-port.md, modules/mesh-knowledge/cmd/mesh-knowledge/testdata/hq-f0892019/02-DECISIONS/0040-what-a-module-is.md, modules/mesh-knowledge/cmd/mesh-knowledge/testdata/hq-f0892019/02-DECISIONS/0085-a-secret-is-a-provision.md, modules/mesh-knowledge/cmd/mesh-knowledge/testdata/hq-f0892019/02-DECISIONS/0114-a-shared-credential-rotates-over-two-credentials.md, modules/mesh-knowledge/cmd/mesh-knowledge/testdata/hq-f0892019/02-DECISIONS/0148-the-meshs-names-are-resolved-not-copied-into-containers.md, modules/mesh-knowledge/cmd/mesh-knowledge/testdata/hq-f0892019/02-DECISIONS/0259-an-ask-is-a-message-on-the-bus-any-channel-answers-it-and-the-asker-acts-on-a-warrant.md, modules/mesh-knowledge/cmd/mesh-knowledge/testdata/hq-f0892019/02-DECISIONS/0272-the-operator-reaches-the-controller-with-mesh-cli-on-every-node-and-a-node-is-the-terminal-only-where-no-agent-runs-as-its-operator.md, modules/mesh-knowledge/cmd/mesh-knowledge/testdata/hq-f0892019/02-DECISIONS/0273-the-agents-home-is-the-modules-and-the-operators-personal-rules-and-lessons-are-registered-through-it.md, modules/mesh-knowledge/cmd/mesh-knowledge/testdata/hq-f0892019/02-DECISIONS/0278-the-issue-tracker-checks-every-new-issue-for-a-duplicate-through-a-judgement-the-agent-makes-without-tools.md, modules/mesh-knowledge/cmd/mesh-knowledge/testdata/hq-f0892019/02-DECISIONS/0288-the-object-store-stays-on-the-maintained-fork-and-garage-is-chosen-only-after-the-consumers-s3-features-are-counted.md and modules/mesh-knowledge/cmd/mesh-knowledge/testdata/hq-f0892019/COMMIT read by no module's build, and rebuild nothing (issue 280)
--- its merge-check.sh (go toolchain)
ok git.novox.be/novox/mesh-catalog/checks/words 0.003s
words: 12 retired words and 70 daemons' lines, none in the 41549 strings of 672 files
ok git.novox.be/novox/mesh-catalog/checks/agenthome 0.012s
agent-home: no archive and no file written into under the agent's home
ok git.novox.be/novox/mesh-catalog/checks/paths 0.006s
paths: no module names another's state on its machine (3 known, listed to go)
long-running resources without health: 69, as kept
testing modules/mesh-knowledge
ok mesh-knowledge/cmd/mesh-knowledge 102.941s
--- its merge-check-typescript.sh (typescript toolchain)
**Merge check** at `156fda4b`
- `mesh/merge-gate`: **PASS** — every machine composes with the change as it did without (4 of 4 compose) (modules: mesh-knowledge)
- `mesh/repo-check`: **PASS** — its merge-check.sh passed, each part in its toolchain: merge-check.sh (go), merge-check-typescript.sh (typescript)
**Delivery plan** — builds mesh-knowledge → novox; no bus step
- tier 0: mesh-knowledge
- novox: receives mesh-knowledge
- read by no module's build: modules/mesh-knowledge/README.md, modules/mesh-knowledge/cmd/mesh-knowledge/fields_test.go, modules/mesh-knowledge/cmd/mesh-knowledge/kit_test.go, modules/mesh-knowledge/cmd/mesh-knowledge/testdata/hq-f0892019/01-RESEARCH/021-finding-a-tool-in-the-mesh/00-overview.md, modules/mesh-knowledge/cmd/mesh-knowledge/testdata/hq-f0892019/01-RESEARCH/030-backups-against-our-own-mistakes/00-overview.md, modules/mesh-knowledge/cmd/mesh-knowledge/testdata/hq-f0892019/01-RESEARCH/030-backups-against-our-own-mistakes/01-what-the-mesh-holds.md, modules/mesh-knowledge/cmd/mesh-knowledge/testdata/hq-f0892019/01-RESEARCH/030-backups-against-our-own-mistakes/02-options-and-proposal.md, modules/mesh-knowledge/cmd/mesh-knowledge/testdata/hq-f0892019/02-DECISIONS/0002-nodes-communicate-over-a-broker.md, modules/mesh-knowledge/cmd/mesh-knowledge/testdata/hq-f0892019/02-DECISIONS/0004-a-node-and-how-it-joins.md, modules/mesh-knowledge/cmd/mesh-knowledge/testdata/hq-f0892019/02-DECISIONS/0037-where-a-module-lives.md, modules/mesh-knowledge/cmd/mesh-knowledge/testdata/hq-f0892019/02-DECISIONS/0038-the-mesh-assigns-the-port.md, modules/mesh-knowledge/cmd/mesh-knowledge/testdata/hq-f0892019/02-DECISIONS/0040-what-a-module-is.md, modules/mesh-knowledge/cmd/mesh-knowledge/testdata/hq-f0892019/02-DECISIONS/0085-a-secret-is-a-provision.md, modules/mesh-knowledge/cmd/mesh-knowledge/testdata/hq-f0892019/02-DECISIONS/0114-a-shared-credential-rotates-over-two-credentials.md, modules/mesh-knowledge/cmd/mesh-knowledge/testdata/hq-f0892019/02-DECISIONS/0148-the-meshs-names-are-resolved-not-copied-into-containers.md, modules/mesh-knowledge/cmd/mesh-knowledge/testdata/hq-f0892019/02-DECISIONS/0259-an-ask-is-a-message-on-the-bus-any-channel-answers-it-and-the-asker-acts-on-a-warrant.md, modules/mesh-knowledge/cmd/mesh-knowledge/testdata/hq-f0892019/02-DECISIONS/0272-the-operator-reaches-the-controller-with-mesh-cli-on-every-node-and-a-node-is-the-terminal-only-where-no-agent-runs-as-its-operator.md, modules/mesh-knowledge/cmd/mesh-knowledge/testdata/hq-f0892019/02-DECISIONS/0273-the-agents-home-is-the-modules-and-the-operators-personal-rules-and-lessons-are-registered-through-it.md, modules/mesh-knowledge/cmd/mesh-knowledge/testdata/hq-f0892019/02-DECISIONS/0278-the-issue-tracker-checks-every-new-issue-for-a-duplicate-through-a-judgement-the-agent-makes-without-tools.md, modules/mesh-knowledge/cmd/mesh-knowledge/testdata/hq-f0892019/02-DECISIONS/0288-the-object-store-stays-on-the-maintained-fork-and-garage-is-chosen-only-after-the-consumers-s3-features-are-counted.md, modules/mesh-knowledge/cmd/mesh-knowledge/testdata/hq-f0892019/COMMIT
Run by the build seat on shanks as `build-1791715470091571643` (`builds --log build-1791715470091571643`).
```
--- the gate: mesh-knowledge
note: mesh-knowledge uses the seat "operator-channel", which no module declares and the mesh does not define among the manifests given; registration judges it against the whole catalogue, and passing the declaring module's manifest too judges it here
mesh-knowledge: ok, 1 tool(s), invokes seat:issue-tracker.reserve, claude-code.claude_code_judge, records.records_status, records.records_list, records.records_read, seat:operator-channel.notify, ready: keep by unit every 30s; watch by its tool knowledge_health every 1m0s
long-running resources without health: 0
files asking for a setting without saying whether it is trusted: 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 0 module(s) changed against 4 machine(s), as the snapshot of 2026-10-11T10:42:35Z 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-11T10:42:35Z
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): mesh-knowledge
notes:
- modules/mesh-knowledge/README.md, modules/mesh-knowledge/cmd/mesh-knowledge/fields_test.go, modules/mesh-knowledge/cmd/mesh-knowledge/kit_test.go, modules/mesh-knowledge/cmd/mesh-knowledge/testdata/hq-f0892019/01-RESEARCH/021-finding-a-tool-in-the-mesh/00-overview.md, modules/mesh-knowledge/cmd/mesh-knowledge/testdata/hq-f0892019/01-RESEARCH/030-backups-against-our-own-mistakes/00-overview.md, modules/mesh-knowledge/cmd/mesh-knowledge/testdata/hq-f0892019/01-RESEARCH/030-backups-against-our-own-mistakes/01-what-the-mesh-holds.md, modules/mesh-knowledge/cmd/mesh-knowledge/testdata/hq-f0892019/01-RESEARCH/030-backups-against-our-own-mistakes/02-options-and-proposal.md, modules/mesh-knowledge/cmd/mesh-knowledge/testdata/hq-f0892019/02-DECISIONS/0002-nodes-communicate-over-a-broker.md, modules/mesh-knowledge/cmd/mesh-knowledge/testdata/hq-f0892019/02-DECISIONS/0004-a-node-and-how-it-joins.md, modules/mesh-knowledge/cmd/mesh-knowledge/testdata/hq-f0892019/02-DECISIONS/0037-where-a-module-lives.md, modules/mesh-knowledge/cmd/mesh-knowledge/testdata/hq-f0892019/02-DECISIONS/0038-the-mesh-assigns-the-port.md, modules/mesh-knowledge/cmd/mesh-knowledge/testdata/hq-f0892019/02-DECISIONS/0040-what-a-module-is.md, modules/mesh-knowledge/cmd/mesh-knowledge/testdata/hq-f0892019/02-DECISIONS/0085-a-secret-is-a-provision.md, modules/mesh-knowledge/cmd/mesh-knowledge/testdata/hq-f0892019/02-DECISIONS/0114-a-shared-credential-rotates-over-two-credentials.md, modules/mesh-knowledge/cmd/mesh-knowledge/testdata/hq-f0892019/02-DECISIONS/0148-the-meshs-names-are-resolved-not-copied-into-containers.md, modules/mesh-knowledge/cmd/mesh-knowledge/testdata/hq-f0892019/02-DECISIONS/0259-an-ask-is-a-message-on-the-bus-any-channel-answers-it-and-the-asker-acts-on-a-warrant.md, modules/mesh-knowledge/cmd/mesh-knowledge/testdata/hq-f0892019/02-DECISIONS/0272-the-operator-reaches-the-controller-with-mesh-cli-on-every-node-and-a-node-is-the-terminal-only-where-no-agent-runs-as-its-operator.md, modules/mesh-knowledge/cmd/mesh-knowledge/testdata/hq-f0892019/02-DECISIONS/0273-the-agents-home-is-the-modules-and-the-operators-personal-rules-and-lessons-are-registered-through-it.md, modules/mesh-knowledge/cmd/mesh-knowledge/testdata/hq-f0892019/02-DECISIONS/0278-the-issue-tracker-checks-every-new-issue-for-a-duplicate-through-a-judgement-the-agent-makes-without-tools.md, modules/mesh-knowledge/cmd/mesh-knowledge/testdata/hq-f0892019/02-DECISIONS/0288-the-object-store-stays-on-the-maintained-fork-and-garage-is-chosen-only-after-the-consumers-s3-features-are-counted.md and modules/mesh-knowledge/cmd/mesh-knowledge/testdata/hq-f0892019/COMMIT read by no module's build, and rebuild nothing (issue 280)
--- its merge-check.sh (go toolchain)
ok git.novox.be/novox/mesh-catalog/checks/words 0.003s
words: 12 retired words and 70 daemons' lines, none in the 41549 strings of 672 files
ok git.novox.be/novox/mesh-catalog/checks/agenthome 0.012s
agent-home: no archive and no file written into under the agent's home
ok git.novox.be/novox/mesh-catalog/checks/paths 0.006s
paths: no module names another's state on its machine (3 known, listed to go)
long-running resources without health: 69, as kept
testing modules/mesh-knowledge
ok mesh-knowledge/cmd/mesh-knowledge 102.941s
--- its merge-check-typescript.sh (typescript toolchain)
```
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.
Fixes hq issue 487.
Held now
reconstructed(true/false, a field of its own),amended(days), researchtouches(atoucheslink where it names a decision, research effort, issue or design; text otherwise, in order),rests-onas its own typed link (no longer acites).getserves them, plus any other frontmatter field underfields.rests-on(decision to decision, held to the rulesextendsis: per-recordrests-onand whole-setrests-on-live) andtouches(from a research effort). Design 55 §2's link table names neither; hq needs a progressive insight or amendment there.Clauses: only from the Decision section's own top-level numbered list with bold leads, never after its first
###subsection (fences respected). Fixtures copied from hq at f08920199d25: ADR 0259, 0272, 0273, 0278, 0288 and also 0040 (0114 and 0148 are the same case; not copied). Each is queued for drafting.No Decision section (11 records): queued for drafting from what it decides (all sections but preamble, consequences, references); above 48 KiB it is marked
no Decision section ... it has no clauses, said byget.Repair:
importwithrefresh: truere-reads, at the commit, every held record whose every version was written by the import or a refresh (nothing pending) and writes it as a new versionrefreshed from hq at <commit>: <path>; ... had lost or misread <what>; a record changed since (drafted, accepted over, corrected) is never touched and its row says so; one found the same is left alone, so a second run changes nothing; dry-run lists per record what would change.Over hq at f08920199d25 (terminal dry-run): written clauses 224 to 196, records to draft 226 to 245. Live, all eight misread records (0040, 0114, 0148, 0259, 0272, 0273, 0278, 0288) are at version 1, so refresh reaches them; the ~226 prose decisions already drafted are not refreshed, so their
reconstructed/amendedstay unserved in their fields map until a later change.Tests (fail first on main: the fields do not exist; 0002's
reconstructedstayed in Extra before the parse fix): every field held and served (memory + postgres); the six records' clauses; a subsection list and a fence; no-Decision-section drafting from the sections and the too-large mark; refresh over records written as the old import did: dry run writes nothing and names changes, real run repairs 12, skips the drafted 0085, second run changes nothing, a drafted record is later skipped.go test -race ./...ok;merge-check.shok.Merge order: independent of #211 (a test merge of both passes
go test -race); either order is fine.Delivery
novox/mesh-catalog@156fda4b33d3— covered since 2026-10-11T11:02:39ZDelivery plan — builds mesh-knowledge → novox; no bus step
Machines
Transitions
73367192into main, walk plan-1791716118369094536)The commit's note under
refs/notes/mesh-plankeeps every transition:git log --notes=mesh-plan.Merge check at
1cc0ab36mesh/merge-gate: PASS — every machine composes with the change as it did without (4 of 4 compose) (modules: mesh-knowledge)mesh/repo-check: PASS — its merge-check.sh passed, each part in its toolchain: merge-check.sh (go), merge-check-typescript.sh (typescript)Delivery plan — builds mesh-knowledge → novox; no bus step
Run by the build seat on shanks as
build-1791714017803049228(builds --log build-1791714017803049228).Merge check at
156fda4bmesh/merge-gate: PASS — every machine composes with the change as it did without (4 of 4 compose) (modules: mesh-knowledge)mesh/repo-check: PASS — its merge-check.sh passed, each part in its toolchain: merge-check.sh (go), merge-check-typescript.sh (typescript)Delivery plan — builds mesh-knowledge → novox; no bus step
Run by the build seat on shanks as
build-1791715470091571643(builds --log build-1791715470091571643).