Compliance Pack
What this screen is for
This screen shows one compliance pack from your tenant's policy screens: the definition of one regulatory regime or governance framework as this release declares it. It is the same definition the platform administrator reads, and it does not vary by tenant. Nothing here can be edited.
A pack gates nothing. Which algorithms your tenant may use is decided by your tenant's algorithm policy, within the deployment's limits, and a pack changes none of it. Use the pack to see what a regime asks for next to the policy you set.
What must exist first
The screen is reached from the tenant's policy screens.
- The permission to read your tenant's algorithm catalogue shows the pack. Without it the entry is not offered.
- A pack identifier this release defines. An identifier that names no pack answers not found.
Decisions you make here
Reading the summary and the sources
The header gives the pack's title, its kind (a regime, or governance), its version and a short summary. Each source is listed with its edition as printed, its publication date at the precision the source prints, and a link to the primary document. A source marked DRAFT is a draft, and so is every calendar entry taken from it.
Reading the controls against your policy
Each control names the source section it transcribes, the source's own force (SHALL, SHOULD, MAY, SHOULD NOT, SHALL NOT) and how it could be evaluated: Platform-observable, from the platform's own state, or Attested by the customer, from evidence outside it.
The algorithms a control names are catalogue identifiers, the same names your algorithm policy lists, so you can compare the two directly. A satisfied platform-observable control does not mean the regime is satisfied. This screen shows the definition only; how your keys stand against a pack the licence includes is on the evaluation screen.
Reading the calendar
The calendar is grouped by use category, in the source's own words. For a Deprecated after, Disallowed after, Not to be used alone after or Recommended until milestone, the date shown is the last day the earlier state holds. For Supported and preferred by and Used exclusively by, it is an inclusive deadline. When the source gives only the year a state begins, as in "from 2027", the new state holds from the first day of that year, whatever the milestone.
A date the source gives as a year is shown as the year, and a milestone without a date shows the source's wording. This screen compares no date with today; the evaluation reads the calendar on a reference day. Entries scoped by risk carry the source's risk class; which class a use case of yours belongs to is your organisation's call.
Reading what is not offered
Not offered lists what the regime requires or recommends that the platform does not offer. Your policy cannot admit these: they are not in the catalogue.
How it relates to other screens
Your tenant's algorithm and lifecycle policies are set from the Policies hub.
Compliance Evaluation shows the pack evaluated against your keys: