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
@@ -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").