Regulated Content

Regulated Content is the workspace foundation for coordinating governed content work across source owners.

Use it when a team needs a generic case workspace for policy, procedure, board note, committee memo, controlled notice, contract pack, evidence narrative, circular response, or other regulated content workflows.

What Regulated Content Owns

Regulated content cases and workspaces.
Workflow template snapshots for review, change, publication, execution, AI-preparation, consultation, impact-analysis, or monitoring handoffs.
Draft intent records that reference source grounding, quality posture, and AI policy posture.
Source context refs to DMS, Source Graph, Enterprise Connectors, Content Extraction, terminology, governed source, regulatory register, or other owners.
Handoff refs to DMS, review-approval, change-management, rendition, document-execution, and audit packages.
AI-preparation eligibility requests for bulk source selection.

Regulated Content is a coordination layer. It does not own DMS documents or versions, review decisions, change transitions, source graph truth, connector jobs, content extraction chunks, AI prompts, model runs, embeddings, vectors, retrieval ranking, audit package generation, work item lifecycle, or compliance posture scores.

User Journey

Open Governance > Regulated Content.
Create a generic case for the content workflow.
Add source context refs from source-owning modules.
Record draft intent, workflow, and handoff posture.
Record an AI-preparation request when sources need eligibility review for AI knowledge use.
When a handoff reaches a decision-like state, inspect the related Decision Receipt for the source-owner ref, target-owner ref, actor, evidence state, and integrity posture.
Use the contributed audit export fields, work descriptors, compliance posture signals, Activity presentation, and security events for follow-up and evidence.

Decision Receipts

Regulated Content records governance decision receipts for stable handoff outcomes such as accepted, completed, rejected, blocked, and reference-only.

The receipt points back to the regulated-content case and handoff, and may link the target owner, such as DMS, review approval, change management, document execution, or audit packages, through sanitized refs. It does not copy DMS content, source text, AI prompts, model output, vectors, storage keys, or target-owner runtime truth.

AI Preparation

AI preparation is a request and eligibility posture in this module. It is not a vectorization engine.

Allowed outcomes include eligible, needs-extraction, already-indexed, policy-blocked, provider-not-configured, unsupported, no-access, retention-blocked, classification-blocked, and deployment-dependent.

If policy allows a source to become AI knowledge, the source path still goes through the owning foundations:


connector or DMS/source owner
  -> content extraction and source-owner access checks
  -> optional AI context indexing owned by AI
  -> Document Intelligence or Copilot retrieval with citations

Cloud And On-Prem

Cloud and on-prem expose the same Regulated Content behavior. Deployment differences are represented as capability states such as deployment-dependent, provider-not-configured, policy-blocked, no-AI profile, or reference-only.

Do Not Use This Module To Claim

Legal validity or publication approval.
Certified AI or OCR accuracy.
Public /api/v1 regulated-content APIs.
Confidential vector search.
Guaranteed SLA, support, residency, or certification.
Provider-specific SharePoint, Power BI, SIEM, or DMS adapter execution.

Those outcomes require source-owner evidence.