06 TRUST

How every delivery
stays checked.

For technical reviewers. The depth behind our promise that nothing ships unchecked: how oversight is built into the way we work.

POLICY PRECEDES INFERENCE
06·1 RULES AND AI, SIDE BY SIDE

Rules handle what must not vary.
AI handles what benefits from intelligence.

CORE / RULE-BASED

Deterministic Core.

For consequential actions with zero-error tolerance. Rule-based execution. No AI override permitted.

RULESLEDGERQUORUMSTATE
BOUNDED / PROBABILISTIC

Probabilistic AI.

For predictions, risk flags, draft content always human-reviewable, never autonomously executed.

RISK FLAGSDRAFTSSCORINGTRIAGE

The two operate side by side under the same governance kernel. Humans remain the final authority on consequential action.

HASH-CHAINED · REPLAY-SAFE · AUDIT-READY
06·2 THE STACK

Four addressable layers. One enforcement contract.

quaicu_kernel ▸ enforcement_contract.app CONTRACT · NON-BYPASSABLE
4 Application Layer APP

The platforms and workflows we build and support for you, across web and mobile. One governance foundation beneath, reused on every engagement.

3 Rule Engine RULE · NO SILENT OVERRIDES

Strict logic. Deterministic execution. No silent overrides. Where your non-negotiables are written, and read on every action.

2 AI Agents AI · GUARDRAILED · DRAFT-ONLY

Bounded intelligence. Probabilistic output. Always reviewable, never autonomous. Agents propose; the kernel decides what gets to run.

1 Trust Layer TRUST · HASH-CHAIN · TENANT-ISOLATED

On-premise, private cloud, or hybrid. Tenant-isolated data storage. Identity management. Encryption at rest and in transit. Immutable audit ledger.

IDP VAULT ENCRYPTION HASH-CHAIN REPLAY
RUNNING LAYERS 04 CONTRACT NON-BYPASSABLE HALT FAIL-CLOSED AUDIT CONTINUOUS STATE NOMINAL
NEVER FAILS SILENTLY
06·3 ENFORCEMENT, LAYER BY LAYER

Every state change in everything we deliver passes through a non-bypassable enforcement model.

01
HITL Checkpoints
Consequential actions await a named human approver. No silent autonomy.
02
State Machine Validation
Transitions are declared, typed, and validated. Illegal states are unreachable.
03
Role-Based Access Control
Authority is granted, scoped, and revocable. Privilege escalation is logged.
04
Approval Workflows
Multi-party where you require it. Single-party never assumed.
05
Policy Engine
Declarative rules versioned per client. Inference is gated before execution.
06
Global Locks
System-wide pause primitives. The kernel can halt itself if invariants drift.

The audit ledger is hash-chained and fully replayable. Critical rules cannot be bypassed by an AI agent, an integrator, or a privileged user. Because every action lives in one ledger, a complete audit report is always ready on request.

// audit ledger · append-only
ledger.append(
  actor: "approver@tenant",
  action: "commit_transition",
  policy: "dual_control@v3",
  prev_hash: "0x9c3a…",
  ts: "2026-05-13T11:42:08Z"
)
06·5 GOVERNANCE LIFECYCLE

Every AI action follows one non-bypassable sequence.

FIG · 06·5 / GOVERNANCE LIFECYCLE · FAIL-CLOSED POLICY PRECEDES INFERENCE
graph TB REQ(["Inbound Action"]) HALT["HALT · Fail-Closed"] DONE(["Governed Result"]) subgraph KERN["Governance Kernel · Non-Bypassable"] EVAL["Policy Evaluation"] GATE["Human Approval Gate"] EXEC["Execution"] SEAL["Audit Ledger Seal"] EMIT["Event Emission"] end REQ --> EVAL EVAL -->|"Allow"| GATE EVAL -->|"Deny / Error"| HALT GATE -->|"Approved"| EXEC GATE -->|"Timeout / Reject"| HALT EXEC -->|"Failure"| HALT EXEC --> SEAL SEAL --> EMIT EMIT --> DONE style KERN fill:#f0eee8,stroke:#0a0a0a,stroke-width:1.5px,color:#0a0a0a style REQ fill:#e3f0e7,stroke:#008746,stroke-width:1.75px,color:#0a0a0a style DONE fill:#e3f0e7,stroke:#008746,stroke-width:1.75px,color:#0a0a0a style HALT fill:#c43a1a,stroke:#0a0a0a,stroke-width:1.75px,color:#fafaf7 style EVAL fill:#fafaf7,stroke:#0a0a0a,color:#0a0a0a style GATE fill:#fafaf7,stroke:#0a0a0a,color:#0a0a0a style EXEC fill:#fafaf7,stroke:#0a0a0a,color:#0a0a0a style SEAL fill:#fafaf7,stroke:#0a0a0a,color:#0a0a0a style EMIT fill:#fafaf7,stroke:#0a0a0a,color:#0a0a0a
FOR ENGINEERS · TECHNICAL DOCUMENTATION

The technical depth continues on kernel.quaicu.org.

API reference, Python SDK guide, CEL policy language, deployment runbooks, and the architecture decisions behind every governance layer.

The system never fails silently.