Fixes hq issue 425 as ADR 0290 and to-be 55 §5 now say (updated 2026-10-11): the knowledge base reviews a proposal itself.
What changed
Every version proposed (a new record, a revision, a progressive insight) is marked due for review. The background work (woken at once by propose, a review always before the next drafting step) asks claude-code.claude_code_judge one question with no tools that holds only the record, the records it links and the rules, answering approve or changes with findings (review.go).
changes: stays proposed, findings kept with the version judged; only its proven author revises, and the revision is reviewed again.
A judgement that cannot be had (unreachable) or read (not approve/changes, changes with no finding, not JSON) leaves the record proposed, says so on it (get's review), and is never an approval; asked again after 10/20 min, at most 3 tries, then the record says its author proposes again.
approve: accepted at once; needs-operator waits for the proven warrant as before. An ask that cannot be published is taken back and reviewed again later.
A record revised while judged is not decided on the old version.
A record with any version written by an unproven caller is never reviewed (the unproven-writer rule kept); author-only revision kept.
The review verb is gone: manifest seats/claims, Verbs, tools, README, tests.
Tests (fail first against main: ReviewStep undefined): approve accepts and moves 0276 §1; the question holds the record, its linked 0276 and the rules and nothing else; changes keeps proposed and the revision is re-reviewed; six unreadable/unreachable answers never approve, with backoff and the 3-try limit; revised-while-judged; unproven never reviewed; needs-operator only on warrant; unpublishable ask; insight reviewed like a proposal; no review verb (also over the bus). go test -race ./... ok (memory and postgres); merge-check.sh with a controller built from mesh-controller main: ok, 69 resources without health as kept.
No schema change: the review state is in the version's JSON body.
Merge order: none needed against the other two PRs of this batch (#?? issue 487 and issue 488 touch other files of this module); merge this one first if in doubt, since it changes kit_test.go's judge.
Fixes hq issue 425 as ADR 0290 and to-be 55 §5 now say (updated 2026-10-11): the knowledge base reviews a proposal itself.
**What changed**
- Every version proposed (a new record, a revision, a progressive insight) is marked due for review. The background work (woken at once by `propose`, a review always before the next drafting step) asks `claude-code.claude_code_judge` one question with no tools that holds only the record, the records it links and the rules, answering `approve` or `changes` with findings (`review.go`).
- `changes`: stays proposed, findings kept with the version judged; only its proven author revises, and the revision is reviewed again.
- A judgement that cannot be had (unreachable) or read (not approve/changes, changes with no finding, not JSON) leaves the record proposed, says so on it (`get`'s `review`), and is never an approval; asked again after 10/20 min, at most 3 tries, then the record says its author proposes again.
- `approve`: accepted at once; `needs-operator` waits for the proven warrant as before. An ask that cannot be published is taken back and reviewed again later.
- A record revised while judged is not decided on the old version.
- A record with any version written by an unproven caller is never reviewed (the unproven-writer rule kept); author-only revision kept.
- The `review` verb is gone: manifest seats/claims, `Verbs`, tools, README, tests.
**Tests** (fail first against main: `ReviewStep` undefined): approve accepts and moves 0276 §1; the question holds the record, its linked 0276 and the rules and nothing else; changes keeps proposed and the revision is re-reviewed; six unreadable/unreachable answers never approve, with backoff and the 3-try limit; revised-while-judged; unproven never reviewed; needs-operator only on warrant; unpublishable ask; insight reviewed like a proposal; no review verb (also over the bus). `go test -race ./...` ok (memory and postgres); `merge-check.sh` with a controller built from mesh-controller main: ok, 69 resources without health as kept.
No schema change: the review state is in the version's JSON body.
Merge order: none needed against the other two PRs of this batch (#?? issue 487 and issue 488 touch other files of this module); merge this one first if in doubt, since it changes `kit_test.go`'s judge.
The mesh proves which machine called, not which agent on it (hq issue 365), so a review verb could not tell a
reviewer from the author. Each version proposed is now judged by claude-code.claude_code_judge in a separate
call that sees only the record, the records it links and the rules: approve accepts (or asks the operator for a
needs-operator record), changes keeps it proposed with the findings for its author, and a judgement that cannot
be had or read leaves it proposed, says so, and never counts as approval.
Deliverynovox/mesh-catalog@6fb827605ada — 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:41 (new) → proposed (announced): novox/mesh-catalog#211's head announced
2026-10-11 10:46 proposed → checked (checked): the verdict names this commit
2026-10-11 10:46 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@6fb827605ada` — **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:41 (new) → proposed (announced): novox/mesh-catalog#211's head announced
- 2026-10-11 10:46 proposed → checked (checked): the verdict names this commit
- 2026-10-11 10:46 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`.
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
Run by the build seat on ace as build-1791713222210787249 (builds --log build-1791713222210787249).
--- 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 1 module(s) changed against 4 machine(s), as the snapshot of 2026-10-11T10:05: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:05:21Z
modules the change moves:
- mesh-knowledge (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): mesh-knowledge
--- its merge-check.sh (go toolchain)
ok git.novox.be/novox/mesh-catalog/checks/words 0.002s
words: 12 retired words and 70 daemons' lines, none in the 41492 strings of 673 files
ok git.novox.be/novox/mesh-catalog/checks/agenthome 0.013s
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 76.445s
--- its merge-check-typescript.sh (typescript toolchain)
**Merge check** at `ebba63d7`
- `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
Run by the build seat on ace as `build-1791713222210787249` (`builds --log build-1791713222210787249`).
```
--- 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 1 module(s) changed against 4 machine(s), as the snapshot of 2026-10-11T10:05: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:05:21Z
modules the change moves:
- mesh-knowledge (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): mesh-knowledge
--- its merge-check.sh (go toolchain)
ok git.novox.be/novox/mesh-catalog/checks/words 0.002s
words: 12 retired words and 70 daemons' lines, none in the 41492 strings of 673 files
ok git.novox.be/novox/mesh-catalog/checks/agenthome 0.013s
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 76.445s
--- 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…
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/bus_test.go, modules/mesh-knowledge/cmd/mesh-knowledge/kit_test.go, modules/mesh-knowledge/cmd/mesh-knowledge/manifest_test.go, modules/mesh-knowledge/cmd/mesh-knowledge/review_bounds_test.go, modules/mesh-knowledge/cmd/mesh-knowledge/review_test.go, modules/mesh-knowledge/cmd/mesh-knowledge/wholeset_test.go, modules/mesh-knowledge/cmd/mesh-knowledge/writers_test.go
Run by the build seat on g14 as build-1791715325574899021 (builds --log build-1791715325574899021).
--- 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 1 module(s) changed against 4 machine(s), as the snapshot of 2026-10-11T10:33: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:33:35Z
modules the change moves:
- mesh-knowledge (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): mesh-knowledge
notes:
- modules/mesh-knowledge/README.md, modules/mesh-knowledge/cmd/mesh-knowledge/bus_test.go, modules/mesh-knowledge/cmd/mesh-knowledge/kit_test.go, modules/mesh-knowledge/cmd/mesh-knowledge/manifest_test.go, modules/mesh-knowledge/cmd/mesh-knowledge/review_bounds_test.go, modules/mesh-knowledge/cmd/mesh-knowledge/review_test.go, modules/mesh-knowledge/cmd/mesh-knowledge/wholeset_test.go and modules/mesh-knowledge/cmd/mesh-knowledge/writers_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 41503 strings of 673 files
ok git.novox.be/novox/mesh-catalog/checks/agenthome 0.008s
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 114.030s
--- its merge-check-typescript.sh (typescript toolchain)
**Merge check** at `6fb82760`
- `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/bus_test.go, modules/mesh-knowledge/cmd/mesh-knowledge/kit_test.go, modules/mesh-knowledge/cmd/mesh-knowledge/manifest_test.go, modules/mesh-knowledge/cmd/mesh-knowledge/review_bounds_test.go, modules/mesh-knowledge/cmd/mesh-knowledge/review_test.go, modules/mesh-knowledge/cmd/mesh-knowledge/wholeset_test.go, modules/mesh-knowledge/cmd/mesh-knowledge/writers_test.go
Run by the build seat on g14 as `build-1791715325574899021` (`builds --log build-1791715325574899021`).
```
--- 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 1 module(s) changed against 4 machine(s), as the snapshot of 2026-10-11T10:33: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:33:35Z
modules the change moves:
- mesh-knowledge (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): mesh-knowledge
notes:
- modules/mesh-knowledge/README.md, modules/mesh-knowledge/cmd/mesh-knowledge/bus_test.go, modules/mesh-knowledge/cmd/mesh-knowledge/kit_test.go, modules/mesh-knowledge/cmd/mesh-knowledge/manifest_test.go, modules/mesh-knowledge/cmd/mesh-knowledge/review_bounds_test.go, modules/mesh-knowledge/cmd/mesh-knowledge/review_test.go, modules/mesh-knowledge/cmd/mesh-knowledge/wholeset_test.go and modules/mesh-knowledge/cmd/mesh-knowledge/writers_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 41503 strings of 673 files
ok git.novox.be/novox/mesh-catalog/checks/agenthome 0.008s
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 114.030s
--- 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 425 as ADR 0290 and to-be 55 §5 now say (updated 2026-10-11): the knowledge base reviews a proposal itself.
What changed
propose, a review always before the next drafting step) asksclaude-code.claude_code_judgeone question with no tools that holds only the record, the records it links and the rules, answeringapproveorchangeswith findings (review.go).changes: stays proposed, findings kept with the version judged; only its proven author revises, and the revision is reviewed again.get'sreview), and is never an approval; asked again after 10/20 min, at most 3 tries, then the record says its author proposes again.approve: accepted at once;needs-operatorwaits for the proven warrant as before. An ask that cannot be published is taken back and reviewed again later.reviewverb is gone: manifest seats/claims,Verbs, tools, README, tests.Tests (fail first against main:
ReviewStepundefined): approve accepts and moves 0276 §1; the question holds the record, its linked 0276 and the rules and nothing else; changes keeps proposed and the revision is re-reviewed; six unreadable/unreachable answers never approve, with backoff and the 3-try limit; revised-while-judged; unproven never reviewed; needs-operator only on warrant; unpublishable ask; insight reviewed like a proposal; no review verb (also over the bus).go test -race ./...ok (memory and postgres);merge-check.shwith a controller built from mesh-controller main: ok, 69 resources without health as kept.No schema change: the review state is in the version's JSON body.
Merge order: none needed against the other two PRs of this batch (#?? issue 487 and issue 488 touch other files of this module); merge this one first if in doubt, since it changes
kit_test.go's judge.Delivery
novox/mesh-catalog@6fb827605ada— 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
ebba63d7mesh/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-1791713222210787249(builds --log build-1791713222210787249).Merge check at
6fb82760mesh/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-1791715325574899021(builds --log build-1791715325574899021).