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

Design 47 G: §716 (a group's members and bases before the take-in) and the lead's answers A-274 to A-280 #577

Merged
mesh-tools merged 14 commits from design/47-G-lead-answers-10 into main 2026-11-12 12:05:40 +00:00
Conversation 1 Commits 14 Files Changed 2
+79 -4
mesh-tools commented 2026-11-12 10:55:48 +00:00
Member
Copy Link
Copy Source
  • §716 (G-21), by the hq-design-writer: the gate keeps a group's members and each member's base from the pull request's announcement, in its states deliveries and groups, heard on the seat git's pull-updated, pull-merged and pull-closed; the take-in copies the base onto RecordPull; groups answers from records and the group key together; no new state, no timer (ADR 0666 §13, ADR 0656 §7).
  • A-274 to A-280 (G-22): the finding writer's subjects from the part's binding; the node-engine reads invokes with the SDK's reader; a pipeline-waits finding names its awaited fingerprint; the approvals state's max-mib; one seat-definition function in mesh-sdk; A-279 (pointing to §716); a bundle's findings follow its membership.

hq's checks pass at the head.

https://claude.ai/code/session_01NcbgfGKaxw984XyAPfLm4h

- §716 (G-21), by the hq-design-writer: the gate keeps a group's members and each member's base from the pull request's announcement, in its states deliveries and groups, heard on the seat git's pull-updated, pull-merged and pull-closed; the take-in copies the base onto RecordPull; groups answers from records and the group key together; no new state, no timer (ADR 0666 §13, ADR 0656 §7). - A-274 to A-280 (G-22): the finding writer's subjects from the part's binding; the node-engine reads invokes with the SDK's reader; a pipeline-waits finding names its awaited fingerprint; the approvals state's max-mib; one seat-definition function in mesh-sdk; A-279 (pointing to §716); a bundle's findings follow its membership. hq's checks pass at the head. https://claude.ai/code/session_01NcbgfGKaxw984XyAPfLm4h
mesh-tools added 14 commits 2026-11-12 10:55:48 +00:00
Answer A-274: the finding writer takes its subjects from the part's own binding c94a65f2d8 
Claude-Session: https://claude.ai/code/session_01NcbgfGKaxw984XyAPfLm4h
Answer A-275: the node-engine reads invokes with the SDK's one reader e98e675673 
Claude-Session: https://claude.ai/code/session_01NcbgfGKaxw984XyAPfLm4h
Answer A-276: a pipeline-waits finding names its awaited fingerprint in its evidence 3631a151a3 
Claude-Session: https://claude.ai/code/session_01NcbgfGKaxw984XyAPfLm4h
Answer A-277: the approvals state's 64 MiB is a declared max-mib the judge bounds 5266949a59 
Claude-Session: https://claude.ai/code/session_01NcbgfGKaxw984XyAPfLm4h
Answer A-277 in the glossary's word: the manifest validator f9aa43bf09 
Claude-Session: https://claude.ai/code/session_01NcbgfGKaxw984XyAPfLm4h
Answer A-278: the seat-definition function lives once in mesh-sdk efcc065f8f 
Claude-Session: https://claude.ai/code/session_01NcbgfGKaxw984XyAPfLm4h
Answer A-279: a member's base is its pull request's base from the forge message 6fc3ccda4b 
Claude-Session: https://claude.ai/code/session_01NcbgfGKaxw984XyAPfLm4h
Correct A-279: a member's base is read from its delivery, which the gate already keeps 3d4691c544 
Claude-Session: https://claude.ai/code/session_01NcbgfGKaxw984XyAPfLm4h
Correct A-279 again: the base comes from the git seat's pull-updated, kept on the pull's record entry b9f7ff6054 
Claude-Session: https://claude.ai/code/session_01NcbgfGKaxw984XyAPfLm4h
A-279's form that stands: the base is kept on the merges entry the Approve makes, copied at take-in 15d73fe09c 
Claude-Session: https://claude.ai/code/session_01NcbgfGKaxw984XyAPfLm4h
Answer A-280: a bundle's findings follow its membership's finding-events stream 77379f62ce 
Claude-Session: https://claude.ai/code/session_01NcbgfGKaxw984XyAPfLm4h
A-280: the code name in a code span 3c40a6e6c8 
Claude-Session: https://claude.ai/code/session_01NcbgfGKaxw984XyAPfLm4h
Design 47 G §716: the gate keeps a group's members and their bases from the announcement f74f9b19be 
Before any take-in the gate held no group: its records open at the take-in, and from G it writes
`merges` no more, so the forge bridge's §715 read of each member's base through `groups` had
nothing to answer from. ADR 0666 §13 has the gate form the group; §716 keeps it in the states
`deliveries` and `groups` the gate already holds (§613), heard on the seat git's pull-updated,
pull-merged and pull-closed, and says who deletes each key and how `groups` answers.
A-236 now points to it, and A-279 is carried over from the answers branch in the form §716 makes
it, its Approve-entry form dropped.

Claude-Session: https://claude.ai/code/session_01NcbgfGKaxw984XyAPfLm4h
Merge §716 (group members before take-in) into the lead answers; A-279 in its form after §716
mesh/delivery merged: source.main moved to novox/hq@5235c0063024
Details
mesh/check being carried to 2132bb711d4e on 5235c0063024 | from f9bdd3b1d1ce
2132bb711d 
Claude-Session: https://claude.ai/code/session_01NcbgfGKaxw984XyAPfLm4h
mesh-tools commented 2026-11-12 10:55:50 +00:00
Author
Member
Copy Link
Copy Source

Delivery novox/hq@2132bb711d4e — merged since 2026-11-12T12:05:43Z

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

Transitions

  • 2026-11-12 10:55 (new) → proposed (announced): novox/hq#577's head announced
  • 2026-11-12 10: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 12:05 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@2132bb711d4e` — **merged** since 2026-11-12T12:05:43Z **Source** — source.main moved to novox/hq@5235c0063024. Whether it reached the machines is `mesh-delivery-view`'s, derived from `source.main`, the wants and the haves. **Transitions** - 2026-11-12 10:55 (new) → proposed (announced): novox/hq#577's head announced - 2026-11-12 10: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 12:05 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 5235c00630 into main 2026-11-12 12:05:40 +00:00
mesh-tools deleted branch design/47-G-lead-answers-10 2026-11-12 12:05:40 +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
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
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: novox/hq#577