AegisLedgerAI never types a status string by hand. Each signal carries five orthogonal state dimensions, and the visible badge is derived from them through a fail-closed priority. A connected source whose controls are paused is shown as connected read-only and paused — never as active execution. The worst dimension always wins.
The public dashboard currently derives to SYNTHETIC. No state is named LIVE until a verified source is independently accepted and its evidence passes.
Fail-closed priority
The first dimension to match, in this order, determines the visible badge:
- Revoked evidence / Quarantined control
- Disconnected
- Expired freshness
- Degraded connectivity / Stale freshness
- Synthetic / Unverified data mode
- Verified-local
- Verified-external
A verified-local signal with revoked evidence is shown as QUARANTINED, not verified. Priority is never re-ordered by a happy path.
The five dimensions
What the bytes actually are — simulated, ingested-but-unverified, or independently verified.
Whether an upstream source is reachable, and whether only the read path is asserted.
Whether the record is within its staleness window or has expired it.
Whether any execution control path is enabled, paused, or quarantined.
The verification status of the accompanying cryptographic evidence.