Design 47: a member naming the SDK member's head is proven by its own merge check (ADR 0402's review)
mesh/merge-gate head e7854a31a6a9 merged into trunk f9c240a957b8 — pass: the change touches no module of the mesh's graph
mesh/repo-check head e7854a31a6a9 merged into trunk f9c240a957b8 — pass: its merge-check.sh passed
mesh/delivery superseded: a newer head of the same pull request

This commit is contained in:
2026-10-16 23:41:37 +02:00
parent 8bfb11da2c
commit e7854a31a6
@@ -190,7 +190,8 @@ would settle it (ADR 0249 §4).
**The SDK by version.** A Go module names the SDK by its released version and fetches it from the mesh's forge,
checked against its recorded checksum; vendored copies go. Inside a group, a member may name the SDK member's
head, and the group's composed check proves they build and compose together (ADR 0402 §2).
head: its own merge check builds it with the SDK member read beside it, and the head stays fetchable after the
group merges because the forge keeps every pull request's head (ADR 0402 §2, §3).
## Checks