Design 47 milestone G, from the developers' questions in join 11 (implement-the-design):
§717 (hq-design-writer, reviewed by the lead): the status view holds the seat mesh-delivery-view (ADR 0540 §1), with one state answers offered as a view; the assigner's asks and wants are views of mesh-wants (ADR 0567 §6); the teller and the status view name them by seat; a follower hears its seat's holder from the seat-holders view (A-295), reached through the catalog half it already follows (§614), with no timer; glossary entry mesh-delivery-view.
A-294: mesh-wants' and mesh-builds' step keeps no token; step-progress names the one caller its seat's definition lists (corrects A-267).
A-295: a callers list names a seat (seat:<seat>), resolved in the SDK from the seat-holders view.
A-296: seat forms in the manifests; a part names its own buckets from its credential's module.
A-297: the runner's step ask id takes the usual ask id form, repeatable per placement.
Design 47 milestone G, from the developers' questions in join 11 (implement-the-design):
- §717 (hq-design-writer, reviewed by the lead): the status view holds the seat `mesh-delivery-view` (ADR 0540 §1), with one state `answers` offered as a view; the assigner's `asks` and `wants` are views of `mesh-wants` (ADR 0567 §6); the teller and the status view name them by seat; a follower hears its seat's holder from the seat-holders view (A-295), reached through the catalog half it already follows (§614), with no timer; glossary entry `mesh-delivery-view`.
- A-294: mesh-wants' and mesh-builds' `step` keeps no token; step-progress names the one caller its seat's definition lists (corrects A-267).
- A-295: a callers list names a seat (`seat:<seat>`), resolved in the SDK from the seat-holders view.
- A-296: seat forms in the manifests; a part names its own buckets from its credential's module.
- A-297: the runner's step ask id takes the usual ask id form, repeatable per placement.
hq checks (`go test ./...`) pass on this head.
https://claude.ai/code/session_01NcbgfGKaxw984XyAPfLm4h
Developer J27 met, building A-210, a status view that claims no seat and an
assigner holding two seats, both followed by the teller by module name. ADR
0540 §1 already names the seat mesh-delivery-view; G defines it with its one
view, puts the assigner's asks and wants on mesh-wants, and has a follower find
the holder in the background so no start stops for it.
Claude-Session: https://claude.ai/code/session_01NcbgfGKaxw984XyAPfLm4h
A seat's view is said on its holder's module subject, so a follower must know
the holder; asking for it every 5 seconds was polling and kept a holder that
moved. It now follows the seat-holders view as A-295's holder function does,
reached from the catalog half's claim, and re-follows when the holder changes.
Claude-Session: https://claude.ai/code/session_01NcbgfGKaxw984XyAPfLm4h
Deliverynovox/hq@b03f5193b8c4 — merged since 2026-11-12T17:59:28Z
Source — source.main moved to novox/hq@023a355cdb. Whether it reached the machines is mesh-delivery-view's, derived from source.main, the wants and the haves.
Transitions
2026-11-12 17:55 (new) → proposed (announced): novox/hq#588's head announced
2026-11-12 17:55 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-11-12 17:59 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-delivery:view -->
**Delivery** `novox/hq@b03f5193b8c4` — **merged** since 2026-11-12T17:59:28Z
**Source** — source.main moved to novox/hq@023a355cdb2c. Whether it reached the machines is `mesh-delivery-view`'s, derived from `source.main`, the wants and the haves.
**Transitions**
- 2026-11-12 17:55 (new) → proposed (announced): novox/hq#588's head announced
- 2026-11-12 17:55 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-11-12 17:59 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`.
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.
Design 47 milestone G, from the developers' questions in join 11 (implement-the-design):
mesh-delivery-view(ADR 0540 §1), with one stateanswersoffered as a view; the assigner'sasksandwantsare views ofmesh-wants(ADR 0567 §6); the teller and the status view name them by seat; a follower hears its seat's holder from the seat-holders view (A-295), reached through the catalog half it already follows (§614), with no timer; glossary entrymesh-delivery-view.stepkeeps no token; step-progress names the one caller its seat's definition lists (corrects A-267).seat:<seat>), resolved in the SDK from the seat-holders view.hq checks (
go test ./...) pass on this head.https://claude.ai/code/session_01NcbgfGKaxw984XyAPfLm4h
Delivery
novox/hq@b03f5193b8c4— merged since 2026-11-12T17:59:28ZSource — source.main moved to novox/hq@023a355cdb. Whether it reached the machines is
mesh-delivery-view's, derived fromsource.main, the wants and the haves.Transitions
The commit's note under
refs/notes/mesh-plankeeps every transition of this change up to its merge:git log --notes=mesh-plan.