4 Commits

Include renames

Author	SHA1	Message	Date
jochen	8f5e8bcb6e	mesh-knowledge: tell a failed whole-set rule to the operator as a warning naming the records, and leave the module healthy (hq issue 504) ... The operator decided on 2026-10-12 that a rule of the record set that fails is a fault of the records, which their authors repair, not the module failing: as issue 508 decided for a proposal never reviewed, health says only whether the module works, and a finding must not hold the module's own rollouts. The findings go through the notice the knowledge base already sends (operator-channel.notify, a warning), once per finding, kept as told across restarts, and cleared when the rule holds again.	2026-10-12 13:25:09 +02:00
jochen	2051d8b80b	mesh-knowledge: ask changes in the review for a decision nothing would cite, so its acceptance never turns the module unhealthy (hq issue 504) ... The whole-set rule cited ran only after acceptance: the review approved a decision with no home and no record linking it, the rule then failed, and the module's health turned red for a fault its author could only repair after the fact. hq held the rule at the record's own merge. The review now judges it ahead, before the judgement: such a decision stays proposed with a changes finding naming the rule. It is not refused at propose, because no record can link a number only reserved.	2026-10-12 13:25:09 +02:00
jschoubben	ebba63d71f	mesh-knowledge: review every proposal in a judgement of its own, and serve no review verb (hq issue 425, ADR 0290 as updated) ... 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.	2026-10-11 12:06:18 +02:00
jschoubben	ba7b455719	Add mesh-knowledge, the knowledge base's first slice (hq issue 425, ADR 0290) ... An agent learns what a decision says only by reading whole records. This module holds every decision record and research effort whole in a database in the store, with clauses that carry their own status and source, typed links read from both ends, and every version. It answers ask, get and holds within a stated bound, and takes a record through reserve, propose (refused on any of the 29 per-record rules), review by someone other than the author, and acceptance, on the operator's proven warrant when the record needs it. The 4 whole-set rules make the module unhealthy when they fail. The import reads hq at a commit through the records module, never overwrites, and changes nothing when run again. Prose decisions get drafted clauses that a second judgement must confirm before they are served.	2026-10-11 04:58:35 +02:00