Policy drift and exceptions
Screen 8.4 — compare released rules with effective configuration and route remediation.
PEEK Platform Administrator · PEEK Technical Reviewer
/peek/customers/tenant-a/8-4 Live walkthrough · Policy drift and exceptions
Drift review compares the agency’s adopted configuration with catalog changes, expired decisions and exceptions, and creates a scoped review item with owner, reason and evidence. It preserves the current valid baseline.
Note — Drift never auto-adopts a recommendation or expands authority — releasing a new recommendation leaves live agency settings unchanged. Explicit restrictive controls still apply immediately.
8.4 · Policy Drift & Exceptions
Compare released rules with effective configuration. Open it at /peek/customers/tenant-a/8-4 (any tenant ID you can access works in place of tenant-a). The primary action is Route remediation, which requires drift.review.
How 8.4 works
1. Compare adopted agency configuration with catalog changes, expired decisions and exceptions
2. Route remediation
Screen 8.4 contract
- Fields shown
- Drift source, affected scope, exception expiry, disposition
- Primary action
- Route remediation
- Required capability
drift.review- Validation
- Drift detection cannot auto-adopt a recommendation or expand authority. Explicit restrictive controls still apply immediately.
- Successful outcome
- Create a scoped review item with owner, reason and evidence; preserve the current valid baseline.
- Screen states
- Loading; empty; ready; restricted; stale; error; review pending
- Audit event
admin.screen.8.4.action(acceptance testAT-UI-8.4)- Requirements
- R02, R06, R28, SYS02, SYS04, SYS06, SYS10, SYS11, SYS20, SYS23, UI-8.4
Boundary — Policy drift does not silently trigger new authority or auto-adoption.
Rejected even if the browser allows it — Release a new recommendation and verify that live agency settings do not change automatically.