Docs/Policies & workflows

Policy sources and applicability

Screen 3.10 — maintain traceable references to official sources and review why they apply to a tenant.

PEEK Technical Reviewer

Live walkthrough · Policy sources and applicability

Policy sources and applicability — /peek/customers/tenant-a/3-10 — /peek/customers/tenant-a/3-10

Policy sources capture the exact official title, issuer, URL, section, dates and the applicability review for a tenant and use. The policy drawer shows verified scope and the accountable decision owner, or a pending-review status.

Note — Unverified, superseded and out-of-scope references can never display as binding. A product rule is labeled as a product rule. A rule from another program imported without applicability evidence shows as unverified scope, not a mandate.

3.10 · Policy Sources & Applicability

Maintain traceable references and why they apply. Open it at /peek/customers/tenant-a/3-10 (any tenant ID you can access works in place of tenant-a). The primary action is Review applicability, which requires authority.review.

How 3.10 works

1. Capture exact source title, issuer, location, section, dates and applicability review for the selected tenant/use

Screen 3.10 contract

Fields shown: Official title, issuer, URL, section, dates, scope, reviewer, status
Primary action: Review applicability
Required capability: authority.review
Validation: Unverified, superseded and out-of-scope references cannot display as binding. A product rule is labeled as a product rule.
Successful outcome: Policy drawer shows verified scope and accountable decision owner, or a pending-review status.
Screen states: Loading; empty; ready; restricted; stale; error; review pending
Audit event: admin.screen.3.10.action (acceptance test AT-UI-3.10)
Requirements: R02, R06, R07, R08, R28, R41, SYS02, SYS04, SYS06, SYS10, SYS11, SYS20, SYS23, UI-3.10

Boundary — Unverified references cannot be labeled binding authority.

Rejected even if the browser allows it — Import a CMS pilot rule into DHS without applicability evidence; show unverified scope rather than a mandate.

Related guides

Policy center and inheritance

Screens 3.1 and 3.2 — review effective policy with its sources and simulate how department, agency and office scopes inherit.

Permitted uses, persona access and evidence

Screens 4.3, 4.4 and 4.9 — recommend SI by persona, constrain processing by data class and purpose, and trace use cases to agency approval evidence.