The canonical ontology for governed execution. Each term is defined once. Each term links to its canonical page. The semantic index for the Decision Infrastructure category.
Decision Infrastructure is the category. System of Intelligence is how it operates.
Every other term below names a property, a primitive, or a relationship.
Quick Index
Category Concepts
The terms that define the Decision Infrastructure category — what it is, the operating model it runs as, and the architectural space it exists to close.
The control layer that governs whether decisions remain admissible when they execute.
Decision Infrastructure is the category. It sits between Decision Systems and Execution in the enterprise stack, governing the moment in which intent becomes consequence. It is distinct from decision intelligence (which makes and improves the decision) and from workflow systems (which route work). It is the runtime governance layer at the commit boundary.
The operating model that validates, executes, and evidences decisions continuously across enterprise state.
A System of Intelligence sits above systems of record and systems of engagement. It is the operating model through which Decision Infrastructure is realized inside an enterprise. The category is what is being built; the operating model is how it works. Records describe what happened; engagement coordinates interaction; intelligence governs whether action is admissible at all. The term predates QuNetra and has been used across the software industry to describe AI-driven software above systems of record and engagement; QuNetra's specific contribution is governing admissibility at the moment of execution through Decision Infrastructure.
The architectural space between approval and action — where state changes and outcomes fail.
The decision-to-execution gap is where regulated outcomes fail. Between approval and the act, documents expire, conditions fail, sanctions lists update, authority changes, and fraud signals emerge. Most enterprise stacks have no architectural position from which to govern this gap. Decision Infrastructure is the layer that closes it — structurally rather than narratively.
Core Execution Concepts
The runtime primitives Decision Infrastructure operates through — where execution is governed, by what property, what discipline, what outcome, and with what evidence.
The architectural location at which intent becomes consequence.
The commit boundary is where a decision attempts to commit to action. Before the boundary, an action is preventable; after the boundary, the action is real. Every admissibility evaluation occurs at this boundary. Naming the boundary is what makes governance enforceable rather than aspirational.
Governance applied at the moment of action, not the moment of decision.
Execution governance is the discipline of enforcing policy against current state at the commit boundary. It is distinct from policy enforcement (which describes the rule), workflow governance (which routes work), and audit (which describes after the fact). Execution governance is real-time, structural, and produces evidence as a side effect of every action.
The property that a proposed action is currently permitted, re-evaluated at the moment of execution rather than the moment of decision.
Runtime admissibility is the architectural primitive that distinguishes governed execution from automated execution. It checks the live state of conditions, authority, evidence, and risk against the policy that authorized the decision. If any dimension has changed in a way that invalidates the original authorization, admissibility fails — and the action is denied, held, or escalated.
The outcome state in which decisions remain admissible at the moment they act — validated, governed, bound, and evidenced at the Commit Boundary.
Governed Execution is the outcome Decision Infrastructure produces when admissibility holds at the moment of action. State, policy, authority, evidence, and risk are revalidated at the Commit Boundary; execution proceeds only when each dimension remains valid. Contrasted with automated execution, which commits without runtime admissibility checks.
Verifiable record of how and why an action was permitted, created at the moment of action.
Evidence at execution is the architectural commitment that evidence is captured in-line at the commit, not reconstructed afterward. Reconstructed evidence is interpretation; evidence captured at execution is fact. This is what makes governed execution defensible to regulators and to internal audit.
The emergent, sustained outcome in which enterprise actions can be trusted because they are executed under current policy, authority, state, and evidence — a property produced by governed execution over time, not a control or process.
Operational Legitimacy is achieved when organizations can demonstrate not only that decisions were made correctly, but that actions were executed appropriately at the moment they became real-world outcomes. It is not a control mechanism, workflow, or governance process — it is the outcome produced when governed execution, runtime admissibility, and evidence at execution operate consistently across the enterprise. Decision Infrastructure exists to make Operational Legitimacy achievable at scale.
Supporting Concepts
Properties and primitives referenced by the core terms. Defined here for precision; understood through the canonical pages above.
The mechanism by which admissibility is evaluated against live state at the commit boundary.
Runtime validation checks current conditions, authority, evidence, and risk against the policy that authorized the decision. It is performed at the commit boundary as the gate that determines whether the action binds. It is not a secondary review — it is the moment of governance.
Whether a proposed action is permitted, given the current state.
Admissibility is a binary property — an action either is or is not permitted at the moment it attempts to commit. Structured exceptions (hold, escalate) preserve the binary outcome while allowing for human intervention. Admissibility is what governed execution checks; runtime admissibility names the check at execution time.
The act of commit at the boundary — the event in which an action becomes real.
Binding is the moment that admissibility is enforced. The commit boundary names the architectural location; admissibility names the property; binding names the act. Distinguishing these three is what makes execution governance coherent. Binding produces both state change and evidence, paired in-line.
Admissibility evaluated continuously for the duration of an in-flight obligation, not just once at decision time.
For actions that remain open over time — held positions, open commits, long-running disbursements — a single check at decision time is not sufficient. Continuous admissibility re-evaluates against current state for the lifetime of the obligation, so that any state change invalidates the action before it acts on stale assumptions. Continuous admissibility is what makes this a runtime layer rather than a checkpoint.
How to use this glossary
These terms name distinct architectural concepts. They are not synonyms. When evaluating a platform, ask which of these properties it provides — and which it claims by name but does not provide structurally.
Relationship Reading Tree
Decision Infrastructure is part of a connected ontology. Use this relationship tree to understand where this concept fits.
Reference Surfaces
Architecture Surfaces
Architecture anchors that explain how Decision Infrastructure operates — distinct from the canonical anchor pages above and the ontology spine.
The canonical category map — the master navigation index for the entire Decision Infrastructure category. Start here to see the whole thing.
The 7-layer architecture of governed consequence — where Decision Infrastructure sits at L6.
The semantic substrate of admissibility — what objects ARE vs whether an action on them is allowed at execution.
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
The canonical introduction to the category. Defines Decision Infrastructure, execution governance, runtime admissibility, and governed execution.
Placement
Where Decision Infrastructure sits between Decision Systems and Consequence Intelligence in the enterprise stack.
Architecture
The architecture that enables execution governance — how Decision Infrastructure operates across enterprise systems.
Related Concepts
The architectural primitives that compose Decision Infrastructure — each governs one facet of how execution remains admissible. Each is defined precisely in this glossary.
The structural point where intent crosses into consequence.
The discipline of controlling execution at the moment decisions become consequences.
The property that an approved decision remains permitted at the moment it acts.
Execution that occurs only when policy, authority, conditions, and evidence remain valid at the act.
Evidence captured at the moment of action — not reconstructed afterward.
The interval between approval and execution where conditions change and admissibility can silently expire.
The semantic substrate of governed execution — the shared vocabulary describing what actions are admissible at execution time. Underlies every term in this glossary.
The immutable record of how a decision became an executed outcome — the canonical primitive in which every glossary term resolves at runtime.
Related Comparisons
Use these comparisons to understand how Decision Infrastructure differs from adjacent categories, systems, and governance models.
The category vs its output cousin — what produces decisions vs what governs them at execution.
Governance defines policy. Infrastructure operationalizes it at execution.
A control plane routes and coordinates actions; Decision Infrastructure governs whether each action should still happen at all.
An execution engine runs the action; Decision Infrastructure governs whether execution may proceed.
Runtime governance is a capability; Decision Infrastructure is the category that contains it.
Workflow-and-approvals systems exit before execution; Decision Infrastructure governs the act itself.
AI Governance defines what should be allowed. Decision Infrastructure governs whether those permissions remain valid at execution.
Why model and process governance frameworks don't close the gap between approval and consequence.
Simulating reality vs governing what is allowed to happen in reality.
Reasoning under jurisdictional and policy constraints vs the workflow systems that operationalize decisions.
Agents act autonomously; Decision Infrastructure governs whether each autonomous action is admissible at execution.
MLOps keeps the model healthy; Decision Infrastructure governs whether the decision it informs is admissible at execution.
GRC documents and reviews controls; Decision Infrastructure enforces them on each action at execution.
iPaaS connects systems and moves data; Decision Infrastructure governs whether the action between them should execute.
Observability explains execution; Decision Infrastructure governs whether it should occur at all.
Knowledge graphs map what is connected; Decision Infrastructure governs whether an action across those connections is admissible.
Sovereign Reasoning bounds how AI reasons; Decision Infrastructure governs whether the resulting action is admissible at execution.
Palantir integrates data and drives action; Decision Infrastructure governs whether each action is admissible at execution — across any platform.
ServiceNow runs and automates the workflow; Decision Infrastructure governs whether each action it fires is admissible at execution.
Pega manages decision workflows; Decision Infrastructure governs whether execution remains legitimate at the act.
Appian automates process execution; Decision Infrastructure governs consequence authorization at the commit boundary.
FICO optimizes decision quality; Decision Infrastructure governs whether a scored decision is still admissible at execution.
Middleware passes messages between systems; Decision Infrastructure governs whether the action a message triggers should execute.
BPM orchestrates the process and moves work to the action; Decision Infrastructure governs whether that action should commit.
Workflow automation runs the sequence; Decision Infrastructure governs whether each action in it should commit.
Salesforce runs the customer workflow; Decision Infrastructure governs whether each action it fires remains legitimate at the act.
Celonis reveals how processes run and drives action; Decision Infrastructure governs whether that action is admissible at execution.
Icertis manages contracts and obligations; Decision Infrastructure governs whether an action taken under them is admissible at execution.
Encompass runs the loan workflow; Decision Infrastructure governs whether each consequential loan action is admissible at execution.
Empower runs loan origination; Decision Infrastructure governs whether each consequential loan action is admissible at execution.
Harvey generates legal reasoning and drafts; Decision Infrastructure governs whether the actions taken from that reasoning are admissible at execution.
iManage manages legal knowledge; Decision Infrastructure governs the consequential actions taken using that information at execution.
Intapp coordinates legal intake, conflicts, and approvals; Decision Infrastructure governs whether execution remains admissible at the act.
Relativity surfaces and reviews evidence; Decision Infrastructure governs the consequential actions taken because of it at execution.
Reveal surfaces evidence with AI-assisted review; Decision Infrastructure governs the consequential execution based on it.
Aderant runs the business of law; Decision Infrastructure governs whether the consequential actions those operations drive are admissible at execution.
NetDocuments manages legal documents and knowledge; Decision Infrastructure governs the consequential actions taken using that information.
Contract lifecycle platforms manage the contract; Decision Infrastructure governs whether actions taken under it remain admissible at execution.
Litera drafts, compares, and perfects legal documents; Decision Infrastructure governs whether the actions taken from those documents are admissible at execution.
Related Reading
Platform & Vision