Decision infrastructure

A direct answer, first

What is AI decision infrastructure?

AI decision infrastructure is the layer between AI or agent capability and consequential organizational action. It determines whether a proposed action is sufficiently evidenced, has its uncertainty made visible, and has been authorized by whoever holds the authority to approve it — before that action is allowed to take effect. Certainty Labs uses the term "AI Decision Plane" to describe this proposed infrastructure layer; it is Certainty Labs' term for the category, not established, universal industry terminology.

01 / Where it sits
  1. Sits above
    AI capability
  2. Sits above
    Agent orchestration
  3. Certainty Labs
    AI Decision Plane
    • Evidence provenance
    • Claims
    • Uncertainty / abstention
    • Policy / authority
    • Human gates
    • Decision record
  4. Sits below
    Enterprise systems
02 / Four distinct layers

Capability, orchestration, decision infrastructure, and record are not the same layer

Model capability, agent orchestration, decision infrastructure, and systems of record.

These four layers are frequently collapsed together in practice. Treating them as one layer is where accountability gaps tend to appear: a system can be highly capable and well-orchestrated while still lacking any layer that checks evidence sufficiency or authority before acting.

  1. 01

    Model capability

    What a foundation model or agent can generate — an output, a plan, a proposed action. Capability alone does not decide whether that output should be trusted or acted on.

  2. 02

    Agent orchestration

    The runtime that sequences tool calls and steps so an agent can attempt a multi-step task. Orchestration decides what an agent tries; it does not decide whether the result is sufficiently evidenced or authorized.

  3. 03

    Decision infrastructure

    The layer that determines whether a proposed action is grounded in sufficient evidence, has its uncertainty made visible, and has been authorized by whoever holds the authority to approve it — before the action executes.

  4. 04

    Systems of record

    The databases, CRMs, and operational systems where an authorized decision takes effect as a change of state. They record that something happened; they do not decide whether it should have.

03 / Why this boundary matters

Capability is not accountability

An agent that can act is not the same as a decision that should be trusted.

A model can generate a plausible recommendation without any evidence backing it. An orchestration runtime can execute a multi-step task without ever checking whether the underlying claims hold up, whether uncertainty was resolved, or whether a human with the relevant authority reviewed the outcome. Decision infrastructure is the layer responsible for asking those questions before consequential action executes, and for preserving the answer as part of a decision record — see the architecture page for how Certainty Labs structures that layer.

04 / Open questions

Not yet settled

What remains an open research question.

  • How much evidence is enough evidence for a given class of decision, and who sets that threshold?
  • Can decision infrastructure be made reusable across applied systems without absorbing each system's business context?
  • How should decision quality be measured independently of whether an outcome happened to be favorable?

These questions are studied through Certainty Labs' research and tested in bounded applied systems.

05 / Collaboration

Working on this boundary yourself?

We're interested in hearing from teams and researchers drawing this same line between capability and accountable action.

Collaborate with Certainty Labs