Design writer and hq-graduate follow the new step 2; the playbook names no record by number
mesh/delivery merged: source.main moved to novox/hq@5ff1298e2173
mesh/check being carried to c1cf0149b6d9 on 5ff1298e2173 | from 1ca5a3a1331f
mesh/delivery merged: source.main moved to novox/hq@5ff1298e2173
mesh/check being carried to c1cf0149b6d9 on 5ff1298e2173 | from 1ca5a3a1331f
Claude-Session: https://claude.ai/code/session_01NcbgfFSnn24M3GcqttoU7i
This commit is contained in:
@@ -24,7 +24,7 @@ about an hour, and said to the operator if it runs past.
|
||||
2. **Record the decisions** (below, *Writing a decision record*): one record per question the effort
|
||||
answers, holding that question, the options weighed and the one chosen. Most efforts answer one question
|
||||
and graduate into one record; a second record is written only for a second question of its own, such as
|
||||
how the change can be checked or delivered at all (the operator, 2026-11-06: research 085 graduated into
|
||||
how the change can be checked or delivered at all (the operator, 2026-11-06: an effort graduated into
|
||||
eleven records where it answered two questions). The choices made while working out the design that
|
||||
follows (a field, a tool, an event, a bound, the order of steps) are the design's: written in the design
|
||||
with their reasons, under the record they follow from, never as records of their own. A clause of an
|
||||
|
||||
Reference in New Issue
Block a user