Appearance
Framework Library
Where to find it: Regulatory Compliance, then Frameworks (/frameworks) and Regulatory Library (/library).
The library is OrviQ's record of what authorities actually wrote. It is the reference layer beneath everything else in the platform.
What a framework is
A framework is a body of regulatory or standards content with internal structure: a regulation, a supervisory circular, an international standard, an internal group policy standard treated as binding.
Each framework holds requirements — individual clauses with a code, a title and the source text. The structure mirrors the source: parts, sections, clauses, sub-clauses.
The immutability rule
This is the property that makes everything downstream trustworthy:
Library content is never mutated by a compliance decision
When you decide clause A.8.1 does not apply to your organisation, OrviQ does not edit A.8.1. It creates a separate Applicability Record that references A.8.1 and holds your decision, your justification, your submitter and your approver.
The consequences are worth spelling out:
- Two scopes can disagree. The same clause can be Applicable in your payments environment and Not Applicable in your treasury environment, simultaneously, with different justifications and different approvers.
- The source text stays quotable. When an auditor asks what the clause says, the library answers with the clause, not with your interpretation of it.
- Framework updates do not destroy your decisions. Decisions attach to the requirement reference, not to a mutated copy of it.
How frameworks get into the library
| Route | Description | Permission |
|---|---|---|
| Catalogue import | Load a structured framework catalogue | library.import |
| Smart Extract | AI-assisted extraction from an uploaded document | library.smart_extract |
| Manual authoring | Write requirements directly | regulatory_library.manage |
The separation between library.import and library.smart_extract is deliberate. Extraction is day-to-day officer work; importing or hand-editing a catalogue is a manager-level capability because it changes the shape of the obligation universe.
What a requirement carries in the library
| Field | Purpose |
|---|---|
| Framework | Which body of content it belongs to |
| Clause code | The authority's own reference, for example A.8.1 or 5.1.2 |
| Title | A short human-readable name |
| Source text | The clause as published |
| Structure | Its position in the hierarchy |
What a library requirement deliberately does not carry: an owner, a status, an applicability decision, a compliance verdict. Those are tenant facts and live in tenant records.
Working with the library
Browse and search in Regulatory Library (/library) to find clauses by text, code or framework.
Review structure in Frameworks (/frameworks) to see the shape of a body of content and how much of it is adopted.
Locate (/locate) helps you find where a concept appears across frameworks — useful when you suspect an obligation is already covered by something you have adopted.
Frameworks and adoption
Having a framework in the library is not the same as adopting it.
| State | Meaning |
|---|---|
| In library | The content exists and can be searched, referenced and mapped against |
| Adopted | A Framework Adoption binds it to a declared scope for a stated purpose, seeding applicability records |
You will often hold library content you have not adopted — a standard you benchmark against, a regulation that applies to a different group entity, a framework you are evaluating.
Permissions
| Action | Permission |
|---|---|
| View regulations and requirements | regulatory_library.read |
| Edit or publish regulations | regulatory_library.manage |
| Import framework catalogues | library.import |
| Run the Smart Extract wizard | library.smart_extract |
All require the compliance core entitlement.
Example
A bank's library holds:
| Framework | Route in | Adopted? |
|---|---|---|
| Information security management standard | Catalogue import | Yes, for two scopes |
| National cyber assurance requirements | Smart Extract from the published document | Yes, group-wide |
| Outsourcing circular | Smart Extract following a change event | Yes, for the outsourcing scope |
| Payment card data standard | Catalogue import | No — retained for reference; the group does not handle card data |
| Group information security standard | Manual authoring | Yes, group-wide |
The payment card standard sits in the library unadopted. It is searchable and mappable, and it costs nothing to keep. If the group later acquires a merchant acquiring business, adopting it is a single governed action rather than a data-loading project.
Troubleshooting
"My applicability decision changed the clause text." It cannot. If clause text looks wrong, it was wrong at import or extraction. Correct it in the library through regulatory_library.manage, which is separately permissioned and audited.
"The same clause appears twice." Extraction can produce near-duplicates from documents that restate obligations. Merge candidates during extraction review rather than publishing both.
"I cannot see Frameworks." The compliance core entitlement is required, plus regulatory_library.read.