Playbooks 01, 02 and 04: settle decisions before versions, test at the cheapest level, acceptance tests through to milestones #371

2026-10-16T00:12:31Z

mesh-tools commented

2026-10-16 00:12:31 +00:00

Research 053's identity part took six versions and about two hours (operator, 2026-10-16: speed up every playbook run).

Playbook 01: check options against the mesh's own rules before offering them; explain questions with a concrete picture; one version per settled set; pre-check what the review returns; try in process before the lab; nothing left open but the build's acceptance tests.
Playbook 02: write a graduation's records side by side, take clauses from the confirmed direction and cite the effort, pre-check each record; the design lists the acceptance tests.
Playbook 04: each milestone names the acceptance tests it proves, in the design and in the table the operator confirms.

Independent review: two rounds (10 findings, then 3 small), approved; round-2 points applied at 80b647a. merge-check.sh green locally (records, index, cycle, words with the catalogue list).

Research 053's identity part took six versions and about two hours (operator, 2026-10-16: speed up every playbook run). - Playbook 01: check options against the mesh's own rules before offering them; explain questions with a concrete picture; one version per settled set; pre-check what the review returns; try in process before the lab; nothing left open but the build's acceptance tests. - Playbook 02: write a graduation's records side by side, take clauses from the confirmed direction and cite the effort, pre-check each record; the design lists the acceptance tests. - Playbook 04: each milestone names the acceptance tests it proves, in the design and in the table the operator confirms. Independent review: two rounds (10 findings, then 3 small), approved; round-2 points applied at 80b647a. merge-check.sh green locally (records, index, cycle, words with the catalogue list).

mesh-tools added 4 commits 2026-10-16 00:12:31 +00:00

Settle research decisions before proposing versions, and test on the cheapest bed (playbook 01) 2a61c57258

Research 053's identity part took six versions and about two hours: options
that broke the mesh's own rules were offered and argued back, a version was
proposed after every answer, and reviews returned findings a pre-check
would have caught. A lab run was planned where an in-process test answered.

Write a graduation's records side by side, from the confirmed direction (playbook 02) ada703e790

Proposing records one after another serialises their reviews and the
operator's asks; retyping the effort's findings into each record makes them
long and gives the review more to send back.

Give the build's acceptance tests a home in the design and milestones, and answer review round 1 a4c5ef69bb

The research playbook named acceptance tests the milestones carry, which
playbooks 02 and 04 did not know; its pre-check also disagreed with the
knowledge base's deferral rule.

Name the acceptance tests in the milestone table and say what the review returns (review round 2)

mesh/merge-gate head 80b647a2ed66 merged into trunk f8c0676b3a1d — pass: the change touches no module of the mesh's graph

Details

mesh/repo-check head 80b647a2ed66 merged into trunk f8c0676b3a1d — pass: its merge-check.sh passed

Details

mesh/delivery delivered

Details

80b647a2ed

mesh-tools commented

2026-10-16 00:12:36 +00:00

Delivery novox/hq@80b647a2ed66 — delivered since 2026-10-16T00:15:02Z

Delivery plan — builds nothing: the change touches no module of the mesh's graph

Transitions

2026-10-16 00:12 (new) → proposed (announced): novox/hq#371's head announced
2026-10-16 00:13 proposed → checked (checked): a verdict names this commit and the trunk's head as its trunk commit
2026-10-16 00:13 checked → ready (accepted): the gate passed or warned, and the repository's own check did not fail
2026-10-16 00:15 ready → published (merged): on the trunk its modules follow: merged there, and its walk opened — or nothing for a walk to move
2026-10-16 00:15 published → delivered (done): nothing for a walk to move

The commit's note under refs/notes/mesh-plan keeps every transition: git log --notes=mesh-plan.

**Delivery** `novox/hq@80b647a2ed66` — **delivered** since 2026-10-16T00:15:02Z **Delivery plan** — builds nothing: the change touches no module of the mesh's graph **Transitions** - 2026-10-16 00:12 (new) → proposed (announced): novox/hq#371's head announced - 2026-10-16 00:13 proposed → checked (checked): a verdict names this commit and the trunk's head as its trunk commit - 2026-10-16 00:13 checked → ready (accepted): the gate passed or warned, and the repository's own check did not fail - 2026-10-16 00:15 ready → published (merged): on the trunk its modules follow: merged there, and its walk opened — or nothing for a walk to move - 2026-10-16 00:15 published → delivered (done): nothing for a walk to move The commit's note under `refs/notes/mesh-plan` keeps every transition: `git log --notes=mesh-plan`.

mesh-tools merged commit 08d6476e52 into main

2026-10-16 00:15:00 +00:00

mesh-tools deleted branch playbooks/01-settle-before-versions

2026-10-16 00:15:00 +00:00

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: novox/hq#371