Deterministic Control Primitives
Norcrest defines a set of deterministic control primitives that make activation of externally effective computing state an explicit, verifiable state transition — rather than a side effect of execution.
These primitives underpin Kayllo as the technology layer and Kayllo Control as the product implementation for AI agent control, robot control systems, and drone command and control.
Primitive set
Snapshot-bound registry context
All evaluation binds to immutable policy, schema, and routing state.
Canonicalisation
Byte-stable representations ensure identical inputs always produce identical hashes.
Commit-gated activation
External effect is prohibited until a deterministic transition is recorded.
Canonical wrapper + identity
Outputs are wrapped, bound to snapshot context, and hashed.
Transmission inhibition
External dissemination is blocked until commit confirmation.
Append-only evidence
All transitions are immutably recorded for verification.
Why primitives matter
Typical systems
- Execution directly causes external effects
- Logs used after the fact
- No enforced determinism
- Trust = runtime system
Deterministic control systems
- External effect requires commit
- Evidence produced during execution
- Determinism enforced
- Verification independent of runtime
Where these primitives are applied
From primitives to product
Norcrest develops the primitives. Kayllo expresses them as system architecture. Kayllo Control delivers them in production.