Playbook 07: the prepare reads the code; the lead answers design questions against the principles #562

2026-11-11T22:53:32Z

mesh-tools commented

2026-11-11 22:53:32 +00:00

The operator, 2026-11-11 about 23:45 CET: yes, a milestone's prepare reads the code as well as the design. In milestone 47/G's develop the lead answered over 100 questions, most of them a design line meeting code (a form the code cannot take, a part assumed built that was not); the prepare had read the design alone.

Playbook 07 step 0: the preparer reads the milestone part and the main file whole, then the code each line lands in at origin/main, and lists every place design and code disagree (Design meets code) beside the design questions.
Step 0b, playbooks 02 and 08, the glossary's design question, AGENTS.md and the preparer's and code reviewer's definitions now follow the replaced instruction implement-the-design (approved 2026-11-11 ~21:48 CET): the lead answers each question in one line against 00-META/principles.md; only a question no principle settles goes to the operator (what they see or how they work, data removed, their terminal) or to hq-design-writer.
playbooks.html follows.

https://claude.ai/code/session_01NcbgfGKaxw984XyAPfLm4h

The operator, 2026-11-11 about 23:45 CET: yes, a milestone's prepare reads the code as well as the design. In milestone 47/G's develop the lead answered over 100 questions, most of them a design line meeting code (a form the code cannot take, a part assumed built that was not); the prepare had read the design alone. - Playbook 07 step 0: the preparer reads the milestone part and the main file whole, then the code each line lands in at origin/main, and lists every place design and code disagree (`Design meets code`) beside the design questions. - Step 0b, playbooks 02 and 08, the glossary's *design question*, AGENTS.md and the preparer's and code reviewer's definitions now follow the replaced instruction implement-the-design (approved 2026-11-11 ~21:48 CET): the lead answers each question in one line against 00-META/principles.md; only a question no principle settles goes to the operator (what they see or how they work, data removed, their terminal) or to hq-design-writer. - playbooks.html follows. https://claude.ai/code/session_01NcbgfGKaxw984XyAPfLm4h

mesh-tools added 2 commits 2026-11-11 22:53:33 +00:00

Have the prepare read the code and list where design and code disagree b6ea3a740c

In milestone 47/G's develop the lead answered over 100 questions, most of
them a design line meeting the code: a form the code cannot take, or a part
assumed built that was not. The prepare had read the design alone. The
operator, 2026-11-11 about 23:45 CET: the prepare reads the code each design
line lands in as well, and lists every such place before any developer
starts; the lead answers each in one line against the principles.

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

Let the lead answer every design question against the principles

mesh/check checking a2da2a3e7451 on 87f2901f556b

mesh/delivery merged: source.main moved to novox/hq@87f2901f556b

Details

a2da2a3e74

The operator replaced the instruction on implementing a design on
2026-11-11 about 21:48 CET: the lead answers each question met while
building in one line against the principles, and only one no principle
settles goes on, to the operator when it changes what they see or how
they work, removes data or needs their terminal, otherwise to the design
writer as a design line. Playbooks 02, 07 and 08, the glossary's design
question, AGENTS.md, the code reviewer and the drawn overview still said
only the operator or the design writer answers; they now say the rule.

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

mesh-tools commented

2026-11-11 22:53:35 +00:00

Delivery novox/hq@a2da2a3e7451 — merged since 2026-11-11T22:54:33Z

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

Transitions

2026-11-11 22:53 (new) → proposed (announced): novox/hq#562's head announced
2026-11-11 22: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-11 22:54 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@a2da2a3e7451` — **merged** since 2026-11-11T22:54:33Z **Source** — source.main moved to novox/hq@87f2901f556b. Whether it reached the machines is `mesh-delivery-view`'s, derived from `source.main`, the wants and the haves. **Transitions** - 2026-11-11 22:53 (new) → proposed (announced): novox/hq#562's head announced - 2026-11-11 22: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-11 22:54 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 87f2901f55 into main

2026-11-11 22:54:31 +00:00

mesh-tools deleted branch meta/prepare-reads-code

2026-11-11 22:54:31 +00:00

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: novox/hq#562