Public entry path
Whether the path visitors travel is currently healthy, measured from outside.
Status pages usually show a wall of green. Ours shows the real state of each capability, including the ones still being validated and the ones we have not finished.
A capability is only marked available while a recent check backs it. Otherwise it drops to Unknown, on purpose.
Read from the running control plane, not written by hand. A capability turns green only while a recent check backs it; when the check ages out it drops to Unknown, and when something is degraded it says so here first.
Every capability has a narrow responsibility, an operational state and evidence that explains the result.
Whether the path visitors travel is currently healthy, measured from outside.
Whether attack-pattern checks are only reporting or actually acting, per service.
When recovery was last rehearsed and whether that rehearsal passed.
The visitor path remains short. Configuration, verification and rollback stay visible to the operator at every stage.
Available, watching, needs setup, degraded, unavailable or planned.
Each state shows when it was last confirmed.
Releases and their effects are published as they happen.
AegiFlow does not turn missing evidence into a reassuring zero. Every state links to its source, freshness and next action.
How this capability behaves in production — grounded in the platform's documented, current operation.
A status page that is always green tells you nothing. Here a capability turns green only while a recent check backs it; when the check ages out, the state drops to Unknown on purpose. Some capabilities are shown as in observation or unavailable because that is genuinely where they are.
Ownership, certificate, origin health and rollback must pass before traffic protection changes.