Runtime Trace Example
Decision Infrastructure asks
“Should it still happen now?”
Illustrative Example
This page uses an illustrative mortgage-funding scenario with anonymized inputs. It is reference education for analysts and buyers; it is not a customer deployment, not a screenshot of production data, and not a benchmark of measured outcomes.
Most enterprise systems describe how a decision is made. Decision Infrastructure describes how a decision is governed at the moment it acts.
This trace walks through one illustrative decision — from approval to outcome — showing what is evaluated at the commit boundary, what verdict is produced, what evidence is captured, and what the system learns afterward.
The runtime flow
Every governed decision moves through the same seven stages. Decision Infrastructure operates at stages 2 through 5.
- 1
Decision
An approved decision arrives, ready to act.
- 2
Runtime Admissibility
The commit boundary evaluates whether the decision remains permitted right now.
- 3
Verdict
ALLOW · HOLD · DENY · ESCALATE — one of four deterministic outcomes.
- 4
Execution
Only an ALLOW verdict permits the act.
- 5
Evidence
Per-decision evidence captured atomically with the act — not assembled afterward.
- 6
Outcome
The real-world consequence (funds wired, loan booked, position closed).
- 7
Consequence Intelligence (Output)
Learning from governed outcomes — improving future decisions.
Scenario
A residential mortgage has been approved internally. Funds are scheduled to release at 2:14 PM. Between the moment of approval and the moment of release, conditions can change — rates can move, documents can expire, authority can be revoked, exposure limits can be reached.
Decision under evaluation
Loan DI-LP-2026-0091 · $487,500 30Y fixed ·
Action: release funding wire · Approver: underwriter UW-024
What Runtime Admissibility evaluates
At the commit boundary, six checks run against the current state of the systems the act will touch.
Authority
“Is the approver still authorized to commit this action?”
Approver role + delegation chain + revocation list at execution time.
Policy
“Does current policy still permit this action?”
Active policy version + applicable controls + regulatory frame in effect at execution.
State
“Has the underlying state changed since approval?”
Borrower / asset / counterparty / system-of-record state, compared to the state at approval.
Evidence
“Are the supporting documents, signals, and conditions still valid?”
Document validity windows, verification freshness, conditional prerequisites.
Timing
“Is the approval still within its validity window?”
Approval timestamp + decision-validity TTL + market-window or rate-lock expiration.
Exposure
“Does the act remain within risk and compliance bounds?”
Concentration limits, AML/OFAC re-screen, jurisdictional rules, capital-markets eligibility.
Trace A — ALLOW
All six checks pass. The verdict is ALLOW. Execution proceeds. Evidence is captured atomically with the act.
Verdict
ALLOW · Execute the funding wire.
Evidence captured at execution
Below is a structurally-representative trace fragment. Field shapes are illustrative; production payloads include additional governed context.
{
"trace_id": "trc_2026-06-01T14:14:07Z_DI-LP-2026-0091",
"decision_ref": "DI-LP-2026-0091",
"action": "release_funding_wire",
"policy_version": "2026.05",
"approver": "UW-024",
"approval_time": "2026-05-29T16:42:18Z",
"evaluation_time": "2026-06-01T14:14:07Z",
"checks": {
"authority": "PASS",
"policy": "PASS",
"state": "PASS",
"evidence": "PASS",
"timing": "PASS",
"exposure": "PASS"
},
"verdict": "ALLOW",
"bound_at": "2026-06-01T14:14:07Z",
"evidence_hash": "sha256:9c3e…b41a"
}Trace B — HOLD
Same approved decision, evaluated four days later. Income verification has expired in the interim. The evidence check fails. The verdict is HOLD. Execution does not proceed; the decision is returned to operations with the exact reason.
Verdict
HOLD · Refresh income verification, then re-evaluate.
From outcome to Decision Intelligence
After execution, the trace becomes part of the system’s learning record. Consequence Intelligence is what an organization produces by reasoning over governed outcomes:
- Which approvals expire most often, and why
- Which authority paths consistently produce HOLDs at execution
- Which policy versions correlate with cleanest commit-boundary outcomes
- Which workflows accumulate the largest decision-to-execution gap
Consequence Intelligence learns from outcomes that were admissible at execution — not from outcomes that should never have occurred.
Decision Infrastructure governs execution and produces evidence at the moment decisions act.
Not at approval time. Not retrospectively. At the act — before consequence becomes irreversible. The runtime trace is the artifact that proves the act was governed.
Reference Surfaces
Reference Surfaces
Understanding a category requires more than comparisons. These reference surfaces explain the core concepts, architecture, vocabulary, and placement of Decision Infrastructure within the enterprise stack.
Definition
What Is Decision Infrastructure?
The canonical introduction to the category. Defines Decision Infrastructure, execution governance, runtime admissibility, and governed execution.
- Category definition
- Execution governance
- Runtime admissibility
- Governed execution
Placement
Where Decision Infrastructure Fits
Where Decision Infrastructure sits between Decision Systems and Consequence Intelligence in the enterprise stack.
- L4 Decisioning
- L5 Decision Systems
- L6 Decision Infrastructure
- L7 Consequence Intelligence
Architecture
Decision Infrastructure Architecture
The architecture that enables execution governance — how Decision Infrastructure operates across enterprise systems.
- Commit boundaries
- Runtime validation
- Execution control
- Evidence generation
Vocabulary
Decision Infrastructure Glossary
The canonical vocabulary of the category — the lexicon analysts can quote precisely.
- Runtime admissibility
- Commit boundary
- Execution governance
- Governed execution
- Evidence at action
Related Concepts
The primitives this trace exercises
Every stage in the trace maps to a canonical primitive of Decision Infrastructure.
Decision Runtime Trace
The canonical primitive this page illustrates — the immutable record of how a decision became an executed outcome.
Commit Boundary
The structural point at which the trace evaluates — intent crosses into consequence.
Runtime Admissibility
The property the six checks evaluate — that the decision remains permitted right now.
Execution Governance
The discipline the trace operationalizes — governance at the act.
Governed Execution
The outcome state the trace produces when the verdict is ALLOW.
Evidence at Execution
The evidence payload captured atomically with the act.
Decision-to-Execution Gap
The interval the trace closes — between approval and act.
Related Comparisons
Related Comparisons
Use these comparisons to understand how Decision Infrastructure differs from adjacent categories, systems, and governance models.
Decision Infrastructure vs Decision Intelligence
The category vs its output cousin — what produces decisions vs what governs them at execution.
Decision Infrastructure vs Decision Governance
Governance defines policy. Infrastructure operationalizes it at execution.
Decision Infrastructure vs Decision Control Plane
A control plane routes and coordinates actions; Decision Infrastructure governs whether each action should still happen at all.
Decision Infrastructure vs Decision Execution Engine
An execution engine runs the action; Decision Infrastructure governs whether execution may proceed.
Decision Infrastructure vs Runtime Governance
Runtime governance is a capability; Decision Infrastructure is the category that contains it.
Decision Infrastructure vs Decision Systems
Workflow-and-approvals systems exit before execution; Decision Infrastructure governs the act itself.
Decision Infrastructure vs AI Governance
AI Governance defines what should be allowed. Decision Infrastructure governs whether those permissions remain valid at execution.
AI Governance vs Decision Systems
Why model and process governance frameworks don't close the gap between approval and consequence.
Decision Infrastructure vs Digital Twin
Simulating reality vs governing what is allowed to happen in reality.
Sovereign Reasoning vs Decision Systems
Reasoning under jurisdictional and policy constraints vs the workflow systems that operationalize decisions.
Decision Infrastructure vs Agentic AI
Agents act autonomously; Decision Infrastructure governs whether each autonomous action is admissible at execution.
Decision Infrastructure vs MLOps
MLOps keeps the model healthy; Decision Infrastructure governs whether the decision it informs is admissible at execution.
Decision Infrastructure vs GRC
GRC documents and reviews controls; Decision Infrastructure enforces them on each action at execution.
Decision Infrastructure vs iPaaS
iPaaS connects systems and moves data; Decision Infrastructure governs whether the action between them should execute.
Decision Infrastructure vs Observability
Observability explains execution; Decision Infrastructure governs whether it should occur at all.
Decision Infrastructure vs Knowledge Graphs
Knowledge graphs map what is connected; Decision Infrastructure governs whether an action across those connections is admissible.
Decision Infrastructure vs Sovereign Reasoning
Sovereign Reasoning bounds how AI reasons; Decision Infrastructure governs whether the resulting action is admissible at execution.
Decision Infrastructure and Palantir
Palantir integrates data and drives action; Decision Infrastructure governs whether each action is admissible at execution — across any platform.
Decision Infrastructure and ServiceNow
ServiceNow runs and automates the workflow; Decision Infrastructure governs whether each action it fires is admissible at execution.
Decision Infrastructure and Pega
Pega manages decision workflows; Decision Infrastructure governs whether execution remains legitimate at the act.
Decision Infrastructure and Appian
Appian automates process execution; Decision Infrastructure governs consequence authorization at the commit boundary.
Decision Infrastructure and FICO
FICO optimizes decision quality; Decision Infrastructure governs whether a scored decision is still admissible at execution.
Decision Infrastructure vs Middleware
Middleware passes messages between systems; Decision Infrastructure governs whether the action a message triggers should execute.
Decision Infrastructure vs BPM
BPM orchestrates the process and moves work to the action; Decision Infrastructure governs whether that action should commit.
Decision Infrastructure vs Workflow Automation
Workflow automation runs the sequence; Decision Infrastructure governs whether each action in it should commit.
Decision Infrastructure and Salesforce
Salesforce runs the customer workflow; Decision Infrastructure governs whether each action it fires remains legitimate at the act.
Decision Infrastructure and Celonis
Celonis reveals how processes run and drives action; Decision Infrastructure governs whether that action is admissible at execution.
Decision Infrastructure and Icertis
Icertis manages contracts and obligations; Decision Infrastructure governs whether an action taken under them is admissible at execution.
Decision Infrastructure and Encompass
Encompass runs the loan workflow; Decision Infrastructure governs whether each consequential loan action is admissible at execution.
Decision Infrastructure and Empower
Empower runs loan origination; Decision Infrastructure governs whether each consequential loan action is admissible at execution.
Decision Infrastructure and Harvey
Harvey generates legal reasoning and drafts; Decision Infrastructure governs whether the actions taken from that reasoning are admissible at execution.
Decision Infrastructure and iManage
iManage manages legal knowledge; Decision Infrastructure governs the consequential actions taken using that information at execution.
Decision Infrastructure and Intapp
Intapp coordinates legal intake, conflicts, and approvals; Decision Infrastructure governs whether execution remains admissible at the act.
Decision Infrastructure and Relativity
Relativity surfaces and reviews evidence; Decision Infrastructure governs the consequential actions taken because of it at execution.
Decision Infrastructure and Reveal
Reveal surfaces evidence with AI-assisted review; Decision Infrastructure governs the consequential execution based on it.
Decision Infrastructure and Aderant
Aderant runs the business of law; Decision Infrastructure governs whether the consequential actions those operations drive are admissible at execution.
Decision Infrastructure and NetDocuments
NetDocuments manages legal documents and knowledge; Decision Infrastructure governs the consequential actions taken using that information.
Decision Infrastructure and Contract Lifecycle Management
Contract lifecycle platforms manage the contract; Decision Infrastructure governs whether actions taken under it remain admissible at execution.
Decision Infrastructure and Litera
Litera drafts, compares, and perfects legal documents; Decision Infrastructure governs whether the actions taken from those documents are admissible at execution.
Related Reading
Long-form explorations
Platform & Vision