Test levels and time budgets in how-we-build and playbooks 07 and 08 (issue 891, ADR 0391) #374

2026-10-16T08:09:43Z

mesh-tools commented

2026-10-16 08:09:43 +00:00

Amends the constitution (how-we-build §5, under §6: decision ADR 0391, accepted with the operator's approval 2026-10-16) and playbooks 07 and 08.

how-we-build §5: new section "Tests run at the lowest level that proves them, within a time budget": unit (well under a second per test; locally, of what changed), integration (whole suite in seconds, never over sixty; only in the forge's checks), end to end (only when the operator asks); test at the lowest level that proves it; a suite over sixty seconds is a defect; reports name tests and times. With how it was earned.
Playbook 07: the context file no longer lists a throwaway database server among the local facts; phase 1 says unit tests of what changed, each well under a second.
Playbook 08: step 3 says the same.

After merge: playbook 05 syncs the constitution page. Follow-up: issue 890 (the catalogue's check takes about seven minutes).

Amends the constitution (how-we-build §5, under §6: decision ADR 0391, accepted with the operator's approval 2026-10-16) and playbooks 07 and 08. - how-we-build §5: new section "Tests run at the lowest level that proves them, within a time budget": unit (well under a second per test; locally, of what changed), integration (whole suite in seconds, never over sixty; only in the forge's checks), end to end (only when the operator asks); test at the lowest level that proves it; a suite over sixty seconds is a defect; reports name tests and times. With how it was earned. - Playbook 07: the context file no longer lists a throwaway database server among the local facts; phase 1 says unit tests of what changed, each well under a second. - Playbook 08: step 3 says the same. After merge: playbook 05 syncs the constitution page. Follow-up: issue 890 (the catalogue's check takes about seven minutes).

mesh-tools added 1 commit 2026-10-16 08:09:44 +00:00

Say ADR 0391's test levels and time budgets in how-we-build and playbooks 07 and 08 (issue 891)

mesh/merge-gate head d9dd8a63d83b merged into trunk 08d6476e5287 — pass: the change touches no module of the mesh's graph

Details

mesh/repo-check head d9dd8a63d83b merged into trunk 08d6476e5287 — pass: its merge-check.sh passed

Details

mesh/delivery delivered

Details

d9dd8a63d8

mesh-tools commented

2026-10-16 08:09:55 +00:00

Delivery novox/hq@d9dd8a63d83b — delivered since 2026-10-16T08:13:28Z

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

Transitions

2026-10-16 08:09 (new) → proposed (announced): novox/hq#374's head announced
2026-10-16 08:10 proposed → checked (checked): a verdict names this commit and the trunk's head as its trunk commit
2026-10-16 08:10 checked → ready (accepted): the gate passed or warned, and the repository's own check did not fail
2026-10-16 08:13 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 08:13 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@d9dd8a63d83b` — **delivered** since 2026-10-16T08:13:28Z **Delivery plan** — builds nothing: the change touches no module of the mesh's graph **Transitions** - 2026-10-16 08:09 (new) → proposed (announced): novox/hq#374's head announced - 2026-10-16 08:10 proposed → checked (checked): a verdict names this commit and the trunk's head as its trunk commit - 2026-10-16 08:10 checked → ready (accepted): the gate passed or warned, and the repository's own check did not fail - 2026-10-16 08:13 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 08:13 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 commented

2026-10-16 08:11:18 +00:00

ready at d9dd8a63d8

The operator's word given in the novox session at 10:10 (constitution amendment under how-we-build §6; decision ADR 0391, accepted).

ready at d9dd8a63d83bc3fe4260a005e33c40c1e8198290 The operator's word given in the novox session at 10:10 (constitution amendment under how-we-build §6; decision ADR 0391, accepted).

mesh-tools commented

2026-10-16 08:11:18 +00:00

mesh-delivery: the ready mark at is cleared: the head is now d9dd8a63d8, pushed after it. Mark the new head ready once it is reviewed.

mesh-delivery: the ready mark at is cleared: the head is now d9dd8a63d83bc3fe4260a005e33c40c1e8198290, pushed after it. Mark the new head ready once it is reviewed.

mesh-tools added the mesh/ready label 2026-10-16 08:13:09 +00:00

mesh-tools commented

2026-10-16 08:13:13 +00:00

ready at d9dd8a63d8

Marked again: the label was cleared between the first label and comment (issue 873). The operator's word given 10:10.

ready at d9dd8a63d83bc3fe4260a005e33c40c1e8198290 Marked again: the label was cleared between the first label and comment (issue 873). The operator's word given 10:10.

mesh-tools merged commit c22b58143b into main

2026-10-16 08:13:26 +00:00

mesh-tools deleted branch fix/891-test-levels-and-budgets

2026-10-16 08:13:27 +00:00

mesh-tools referenced this pull request

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

Playbooks 07 and 08: the five rules from the delivery-time audit #375

mesh-tools referenced this issue from a commit

2026-10-16 08:22:46 +00:00

Merge main into feature 57's release branch, so it merges cleanly into main: playbooks 07 and 08 take main's #374 (feature 57)

mesh-tools referenced this pull request

2026-10-16 08:22:54 +00:00