Designs 20, 25, 26, 32, 51, 55 and playbook 07: the registry milestone as built (issue 1966) #514

2026-11-04T17:50:36Z

mesh-tools commented

2026-11-04 17:50:36 +00:00

The designs the registry milestone builds (issue 1966), amended from ADR 0605-0631 and the milestone's three review rounds: design 25 §12 (bus state, the bus module's warrant spent once in its read-only state spent, seven first-view tools by ADR 0631), design 26 (where a seat's code goes; one generator), design 32 (a package named in its own language; the read-only state field, a design limit of the review), design 51 (the registries: the shared parts receiver, the 8 GiB incoming cap, kept for a shared digest, the forge removing what it no longer declares; on a fresh mesh the front cannot be raised yet, issue 1152), designs 20 and 55; the glossary; playbook 06 and playbook 07's pin line (the check builds against the group's heads, ADR 0573). The design statuses close with the delivery of the code group (feat/registry-milestone in eight repositories).

Reviewed-by: review-seams-and-tools@shanks at 304ce84cac
Reviewed-by: review-health-and-events@shanks at 304ce84cac

https://claude.ai/code/session_01JG73KJNrH5EgFXMKKYSrig

The designs the registry milestone builds (issue 1966), amended from ADR 0605-0631 and the milestone's three review rounds: design 25 §12 (bus state, the bus module's warrant spent once in its read-only state `spent`, seven first-view tools by ADR 0631), design 26 (where a seat's code goes; one generator), design 32 (a package named in its own language; the read-only state field, a design limit of the review), design 51 (the registries: the shared parts receiver, the 8 GiB incoming cap, `kept` for a shared digest, the forge removing what it no longer declares; on a fresh mesh the front cannot be raised yet, issue 1152), designs 20 and 55; the glossary; playbook 06 and playbook 07's pin line (the check builds against the group's heads, ADR 0573). The design statuses close with the delivery of the code group (feat/registry-milestone in eight repositories). Reviewed-by: review-seams-and-tools@shanks at 304ce84cac1820f04eb56cff622ae6949baec0f5 Reviewed-by: review-health-and-events@shanks at 304ce84cac1820f04eb56cff622ae6949baec0f5 https://claude.ai/code/session_01JG73KJNrH5EgFXMKKYSrig

mesh-tools added 12 commits 2026-11-04 17:50:36 +00:00

Designs 25, 26, 20, playbook 06, glossary: follow ADR 0625 to 0627 for the registry milestone da1c7f30a9

Design 25 § 12.3 now says how the bus module's process really receives a person's
request (its own state requests, the warrant verified by the process itself), the
process account with keeps it holds beside the snapshot account, and that
mesh-broker's events go on the shared stream like every seat's, with the 30-day
history its own stream. Design 26 gains where a seat's code goes: a package per seat,
the seat-set package in mesh-contracts, the seven client packages and the
seat-neutral parts transfer; design 20 and playbook 06 tell a module's author the
same, and the glossary gains client package and seat-set package. mesh-developer
stops at two thirds of its context, as the milestone's agents learned.

Claude-Session: https://claude.ai/code/session_01JG73KJNrH5EgFXMKKYSrig

Design 32: a package is named by its name in its own language, one name across the indexer, builder, registry seat and users aced03a287

Claude-Session: https://claude.ai/code/session_01JG73KJNrH5EgFXMKKYSrig

Design 26: the seat definitions' generator is one program in the Go build module, run by both build modules bdc5ae4fe6

Claude-Session: https://claude.ai/code/session_01JG73KJNrH5EgFXMKKYSrig

mesh-developer: run the repository's own checks whole before reporting a head, and start no agents of your own 901c92a924

Claude-Session: https://claude.ai/code/session_01JG73KJNrH5EgFXMKKYSrig

Designs 25, 51: follow review round 1 of the registry milestone 8f75606167

Design 25 counts seven first-view tools, the indexer's graph granted to the
assigner alone (ADR 0631); the bus module's process wakes on its own decided
and acts on a warrant once (ADR 0259 §6, ADR 0620 §2) instead of a timer, and
the tools watch their request key; §12.7 carries the rows, and its first-view
row, split by an earlier edit, is one row again. Design 51's incoming store
asks the objects template's most, 8 GiB, with no lifetime; the holder drops an
idle transfer itself (ADR 0611 §3).

Claude-Session: https://claude.ai/code/session_01JG73KJNrH5EgFXMKKYSrig

Designs 25, 51: write what review round 1 settled (acted key, ask lifetime, loopback bootstrap, shared idle drop, shared-digest tag, forge account removal) c3d8367b33

Claude-Session: https://claude.ai/code/session_01JG73KJNrH5EgFXMKKYSrig

Design 51: cite ADR 0627 for the holders' shared receiving side, ADR 0611 §3 for the drop 5499c3546b

Claude-Session: https://claude.ai/code/session_01JG73KJNrH5EgFXMKKYSrig

Design 51: name ADR 0627 among its decisions b3a9970ac7

Claude-Session: https://claude.ai/code/session_01JG73KJNrH5EgFXMKKYSrig

Playbook 07: a group's pin is for GOWORK=off; the check builds against the group's heads (ADR 0573), so an older pin is not refused b0a9fa14da

The line said the checker refuses an older commit of the same branch; that refusal was removed as a fault of the check
(issue 1585). Found pinning the registry milestone, where mesh-sdk and mesh-contracts import each other.

Claude-Session: https://claude.ai/code/session_01JG73KJNrH5EgFXMKKYSrig

Designs 25, 51: follow review round 2 (decided via uses, spend record apart, fix checks, genesis gap, kept answer) 571c0a3e68

Claude-Session: https://claude.ai/code/session_01JG73KJNrH5EgFXMKKYSrig

Designs 25, 51: name the spent state; a shared-digest tag is recorded as kept e0a70a468b

Claude-Session: https://claude.ai/code/session_01JG73KJNrH5EgFXMKKYSrig

Designs 32, 25: a state may be read-only to the tools; nats_requests reads spent so

mesh/delivery merged: source.main moved to novox/hq@d4ae72782336

Details

mesh/check being carried to 304ce84cac18 on d4ae72782336 | from 273d608d9faa

304ce84cac

Claude-Session: https://claude.ai/code/session_01JG73KJNrH5EgFXMKKYSrig

mesh-tools commented

2026-11-04 17:50:41 +00:00

Delivery novox/hq@304ce84cac18 — merged since 2026-11-04T18:19:27Z

Source — source.main moved to novox/hq@d4ae727823. Whether it reached the machines is mesh-delivery-view's, derived from source.main, the wants and the haves.

Transitions

2026-11-04 17:50 (new) → proposed (announced): novox/hq#514's head announced
2026-11-04 17:50 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-04 18:19 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.

**Delivery** `novox/hq@304ce84cac18` — **merged** since 2026-11-04T18:19:27Z **Source** — source.main moved to novox/hq@d4ae72782336. Whether it reached the machines is `mesh-delivery-view`'s, derived from `source.main`, the wants and the haves. **Transitions** - 2026-11-04 17:50 (new) → proposed (announced): novox/hq#514's head announced - 2026-11-04 17:50 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-04 18:19 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-tools merged commit d4ae727823 into main

2026-11-04 18:19:24 +00:00

mesh-tools deleted branch docs/registry-milestone-designs

2026-11-04 18:19:25 +00:00

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: novox/hq#514