mesh-knowledge: the review is shown every link kind propose accepts and a research effort's status apart from its state (hq issue 492)
mesh/merge-gate pass: builds mesh-knowledge → novox; no bus step; every machine composes with the change as it did without (4 of 4 compose)
mesh/repo-check pass: its merge-check.sh passed, each part in its toolchain: merge-check.sh (go), merge-check-typescript.sh (typescript)
mesh/delivery delivered

The first live review sent research 046 back for a touches link the rules never named and a status proposed
that is the record's state, not the effort's. The rules now list LinkKinds, the one list propose holds a link
to, each with its meaning.
This commit is contained in:
2026-10-11 13:07:29 +02:00
parent 73367192c1
commit a6e2881448
4 changed files with 86 additions and 1 deletions
+3 -1
View File
@@ -96,7 +96,9 @@ as text. `get` serves each, and any other field a record of hq wrote under `fiel
3. Revise it by proposing again; every version is kept.
4. The knowledge base reviews every version proposed itself. It asks the agent module's judge
(`claude-code.claude_code_judge` on this node) one question, in a separate call with no tools, that holds only
the record, the records it links and the rules, and answers `approve` or `changes` with findings. The background
the record, the records it links and the rules, and answers `approve` or `changes` with findings. The rules it sees
name every kind of link `propose` accepts, from the one list `propose` holds a link to, and the record it sees
shows its state in the knowledge base apart from a research effort's own status (hq issue 492). The background
work asks it at once, before the next step of any drafting, one judgement at a time.
- On `changes` the record stays proposed, the findings kept with the version they judged (`get` shows them).
Its author revises it by proposing it again, and that version is reviewed again.