Core Primitives
These primitives make activation of externally effective computing state a deterministic, verifiable state transition — governed by commit, bound to snapshot context, and evidenced by hash-addressed artefacts.
Execution yields provisional computational state. External visibility and transmissibility remain inhibited until verification gates succeed under a snapshot-bound registry context, and a publication commit records a deterministic transition. The publication wrapper and publication hash become the evidence credential for activation.
- Canonicalisation produces byte-stable representations
- Snapshot resolution binds execution to immutable registry context
- Verification gates enforce constraints and allowlists prior to activation
- Publication commit records a deterministic transition event
- Transmission inhibition release enables controlled dissemination post-commit
- Append-only evidence + export bundle support independent verification & replay
Primitive set
Each primitive is expressed as an infrastructure control surface. Together they separate execution from activation and produce deterministic artefacts that can be independently verified across heterogeneous systems.
Snapshot-bound registry context
Policy, schema, routing, constraints, and identifiers are resolved against an immutable snapshot prior to activation.
Canonicalisation engine
Byte-stable serialisation yields identical bytes for identical logical content, enabling deterministic hashes.
Commit-gated activation
Externally effective activation is prohibited until a deterministic publication commit records the transition event.
Publication wrapper + publication hash
Verified outputs are wrapped with snapshot bindings, canonicalised, and hashed to create a publication hash.
Transmission inhibition
Dissemination interfaces remain inhibited until commit recording is confirmed (fail-closed).
Append-only evidence + export bundles
Commit events and artefacts are stored immutably; export bundles contain sufficient canonical artefacts to recompute hashes offline.
Determinism is treated as a constraint: equivalent canonical inputs + identical snapshot context must produce identical publication hashes. This enables independent verification nodes to validate activation without trusting a single execution environment.
Evidence & replay surface
Evidence is produced as an operational by-product. The export bundle supports verification and replay by recomputation under snapshot-bound context.
- canonical input envelope
- snapshot identifier and registry references
- verification gate outputs and constraint results
- publication wrapper
- publication hash
- commit event metadata recorded in append-only storage
- trace identifiers for cross-node correlation
