§ Safety & GovernanceDocument · REG-SG-2026.04

You never trust the AI. You trust the deterministic boundaries constraining it.

Every guarantee below is a platform-level mechanism, not a policy document. They exist whether or not an operator remembers them.

S.01Immutability

Audit trail on every decision.

Append-only event ledger with a propagating trace_id on every cognitive step. Reconstruct what happened, who decided, which rule version ran, and what evidence was used.

Storage
Append-only event log
Trace model
Propagating trace_id
Replay
Deterministic from events
S.02Temporal safety

Regulatory versioning. In-flight cases don't break.

Past work remains re-runnable on the exact forms, agents, and rules that were live when it opened. Mid-flight changes do not rewrite running workloads.

Version model
SCD Type 2
Resolution
At case instantiation
Replay fidelity
Byte-identical
S.03Earned autonomy

Configurable autonomy ceilings.

Every agent operates within an operations-set ceiling. The engine enforces it, the agent cannot self-promote, and every promotion is logged.

Level 1 · Default
Always review

Every action routes to a human reviewer before execution. No agent ships without this first.

Level 2 · Earned
Graduated

Routine actions execute; flagged or low-confidence outputs halt for human sign-off. Most agents operate here.

Level 3 · Restricted
Fully autonomous

Reserved for mechanical tasks only. Scoped workflows; never PHI, never pricing, never signed outputs.

S.04Structural determinism

Deterministic, typed agent pipelines.

Agent execution is a deterministic pipeline. AI is one bounded step with typed input and output; validation, MCP calls, schema checks, and routing remain explicit.

Pipeline model
Typed DAG
LLM surface
Single step per node
Contract
Zod + JSON schema
S.05Halt semantics

Workspace-wide emergency brake.

One action pauses every agent, queue, and outbound message across a workspace. A halted workspace resumes only on explicit operator release.

Scope
Workspace-wide
Enforcement
Every task, every tick
Release
Explicit operator command
S.06Operator-owned

Configurable without engineers.

Process managers adjust graphs, prompts, autonomy, and MCP scopes in conversation. Every change is versioned; engineering owns the engine, not the ops logic.

Authoring
Conversational graph
Change unit
Versioned template
Deploy
Zero — published
§ Next step

See the governance story live.

We’ll walk through a redacted trace, toggle an autonomy ceiling, and show the emergency brake halting every active queue.

Book the walkthrough How it sits above your stack
Related
Three-Tier Separation Model
Reference
SCD2 · MCP Registry · Recovery Path Engine
Document
REG-SG-2026.04