From d0a2950bb0c0be8cfc1ce794e86ce0c2979281f9 Mon Sep 17 00:00:00 2001 From: jochen Date: Sun, 18 Oct 2026 17:05:46 +0200 Subject: [PATCH] Playbook 02: wrap the check line and name the step it means (review round 1) --- 00-META/process/02-graduation.md | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) diff --git a/00-META/process/02-graduation.md b/00-META/process/02-graduation.md index 9796d730..b0bd9371 100644 --- a/00-META/process/02-graduation.md +++ b/00-META/process/02-graduation.md @@ -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*.