Operator quorum.
Each operator publishes an audit record on a 60-second cadence that anyone can check independently without contacting Warrant. This page aggregates every operator and surfaces consensus and liveness. A regulator can audit the underlying record directly at operator-host/verifier/audit on any listed operator.
Per-operator state
Status flags: green in-window and agreeing with the majority. stale last update older than the 60-second window. divergent at least one consensus field disagrees with the majority. unreachable transport failure. malformed audit record missing a required field.
Cross-operator consensus
Three fields drive incident detection. Multiple buckets on any field is a published incident — operators MUST be running identical software against an identical regulation corpus, and their independent records MUST agree across the network.
What "incident" means
When the aggregator surfaces incident, one of three things is true: the reachable operator count is below the 5-operator floor (PRE-D.4), there's no clear majority on a field, or every operator is unreachable. In every case the on-call rotation is paged and downstream verifiers MUST treat any record issued during the incident window as provisional pending re-attestation.
Every audit record this page renders is independently verifiable without contacting Warrant — each is tamper-evident and offline-checkable, and commits to all the other fields. Verifiers MUST re-check the record against the operator's published registry at warrant.build/.well-known/operator-keys/<operator_id> before trusting an operator's claims downstream.