Aether

Koverse edge system · Sole designer · SAIC, 2021–2026

Some sites can never appear on a map, but their data still has to reach the people cleared to see it. I designed Aether to do both. The original is classified, so the version below is a live rebuild.

Craft detail

The Site KILO detail panel: latitude, longitude and region all rendered as NOT HELD chips under the line governed, visible, never plotted, beside a sidebar explaining that geography is treated as data and carries a label like any record. — Site KILO

A location the system holds and will not show. Governed, visible, never plotted.

The three panels of the Aether import confirmation: what changes on commit, what does not change, and if a label is wrong, with immediate, 61 accounts and not recallable set at full weight above the typed dataset confirmation field. — Import confirmation

What the next click reaches, before you make it. Reads that already happened cannot be recalled.

A run of Aether site rows showing all three status states: blue diamonds for synced sites, an amber diamond for Guam NAVBASE degraded at 0.3 GB/s, and a hollow diamond for Faslane HMNB offline. — Site status

Blue synced. Amber degraded. Hollow offline, because offline is an absence, not an alarm.

The whole system

The real thing, live, not a walkthrough. Go be the data scientist: import five files, hover a site that will not say where it is.

The Aether overview for the Trident Submarine edge deployment, the prototype's first frame: 23 datastreams connected, 11 of 15 sites reporting, 1.2 million ABAC decisions in 24 hours, and a table of available datastreams.

There is a decision behind every screen. Ask me about any of them.