Protection states, from observation to enforcement
What Observe, Shadow and Enforcing mean, which gates sit between them and how you move safely in both directions.
You know exactly what changes for visitors in each protection state.
Observe
Traffic is measured; nothing changes for visitors. Inventory, threat relevance and traffic telemetry accumulate so every later decision has evidence.
Shadow
Candidate rules run against real traffic without blocking anything. You see exactly what would have been flagged, and false positives cost nothing.
Enforcing
The Safety Contract permits only bounded scope, a TTL and a defined rollback path. Provider-changing enforcement remains unavailable until certificate, origin-stability, health, shadow and rollback gates all have fresh evidence. This page defines the state model; the live status reports what is currently active. Autonomous blanket blocking does not exist in AegiFlow.
Moving between states
Transitions are explicit operator decisions and work in both directions. Returning to Observe is always permitted by policy, but the broker still requires a verified provider rollback receipt before the runtime can claim that the change completed.
Verification
- You can list the gates required before enforcement
- You know how to return to a previous state