novox/hq
13
0
Fork 0
Code Issues Pull Requests 1 Releases Wiki Activity

Playbooks 07 and 04: a milestone is one release, never cut for size or time #401

Merged
mesh-tools merged 2 commits from fix/pb07-a-milestone-is-one-release into main 2026-10-17 11:50:34 +00:00
Conversation 4 Commits 2 Files Changed 3
+34 -30
mesh-tools commented 2026-10-17 11:43:41 +00:00
Member
Copy Link
Copy Source

The operator, 2026-10-17: a milestone is finished whole, brought to main once and released once. Cutting it into steps for size or time adds a review, a merge check, an Approve and a delivery plan of waiting each time, so the fewest cuts is the fastest. Milestones are cut by release order when a design is broken up (playbook 04), so a milestone never needs a second release.

  • Playbook 07: the two-hour split into steps goes; one milestone is one release; the develop bound is the milestone's issues; the reporting layouts name the milestone.
  • Playbook 04: a milestone is one release; milestones are cut by release order (a new manifest word before the catalogue, an SDK change before its users, until design 47's milestones 3 and 6 lift those orders).
  • Design 47: its line that milestones 5 and 6 are split into steps now says each milestone is one release.

Checks: records, index, cycle and words pass locally.

The operator, 2026-10-17: a milestone is finished whole, brought to main once and released once. Cutting it into steps for size or time adds a review, a merge check, an Approve and a delivery plan of waiting each time, so the fewest cuts is the fastest. Milestones are cut by release order when a design is broken up (playbook 04), so a milestone never needs a second release. - Playbook 07: the two-hour split into steps goes; one milestone is one release; the develop bound is the milestone's issues; the reporting layouts name the milestone. - Playbook 04: a milestone is one release; milestones are cut by release order (a new manifest word before the catalogue, an SDK change before its users, until design 47's milestones 3 and 6 lift those orders). - Design 47: its line that milestones 5 and 6 are split into steps now says each milestone is one release. Checks: records, index, cycle and words pass locally.
mesh-tools commented 2026-10-17 11:43:47 +00:00
Author
Member
Copy Link
Copy Source

Merge check at 1dafc359
Judged: head 1dafc359fe7c merged into trunk 0f63a73def93

  • mesh/merge-gate: FAIL — head 1dafc359fe does not merge cleanly into trunk 0f63a73def: in conflict 00-META/process/07-feature-branches.md
  • mesh/repo-check: FAIL — head 1dafc359fe does not merge cleanly into trunk 0f63a73def: in conflict 00-META/process/07-feature-branches.md

Run by the build seat on ace as build-1792237423564159183 (builds --log build-1792237423564159183).

head 1dafc359fe7c does not merge cleanly into trunk 0f63a73def93: in conflict 00-META/process/07-feature-branches.md
**Merge check** at `1dafc359` Judged: head `1dafc359fe7c` merged into trunk `0f63a73def93` - `mesh/merge-gate`: **FAIL** — head 1dafc359fe7c does not merge cleanly into trunk 0f63a73def93: in conflict 00-META/process/07-feature-branches.md - `mesh/repo-check`: **FAIL** — head 1dafc359fe7c does not merge cleanly into trunk 0f63a73def93: in conflict 00-META/process/07-feature-branches.md Run by the build seat on ace as `build-1792237423564159183` (`builds --log build-1792237423564159183`). ``` head 1dafc359fe7c does not merge cleanly into trunk 0f63a73def93: in conflict 00-META/process/07-feature-branches.md ```
mesh-tools commented 2026-10-17 11:43:52 +00:00
Author
Member
Copy Link
Copy Source

Delivery novox/hq@addbd74c3924 — delivered since 2026-10-17T11:50:35Z

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

Transitions

  • 2026-10-17 11:47 (new) → proposed (announced): novox/hq#401's head announced
  • 2026-10-17 11:48 proposed → checked (checked): a verdict names this commit and the trunk's head as its trunk commit
  • 2026-10-17 11:48 checked → ready (accepted): the gate passed or warned, and the repository's own check did not fail
  • 2026-10-17 11:50 ready → published (merged): on the trunk its modules follow: merged there, and its walk opened — or nothing for a walk to move
  • 2026-10-17 11:50 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-delivery:view --> **Delivery** `novox/hq@addbd74c3924` — **delivered** since 2026-10-17T11:50:35Z **Delivery plan** — builds nothing: the change touches no module of the mesh's graph **Transitions** - 2026-10-17 11:47 (new) → proposed (announced): novox/hq#401's head announced - 2026-10-17 11:48 proposed → checked (checked): a verdict names this commit and the trunk's head as its trunk commit - 2026-10-17 11:48 checked → ready (accepted): the gate passed or warned, and the repository's own check did not fail - 2026-10-17 11:50 ready → published (merged): on the trunk its modules follow: merged there, and its walk opened — or nothing for a walk to move - 2026-10-17 11:50 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-17 11:45:19 +00:00
