15 Commits

Author SHA1 Message Date
lilleman 4873ee9e74 Key project-record's copies per worktree
CI / tests (pull_request) Successful in 2m8s
2026-11-15 22:45:04 +01:00
lilleman 9508838439 Answer prose round 1: 0 🔴, 9 🟡 (0 misread); name the five as project records, cut what CLAUDE.md already says, and reword the comments the round named
CI / tests (pull_request) Successful in 2m27s
2026-11-14 00:25:18 +01:00
lilleman 084bc74b1c Read and write each record through the store its config names, and open one for agents with project-record
CI / tests (pull_request) Successful in 2m14s
2026-11-13 23:54:04 +01:00
lilleman c034c43259 Answer stability round 1: 0 🔴, 7 🟡 (0 misread); fail where the principles folder is missing or empty, say a reviewer without the header line reports it, fix the README and CHANGELOG lines the header made false, name the folder once as the config's principles folder 2026-11-12 23:40:35 +01:00
lilleman d96ea9ea3c Hand reviewers the technical principles from the folder a project's config names
CI / tests (pull_request) Failing after 2m11s
2026-11-12 23:21:31 +01:00
lilleman dcb9abf644 Answer stability round 1: 1 🔴, 3 🟡 (0 misread); keep the global rules generic, and say in one always-loaded rule of this repo where AGENTS.md's parts went 2026-11-11 16:46:27 +01:00
lilleman 9b770e4893 Fold AGENTS.md into the decision log, .claude/rules/, README and the panel's seat prompts; load CLAUDE.md once in this repo
CI / tests (pull_request) Successful in 2m7s
2026-11-11 16:32:48 +01:00
lilleman 6d6876fbcf Answer prose round 1: 1 🔴, 7 🟡 (0 misread); state principle 6 as the code runs it, call them project principles, ask on every principle change
CI / tests (pull_request) Successful in 2m7s
2026-11-11 16:07:06 +01:00
lilleman c9a2c7b704 Propose a principle when a new decision shares its rule with decisions already listed
CI / tests (pull_request) Failing after 2m6s
2026-11-11 15:59:29 +01:00
lilleman 0c2f37d284 Distil 41 decision titles in AGENTS.md into seven principles, and say so where AGENTS.md's list is described 2026-11-11 15:57:43 +01:00
lilleman 118a7d22d3 Check each new decision against the project's principles, in rules/decisions.md and larv-review 2026-11-11 15:50:13 +01:00
lilleman dc5cd6ce65 Read the plan and the records only as far as the chunk needs 2026-10-13 17:08:27 +02:00
lilleman 950f06c0be Answer architecture round 1: give the rules/ design its own decision with its premise, move where a choice goes into the comment rules, let each rule file's paths frontmatter be the one map and check every rule file named exists, pass the judge its rules folder, and file two findings outside the chunk 2026-10-13 00:46:11 +02:00
lilleman de0dad7d58 Answer prose round 1: list the judge's rule files in the vocabulary, widen the stability reviewer's prose bar, and reword the router, the maintenance rules and the decision 2026-10-13 00:38:48 +02:00
lilleman 6f8a650ac0 Make CLAUDE.md a short router, and move each topic's rules to a file under rules/ that loads when a session touches a matching file 2026-10-13 00:24:17 +02:00