Skip to content

Regulatory Compliance ​

Everything from watching a regulator publish to stating a governed position on whether you meet the obligations inside it.


Pages in this area ​

PageRouteWhat it does
Regulatory Sources/reg-intel/sourcesMonitored external publication points
Regulatory Changes/reg-intel/changesDetected changes awaiting triage
Frameworks/frameworksAdopted and available bodies of regulatory content
Assets & Inventory/inventoryThe technology inventory
Scope & Applicability/scope-applicabilityFramework adoptions and applicability decisions
Scope Registry/scope-registryDeclared scopes and effective-dated membership
Requirements/requirementsThe obligation register
Compliance Activities/activitiesDecomposed, ownable obligation work
Regulatory Library/librarySearch and browse regulatory content
Smart Extract/smart-extractAI-assisted extraction from documents
Requirement Assurance/ncapThe five-dimension assurance cockpit

Documentation for this area ​

ArticleWhat it covers
Regulatory & Compliance overviewThe whole domain, with a reading order
The Requirement PipelineThe twelve stages and why each is separate
Compliance DeterminationWhat contributes, what does not, and why percentages are never fabricated
Requirements RegisterFields, tabs, statuses and ownership
Framework AdoptionBinding a framework to a scope
Scope & ApplicabilityApplicable, Not Applicable, and the approval that makes it authoritative
Statement of ApplicabilityLive derivation, historical reconstruction and export
Requirement AssuranceThe five dimensions and governed review

If you read one page in this area

Read The Requirement Pipeline. Most questions about this domain are answered by knowing which stage you are at.


Permissions and entitlement ​

Core requires the Compliance Core entitlement. Regulatory Intelligence requires its own. Key permissions: obligations.read, compliance.read, assurance.read, scope.read, reg_intel.read, library.smart_extract.


OrviQ Enterprise Governance, Risk & Compliance Platform