Impact Analysis

Impact Analysis is the workspace module for source-backed decision support.

Use it when a team needs to evaluate a policy, process, control, document, operating model, customer requirement, or regulated change before moving to approval, reporting, or execution.

What Impact Analysis Owns

Analysis cases.
Model and profile snapshots.
Assumptions, scenarios, options, alternatives, and impact dimensions.
Source refs to Source Graph, regulated content, DMS, regulatory register, connectors, governed evidence, or other source owners.
KPI and monitoring candidate refs.
Confidence, limitation, and reviewer decision snapshots.
Decision-brief and audit-export handoff refs.

Impact Analysis is a decision-support module. It does not own governed indicators, monitoring runs, source graph truth, regulatory register truth, DMS content, AI prompts, model runs, embeddings, vectors, final policy approval, compliance posture scores, or audit package generation.

User Journey

Open Governance > Impact Analysis.
Create an analysis case for the decision or change being reviewed.
Record the model/profile snapshot, assumptions, scenarios, options, and impact dimensions.
Add source refs and citation/supporting evidence refs from owning modules.
Record reviewer decisions, limitations, and confidence posture.
Inspect the related Decision Receipt for approved, rejected, changes-requested, or blocked review decisions.
Use the decision-brief/export handoff refs for audit packages, work follow-up, posture signals, monitoring, or regulated content workflows.

Decision Receipts

Impact Analysis records governance decision receipts for review decisions that approve, reject, request changes, or block the analysis.

The receipt binds the impact-analysis review to the parent case, reviewer or approver member refs, decision/rationale evidence refs, and integrity state. It remains a provenance artifact only; it does not become final approval truth, posture scoring, BI output, simulation output, or audit package generation.

Stress And Scenario Evidence

Use stress evidence when a team needs to show how governance behaves under pressure before changing source truth.

Typical records include stress-test cases, operational scenarios, scenario templates, perturbation runs, expected behavior, observed behavior, and improvement handoff refs. These records should reference safe source-owner evidence such as workflow gate outcomes, monitor freshness, indicator breach state, source graph drift, AI agent stop conditions, AI quality acceptance, or multilingual parity evidence.

Stress evidence is reviewed decision support. It can create work descriptors, posture signals, and audit-package fields, but it does not mutate control, risk, incident, source graph, work item, AI, or compliance-posture truth directly.

AI Boundary

AI can assist with assumptions, scenario outlines, alternatives, risk/control candidates, KPI suggestions, and draft decision briefs when policy allows.

AI output remains advisory until reviewed. This module records source refs, snapshots, reviewer decisions, and capability states. It does not execute AI, store prompts, create embeddings, rank retrieval results, or decide final approval.

Cloud And On-Prem

Cloud and on-prem expose the same Impact Analysis behavior. Deployment differences should appear as capability states such as deployment-dependent, provider-not-configured, policy-blocked, no-AI profile, reference-only, or evidence-required.

Do Not Use This Module To Claim

Predictive modelling, simulation engines, or BI warehouse behavior.
Automatic stress-test pass/fail decisions without reviewer evidence.
Certified legal, operational, financial, or regulatory conclusions.
Guaranteed AI, OCR, or translation accuracy.
Public /api/v1 impact-analysis APIs.
Confidential vector search or automatic vectorization.
Fixed SLA, support, residency, or certification.

Those outcomes require supporting source-owner evidence.