Playbooks 07 and 08: every review asks where each piece of state lives and whether a repository holds mesh setup #493

2026-10-28T16:45:08Z

mesh-tools commented

2026-10-28 16:45:08 +00:00

The operator, 2026-10-28: "repositories are fully mesh agnostic, they know nothing about the mesh setup and especially not any nodes"; "Design everything nats native"; "if there is a problem/seam/integration/data/..., it should be handled by our nats broker". That day a lead built a placement design on an accepted record that kept node-specific placement in repository files, without checking it against those principles.

Playbook 07 step 2, item 10: the reviewer asks of every change and design (1) where each piece of state lives and how each seam travels — anything not bus state, a stream or a seat's verb is a finding, even when an accepted record put it there (name the record to supersede); (2) whether a repository holds this mesh's setup (node names, placement, settings) — a finding. How it is checked: one report line per question; a report without them is not an approval.
Playbook 08 step 4 points to it.
playbooks.html matches.

Checks: go test ./... at the root passes.

Reviewed-by: rev-pb07@shanks at a9830f5110

The operator, 2026-10-28: "repositories are fully mesh agnostic, they know nothing about the mesh setup and especially not any nodes"; "Design everything nats native"; "if there is a problem/seam/integration/data/..., it should be handled by our nats broker". That day a lead built a placement design on an accepted record that kept node-specific placement in repository files, without checking it against those principles. - Playbook 07 step 2, item 10: the reviewer asks of every change and design (1) where each piece of state lives and how each seam travels — anything not bus state, a stream or a seat's verb is a finding, even when an accepted record put it there (name the record to supersede); (2) whether a repository holds this mesh's setup (node names, placement, settings) — a finding. How it is checked: one report line per question; a report without them is not an approval. - Playbook 08 step 4 points to it. - playbooks.html matches. Checks: go test ./... at the root passes. Reviewed-by: rev-pb07@shanks at a9830f51106c7419595be4f5a7b76ab62514627c

mesh-tools added 1 commit 2026-10-28 16:45:08 +00:00

Playbooks 07 and 08: the review asks where state lives and how seams travel, and whether a repository holds mesh setup

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

Details

mesh/check pass a9830f51106c on eec73b8af0d7 | carried from 292232dad226 | unit 39 run, 0 kept, 1 skipped | integration 39 run, 0 kept, 1 skipped | co…

a9830f5110

mesh-tools commented

2026-10-28 16:45:10 +00:00

Delivery novox/hq@a9830f51106c — merged since 2026-10-28T16:46:36Z

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

Transitions

2026-10-28 16:45 (new) → proposed (announced): novox/hq#493's head announced
2026-10-28 16:45 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-10-28 16:46 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@a9830f51106c` — **merged** since 2026-10-28T16:46:36Z **Source** — source.main moved to novox/hq@292232dad226. Whether it reached the machines is `mesh-delivery-view`'s, derived from `source.main`, the wants and the haves. **Transitions** - 2026-10-28 16:45 (new) → proposed (announced): novox/hq#493's head announced - 2026-10-28 16:45 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-10-28 16:46 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 292232dad2 into main

2026-10-28 16:46:35 +00:00

mesh-tools deleted branch pb/state-and-seams

2026-10-28 16:46:35 +00:00

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: novox/hq#493