Pre-production · synthetic data · runs entirely in your browser
Watch a callout become a sealed, tamper-evident record.
This is the WARDEN command console with a simulated thermal feed and telemetry. Everything you see forms live: the operating picture, the governance panel, and the cryptographic ledger — the sequence the console is designed to record at a real incident. No aircraft, no network, no stored imagery.
Operating pictureThermal · simulated
Feed offline
DFR // STANDBY
TELEMETRY OFFLINE
NO FACIAL RECOGNITION · OVERWATCH ONLY
Awaiting callout
Press Run demo to open a callout, authorise flight and bind the feed.
Nothing is captured without an incident.
Incident
—
Type
—
Location
—
Status
—
Altitude
—
Battery
—
Ground spd
—
Mode
—
Governance
Your rolecommander
Lawful basispublic task (proposed) · DPA 2018
Facial recognitionnot integrated
Retention—
Stored medialive-only by default
Recordhash-chained
Overwatch ledgerSHA-256 · demo key
tamper-evident
AUDIT LEDGER · ARMED
Every authorise, flag, purge and seal is hash-chained, here with a throwaway demo key in your browser.
Run the demo to begin.
Every authorise, flag, purge and seal is hash-chained, here with a throwaway demo key in your browser.
Run the demo to begin.
Real: content_hash is a genuine SHA-256 over the canonical event, each chain_hash really links an event to the last, and the verifier recomputes the whole chain. Simulated: this whole console is a browser simulation: the thermal feed, the telemetry, the media purge (Warden's scheduled deletion is designed but not yet switched on), and the chain itself, which links events with a keyed hash (HMAC) under a throwaway demo key written into this page. The live ledger does not work that way: Warden's backend chains each event with keyless SHA-256 and signs each link with Ed25519 under its published key, whose fingerprint is on Verify, so anyone holding an export can check it without Warden. Events up to its latest time-stamped anchor (one whose token verifies) also carry an outside RFC 3161 time-stamp, so they cannot be altered undetected after that time-stamp; newer events are not covered until the next anchor. Tamper-evident, not unbreakable.