Make great documentation goal 1.2, and plan the README's reorganisation and the nested-template gaps #33
@@ -11,7 +11,7 @@
|
||||
wait for one.
|
||||
- README goal 2 is gated at 7.0 on the `comprehension-panel` skill, and below it
|
||||
nothing else merges — no feature, no category, no data — bar a security fix, a
|
||||
dependency bump, a repair of a promise goals 3 to 5 make, and the infrastructure
|
||||
dependency bump, a repair of behaviour the README documents, and the infrastructure
|
||||
the round itself runs on. `todo.md` carries the round: a PR per item it plans, the nine-seat
|
||||
findings at depth 1 or a restructure the maintainer approved, then the nine-seat run
|
||||
again, until the score passes. At or above 7.0
|
||||
|
||||
@@ -830,8 +830,8 @@ the Development section below, and who ships a register the five above then draw
|
||||
holding the rest, names that tell the truth, and a file that stands with no second
|
||||
document open beside it. A simulated reader panel scores those four, the score is a
|
||||
ratchet no release lowers, and [`AGENTS.md`](AGENTS.md) says what each pull request
|
||||
owes it. Below the floor it holds back new capability, never a repair of a promise
|
||||
goals 3 to 5 already make, as long as the round that lifts the score stays planned.
|
||||
owes it. Below the floor it holds back new capability, never a repair of behaviour
|
||||
this README already documents, as long as the round that lifts the score stays planned.
|
||||
3. **Valid by construction** — every value passes the check a current release of
|
||||
its real consumer applies; facts that belong together come from one draw, within
|
||||
a value and across categories.
|
||||
|
||||
Reference in New Issue
Block a user