spec: scope receive.unit to origination; trusted replication applies directly
commit
ed7fac0spec: scope receive.unit to origination; trusted replication applies directly
Fetch from a remote whose own receive already admitted the state is replication, not origination: re-verification is an opt-in audit, and the work set remains reconstructible by scan. Merges the replicating machinery authors itself remain origination.
Assisted-by: Claude:claude-fable-5
Reviews
No reviews of this commit yet — record a verdict below.
Start a review
docs/spec/receive.adoc
@@ -15,6 +15,15 @@
Gate evaluation (<<gate.tip-signed>> through <<gate.atomic-cas>>), effect
matching, and enqueue MUST live inside `receive`, above its trait
parameters, never duplicated in a caller.
+This requirement governs origination — proposing new state to a store.
+Replicating refs a trusted remote has already admitted through its own
+`receive` (<<sync.forge-transfer>>) MAY apply them directly: the source's
+gate already judged that state, so re-verification on fetch is an opt-in
+audit rather than an obligation, and the work set stays reconstructible
+by scan regardless (<<receive.reconstructible>>).
+Commits the replicating machinery authors itself — divergence and
+adoption merges (<<gate.same-actor-divergence>>, <<gate.adoption-merge>>)
+— are origination, not replication.
--
[role="requirement", id="receive.proposal-shape"]