Reviewing whether a mandate still holds after deployment.
Compliance signals can stay green while the gap between what a system was authorized to do and what it is actually doing quietly widens. This page explains the idea and how to request a review — not the internal metrics or thresholds used to detect it.
Passing controls is not the same as an unchanged mandate.
A system can pass every scheduled control and still be operating further from its original mandate — the documented condition under which it was originally approved to act — than anyone realizes, because nothing in a routine control checks for that specific gap.
This review looks at the distance between what was authorized and what is happening now, and how long that gap has existed — not at whether the system's outputs are individually correct.
A bounded finding
Whether the current operating state still matches the authorized mandate, within the scope reviewed.
A reliance boundary
Where the finding may be used to support a decision, and where it stops applying.
A reopen condition
What would make this finding due for another look.
The full technical protocol — including how drift is formally measured — is published as a citable research specification, not disclosed as an operating method here.