Appearance
Content Library & Content 2.0
Where to find it: Policy Governance, then Content Library (/governance/packs).
The Content Library provides tenants with immediate access to OrviQ's certified Content 2.0 corpus. It allows compliance and governance teams to browse, preview, and adopt pre-structured, atomic governance instruments directly into their internal policy register.
Requires the content_library entitlement.
Authoritative Content 2.0 Inventory
The Content 2.0 release delivers a curated corpus designed specifically for regulated financial institutions and enterprise operating environments:
| Metric | Certified Count | Description |
|---|---|---|
| Unique Governance Instruments | 110 | Certified instruments (DOC-2026-0001 through DOC-2026-0110) spanning universal governance, prudential banking, Shariah compliance, and market infrastructure |
| Document Sections | 518 | Structured thematic subdivisions across all 110 governance instruments |
| Atomic Statements | 1,058 | Actionable, single-obligation governance statements engineered for operational mapping |
| Pending Substantiation Statements | 25 | Specialized clauses requiring tenant-specific parameterization |
| Total Pack Memberships | 190 | Cumulative inclusions of the 110 governance instruments across certified packs |
Governance instruments vs. policy templates
OrviQ deliberately classifies these 110 items as governance instruments rather than generic "policy templates". The corpus contains complete institutional governance charters, codes of conduct, supervisory frameworks, committee terms of reference, and statutory standards in addition to operational policies.
Certified Content Packs
The library organizes governance instruments into five certified domain packs:
| Pack Key | Pack Title | Document Memberships | Target Scope & Jurisdiction |
|---|---|---|---|
ORV-PACK-CORE | OrviQ Core Governance Library | 103 | Universal corporate governance, information security, data protection, business continuity, risk management, and vendor oversight |
ORV-PACK-BANKING | Commercial Banking & Risk Governance Pack | 37 | Prudential banking operations, credit risk, market risk, liquidity management, AML/CFT, capital adequacy, and internal audit |
ORV-PACK-SBP | Pakistan / State Bank of Pakistan Governance Pack | 38 | Targeted statutory compliance for State Bank of Pakistan (SBP) circulars, PRs, and regulatory inspection readiness |
ORV-PACK-ISLAMIC | Islamic Banking & Shariah Governance Pack | 7 | Shariah governance framework, Islamic banking contracts, Murabaha/Ijarah controls, and Shariah board compliance |
ORV-PACK-PAYMENTS | Digital Payments & Financial Infrastructure Pack | 5 | Payment systems operator (PSO) governance, digital wallet security, interchange standards, and clearing house rules |
Note: The sum of pack memberships (190) exceeds the count of unique governance instruments (110) because foundational governance instruments (such as Enterprise Risk Management, Information Security, and Business Continuity) are members of multiple domain packs.
Adoption Workflow
When a team decides to utilize an instrument from the Content Library, they initiate the governed adoption workflow:
- Preview & Selection: Users holding
policy_pack.readinspect instrument metadata, structured sections, and atomic statements in the read-only catalog preview. - Adoption (
policy_pack.adopt): The compliance officer chooses between full pack adoption or selective instrument adoption. - Tenant Instantiation: The adoption engine creates a tenant-local
PolicyRecordand correspondingPolicyStatementrows in the tenant's private database. - Draft Status: All adopted instruments enter the tenant register with lifecycle state
draft. They are immediately editable, versionable, and ready for internal stakeholder review. - Immutable Provenance: Each adopted policy and statement retains an immutable catalog source reference (
source_pack_idand template version identifier), preserving full audit traceability to the originating certified release.
Decoupled Retention & Ship-Dark Behavior
The Content Library enforces strict decoupling between catalog subscription and adopted policy ownership:
- Adopted policies survive entitlement disablement: If a tenant subsequently revokes or disables the
content_libraryentitlement:- All previously adopted policies remain fully functional, editable, and versionable in the tenant's internal Policy Register.
- Active operationalizations, indicator links, and employee attestation campaigns remain completely intact.
- Only browsing the external catalog at
/governance/packsand minting new adoptions are blocked.
- Tenant Ownership: Once adopted, a policy is owned exclusively by the tenant. Content updates in the central catalog never overwrite internal draft or published text without explicit, governed change impact triage.
Semantic Doctrine
Semantic Doctrine: Adoption != Compliance
Adopting a certified governance pack into your tenant creates internal draft policy text. It establishes that formal documentation exists within your organization.
- Adoption is not compliance: Adopting
ORV-PACK-BANKINGdoes not certify regulatory compliance with central bank requirements. - Adoption is not operationalization: Pre-structured statements must be operationalized against internal controls, systems, and accountable owners.
- Adoption is not adherence: Having adopted policy statements does not demonstrate that staff follow them or that automated controls enforce them.
Permissions Reference
| Action | Permission Key | Required Role(s) |
|---|---|---|
| Browse Content 2.0 catalog, packs, and adoptions | policy_pack.read | Tenant Admin, Compliance Manager, Compliance Officer, Auditor |
| Author and version catalog packs/templates | policy_pack.author | Tenant Admin, Compliance Manager |
| Preview and adopt packs into tenant policies | policy_pack.adopt | Tenant Admin, Compliance Manager, Compliance Officer |