Architecture

Where Certainty sits in the stack

The AI Decision Plane architecture.

Certainty Labs is defining the layer between AI and agent capability and consequential enterprise action — the infrastructure that determines whether a proposed action is sufficiently evidenced, bounded, and authorized before it executes.

01 / The stack
  1. Sits above
    AI capability

    Foundation models and agent capability that can generate outputs and propose actions.

  2. Sits above
    Agent orchestration

    Workflow and tool-calling runtimes that sequence what an agent attempts to do.

  3. Certainty Labs
    AI Decision Plane

    Determines whether a proposed action is sufficiently evidenced, bounded, and authorized before it changes enterprise state — and preserves why.

    • Evidence provenance
    • Claims
    • Uncertainty / abstention
    • Policy / authority
    • Human gates
    • Decision record
  4. Sits below
    Enterprise systems

    Systems of record where an authorized decision takes effect as consequential action.

Architectural direction: we are progressively extracting these decision primitives from applied systems into reusable infrastructure.

02 / Category boundary

What Certainty owns, and what it deliberately does not

A bounded layer, not a full stack.

Certainty Labs owns the decision layer itself. It does not own model capability, agent orchestration, or the systems of record on either side of it.

Certainty owns

  • Evidence provenance
  • Claims
  • Uncertainty / abstention
  • Policy / authority
  • Human gates
  • Decision records

Certainty does not own

  • Foundation models
  • Model training
  • General agent orchestration
  • Workflow execution
  • Raw telemetry
  • Systems of record
03 / Operating model

A decision as a connected record

From evidence to accountable action.

The system must preserve the reasoning and authority surrounding a decision—not only its final output.

  1. 01Evidence
  2. 02Claims
  3. 03Uncertainty
  4. 04Recommendation
  5. 05Human judgment
  6. 06Decision record
  7. 07Outcome
04 / Design principles

System behavior, not slogans

Principles before automation.

  1. 01

    Evidence before confidence

    Claims earn confidence through traceable evidence, not persuasive output.

  2. 02

    Uncertainty remains visible

    Unknowns and conflicts stay attached to the decision instead of disappearing behind a score.

  3. 03

    Human authority is explicit

    Consequential action records who had the authority to approve it.

  4. 04

    Systems must be able to abstain

    A dependable system can stop when evidence or authority is insufficient.

  5. 05

    Decisions require an audit trail

    Reasoning, authorization, action, and outcome remain connected over time.

  6. 06

    Products remain independently bounded

    Shared foundations never silently absorb a product’s entities, context, or workflows.

05 / Evidence in code

Architecture as commitment

Accountability must exist in the architecture.

Accountability is represented as a system concern—not added later as marketing language.

  readonly outcome: string;
  readonly decisionStatement: string;
  readonly justifyingClaimRefs: readonly Claim["draftId"][];
  readonly uncertainty: Uncertainty;
packages/agent-contracts/src/entities/recommendation.ts

The contract keeps an agent's outcome, decision statement, justifying claim references, and uncertainty attached to one proposal shape — evidence and claims must resolve to a recommendation before a human decision is made.