Answer prose round 1: 0 🔴, 4 🟡; reword the contributor sentences

This commit is contained in:
2026-10-21 22:26:19 +02:00
parent 2407689747
commit 453a8e3b94
3 changed files with 3 additions and 3 deletions
+1 -1
View File
@@ -2,7 +2,7 @@
## Unreleased
- Every project's audience now includes the contributor, the person who reads the code to change it, and larv-review's comprehension check names them as the reader it serves. A README doesn't list them; only its `**Void:** code health` line drops them.
- Every project's audience now includes the contributor, the person who reads the code to change it. A README doesn't list them; only its `**Void:** code health` line drops them. larv-review's comprehension check now measures how hard the project is for them to read.
- `settings.json` no longer carries a model: each machine keeps the one you pick with `/model`. Git's clean filter `bin/settings_filter.py` drops `"model"` and sorts the keys, so neither a pick nor Claude Code's key order can reach a commit. Update now starts with `git add settings.json`: without it, Update's `git checkout -f` drops the machine's model. On upgrade, on each machine:
1. Turn the filter on in `~/.claude`: `git config filter.settings.clean bin/settings_filter.py`.
2. Pick a model with `/model`. Until you do, Claude Code runs its default model; this repo set `opus` before.
+1 -1
View File
@@ -9,4 +9,4 @@ paths:
- **Mark each goal `**Maintain:**` or `**Achieve:**`.** A maintain goal is a state to hold: a change that breaks it is redesigned or dropped, whatever its value to other goals. An achieve goal is a direction to pursue, weighed against the other achieve goals. Under each achieve goal, three indented bullets: `Signal:` what moving towards it looks like, `Counter-signal:` what shows it is bought at a wrong price, and `Why:` one line on how the two connect. A goal with sub-goals states its own signal. A maintain goal has no bullets. BANNED: an unmarked goal; an achieve goal with no signal; `**Achieve:** Delivery speed.` with the signal `faster`. GOOD: `**Achieve:** Delivery speed.` with `Signal: hours from a chunk's start to its merge fall.`, `Counter-signal: 🔴 findings per chunk rise.` and `Why: speed bought by skipping review shows up as defects.`
- **Leave code health out of the README.** `~/.claude/CLAUDE.md` → "Shared goal" states it for every project, ranked first, and says when and how a README voids it. File an item to drop a README goal that restates it: the goals after it renumber, and every Moves cell and decision citing them must follow.
- **Audience** names who depends on the project and what they may rely on.
- **The contributor is in every project's audience**, whoever the README names: the person who reads the code to change it. Don't list them. A README drops them only with the `**Void:** code health` line (`~/.claude/CLAUDE.md` → "Shared goal"), the one place a project says maintainability doesn't matter.
- **Every project's audience includes the contributor**: the person who reads the code to change it. The README doesn't list them, and drops them only with the `**Void:** code health` line (`~/.claude/CLAUDE.md` → "Shared goal").
+1 -1
View File
@@ -114,7 +114,7 @@ Launch principles-auditor on the trigger in §3: one for the README's goals and
### Comprehension check
The comprehension check records how hard the project is to read for the contributor, the reader it serves (`~/.claude/rules/goals-and-audience.md`), and blocks no merge. Simulated readers, the seats, launched per `~/.claude/skills/comprehension-panel/SKILL.md`, each read the whole project, not the diff. It reports no findings and is no pass: it runs once, in §5, after every pass is done, the auto-reviewer included, so it reads the branch as review left it. It runs a paired ruling when the architecture pass's trigger fired, whether or not a precedent, the user's no or an opt-out skipped its architect, and a scoring run where one is due. It skips only as "Opt-out" or "Suspended" below says.
The comprehension check records how hard the project is for its contributor to read (`~/.claude/rules/goals-and-audience.md`), and blocks no merge. Simulated readers, the seats, launched per `~/.claude/skills/comprehension-panel/SKILL.md`, each read the whole project, not the diff. It reports no findings and is no pass: it runs once, in §5, after every pass is done, the auto-reviewer included, so it reads the branch as review left it. It runs a paired ruling when the architecture pass's trigger fired, whether or not a precedent, the user's no or an opt-out skipped its architect, and a scoring run where one is due. It skips only as "Opt-out" or "Suspended" below says.
**Paired ruling.** Each seat votes whether the project reads better, the same or worse at this branch's head than at the base.