Aether

Koverse edge system · Lead designer · SAIC, 2021–2025

Aether is the edge system of SAIC’s Koverse Data Platform: sites around the world publishing streams of sensitive data, with every record locked to the people cleared to see it. The engineering worked. Adoption didn’t. I was brought in early in my career, often the least technical person in a room of PhDs and data scientists, and my job turned out to be asking the questions everyone assumed were already answered.

The original is classified, so everything below is a working rebuild.

Two jobs

The site. An edge site publishes its streams and decides, down to a single field, who can read them. Access runs on attributes, so the screen shows what each choice will release before it happens.

The Aether datastream screen for sonar_contact_tracks: throughput now, 24-hour average, peak and records today, a trailing 60-second throughput chart, three subscribers and a live event log of ABAC read decisions.

Datastream

A site’s published stream, who subscribes to it, and every read decision as it lands.

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

Shows exactly what the import will release before you click, because once a record has been read, it can't be pulled back.

The admin. One dashboard to see every site and stream, route data, and manage who subscribes to what, including sites that can never be shown on a map.

The Aether geographic reference: sites plotted on a world map with San Diego NAVBASE open, showing five streams, 2.4 GB/s and 186K decisions in 24 hours over a live throughput strip, beside the site list with Guam degraded, Faslane offline and two sites whose locations are withheld.

Map

Every site at a glance: blue is synced, amber degraded, and offline sites are drawn hollow because there’s no signal to fill in. Open one for its streams and the last day’s decisions.

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 site the system knows about but never puts on the map. Its data still reaches the people cleared to see it.

The whole system

This is a working rebuild. Try it the way a data scientist would: import five files, then hover over the site that won't show its location.

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.

Most of the work was subtraction: cutting steps nobody needed until the product matched the way analysts already worked. Koverse is still an SAIC product today.