Decision Infrastructure and iManage
How Decision Infrastructure complements legal document and knowledge management in the legal technology stack.
Why this is not a replacement relationship
iManage is a powerful platform for managing legal documents, work product, knowledge, and matter content. Decision Infrastructure does not replace it — it adds the runtime layer that governs whether the consequential actions taken using that information remain admissible at the moment they execute.
They sit at different layers of the same stack: iManage operates at the document and knowledge management layer; Decision Infrastructure operates at L6 — the governance layer between decisions and their consequences.
What iManage Does Well
iManage spans documents, knowledge, matter context, conflicts information, and information governance. Within a legal team it can:
- manage documents and work product across matters
- organize legal knowledge and institutional memory
- maintain matter context, versioning, and access security
- hold conflicts information — conflict records, approvals, and clearances
- enforce information governance — ethical walls, client restrictions, and need-to-know controls
Examples include iManage DMS for documents and knowledge and iManage Conflicts Manager for conflicts information and information barriers — though equivalent capabilities may exist in other platforms. The relationship is the same regardless: iManage holds the information and restrictions; Decision Infrastructure governs whether an action taken under them is admissible at execution, including on restricted matters and behind information barriers.
What Happens After iManage?
iManage manages the legal information. Decision Infrastructure validates admissibility before the consequential actions taken using that information become real.
Examples include:
- taking an action on a matter under a client restriction
- proceeding where an ethical wall applies
- using work product whose access has since changed
- acting beyond what a conflict clearance still covers
- executing on a restricted or need-to-know matter
The question shifts from “what information exists?” to “may this action be taken using that information now?” — and that question is resolved at L6.
L5 · Decision Systems
iManage
L6 · Decision Infrastructure
Governs whether the action may execute now.
L7 · Decision Intelligence
Learns from governed outcomes.
iManage manages legal knowledge.
Decision Infrastructure governs legal execution.
What Decision Systems Fix — and What They Don’t
L5 · Decision Systems
Decision Systems
What they fix
- Structured decisions
- Decision tracking
- Traceability
- Repeatability
What they don’t answer
- Should this decision exist?
- Is it valid under current constraints?
- Can it control execution?
- Will it produce evidence?
Core question: “What decision was made?”
L6 · Decision Infrastructure
Decision Infrastructure
What it adds
- Decisions validated before execution
- Policy enforced at runtime
- Human and AI accountability
- Evidence across the lifecycle
- Runtime admissibility
Core shift
From structuring decisions to governing whether decisions are valid, executable, and accountable.
Core question: “Is this decision valid, executable, and defensible?”
Most platforms optimize decisions. Very few govern them.
L5, L6, and L7: Different Roles
iManage holds the information; Decision Infrastructure governs the act taken from it. The distinction is not a feature gap — it is a different layer of the stack.
L5 produces and routes decisions.
L6 governs whether those decisions remain admissible at execution.
L7 learns from the outcomes of governed execution.
Why Trusted Decision Intelligence Requires L6
Decision Systems determine what should happen. Decision Infrastructure determines whether it may happen now.
Decision Intelligence learns from outcomes. If those outcomes were never validated at execution, the learning is built on actions that may never have been admissible.
Decision Intelligence is not the input to Decision Infrastructure. It is the output of governed execution.
Frequently Asked Questions
Does Decision Infrastructure replace document management?
No. iManage remains the authoritative system for legal documents, work product, and knowledge. Decision Infrastructure is the runtime governance layer (L6) that governs whether the consequential actions taken using that information remain admissible at execution. They are complementary layers.
What happens after knowledge becomes action?
When information in iManage becomes the basis for a consequential action, Decision Infrastructure revalidates at the commit boundary whether that action is still admissible under current authority, policy, and constraints — and returns Allow, Hold, Deny, or Escalate with evidence before it executes.
Does it govern conflicts and information barriers?
iManage holds the conflicts information — records, approvals, clearances — and the ethical walls and client restrictions that govern access. Decision Infrastructure governs whether a consequential action is still admissible against those restrictions at the moment it executes: if a clearance, an ethical wall, or authority has changed since the work began, the action is held, denied, or escalated with evidence. iManage holds the restriction; L6 enforces it at the act.
Is it an iManage replacement?
No. It does not store, version, or organize documents and knowledge. It governs the admissibility of actions at the commit boundary — independent of, and portable across, the systems that hold the information, including iManage.
Can it run alongside iManage?
Yes. iManage manages the documents and knowledge; Decision Infrastructure governs whether each action taken using that information is admissible at execution and captures independent evidence. The knowledge layer holds; L6 governs the act.
Where does iManage sit in the stack?
At the document and knowledge management layer — above the decision systems that coordinate work and above the commit boundary where actions execute. Decision Infrastructure sits at L6, between the decision and its consequence. See the full model on Where Decision Infrastructure Fits.
Why does Decision Intelligence depend on L6?
Decision Intelligence (L7) learns from outcomes. Without L6, it may learn from legal actions that were never admissible. With L6, it learns only from governed execution — making the resulting intelligence trustworthy.
Related Concepts
Vocabulary an analyst can quote
The canonical concepts referenced on this page, each with its one-sentence definition.
Where Decision Infrastructure Fits
The canonical L5 → L6 → L7 model — the full explanation of the stack.
Execution Governance
Ensures decisions remain admissible at the moment they execute.
Runtime Admissibility
Validation of authority, policy, and constraints immediately before execution.
Commit Boundary
The point where a decision becomes a consequential action.
Legal Decision Intelligence
How QuNetra governs consequential legal execution in regulated practice.
Evidence at Execution
Evidence captured at the moment of action, not reconstructed after.
How the Layers Work Together
Where each legal-technology layer sits relative to Decision Infrastructure. L6 governs whether consequential legal actions remain admissible, authorized, compliant, and evidenced at execution.
Legal AI, research, drafting, analysis
Document, knowledge & matter management
The consequential legal action commits
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 Decision Intelligence in the enterprise stack.
- L4 Decisioning
- L5 Decision Systems
- L6 Decision Infrastructure
- L7 Decision 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 Comparisons
Related Comparisons
Use these comparisons to understand how Decision Infrastructure differs from adjacent categories, systems, and governance models.
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 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 Icertis
Icertis manages contracts and obligations; Decision Infrastructure governs whether an action taken under them is admissible at execution.
Decision Infrastructure vs Decision Systems
Workflow-and-approvals systems exit before execution; Decision Infrastructure governs the act itself.