Playbooks 07 and 08: lessons of 2026-10-28 (the report's tree, its cadence, named local integration tests, member repositories during a check, delivered means what the nodes run, real-shaped fixtures) #489

2026-10-28T10:13:41Z

mesh-tools commented

2026-10-28 10:13:41 +00:00

Lessons from 2026-10-28's work on design 47 (L2), each a rule with how it is checked:

The lead's five-minute report starts with the tree drawn from the knowledge base's progress verb (detail minimal; detailed about every thirty minutes), never by hand; the report quotes the verb's read-at time. (A hand-drawn tree showed two milestones wrongly.)
Every five-minute report ends by scheduling the next, so incoming agent reports never replace it. Cadence corrected from ten to five minutes, as the instruction how-work-is-done says.
Before a group's single push, the integration tests that exercise the change run locally against an embedded bus, picked by name; not a whole module or level. The pull request names them. (A group's one check failed on an integration test only vetted locally.)
While a group is checked, no merge or push into a repository that is one of its members: a moved trunk asks the group's check again. (About 12 minutes lost.)
"On the machines" is read with the nodes' haves and the indexer's record before a change is called delivered. (It was said for a module the indexer never re-read.)
A test fixture writes state in its real writer's form. (A fixture without a value's source made a check fail on correct code.)

Rule bent and said: rule 3 runs more than "a single integration test" locally, but only named tests of the touched packages; one check per release still holds.
Checked: go test ./... at the root passes.

Reviewed-by: rev-pb-1028@shanks at dd36b7557a

Lessons from 2026-10-28's work on design 47 (L2), each a rule with how it is checked: 1. The lead's five-minute report starts with the tree drawn from the knowledge base's progress verb (detail minimal; detailed about every thirty minutes), never by hand; the report quotes the verb's read-at time. (A hand-drawn tree showed two milestones wrongly.) 2. Every five-minute report ends by scheduling the next, so incoming agent reports never replace it. Cadence corrected from ten to five minutes, as the instruction how-work-is-done says. 3. Before a group's single push, the integration tests that exercise the change run locally against an embedded bus, picked by name; not a whole module or level. The pull request names them. (A group's one check failed on an integration test only vetted locally.) 4. While a group is checked, no merge or push into a repository that is one of its members: a moved trunk asks the group's check again. (About 12 minutes lost.) 5. "On the machines" is read with the nodes' haves and the indexer's record before a change is called delivered. (It was said for a module the indexer never re-read.) 6. A test fixture writes state in its real writer's form. (A fixture without a value's source made a check fail on correct code.) Rule bent and said: rule 3 runs more than "a single integration test" locally, but only named tests of the touched packages; one check per release still holds. Checked: `go test ./...` at the root passes. Reviewed-by: rev-pb-1028@shanks at dd36b7557ae67a11f786951e4ecd813865812c39

mesh-tools added 2 commits 2026-10-28 10:13:41 +00:00

Playbooks 07 and 08: lessons of 2026-10-28 (progress tree, report cadence, local integration run, group members, delivered, fixtures) d348256090

Playbooks 07 and 08: the local integration run is the named tests that exercise the change; the report's tree is drawn from the verb

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

Details

mesh/check pass dd36b7557ae6 on 8f8393fa9343 | carried from 2ea3368b76d1 | unit 39 run, 0 kept, 1 skipped | integration 39 run, 0 kept, 1 skipped | co…

dd36b7557a

mesh-tools commented

2026-10-28 10:13:47 +00:00

Delivery novox/hq@dd36b7557ae6 — merged since 2026-10-28T10:15:20Z

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

Transitions

2026-10-28 10:13 (new) → proposed (announced): novox/hq#489's head announced
2026-10-28 10:13 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 10:15 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@dd36b7557ae6` — **merged** since 2026-10-28T10:15:20Z **Source** — source.main moved to novox/hq@8f8393fa9343. Whether it reached the machines is `mesh-delivery-view`'s, derived from `source.main`, the wants and the haves. **Transitions** - 2026-10-28 10:13 (new) → proposed (announced): novox/hq#489's head announced - 2026-10-28 10:13 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 10:15 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 8f8393fa93 into main

2026-10-28 10:15:19 +00:00

mesh-tools deleted branch pb/lessons-2026-10-28

2026-10-28 10:15:19 +00:00

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: novox/hq#489