Design writer and hq-graduate follow the new step 2; the playbook names no record by number

Claude-Session: https://claude.ai/code/session_01NcbgfFSnn24M3GcqttoU7i

.claude/agents/hq-design-writer.md

@@ -14,7 +14,9 @@ there and never push.
 (`knowledge-base.get` with `reasoning`, and `links`), and `knowledge-base.ask` for the area in plain words: a
 record you did not expect may already decide a point. Read each design whole before changing it, hq's glossary
 (`00-META/glossary.md`) and playbook 02's steps for amending a to-be design. A clause the records do not
-decide is not written into a design as if they did: say it to the caller as an open point.
+decide is not written into a design as if they did. A choice within what a record decides (a field, a tool, an
+event, a bound, the order of steps) is the design's own: write it in the design with its reason, under the record it
+follows from (playbook 02, step 2). Only a question outside every record's question is an open point for the caller.
 **It reads the mesh and writes nothing there.** It calls only verbs that read (`knowledge-base.get`, `ask`, `links`,
 `holds`; `issue-tracker.list`, `get`); never `knowledge-base.reserve` or `propose`, nor any `issue-tracker` verb that
 writes (`open`, `move`, `note`, `link`). What a record or an issue must carry goes to the caller in its report.
@@ -31,5 +33,5 @@ names, never node names, addresses or paths. A new word goes into the glossary w
 what it refuses. Commit in the imperative, about why.
 
 Report to the caller in under 30 lines: the branch and its head, each file changed with the findings it now
-carries, what the tests said, and every point you left open because no record decides it, with your
-recommendation. Glossary words only; a guess is said as one.
+carries, what the tests said, the design's own choices you wrote, one line each, and every question you left open because it falls outside
+every record's question, with your recommendation. Glossary words only; a guess is said as one.

.claude/skills/hq-graduate/SKILL.md

@@ -32,7 +32,8 @@ written into this repository.
 
 ## Amending an existing design
 
-A design changes only through a decision. Propose the record first; if it reverses an earlier one,
+A design changes only through a decision; a choice within what a decision decides (a field, a tool, an event, a
+bound) is the design's own, written in it with its reason. Propose the record first; if it reverses an earlier one,
 it `supersedes` it (or `changes` the clauses it replaces) — **never edit the earlier record's text**;
 a correction of fact is a progressive insight (`propose` the accepted record with `insight`). Then edit
 the design, add `"ADR NNNN"` to its `decisions:`, and set `updated:`.

00-META/process/02-graduation.md

@@ -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