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
14 Commits
Author SHA1 Message Date
jschoubben 2132bb711d 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
mesh/check being carried to 2132bb711d4e on 5235c0063024 | from f9bdd3b1d1ce
Claude-Session: https://claude.ai/code/session_01NcbgfGKaxw984XyAPfLm4h
2026-11-12 11:55:00 +01:00
jschoubben f74f9b19be Design 47 G §716: the gate keeps a group's members and their bases from the announcement
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
2026-11-12 11:54:16 +01:00
jschoubben 3c40a6e6c8 A-280: the code name in a code span
Claude-Session: https://claude.ai/code/session_01NcbgfGKaxw984XyAPfLm4h
2026-11-12 11:47:35 +01:00
jschoubben 77379f62ce Answer A-280: a bundle's findings follow its membership's finding-events stream
Claude-Session: https://claude.ai/code/session_01NcbgfGKaxw984XyAPfLm4h
2026-11-12 11:47:17 +01:00
jschoubben 15d73fe09c A-279's form that stands: the base is kept on the merges entry the Approve makes, copied at take-in
Claude-Session: https://claude.ai/code/session_01NcbgfGKaxw984XyAPfLm4h
2026-11-12 11:42:50 +01:00
jschoubben b9f7ff6054 Correct A-279 again: the base comes from the git seat's pull-updated, kept on the pull's record entry
Claude-Session: https://claude.ai/code/session_01NcbgfGKaxw984XyAPfLm4h
2026-11-12 11:40:20 +01:00
jschoubben 3d4691c544 Correct A-279: a member's base is read from its delivery, which the gate already keeps
Claude-Session: https://claude.ai/code/session_01NcbgfGKaxw984XyAPfLm4h
2026-11-12 11:38:26 +01:00
jschoubben 6fc3ccda4b Answer A-279: a member's base is its pull request's base from the forge message
Claude-Session: https://claude.ai/code/session_01NcbgfGKaxw984XyAPfLm4h
2026-11-12 11:37:27 +01:00
jschoubben efcc065f8f Answer A-278: the seat-definition function lives once in mesh-sdk
Claude-Session: https://claude.ai/code/session_01NcbgfGKaxw984XyAPfLm4h
2026-11-12 11:28:25 +01:00
jschoubben f9aa43bf09 Answer A-277 in the glossary's word: the manifest validator
Claude-Session: https://claude.ai/code/session_01NcbgfGKaxw984XyAPfLm4h
2026-11-12 11:26:13 +01:00
jschoubben 5266949a59 Answer A-277: the approvals state's 64 MiB is a declared max-mib the judge bounds
Claude-Session: https://claude.ai/code/session_01NcbgfGKaxw984XyAPfLm4h
2026-11-12 11:25:55 +01:00
jschoubben 3631a151a3 Answer A-276: a pipeline-waits finding names its awaited fingerprint in its evidence
Claude-Session: https://claude.ai/code/session_01NcbgfGKaxw984XyAPfLm4h
2026-11-12 11:19:18 +01:00
jschoubben e98e675673 Answer A-275: the node-engine reads invokes with the SDK's one reader
Claude-Session: https://claude.ai/code/session_01NcbgfGKaxw984XyAPfLm4h
2026-11-12 11:06:14 +01:00
jschoubben c94a65f2d8 Answer A-274: the finding writer takes its subjects from the part's own binding
Claude-Session: https://claude.ai/code/session_01NcbgfGKaxw984XyAPfLm4h
2026-11-12 11:00:39 +01:00