Decision Dossiers
Decision Dossiers are governed AI-supported artifacts for decision work. They collect citations, coverage notes, recommendations, review posture, and evidence references in one place before a policy, procedure, control, watcher, or other owning workflow is allowed to publish final truth.
The dossier is not the final decision system. It is the reviewable artifact that helps people understand what the AI used, what is missing, what options were considered, and what needs approval.
What You Can Manage
| Record | Use it for |
|---|---|
| Decision brief | Capture facts, assumptions, options, risks, alternatives, citations, and the recommended next step. |
| Coverage matrix | Compare a policy, framework, requirement, or control set against available evidence and gaps. |
| Policy or procedure draft | Keep an assisted drafting artifact separate from final DMS or policy truth. |
| Impact analysis | Record scenario assumptions, affected areas, and operational impact notes for review. |
| Monitoring plan | Capture candidate KPIs, baselines, targets, data sources, and gap or delay signals. |
| Policy-to-action candidate | Record proposed obligations, controls, evidence, lifecycle, responsibility, or watcher bindings before owner approval. |
Dossiers can be created, updated, approved, rejected, and archived. Approval in this surface records the dossier review posture only. Publishing to documents, controls, obligations, risks, findings, incidents, lifecycle reviews, or watchers must still go through the owning module.
How To Use It
- Start from an approved AI system, retrieval policy, AI run, source document, catalog pack, or other governed source reference.
- Capture citations and evidence refs instead of raw source text.
- Record coverage and recommendations as structured summaries.
- Use review posture to show whether the dossier is draft, under review, approved, rejected, or archived.
- Move final work through the owning workflow when the customer policy allows publication.
Boundaries
Decision dossiers should contain refs and sanitized summaries. Do not paste raw document text, provider prompts, provider responses, credentials, storage paths, or private reviewer notes into dossier snapshots.
AI does not directly write final truth for:
- DMS documents or approved policy versions;
- obligations, controls, evidence requirements, or lifecycle definitions;
- risks, findings, incidents, violations, exceptions, or submissions;
- authority-facing assurance snapshots.
Those records remain owned by their source modules and governed foundations. The dossier can support the review, but the owning module performs the final mutation.
Cloud, Sovereign, And No-AI Profiles
Cloud and Sovereign AI-enabled deployments include Decision Dossiers inside the optional AI feature bundle.
No-AI Sovereign profiles physically exclude the AI feature bundle, including Decision Dossier pages, routes, schema, and runtime code. Customers moving from no-AI to AI-enabled deployments should use the supported upgrade path, configure providers and authorizations, and register context sources before using dossiers for production decisions.