Commit-Gated · Snapshot-Bound · Deterministic
Deterministic Control Architecture
Norcrest defines a control architecture in which externally effective computing state is not produced by execution — it emerges only after verification and a deterministic commit-bound state transition.
This architecture underpins Kayllo and is delivered in Kayllo Control for AI agents, robotics, and autonomous systems.
End-to-end flow
- Ingress & canonicalisation — inputs normalised into deterministic form
- Snapshot resolution — all policy, schema, and routing bound to immutable context
- Deterministic evaluation — constraints and routing applied
- Execution — produces provisional state (non-authoritative)
- Verification gates — enforce eligibility for activation
- Commit + wrapper hashing — transition identity created
- Append-only recording — transition immutably stored
- Activation release — external effect enabled post-commit
- Export bundle — enables independent verification
Core architectural properties
Execution isolation
Outputs remain non-authoritative until commit.
Effect: no premature external action
Deterministic state
Identical inputs + snapshot produce identical identities.
Effect: replayable systems
Verification-first
External effect requires passing verification gates.
Effect: control before action
Why this architecture is different
Typical AI architecture
- Execution → immediate action
- Monitoring after execution
- Logs as evidence
- Trust tied to system
Deterministic control architecture
- Execution → verification → commit → action
- Control before external effect
- Evidence produced during flow
- Verification independent of system
Where this architecture is applied
From architecture to system
Norcrest defines the architecture. Kayllo implements it. Kayllo Control delivers it.