Patent pending

SARVA System for Aligned Runtime Verification & Authorization

Govern AI activity. Deterministic decisions on supported paths.

SARVA evaluates supported requests against deterministic governance controls, authority context and organizational policy, and resolves each to one of three outcomes: allow, escalate or block.

— The principle

Capability does not confer authority.

Capability

what it can do

≠Authority

what it may invoke

≠Permission

what policy allows

An AI may be technically capable of an action without being authorized to perform it — and authorization is not the same as being permitted by policy. SARVA keeps an AI’s proposal structurally separate from execution authority.

— The Pipeline

Supported requests pass five gates.

If a gate determines a supported request should not proceed, the pipeline resolves it as escalated or blocked, and the decision is recorded.

Gate 0

Ethics

Evaluates the request against the ethical and safety boundaries defined in policy.

Gate 1

Capability

Has this agent been authorized to perform this type of action?

Gate 2

Sandbox

Is this a recognized action type? No prohibited payloads.

Gate 3

Guard

Does active policy and role permit this specific request right now?

Gate 4

Irreversibility / Authority Boundary

Addresses the authority boundary before supported consequential external effects.

Governed decisions are recorded as integrity-protected evidence in COSMOS, linked to the policy version in force.

— Decision flow

Three outcomes.

Every supported request resolves to one of three outcomes.

Allowed

Proceed

The request is permitted on the supported path. The decision is recorded.

✓  Policy passed
Escalated

Review

The request requires further evaluation or human review before proceeding. It may resolve to allow or block.

△  Deeper evaluation
Blocked

Denied

The request does not meet policy and is not permitted on the supported path. The decision is recorded.

✕  Policy not met
— Governance constructs

Five constructs. Five failure modes addressed.

01

Irreversibility / Authority Boundary

Addresses the authority boundary before supported consequential external effects.

02

Authority Freshness

Authority is not assumed to last indefinitely. It is re-confirmed rather than carried forward.

03

Current-Policy Validation

Supported governed requests are evaluated against the current applicable policy, preventing earlier policy state from being treated as current authority.

04

Non-Transitive Authorization

Authority does not automatically pass from one agent or step to the next.

05

Authority Scope Protection

Designed to prevent authority from silently expanding as requests move through supported agents, services and workflows.

— Recorded as evidence

Decisions become evidence.

Governed decisions are recorded with context and the policy version in force. Supported requests are evaluated before they proceed on the supported path.

Decision recording

Governed decisions are recorded with context, timestamps and policy references.

Policy-version traceability

Each governed decision is linked to the policy version in force at the time.

Decision boundary

Supported requests that fail policy are resolved as blocked and recorded.

Evidence lives in COSMOS. Explore COSMOS

— Maturity

The core governance and evidence architecture is implemented and tested. MRCortex is completing the enforced consequential-execution architecture required for Customer-Ready V1.

Customer-Ready V1 in development

— How it connects

Discovery → See · SARVA → Govern · COSMOS → Prove

Discovery · See

Identifies what exists

Identifies AI systems and their access context. Explore Discovery

SARVA · Govern

Governs AI activity

Evaluates supported requests and returns a decision. (this page)

COSMOS · Prove

Preserves verifiable evidence

Records governed decisions as integrity-protected evidence. Explore COSMOS

Capability does not confer authority.