4 Commits

Include renames

Author	SHA1	Message	Date
jschoubben	9cfb5f9edb	mesh-knowledge: keep when an owed review is due, say it in the history, and tell the operator once after its last try (hq issue 497) ... 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.	2026-10-11 19:24:07 +02:00
jschoubben	6fb827605a	mesh-knowledge: bound every review failure per record, make one out of tries loud, and let only its author revise a pending insight (review of #211)	2026-10-11 12:41:24 +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