Expand description
Recheck policy freshness at queued, offline, and migration (NET-05.18).
A cached PolicyOutcome::Allow is not sufficient after queue, offline, or
migration. Sensitive work stays pending until a fresh Allow with a current
grant. A separately authorized help/accessibility path remains available while
sensitive work is pending. Blocked and Suspended contacts stay Denied;
payment cannot bypass. Packages remain open.
Structs§
- Freshness
Table - Sixteen-slot table of sensitive work waiting on a fresh current grant.
Enums§
- Freshness
Verdict - Result of a freshness recheck. Sensitive pending is not a help-path error.
- Recheck
Reason - Why admission must recheck protective policy and grant freshness.
Constants§
- MAX_
PENDING - Occupied sensitive-pending slots. A 17th distinct pending id is Capacity.
Functions§
- cached_
allow_ skips_ recheck - Cached Allow never skips a queued / offline / migration recheck.
- help_
accessible_ while_ sensitive_ pending - Help/accessibility remains available while sensitive work is pending.
- recheck
- Admit or re-admit after queued, offline, or migration.