Batches 6 and 7 of milestone G's develop answers (playbook 02, answering design questions), with three rounds of the review by architectural domain and their fixes.
New parts G-16 (§587-§594), G-17 (§610-§676) and G-18 (§677-§705); amended G-4, G-8, G-9, G-12, G-14, G-15, G.md and the glossary's recovery-module entry.
The operator's answers, 2026-11-11 at lead-47's terminal: O-1 the builder publishes unpublished versions again by itself (ADR 0674, accepted); O-2 to O-5 (delivery parts' old sections, gitea/distribution entries, the gate's moved keys, S-51); O-6 no named caller lists, every verb its class default; O-7 a protected stream's snapshot is never handed out, only restored in place by the bus module (ADR 0675, proposed); O-8 a module's call of a marked verb is one call with a gate before its running (ADR 0676, proposed); O-9 a delivery waits while an outside cause is named and asks the operator after 30 minutes (record to come, ADR 0241 §25).
Develop questions D-1 to D-49 answered as design lines (internal form).
Review by architectural domain: round 1 on d004b90e (all four), round 2 on 9381cde1 (security-and-upgrade, seams-and-tools), round 3 on 9381cde1..ccc8a4c (all four); every must fixed in 9381cde1, 51c6dcb, 350d05b/ccc8a4c and 414490f as the reviewers proposed. e6c8bb1 (O-9, §705, and two mesh-host places in §428) came after round 3 and has had no review by domain; it is small and its record goes through the knowledge base's review.
The main file's size (249 KB, over 80 KB) predates this branch and is not fixed here.
go test ./... at the root passes.
Record clauses touched (carried by ADR 0675, ADR 0676, the O-9 record and research 087's one decision): ADR 0666 §20; ADR 0672 §1, §3, §7, §8, §10; ADR 0626 §1, §3; ADR 0436 §3; ADR 0286 §7, §8, §13, §24, §30, §37, §47; ADR 0241 §25.
Reviewed-by: review-security-and-upgrade, review-seams-and-tools, review-running-and-testing, review-health-and-events (for lead-47@shanks) at ccc8a4c; fixes by their proposals at 414490f; e6c8bb15d1 not reviewed by domain
Batches 6 and 7 of milestone G's develop answers (playbook 02, answering design questions), with three rounds of the review by architectural domain and their fixes.
- New parts G-16 (§587-§594), G-17 (§610-§676) and G-18 (§677-§705); amended G-4, G-8, G-9, G-12, G-14, G-15, G.md and the glossary's recovery-module entry.
- The operator's answers, 2026-11-11 at lead-47's terminal: O-1 the builder publishes unpublished versions again by itself (ADR 0674, accepted); O-2 to O-5 (delivery parts' old sections, gitea/distribution entries, the gate's moved keys, S-51); O-6 no named caller lists, every verb its class default; O-7 a protected stream's snapshot is never handed out, only restored in place by the bus module (ADR 0675, proposed); O-8 a module's call of a marked verb is one call with a gate before its running (ADR 0676, proposed); O-9 a delivery waits while an outside cause is named and asks the operator after 30 minutes (record to come, ADR 0241 §25).
- Develop questions D-1 to D-49 answered as design lines (internal form).
- Review by architectural domain: round 1 on d004b90e (all four), round 2 on 9381cde1 (security-and-upgrade, seams-and-tools), round 3 on 9381cde1..ccc8a4c (all four); every must fixed in 9381cde1, 51c6dcb, 350d05b/ccc8a4c and 414490f as the reviewers proposed. e6c8bb1 (O-9, §705, and two mesh-host places in §428) came after round 3 and has had no review by domain; it is small and its record goes through the knowledge base's review.
- The main file's size (249 KB, over 80 KB) predates this branch and is not fixed here.
- `go test ./...` at the root passes.
Record clauses touched (carried by ADR 0675, ADR 0676, the O-9 record and research 087's one decision): ADR 0666 §20; ADR 0672 §1, §3, §7, §8, §10; ADR 0626 §1, §3; ADR 0436 §3; ADR 0286 §7, §8, §13, §24, §30, §37, §47; ADR 0241 §25.
Reviewed-by: review-security-and-upgrade, review-seams-and-tools, review-running-and-testing, review-health-and-events (for lead-47@shanks) at ccc8a4c; fixes by their proposals at 414490f; e6c8bb15d1a74930de90f10cebd6b5dca39ba410 not reviewed by domain
https://claude.ai/code/session_01JG73KEq4zoDfM9WtYpcQgZ
Eight questions met in the join and develop after batch 5 are written as
lines §587 to §594 of a new part G-16, each of internal form within the
records and lines it cites: the ledger's upkeep calls' shapes, publishing
again every unpublished reserved version, a whole read of a module's build
keys, one event of a node's capabilities (manifest-reads-changed, ADR 0618
§4, ADR 0673 §2), the object stores' caps, the gate's merge path from G's
delivery, the gate's dropped Approve-per-merge reads, and the manifest
readers on the catalog graph entry. §568 now cites ADR 0673 in place of
"number to come". The automatic publish on a registry holder's running is
left to the operator: no record decides it.
Claude-Session: https://claude.ai/code/session_01JG73KEq4zoDfM9WtYpcQgZ
Design 47 G §614 answers develop's D-5 and D-12 ahead of the rest of
batch 7: the reader through meshcatalogclient on the part's one views
reader, the branches from the registrations or the gate's source, the
manifest entries each part declares, an older build's entry asked once by
fingerprint, a none-yet branch read as empty, the first pass after every
first view, and a dropped branch's findings cleared.
Claude-Session: https://claude.ai/code/session_01JG73KEq4zoDfM9WtYpcQgZ
Batch 7 of design 47 G is written as §610 to §676 in G-17 (§614 was
committed ahead): the operator's answers on callers by class, on the five
parts that move only their findings, on the forge and image registry's
other entries, and on the gate's kept data; the refreshed build maps'
questions of mesh-tools, mesh-host and mesh-networking, mesh-sdk,
mesh-delivery, mesh-catalog and mesh-contracts; and develop's D-1 to D-15.
§588 now carries the operator's yes to publishing again on an event, its
record to come. Lines the answers correct are corrected in place, in G and
in design 34 every-event and design 46 7-approval-mark, which ship in G's
release. The main file now lists ADR 0668 and ADR 0672.
Claude-Session: https://claude.ai/code/session_01JG73KEq4zoDfM9WtYpcQgZ
The four reviewers' musts on §587 to §676 are written into the lines they
name: the snapshot sent on its call's own session with its digest
recorded, warrants matched to the current ask and its digest, the gate's
copy at every start, the recovery module's hand tools as seat verbs, the
catalog half's pending entries and the node-engine following no branch,
the keeper following a moved finding stream, the builder's republish queue
and its toolchain wait, and more. The operator's answer of about 16:10 CET
ends every named caller list: every verb takes its class's default, and a
module's process that calls a marked verb carries the operator's warrant
for that one call (§677). Develop's D-16 to D-18 are §678 to §680, in a new
part G-18 so that G-17 stays under 60 KB.
Claude-Session: https://claude.ai/code/session_01JG73KEq4zoDfM9WtYpcQgZ
The holder of a marked verb a process serves now asks, checks and claims
the warrant itself, under its own name and in its own state, and a holder
of before G is never reached (§677). The keeper's snapshot is sent by the
keeper's own verb and a protected stream's never leaves it, restored in
place (§681, the operator's O-7). The recovery module's hand verbs get
their fields, answers and asker (§682); the node-engine keeps its entries
on its node (§683); the grants part composes a want's account before its
first views, so no cycle stands (§684). The republish queue is kept on the
bus, §588 rests on ADR 0674, and D-20 to D-25 are §685 to §690.
Claude-Session: https://claude.ai/code/session_01JG73KEq4zoDfM9WtYpcQgZ
The operator's O-8: the holder keeps a module's call, asks, and runs that
same call on the Approve; the caller hears the end on its own subject of
the seat's gated-ended and never calls again, while a person through the
tool runner keeps ADR 0286 §37's path for now (§677, resting on a record
to come). Develop's D-26 to D-31 and the reader release's order are §691
to §697, with §668, §682 and §554 corrected to them.
Claude-Session: https://claude.ai/code/session_01JG73KEq4zoDfM9WtYpcQgZ
Every must of the last review round is written as its reviewer proposed or
as the narrowest line: the gated call keyed by its own call id with one ask
per act across instances, the holder granted from its want, the keeper's
protected restore on a standing grant with a cancel and its partial stream
removed, the node-engine's kept entries in its composition state, the
indexer ordered before the parts that ask its entries, and G's own deletions
moving the gate's copy mark. Develop's D-33 to D-49 are §698 to §704.
Claude-Session: https://claude.ai/code/session_01JG73KEq4zoDfM9WtYpcQgZ
Deliverynovox/hq@e6c8bb15d1a7 — merged since 2026-11-11T20:09:08Z
Source — source.main moved to novox/hq@60e99f3875. Whether it reached the machines is mesh-delivery-view's, derived from source.main, the wants and the haves.
Transitions
2026-11-11 20:04 (new) → proposed (announced): novox/hq#552's head announced
2026-11-11 20:04 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-11 20:09 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@e6c8bb15d1a7` — **merged** since 2026-11-11T20:09:08Z
**Source** — source.main moved to novox/hq@60e99f38759b. Whether it reached the machines is `mesh-delivery-view`'s, derived from `source.main`, the wants and the haves.
**Transitions**
- 2026-11-11 20:04 (new) → proposed (announced): novox/hq#552's head announced
- 2026-11-11 20:04 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-11 20:09 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.
Batches 6 and 7 of milestone G's develop answers (playbook 02, answering design questions), with three rounds of the review by architectural domain and their fixes.
d004b90e(all four), round 2 on9381cde1(security-and-upgrade, seams-and-tools), round 3 on 9381cde1..ccc8a4c (all four); every must fixed in9381cde1,51c6dcb, 350d05b/ccc8a4c and414490fas the reviewers proposed.e6c8bb1(O-9, §705, and two mesh-host places in §428) came after round 3 and has had no review by domain; it is small and its record goes through the knowledge base's review.go test ./...at the root passes.Record clauses touched (carried by ADR 0675, ADR 0676, the O-9 record and research 087's one decision): ADR 0666 §20; ADR 0672 §1, §3, §7, §8, §10; ADR 0626 §1, §3; ADR 0436 §3; ADR 0286 §7, §8, §13, §24, §30, §37, §47; ADR 0241 §25.
Reviewed-by: review-security-and-upgrade, review-seams-and-tools, review-running-and-testing, review-health-and-events (for lead-47@shanks) at ccc8a4c; fixes by their proposals at 414490f;
e6c8bb15d1not reviewed by domainhttps://claude.ai/code/session_01JG73KEq4zoDfM9WtYpcQgZ
Delivery
novox/hq@e6c8bb15d1a7— merged since 2026-11-11T20:09:08ZSource — source.main moved to novox/hq@60e99f3875. 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.