Author
Member
Copy Link
Copy Source

Merge check at 4872ccdb
Judged: head 4872ccdb6b3b merged into trunk 0f63a73def93

  • mesh/merge-gate: FAIL — head 4872ccdb6b does not merge cleanly into trunk 0f63a73def: in conflict 00-META/process/04-build-handoff.md, 00-META/process/07-feature-branches.md
  • mesh/repo-check: FAIL — head 4872ccdb6b does not merge cleanly into trunk 0f63a73def: in conflict 00-META/process/04-build-handoff.md, 00-META/process/07-feature-branches.md

Run by the build seat on shanks as build-1792237516199255860 (builds --log build-1792237516199255860).

head 4872ccdb6b3b does not merge cleanly into trunk 0f63a73def93: in conflict 00-META/process/04-build-handoff.md, 00-META/process/07-feature-branches.md
**Merge check** at `4872ccdb` Judged: head `4872ccdb6b3b` merged into trunk `0f63a73def93` - `mesh/merge-gate`: **FAIL** — head 4872ccdb6b3b does not merge cleanly into trunk 0f63a73def93: in conflict 00-META/process/04-build-handoff.md, 00-META/process/07-feature-branches.md - `mesh/repo-check`: **FAIL** — head 4872ccdb6b3b does not merge cleanly into trunk 0f63a73def93: in conflict 00-META/process/04-build-handoff.md, 00-META/process/07-feature-branches.md Run by the build seat on shanks as `build-1792237516199255860` (`builds --log build-1792237516199255860`). ``` head 4872ccdb6b3b does not merge cleanly into trunk 0f63a73def93: in conflict 00-META/process/04-build-handoff.md, 00-META/process/07-feature-branches.md ```
jschoubben added 2 commits 2026-10-17 11:47:50 +00:00
Playbooks 07 and 04: a milestone is one release, never cut for size or time; milestones are cut by release order (the operator, 2026-10-17) 6bf18062c4
Playbook 04 and design 47: the milestone is one release, not a feature step (review of #401)
mesh/merge-gate head addbd74c3924 merged into trunk 0f63a73def93 — pass: the change touches no module of the mesh's graph
Details
mesh/repo-check head addbd74c3924 merged into trunk 0f63a73def93 — pass: its merge-check.sh passed
Details
mesh/delivery delivered
Details
addbd74c39
jschoubben force-pushed fix/pb07-a-milestone-is-one-release from 4872ccdb6b to addbd74c39 2026-10-17 11:47:50 +00:00 Compare
mesh-tools added the mesh/ready label 2026-10-17 11:48:48 +00:00
mesh-tools commented 2026-10-17 11:48:48 +00:00
Author
Member
Copy Link
Copy Source

ready at addbd74c39

Reviewed by review-events@shanks: Rebased onto main 0f63a73: playbooks 04 and 07 and design 47 say the one-release rule consistently, main's additions kept; no step or two-hour rule left; both checks pass. Marked through mesh-delivery.mark-ready (novox/hq issue 913).

ready at addbd74c3924eedf418c8df345a8634b2b2d7213 Reviewed by review-events@shanks: Rebased onto main 0f63a73: playbooks 04 and 07 and design 47 say the one-release rule consistently, main's additions kept; no step or two-hour rule left; both checks pass. Marked through mesh-delivery.mark-ready (novox/hq issue 913).
mesh-tools merged commit 2b04a5f0a1 into main 2026-10-17 11:50:34 +00:00
mesh-tools deleted branch fix/pb07-a-milestone-is-one-release 2026-10-17 11:50:34 +00:00
Sign in to join this conversation.
Reviewers
No Reviewers
Labels
Clear labels
mesh/ready
Reviewed and ready: mesh-delivery merges at the marked head once its checks pass (hq ADR 0364)
No labels mesh/ready
Milestone
No items
No Milestone
Assignees
Clear assignees
agent-ace agent-g14 agent-novox agent-shanks jschoubben mesh-tools miel.truyen nox-agent
No Assignees
2 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: novox/hq#401