The operator asked why issue state is managed in hq markdown. Playbook 07's write-back had the lead copy "delivered ()" into a design's Milestones table; the issue tracker (resolved, fixed-by) and the delivery records already hold that, and AGENTS.md says cross-cutting views are generated when read, never stored.
Playbook 07: when a milestone's delivery plan is done, its issues are resolved with fixed-by; the design's entry is not changed. Its check now flags a "delivered" in a Milestones entry as a copy.
Design 47: the three copied cells removed (milestones 1, 2 and phase II release 1).
The design's frontmatter status (AGENTS.md assigns it to the doc) and the pause notes on issues stay.
Checks run locally: records, index, cycle, words, each exit 0.
Issue 1038 (playbook 08, small fix).
The operator asked why issue state is managed in hq markdown. Playbook 07's write-back had the lead copy "delivered <date> (<pull requests>)" into a design's Milestones table; the issue tracker (resolved, fixed-by) and the delivery records already hold that, and AGENTS.md says cross-cutting views are generated when read, never stored.
- Playbook 07: when a milestone's delivery plan is done, its issues are resolved with fixed-by; the design's entry is not changed. Its check now flags a "delivered" in a Milestones entry as a copy.
- Design 47: the three copied cells removed (milestones 1, 2 and phase II release 1).
The design's frontmatter status (AGENTS.md assigns it to the doc) and the pause notes on issues stay.
Checks run locally: records, index, cycle, words, each exit 0.
The tracker and the delivery records hold whether a milestone is delivered, when and by what;
a copy in the design's table is a central status kept by hand (AGENTS.md). Design 47 loses its
copied cells.
Deliverynovox/hq@b5d3f2394798 — delivered since 2026-10-17T16:23:56Z
Delivery plan — builds nothing: the change touches no module of the mesh's graph
Transitions
2026-10-17 16:21 (new) → proposed (announced): novox/hq#408's head announced
2026-10-17 16:22 proposed → checked (checked): a verdict names this commit and the trunk's head as its trunk commit
2026-10-17 16:22 checked → ready (accepted): the gate passed or warned, and the repository's own check did not fail
2026-10-17 16:23 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 16:23 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@b5d3f2394798` — **delivered** since 2026-10-17T16:23:56Z
**Delivery plan** — builds nothing: the change touches no module of the mesh's graph
**Transitions**
- 2026-10-17 16:21 (new) → proposed (announced): novox/hq#408's head announced
- 2026-10-17 16:22 proposed → checked (checked): a verdict names this commit and the trunk's head as its trunk commit
- 2026-10-17 16:22 checked → ready (accepted): the gate passed or warned, and the repository's own check did not fail
- 2026-10-17 16:23 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 16:23 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`.
Reviewed by reviewer-1038@shanks: Approved against issue 1038: playbook 07 drops the milestone-date write-back and checks that a Milestones section holds no copied state; design 47 loses exactly its delivered cells. Design 57's leftover copy is issue 1039. Marked through mesh-delivery.mark-ready (novox/hq issue 913).
ready at c753ff068a55f7a6543168581fda627c6a5886af
Reviewed by reviewer-1038@shanks: Approved against issue 1038: playbook 07 drops the milestone-date write-back and checks that a Milestones section holds no copied state; design 47 loses exactly its delivered cells. Design 57's leftover copy is issue 1039. Marked through mesh-delivery.mark-ready (novox/hq issue 913).
mesh-delivery: the label mesh/ready is taken off: no "ready at" comment by a listed account follows both the label's last addition and the last push; the head is now b5d3f23947. Review it and mark that head with mesh-delivery.mark-ready, which writes label and comment in the order the forge counts.
mesh-delivery: the label mesh/ready is taken off: no "ready at" comment by a listed account follows both the label's last addition and the last push; the head is now b5d3f239479828129e120a38f93788885392036d. Review it and mark that head with `mesh-delivery.mark-ready`, which writes label and comment in the order the forge counts.
Reviewed by reviewer-1038@shanks: Approved: b5d3f23 drops design 57's State column and copied delivery text (issue 1039 folded); milestone 3's wait already lives as notes on 680/682/683. Both checks pass at this head. Marked through mesh-delivery.mark-ready (novox/hq issue 913).
ready at b5d3f239479828129e120a38f93788885392036d
Reviewed by reviewer-1038@shanks: Approved: b5d3f23 drops design 57's State column and copied delivery text (issue 1039 folded); milestone 3's wait already lives as notes on 680/682/683. Both checks pass at this head. Marked through mesh-delivery.mark-ready (novox/hq issue 913).
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Issue 1038 (playbook 08, small fix).
The operator asked why issue state is managed in hq markdown. Playbook 07's write-back had the lead copy "delivered ()" into a design's Milestones table; the issue tracker (resolved, fixed-by) and the delivery records already hold that, and AGENTS.md says cross-cutting views are generated when read, never stored.
The design's frontmatter status (AGENTS.md assigns it to the doc) and the pause notes on issues stay.
Checks run locally: records, index, cycle, words, each exit 0.
Delivery
novox/hq@b5d3f2394798— delivered since 2026-10-17T16:23:56ZDelivery plan — builds nothing: the change touches no module of the mesh's graph
Transitions
The commit's note under
refs/notes/mesh-plankeeps every transition:git log --notes=mesh-plan.ready at
c753ff068aReviewed by reviewer-1038@shanks: Approved against issue 1038: playbook 07 drops the milestone-date write-back and checks that a Milestones section holds no copied state; design 47 loses exactly its delivered cells. Design 57's leftover copy is issue 1039. Marked through mesh-delivery.mark-ready (novox/hq issue 913).
mesh-delivery: the label mesh/ready is taken off: no "ready at" comment by a listed account follows both the label's last addition and the last push; the head is now
b5d3f23947. Review it and mark that head withmesh-delivery.mark-ready, which writes label and comment in the order the forge counts.ready at
b5d3f23947Reviewed by reviewer-1038@shanks: Approved:
b5d3f23drops design 57's State column and copied delivery text (issue 1039 folded); milestone 3's wait already lives as notes on 680/682/683. Both checks pass at this head. Marked through mesh-delivery.mark-ready (novox/hq issue 913).