Playbooks 01 and 02: one record per question an effort answers; design choices live in the design #522

2026-11-06T19:53:23Z

mesh-tools commented

2026-11-06 19:53:23 +00:00

The operator, 2026-11-06 20:3x: "I would've thought we had 1 or maybe 2 ADRs for our research and design"; "fix the playbook and go to less records". An effort graduated into eleven records where it answered two questions, because playbook 02 step 2 asked for one record per choice that could be reversed on its own, so every design choice became a record.

Playbook 02 step 2: one record per question the effort answers (its question, the options weighed, the one chosen); the choices made while working out the design are the design's, written in it with their reasons. How it is checked: the lead names each record's question in the graduation report, and more than two records for one effort is said to the operator first.
Playbook 02, Amending an existing design: a choice within what a decision decides is the design's own.
Playbook 01 step 7: the Direction states the question, its options and the one proposed, and the design choices in a line each.
playbooks.html, the hq-design-writer agent and the hq-graduate skill follow it.

No record decides how many records an effort graduates into (the reviewer asked the knowledge base); the old rule came from a playbook commit. go test ./... passes.

Reviewed-by: mesh-code-reviewer@shanks at c1cf0149b6

https://claude.ai/code/session_01NcbgfFSnn24M3GcqttoU7i

The operator, 2026-11-06 20:3x: "I would've thought we had 1 or maybe 2 ADRs for our research and design"; "fix the playbook and go to less records". An effort graduated into eleven records where it answered two questions, because playbook 02 step 2 asked for one record per choice that could be reversed on its own, so every design choice became a record. - Playbook 02 step 2: one record per question the effort answers (its question, the options weighed, the one chosen); the choices made while working out the design are the design's, written in it with their reasons. How it is checked: the lead names each record's question in the graduation report, and more than two records for one effort is said to the operator first. - Playbook 02, Amending an existing design: a choice within what a decision decides is the design's own. - Playbook 01 step 7: the Direction states the question, its options and the one proposed, and the design choices in a line each. - playbooks.html, the hq-design-writer agent and the hq-graduate skill follow it. No record decides how many records an effort graduates into (the reviewer asked the knowledge base); the old rule came from a playbook commit. `go test ./...` passes. Reviewed-by: mesh-code-reviewer@shanks at c1cf0149b6d933f8d8f0e68ad089d01925d6060e https://claude.ai/code/session_01NcbgfFSnn24M3GcqttoU7i

mesh-tools added 2 commits 2026-11-06 19:53:24 +00:00

Playbooks 01 and 02: one record per question an effort answers; design choices live in the design 5e3b836404

Research 085 graduated into eleven records where it answered two questions:
the rule 'one record per choice that could be reversed on its own' made
every design choice a record of its own.

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

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

Details

mesh/check being carried to c1cf0149b6d9 on 5ff1298e2173 | from 1ca5a3a1331f

c1cf0149b6

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

mesh-tools commented

2026-11-06 19:53:29 +00:00

Delivery novox/hq@c1cf0149b6d9 — merged since 2026-11-06T19:55:25Z

Source — source.main moved to novox/hq@5ff1298e21. Whether it reached the machines is mesh-delivery-view's, derived from source.main, the wants and the haves.

Transitions

2026-11-06 19:53 (new) → proposed (announced): novox/hq#522's head announced
2026-11-06 19:53 proposed → ready (accepted): a verdict names this commit and the trunk's head as its trunk commit, the gate passed or warned, and the repository's own check did not fail; or the check gates no merge (check-gates-merge false)
2026-11-06 19:55 ready → merged (merged): on the trunk its modules follow: merged there

The commit's note under refs/notes/mesh-plan keeps every transition of this change up to its merge: git log --notes=mesh-plan.

**Delivery** `novox/hq@c1cf0149b6d9` — **merged** since 2026-11-06T19:55:25Z **Source** — source.main moved to novox/hq@5ff1298e2173. Whether it reached the machines is `mesh-delivery-view`'s, derived from `source.main`, the wants and the haves. **Transitions** - 2026-11-06 19:53 (new) → proposed (announced): novox/hq#522's head announced - 2026-11-06 19:53 proposed → ready (accepted): a verdict names this commit and the trunk's head as its trunk commit, the gate passed or warned, and the repository's own check did not fail; or the check gates no merge (check-gates-merge false) - 2026-11-06 19:55 ready → merged (merged): on the trunk its modules follow: merged there The commit's note under `refs/notes/mesh-plan` keeps every transition of this change up to its merge: `git log --notes=mesh-plan`.

mesh-tools merged commit 5ff1298e21 into main

2026-11-06 19:55:23 +00:00

mesh-tools deleted branch docs/one-record-per-question

2026-11-06 19:55:24 +00:00

mesh-tools referenced this pull request

2026-11-06 20:37:59 +00:00

Design 47 follows ADR 0656 and ADR 0644: the delivery's own parts checked and delivered by their own change (issue 1921) #523

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: novox/hq#522