TRUST

How every delivery
stays checked.

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

RULES ARE CHECKED BEFORE AI ACTS
01 RULES AND AI, SIDE BY SIDE

Rules handle what must not vary.
AI helps where judgment is useful.

FIXED RULES

Fixed rules.

For important actions where mistakes are not acceptable. The same input always gives the same result, and AI is not allowed to override them.

RULESRECORDAPPROVALSPERMISSIONS
AI, WITHIN LIMITS

AI within limits.

For predictions, risk flags and draft content: always reviewable by a person, never run on its own.

RISK FLAGSDRAFTSSCORINGTRIAGE

Both run under the same Governance Kernel. People have the final say on anything important.

TAMPER-EVIDENT · REPLAYABLE · AUDIT-READY
02 THE STACK

Four layers. One set of rules for all of them.

quaicu_kernel ▸ enforcement_contract.app RULES · ALWAYS CHECKED
4 Application Layer APP

The platforms and workflows we build and support for you, across web and mobile. The same governance foundation sits underneath every engagement.

3 Rule Engine RULE · NO SILENT OVERRIDES

Where your non-negotiables are written down. They are checked on every action, give the same result every time, and are designed so no one can quietly override them.

2 AI Agents AI · GUARDRAILED · DRAFT-ONLY

AI drafts and suggests within limits, and a person can review everything it produces. AI proposes; your rules and your approvers decide what runs. It runs nothing on its own, except fixes you pre-approve under out-of-hours cover.

1 Trust Layer TRUST · TAMPER-EVIDENT · SEPARATE PER CLIENT

On-premise, private cloud, hybrid, or hosted by us on AWS in India. Each client's data stored separately. Sign-in and access management. Encryption at rest and in transit. An audit record designed so it can't be edited after the fact.

SIGN-IN SECRETS VAULT ENCRYPTION TAMPER-EVIDENT LOG REPLAY
RUNNING LAYERS 04 RULES ALWAYS CHECKED ON ERROR STOP AUDIT CONTINUOUS STATUS HEALTHY
BUILT TO STOP AND ALERT
03 CHECKS, LAYER BY LAYER

Every change in everything we deliver is designed to pass through the same checks.

01
Human sign-off
Important actions wait for a named person to approve them. Nothing runs on its own, except fixes you pre-approve for out-of-hours cover.
02
Allowed steps only
Each step can only move to an allowed next step. The allowed steps are written down and checked.
03
Access by role
People get only the access their role needs, and it can be taken away. Any increase in access is logged.
04
Approval steps
Two or more approvers where you require it. You decide how many sign-offs each kind of change needs.
05
Your rules, in writing
Rules are written down and versioned for each client. AI output is checked against your rules before anything runs.
06
Emergency stop
We can pause all changes at once if something looks wrong. The system is designed to pause itself if its core checks stop holding.

Every action is written to one audit record. Each entry is linked to the one before it, so the record is designed so it can't be edited after the fact, and it can be replayed step by step. Critical rules are designed so no AI agent, integrator or privileged user can bypass them. Because everything is in one record, we can produce a full audit report when you ask.

With out-of-hours cover, fixes you pre-approve, within rules you agree with us in advance, can run on their own; a person reviews each one the next working day. Everything else waits for a person.

// audit record · add-only
ledger.append(
  actor: "approver@tenant",
  action: "commit_transition",
  policy: "dual_control@v3",
  prev_hash: "0x9c3a…",
  ts: "2026-05-13T11:42:08Z"
)
04 HOW AN AI ACTION RUNS

Every AI action is designed to follow one sequence.

FIG · 04 / HOW AN AI ACTION RUNS · STOPS ON ERROR RULES ARE CHECKED BEFORE AI ACTS
graph TB REQ(["Request for an action"]) HALT["Stop · nothing runs"] DONE(["Checked result"]) subgraph KERN["Governance Kernel"] EVAL["Check against your rules"] GATE["A person approves"] EXEC["Run"] SEAL["Write to the audit record"] EMIT["Notify connected systems"] 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
05 SUB-PROCESSORS

Who handles your data
on our behalf.

These providers handle client code, requests or messages while we do your work. We list them so you can see where your information goes.

Anthropic
AI model provider for our coding agent, including its cloud sessions. Sees the code, request details and outputs for the work in hand. Used under business terms that do not allow training on your content. Standard retention is 30 days.
OpenAI
AI model provider for our second coding agent, including its cloud tasks. Sees the code, request details and outputs for the work in hand. Used under business terms; business data is not used for training by default.
Meta (WhatsApp Business Platform)
Carries requests and status messages. Sees phone numbers, names, message text and attachments.
Amazon Web Services (India region)
Hosts our internal system, each client's request bot, and the software we host for clients.

Where each provider processes data is set out in its own terms and confirmed in your agreement. We update this list when providers change. Last reviewed November 2026.

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.

Built to stop and alert, not fail silently.