Fixes novox/hq issue 497 (a knowledge-base review that could not be had seemed lost when the tool runner restarted).
What the live case actually was
The try count was already kept in the store, with the version (judging in the version body), and the background loop reads the store at start and every minute. ADR 0294's history shows try 1 at 16:11:17 UTC; with a 10-minute pause, try 2 was due at 16:21:17. The record was proposed again by hand at 16:20:26, 51 seconds before that. So the restart did not lose the try: nothing said when it was due, and the pause was read as a loss.
What this changes
Judging keeps due, when a failed review is asked again (zero after the last try). The background loop takes it up at that time, also after a restart. A version kept before this change has no due, and falls back to the same pause from its last try.
The history line and get's review say when: not reviewed: ... (try 1 of 3); it stays proposed, and it is asked again at 2026-10-11 16:21 UTC.
After the last try, the history says (try 3 of 3, the last); it stays proposed and nothing of it is in force, the operator is told, and its author proposes it again .... The operator is told once, on seat:operator-channel.notify (the channel the module already uses for drafted clauses), keyed by record and version in the told table. That way a restart does not tell it twice. The module's health keeps naming the record, as before. No schema change: told already takes any key.
A review that could not be had is still never an approval.
Tests
TestAReviewOwedOutlivesARestartAndItsLastTryIsSaid restarts the module (a new KB over the same store) before each try. It checks that each try is not asked early, is taken up when due and is counted in the store. It checks that the history and get say when the next try comes, and that the last try is said and told once, also across a further restart. On main it fails at the history line (no time given) and at the operator being told. The restart and count parts pass on main, because the count was already in the store. Run on memory here, on postgres where the build has one.
go vet ./..., go test -race (all pass), and the words check are clean.
Fixes novox/hq issue 497 (a knowledge-base review that could not be had seemed lost when the tool runner restarted).
## What the live case actually was
The try count was already kept in the store, with the version (`judging` in the version body), and the background loop reads the store at start and every minute. ADR 0294's history shows try 1 at 16:11:17 UTC; with a 10-minute pause, try 2 was due at 16:21:17. The record was proposed again by hand at 16:20:26, 51 seconds before that. So the restart did not lose the try: nothing said when it was due, and the pause was read as a loss.
## What this changes
- `Judging` keeps `due`, when a failed review is asked again (zero after the last try). The background loop takes it up at that time, also after a restart. A version kept before this change has no `due`, and falls back to the same pause from its last try.
- The history line and `get`'s `review` say when: `not reviewed: ... (try 1 of 3); it stays proposed, and it is asked again at 2026-10-11 16:21 UTC`.
- After the last try, the history says `(try 3 of 3, the last); it stays proposed and nothing of it is in force, the operator is told, and its author proposes it again ...`. The operator is told once, on `seat:operator-channel.notify` (the channel the module already uses for drafted clauses), keyed by record and version in the `told` table. That way a restart does not tell it twice. The module's health keeps naming the record, as before. No schema change: `told` already takes any key.
- A review that could not be had is still never an approval.
## Tests
`TestAReviewOwedOutlivesARestartAndItsLastTryIsSaid` restarts the module (a new KB over the same store) before each try. It checks that each try is not asked early, is taken up when due and is counted in the store. It checks that the history and `get` say when the next try comes, and that the last try is said and told once, also across a further restart. On main it fails at the history line (no time given) and at the operator being told. The restart and count parts pass on main, because the count was already in the store. Run on memory here, on postgres where the build has one.
`go vet ./...`, `go test -race` (all pass), and the words check are clean.
A failed review's try count was already kept with the version, but not when it was asked again, so a 10-minute
pause read as a review lost to a restart; and after the last try only the history and the health said so.
Deliverynovox/mesh-catalog@c394ecd9fdc8 — failed since 2026-10-11T18:16:21Z
Covered: covered after its failure: a later walk that contains it was delivered: plan-1791744131193016639 (novox/mesh-catalog at 3fa07682 into main, done, contains its merge 977e7a6f)
Delivery plan — builds mesh-knowledge → novox; no bus step
tier 0: mesh-knowledge
novox: receives mesh-knowledge
Machines
build-agent on ace: passed — carried by plan-1791740991500526659
mesh-knowledge on novox: rolled-back — not healthy within 10m0s of its apply: its process mesh-knowledge.watch on novox fails its tool check
Transitions
2026-10-11 17:41 (new) → proposed (announced): novox/mesh-catalog#219's head announced
2026-10-11 17:46 proposed → checked (checked): the verdict names this commit
2026-10-11 17:46 checked → ready (accepted): the gate passed or warned, and the repository's own check did not fail
2026-10-11 18:05 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:05 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 18:16 delivering → failed (failed): its walk failed, carrying its own commit: a gate on a first machine (what it carried put back), a build, a machine
The commit's note under refs/notes/mesh-plan keeps every transition: git log --notes=mesh-plan.
<!-- mesh-delivery:view -->
**Delivery** `novox/mesh-catalog@c394ecd9fdc8` — **failed** since 2026-10-11T18:16:21Z
**Covered**: covered after its failure: a later walk that contains it was delivered: plan-1791744131193016639 (novox/mesh-catalog at 3fa07682 into main, done, contains its merge 977e7a6f)
**Delivery plan** — builds mesh-knowledge → novox; no bus step
- tier 0: mesh-knowledge
- novox: receives mesh-knowledge
**Machines**
- build-agent on ace: passed — carried by plan-1791740991500526659
- mesh-knowledge on novox: rolled-back — not healthy within 10m0s of its apply: its process mesh-knowledge.watch on novox fails its tool check
**Transitions**
- 2026-10-11 17:41 (new) → proposed (announced): novox/mesh-catalog#219's head announced
- 2026-10-11 17:46 proposed → checked (checked): the verdict names this commit
- 2026-10-11 17:46 checked → ready (accepted): the gate passed or warned, and the repository's own check did not fail
- 2026-10-11 18:05 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:05 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 18:16 delivering → failed (failed): its walk failed, carrying its own commit: a gate on a first machine (what it carried put back), a build, a machine
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: 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/review_owed_test.go
Run by the build seat on g14 as build-1791739488357654029 (builds --log build-1791739488357654029).
--- 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, 2 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-11T17:21:39Z 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-11T17:21:39Z
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 and modules/mesh-knowledge/cmd/mesh-knowledge/review_owed_test.go 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.004s
words: 12 retired words and 70 daemons' lines, none in the 41847 strings of 678 files
ok git.novox.be/novox/mesh-catalog/checks/agenthome 0.009s
agent-home: no archive and no file written into under the agent's home
ok git.novox.be/novox/mesh-catalog/checks/paths 0.005s
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 124.511s
--- its merge-check-typescript.sh (typescript toolchain)
**Merge check** at `9cfb5f9e`
- `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/review_owed_test.go
Run by the build seat on g14 as `build-1791739488357654029` (`builds --log build-1791739488357654029`).
```
--- 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, 2 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-11T17:21:39Z 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-11T17:21:39Z
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 and modules/mesh-knowledge/cmd/mesh-knowledge/review_owed_test.go 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.004s
words: 12 retired words and 70 daemons' lines, none in the 41847 strings of 678 files
ok git.novox.be/novox/mesh-catalog/checks/agenthome 0.009s
agent-home: no archive and no file written into under the agent's home
ok git.novox.be/novox/mesh-catalog/checks/paths 0.005s
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 124.511s
--- its merge-check-typescript.sh (typescript toolchain)
```
A notice left open kept telling the operator a record was proposed and not in force after it was proposed again
or accepted, and a later version's notice merged into it.
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/kit_test.go, modules/mesh-knowledge/cmd/mesh-knowledge/review_owed_test.go
Run by the build seat on ace as build-1791740201264706908 (builds --log build-1791740201264706908).
--- 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, 2 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-11T17:31:39Z 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-11T17:31:39Z
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/kit_test.go and modules/mesh-knowledge/cmd/mesh-knowledge/review_owed_test.go 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 41867 strings of 678 files
ok git.novox.be/novox/mesh-catalog/checks/agenthome 0.010s
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 90.552s
--- its merge-check-typescript.sh (typescript toolchain)
**Merge check** at `d4576167`
- `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/kit_test.go, modules/mesh-knowledge/cmd/mesh-knowledge/review_owed_test.go
Run by the build seat on ace as `build-1791740201264706908` (`builds --log build-1791740201264706908`).
```
--- 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, 2 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-11T17:31:39Z 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-11T17:31:39Z
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/kit_test.go and modules/mesh-knowledge/cmd/mesh-knowledge/review_owed_test.go 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 41867 strings of 678 files
ok git.novox.be/novox/mesh-catalog/checks/agenthome 0.010s
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 90.552s
--- its merge-check-typescript.sh (typescript toolchain)
```
mesh/delivery covered after its failure: a later walk that contains it was delivered: plan-1791744131193016639 (novox/mesh-catalog at 3fa07682 into main,…
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/kit_test.go, modules/mesh-knowledge/cmd/mesh-knowledge/review_owed_test.go
Run by the build seat on g14 as build-1791740509051212635 (builds --log build-1791740509051212635).
--- 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, 2 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-11T17:40:52Z 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-11T17:40:52Z
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/kit_test.go and modules/mesh-knowledge/cmd/mesh-knowledge/review_owed_test.go 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 41871 strings of 678 files
ok git.novox.be/novox/mesh-catalog/checks/agenthome 0.010s
agent-home: no archive and no file written into under the agent's home
ok git.novox.be/novox/mesh-catalog/checks/paths 0.005s
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 124.387s
--- its merge-check-typescript.sh (typescript toolchain)
**Merge check** at `c394ecd9`
- `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/kit_test.go, modules/mesh-knowledge/cmd/mesh-knowledge/review_owed_test.go
Run by the build seat on g14 as `build-1791740509051212635` (`builds --log build-1791740509051212635`).
```
--- 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, 2 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-11T17:40:52Z 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-11T17:40:52Z
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/kit_test.go and modules/mesh-knowledge/cmd/mesh-knowledge/review_owed_test.go 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 41871 strings of 678 files
ok git.novox.be/novox/mesh-catalog/checks/agenthome 0.010s
agent-home: no archive and no file written into under the agent's home
ok git.novox.be/novox/mesh-catalog/checks/paths 0.005s
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 124.387s
--- 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 novox/hq issue 497 (a knowledge-base review that could not be had seemed lost when the tool runner restarted).
What the live case actually was
The try count was already kept in the store, with the version (
judgingin the version body), and the background loop reads the store at start and every minute. ADR 0294's history shows try 1 at 16:11:17 UTC; with a 10-minute pause, try 2 was due at 16:21:17. The record was proposed again by hand at 16:20:26, 51 seconds before that. So the restart did not lose the try: nothing said when it was due, and the pause was read as a loss.What this changes
Judgingkeepsdue, when a failed review is asked again (zero after the last try). The background loop takes it up at that time, also after a restart. A version kept before this change has nodue, and falls back to the same pause from its last try.get'sreviewsay when:not reviewed: ... (try 1 of 3); it stays proposed, and it is asked again at 2026-10-11 16:21 UTC.(try 3 of 3, the last); it stays proposed and nothing of it is in force, the operator is told, and its author proposes it again .... The operator is told once, onseat:operator-channel.notify(the channel the module already uses for drafted clauses), keyed by record and version in thetoldtable. That way a restart does not tell it twice. The module's health keeps naming the record, as before. No schema change:toldalready takes any key.Tests
TestAReviewOwedOutlivesARestartAndItsLastTryIsSaidrestarts the module (a new KB over the same store) before each try. It checks that each try is not asked early, is taken up when due and is counted in the store. It checks that the history andgetsay when the next try comes, and that the last try is said and told once, also across a further restart. On main it fails at the history line (no time given) and at the operator being told. The restart and count parts pass on main, because the count was already in the store. Run on memory here, on postgres where the build has one.go vet ./...,go test -race(all pass), and the words check are clean.Delivery
novox/mesh-catalog@c394ecd9fdc8— failed since 2026-10-11T18:16:21ZCovered: covered after its failure: a later walk that contains it was delivered: plan-1791744131193016639 (novox/mesh-catalog at
3fa07682into main, done, contains its merge977e7a6f)Delivery plan — builds mesh-knowledge → 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
9cfb5f9emesh/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 g14 as
build-1791739488357654029(builds --log build-1791739488357654029).Merge check at
d4576167mesh/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 ace as
build-1791740201264706908(builds --log build-1791740201264706908).Merge check at
c394ecd9mesh/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 g14 as
build-1791740509051212635(builds --log build-1791740509051212635).