Execution Model
Canonical payload → deterministic state root → portable artifact.
Run through the execution interface.
Authority Stack
The system establishes a clear hierarchy of truth.
Authority Stack
If mismatch occurs, recomputation from canonical payload governs. State root resolves disputes.
Determinism Invariants
Determinism Rules
- No wall-clock time
- No randomness
- No insertion-order ambiguity
- No runtime entropy
- Pure function boundary
Guarantee
Identical structured input + identical branch context = identical state root.
Branch Isolation
Each branch operates within its own state scope.
- Own state scope
- No cross-branch memory
- No shared mutable state
- Own state scope
- No cross-branch memory
- No shared mutable state
- Own state scope
- No cross-branch memory
- No shared mutable state
Isolation is structural, not conventional.
Artifact Lifecycle
From payload lock to audit retrieval.
Reproducibility Check
Verify deterministic computation from canonical payload.
Reproducibility Check
Verification interface. Protocol remains server-authoritative.
Uses protocol core: canonicalize() + hashCanonicalSync()
Security Properties
Once computed, state roots cannot be modified without detection.
Verification Records are indexed and retrievable for compliance review.
Verification Records are self-contained and verifiable across systems.