Activating a PolicySet compiles every active set into one snapshot (< 2 s at 10k rules),
signs it with the ed25519 snapshot key, and stores it; the snapshot id is the content address
of the CBOR blob, served over GET /v1/snapshot with an ETag. Distribution is pull-based, with
a push nudge for idle sessions:
a busy session adopts it via the post-decision check of straza service (a background
conditional GET, at most once per the managed config's snapshotLagSeconds for each user, default
30 s; a busy session lags at most one tool call plus that); an idle session whose push stream is
up gets the policy-update push nudge and adopts in under 5 s, and without one no timer runs: its
first call after a change still decides on the old snapshot unless that call renews the session,
and the check it starts brings the new one for the calls after it; new sessions and token refreshes fetch it
at checkin. In every lane the blob is fetched and its signature
verified before the session's snapshot id advances. An id alone would brick hooks.
If the security layer is unreachable and no valid signed snapshot exists within the grace TTL
(enterprise default 0, standalone 15 min), the client fails closed and denies everything
governed. When a change must land in under 2 seconds, the lever is the session kill switch,
not policy distribution.