Playbooks 01 and 02: review by architectural domain, sections named by title with no file references, and storage forms that fit (the operator, 2026-11-02) #499

2026-11-02T18:23:10Z

mesh-tools commented

2026-11-02 18:23:10 +00:00

What the operator asked on 2026-11-02, written into the playbooks:

Review by architectural domain. Before a research effort's direction is proposed and before a design is merged, reviewers on the larger model, about two architectural domains each, review it against security, seams, running qualities, health, events and logs, testing, upgrade and tools. They never reopen a decision. The direction and the design end with a Reviewed by architectural domain section (playbook 01, new section; playbook 02 step 3 and Amending an existing design). Nothing refuses one without it yet; the reviewer holds it.
Sections named by title, never as files. A record's section has a plain title, references name a title, code evidence names repository, commit and function (no path, no line), and once proposed the knowledge base holds the only copy (playbook 01 step 4; the research skill). ADR 0592 makes the knowledge base refuse file-like names (issue 1966).
Storage forms that fit. A piece of state takes the bus storage form that fits it; a form the manifest lacks is added to mesh-sdk and named to the operator with its cost (playbook 01, seams).
Glossary: architectural domain; the Homonyms gain domain: bare it keeps the mesh-domain sense (qualified form mesh domain), the review's sense is always architectural domain.
The drawn overview (playbooks.html) follows the steps.

go test ./... passes.

Reviewed-by: review-hq-pb@shanks at 633c587a1e

What the operator asked on 2026-11-02, written into the playbooks: - **Review by architectural domain.** Before a research effort's direction is proposed and before a design is merged, reviewers on the larger model, about two architectural domains each, review it against security, seams, running qualities, health, events and logs, testing, upgrade and tools. They never reopen a decision. The direction and the design end with a *Reviewed by architectural domain* section (playbook 01, new section; playbook 02 step 3 and *Amending an existing design*). Nothing refuses one without it yet; the reviewer holds it. - **Sections named by title, never as files.** A record's section has a plain title, references name a title, code evidence names repository, commit and function (no path, no line), and once proposed the knowledge base holds the only copy (playbook 01 step 4; the research skill). ADR 0592 makes the knowledge base refuse file-like names (issue 1966). - **Storage forms that fit.** A piece of state takes the bus storage form that fits it; a form the manifest lacks is added to mesh-sdk and named to the operator with its cost (playbook 01, seams). - **Glossary:** *architectural domain*; the Homonyms gain *domain*: bare it keeps the mesh-domain sense (qualified form *mesh domain*), the review's sense is always *architectural domain*. - The drawn overview (playbooks.html) follows the steps. `go test ./...` passes. Reviewed-by: review-hq-pb@shanks at 633c587a1eef8dda8740b0af22865638b4fbc6d1

mesh-tools added 5 commits 2026-11-02 18:23:11 +00:00

Playbooks 01 and 02: review a direction and a design by aspect before proposing or merging, and name a record's sections by title with no file references, as the operator asked on 2026-11-02 0ac621e03f

Glossary: review aspect; playbook 01: a piece of state takes the bus storage form that fits it, and a form added to mesh-sdk is named to the operator with its cost b861b3ae36

Review fixes: the research skill names sections by title, the drawn overview's order and bounds follow the playbooks, an amended design is reviewed by aspect, and storage forms use glossary words f5624e7d9f

Architectural domain for the review's eight concerns, and the glossary's domain qualified as mesh domain in the homonyms, as the operator chose on 2026-11-02 6f2bacf6c4

Glossary: bare domain keeps the mesh-domain sense; only the review's sense is always qualified, so the homonym rule holds without rewriting every use

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

Details

mesh/check pass 633c587a1eef on 2731c796f0d6 | carried from 7021d0cf5ac0 | unit 39 run, 0 kept, 1 skipped | integration 39 run, 0 kept, 1 skipped | co…

633c587a1e

mesh-tools commented

2026-11-02 18:23:13 +00:00

Delivery novox/hq@633c587a1eef — merged since 2026-11-02T18:27:16Z

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

Transitions

2026-11-02 18:23 (new) → proposed (announced): novox/hq#499's head announced
2026-11-02 18:23 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-02 18:27 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@633c587a1eef` — **merged** since 2026-11-02T18:27:16Z **Source** — source.main moved to novox/hq@fa3d8aaeec69. Whether it reached the machines is `mesh-delivery-view`'s, derived from `source.main`, the wants and the haves. **Transitions** - 2026-11-02 18:23 (new) → proposed (announced): novox/hq#499's head announced - 2026-11-02 18:23 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-02 18:27 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 fa3d8aaeec into main

2026-11-02 18:27:14 +00:00

mesh-tools deleted branch docs/review-by-aspect

2026-11-02 18:27:14 +00:00

mesh-tools referenced this pull request

2026-11-02 18:39:39 +00:00

Four reviewer agents carry playbook 01's review by architectural domain, two architectural domains each #500

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: novox/hq#499