QuNetra Ontology
Reference Surface
This page is part of the canonical Decision Infrastructure reference model.
The semantic substrate of governed execution.
Decision Infrastructure is the architectural layer that governs how decisions are validated, executed, and evidenced at the moment they act. It is not policy management, not workflow orchestration, not an AI overlay — it is the runtime governance layer that sits between decision formation and irreversible consequence.
The vocabulary of that layer is the Decision Infrastructure ontology — a structured set of runtime-enforceable terms clustered into core concepts, runtime primitives, lifecycle models, and comparison frameworks. Each cluster anchors a canonical surface with its own DefinedTerm definitions, architectural diagrams, and analyst-grade reference briefs.
This page is the navigation index for that ecosystem — not a marketing landing page, not a product overview. It maps the canonical runtime-governance vocabulary so analysts, enterprise architects, AI governance leaders, and platform-governance teams can navigate the ontology as a coherent semantic network.
How the Category Fits Together
Three distinct roles, one model: the operating model, the category, and the output it produces.
The Execution Spine
The canonical execution backbone — one decision, traced from the gap to the evidence. Each layer links to its reference page.
01 · Architecture
Core Concepts
The canonical pages that define what Decision Infrastructure is — the architectural category, where it sits in the enterprise stack, the operating model, and the architectural primitives that anchor it.
- What Is Decision Infrastructure?The architectural layer that governs whether decisions remain admissible at execution time.
- Where Decision Infrastructure FitsThe canonical category anchor — Decision Infrastructure as Layer 6 of the Enterprise Control Stack.
- System of IntelligenceThe operating model above systems of record and systems of engagement — the layer that validates, executes, and evidences continuously.
- The Control StackThe canonical 7-layer architecture of governed consequence.
- Decision Infrastructure ArchitectureThe architectural layout — how Decision Infrastructure operates across enterprise systems.
- The Commit BoundaryThe architectural location at which intent becomes consequence.
- Runtime AdmissibilityThe property that a proposed action remains permitted at the moment of execution — re-evaluated against live state, not just at decision time.
- Execution GovernanceThe operational discipline of controlling execution at the moment decisions become consequences — distinct from data, AI, model, and process governance.
- Governed ExecutionThe outcome state Decision Infrastructure produces — execution permitted only when policy, authority, conditions, evidence, and risk remain valid at the commit boundary.
- Evidence at ExecutionVerifiable evidence generated in-line at the commit boundary — created when action occurs, not reconstructed afterward from logs.
- Operational LegitimacyThe result Decision Infrastructure produces over time — the condition in which enterprise actions can be trusted because they were executed under current policy, authority, state, and evidence. The outcome, not a mechanism.
02 · Discipline
Runtime Governance
The discipline of governing whether actions remain permitted at the moment they act. Re-evaluated at the commit boundary against live state, authority, policy, and evidence — not at decision time. Resolves deterministically into one of four verdicts.
Action proceeds. Evidence captured at binding.
Revalidation required. Action paused, not failed.
Action refused at the boundary. Reason captured.
Higher authority review required.
03 · Architecture
Lifecycle Models
Governed execution preserves three orthogonal lifecycle models. Most enterprise systems collapse them into a single record — the collapse is the structural failure mode behind a large class of enterprise AI failures.
- Semantic LifecycleDocument → Knowledge → Decision → Execution → Evidence. The chain of meaning-extraction; models what the system knows.
- Governance LifecycleAdmissibility → Runtime Validation → Governance → Binding → Evidence. The canonical model of runtime admissibility enforcement at the commit boundary.
- Decision Runtime TraceDecision → Admissibility → Runtime Validation → Commit/Binding → Execution → Evidence. The immutable, time-ordered record of what actually executed.
04 · Vocabulary
Governance Ontology
The shared vocabulary describing what actions are admissible at execution time. Orthogonal to domain ontology (MISMO, FIBO, HL7, LegalRuleML) — neither is derivable from the other.
Canonical Vocabulary — 8 Terms
- Admissibility
- The property that a proposed action is currently permitted under the live state of policy, authority, conditions, exposure, evidence, and risk.
- Runtime Validation
- The continuous evaluation between admissibility and binding; catches state drift before the act.
- Binding
- The atomic architectural event at which intent becomes consequence — the system-of-record mutation.
- Governed Execution
- Execution that proceeds only when admissibility is verified at the binding moment — refused, held, or allowed deterministically.
- Evidence at Execution
- Evidence generated atomically with binding — recorded in the runtime trace at the moment of action, not assembled afterward from logs.
- Replay Governance
- The ability to reconstruct deterministically what an enterprise system should have decided at a prior moment, using only the inputs available at that moment.
- Escalation
- A structured deferral of binding when admissibility cannot be deterministically decided — held pending higher-authority review.
- Continuous Admissibility
- Admissibility evaluated continuously for the duration of an obligation — invalidates before stale assumptions can act.
05 · Primitives
Runtime Primitives
The architectural primitives that resolve at the commit boundary. These are not product features — they are the structural objects that distinguish governed execution from automated execution.
- Commit BoundaryThe architectural location at which intent becomes consequence — the atomic moment where every governance term resolves.
- Decision Runtime TraceThe structured, immutable, time-ordered architectural artifact recording a single decision from intent to consequence.
- Evidence at ExecutionEvidence generated in-line with binding — the trace IS the evidence.
- Replay GovernanceDeterministic reconstruction against pinned reference state.
- Deterministic ReconstructionGiven identical anchored inputs and policy versions, the trace yields the same verdict on replay — every time, by anyone.
06 · Category Boundaries
Comparison Frameworks
Decision Infrastructure positioned against adjacent categories that it is most commonly confused with. The distinctions are architectural, not vocabulary refinements.
- Decision Infrastructure vs Decision IntelligenceCategory vs output — Decision Infrastructure governs whether decisions remain admissible at execution; Consequence Intelligence learns from the resulting outcomes.
- AI Governance vs Decision SystemsPolicy overlay vs runtime admissibility — governance frameworks describe controls; decision systems enforce them at the act.
- Decision Infrastructure vs Digital TwinSimulation of state vs governance of execution — twins prove what works; DI determines what is allowed.
- Sovereign Reasoning vs Decision SystemsReasoning autonomy vs runtime control — sovereign reasoning forms decisions; decision systems govern whether they execute.
- Decision Infrastructure vs Decision SystemsWorkflow orchestration vs execution governance — routing decisions vs binding them admissibly at the commit boundary.
07 · Research
Analyst Briefs
Architecture-grade reference briefs — analyst-oriented, research-oriented, suitable for Gartner / Forrester / IDC briefings and architectural review boards.
- Governance Ontology vs Domain OntologyThe orthogonality of two architectural layers most enterprises collapse into one.
- Three Lifecycle Models in Decision InfrastructureWhy governed execution requires three orthogonal lifecycles bound at the commit boundary.
- What Is a Decision Runtime Trace?The primitive definition — six stages, anchored, immutable, externally verifiable.
- The Real Market Shift in Legal TechnologyIndustry architecture analysis — legal moves from billing platforms to AI-native operating environments.
- CFO ROI — Decision InfrastructureApproved ≠ Realized — the economic gap closed by governing execution.
08 · Diagrams
Canonical Visuals
The architectural diagrams that anchor the ontology cluster. Each is rendered at native 1600×900 and opens to a brand-attributed standalone variant for analyst-context distribution.
09 · Lexicon
Glossary Spine
The seven canonical terms that anchor the Decision Infrastructure category. Each links to its primary definitional surface. For the full vocabulary, see the canonical Governance Ontology page and the Decision Infrastructure Glossary.
- Decision Infrastructure
- The architectural layer that governs how decisions are validated, executed, and evidenced at the moment they act.
- Runtime Admissibility
- The property that an approved decision remains executable at the moment of execution, given live state, authority, and policy.
- Commit Boundary
- The architectural location at which intent becomes consequence — where every governance verdict resolves.
- Governance Ontology
- The shared vocabulary describing what actions are admissible at execution time within enterprise systems.
- Governed Execution
- Execution that proceeds only when admissibility is verified at the binding moment — refused, held, or allowed deterministically.
- Decision Runtime Trace
- The canonical record of how a decision moved from intent to consequence — anchored, immutable, externally verifiable.
- Evidence at Execution
- Evidence generated atomically with binding — the trace IS the evidence.
Relationship Reading Tree
Relationship to Other Concepts
Decision Infrastructure is part of a connected ontology. Use this relationship tree to understand where this concept fits.
- System of Intelligence
- Decision Infrastructure
- Decision-to-Execution Gap
- Commit Boundary
- Execution Governance
- Runtime Admissibility
- Governed Execution
- Evidence at Execution
- Operational Legitimacy (Result)
- Consequence Intelligence (Output)
Reference Surfaces
Architecture Surfaces
Architectural reference indexes
Architecture anchors that explain how Decision Infrastructure operates — distinct from the canonical anchor pages above and the ontology spine.
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
Architectural primitives the ontology indexes
The ontology is the map; these are the canonical primitives it indexes. Each governs one facet of how execution remains admissible.
Commit Boundary
The structural point where intent crosses into consequence.
Execution Governance
The discipline of controlling execution at the moment decisions become consequences.
Runtime Admissibility
The property that an approved decision remains permitted at the moment it acts.
Governed Execution
Execution that occurs only when policy, authority, conditions, and evidence remain valid at the act.
Evidence at Execution
Evidence captured at the moment of action — not reconstructed afterward.
Decision-to-Execution Gap
The interval between approval and execution where conditions change and admissibility can silently expire.
Governance Ontology
The semantic substrate that admissibility evaluations operate on — the shared vocabulary distinct from domain ontology.
Decision Runtime Trace
The immutable record of how a decision became an executed outcome — the artifact in which every ontology term resolves at runtime.
System of Intelligence
The operating model that runs the ontology at runtime across enterprise state.
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 of the ontology
Platform & Vision