Playbook 02: wrap the check line and name the step it means (review round 1)
mesh/merge-gate head d0a2950bb0c0 merged into trunk 42ecaa7ac419 — pass: the change touches no module of the mesh's graph
mesh/repo-check head d0a2950bb0c0 merged into trunk 42ecaa7ac419 — pass: its merge-check.sh passed
mesh/delivery delivered

This commit is contained in:
2026-10-18 17:05:46 +02:00
parent 8e76098412
commit d0a2950bb0
+3 -2
View File
@@ -166,5 +166,6 @@ when one fails. In this repository, `records.py` checks that a design's `decisio
"ADR NNNN" in the text are well formed, and that no record is written here; `index.py` checks the reading
order's six topics, which the knowledge base reads. The three habits of graduating step 2 (side by side, clauses
from the direction, the pre-check) are the lead's, read by the reviewer; `propose` refuses a link to nothing,
a deferral no issue tracks and a retired word, and the review returns a record named but not linked. The rounds are read in `knowledge-base.get` (its reviews, one per version): a question to the operator
about a record's wording after its third round is the failure of step 4.
a deferral no issue tracks and a retired word, and the review returns a record named but not linked.
The rounds are read in `knowledge-base.get` (its reviews, one per version): a question to the operator about a
record's wording after its third round is the failure of step 4 of *Writing a decision record*.