Skip to content

Intelligence and datasets

Protocol decoders produce observations. Intelligence services correlate those observations into useful entities while preserving source, protocol, receiver, and capture-time provenance.

Station intelligence

Station intelligence combines decoded identity, frequency, callsigns, signal relationships, and local regulatory context. It does not turn an FCC record into proof that a particular over-the-air station was heard; the relationship and its evidence remain explicit.

StationIntelligenceService is the shared browser facade over a station worker and separate learned-state IndexedDB. Decoder rows read compact RAM projections; explicit investigations request bounded history and regulatory dossiers. FCC records remain in their independent reference store, not copied into each RF observation. Station evidence explains transmitter roles, replay identity, receiver-relative geography and loss accounting.

Aviation intelligence

flowchart TB
    ES[1090ES observations] --> NORM[Protocol-normalized observations]
    UAT[978 UAT observations] --> NORM
    FAA[FAA local metadata] --> ENRICH[Evidence-qualified enrichment]
    NORM --> ID[Cross-protocol identity resolution]
    ID --> LIVE[Incremental current aircraft]
    ID --> HISTORY[(Authoritative observation history)]
    ENRICH --> LIVE
    LIVE --> DELTA[Changed-aircraft deltas]
    DELTA --> TABLE[Aviation workspace]
    DELTA --> MAP[Entity-keyed map]
    HISTORY --> REPLAY[Indexed as-of queries]

The same aircraft can have 1090ES and UAT provenance. Fresh, trustworthy state wins field by field; the losing observation is not discarded. FAA enrichment adds registration, type, manufacturer/model, ownership, and category evidence. Government/military classification is conservative and is never based on a callsign alone.

The workspace and map share AviationIntelligenceService and aircraft selection, separate from amateur station/FCC identity. Live projections are RAM-only; explicit history queries use the aviation worker and IndexedDB. See aviation identity, paging and replay limits.

SATCOM product intelligence

Validated GOES HRIT CADUs feed a dedicated product worker. It demultiplexes virtual channels, reconstructs packets/files, assembles segmented imagery, parses received metadata, and stores originals and derivatives. Product source is distinct from relay spacecraft: GOES can relay imagery or messages whose originating source differs.

Local-first update pattern

Large external reference datasets follow this pattern where practical:

flowchart TB
    SOURCE[Authoritative public source] --> UPDATE[Bounded appliance updater]
    UPDATE --> GEN[Atomic versioned generation]
    GEN --> STATIC[Pi-local served artifact]
    STATIC --> HYDRATE[Browser hydration / SQLite / cache]
    HYDRATE --> QUERY[Offline query and enrichment]

The appliance updater validates and atomically publishes a generation. The browser hydrates or queries it locally. Ordinary decoding does not call an Internet API.

This is not a universal appliance-ownership rule: the FCC corpus is the browser-managed exception below. Its appliance component relays a fixed archive; it does not build or retain a regulatory database.

FCC corpus

The gateway provides a fixed-source streaming relay for the FCC weekly Amateur archive. The browser verifies and imports the corpus into SQLite WASM/OPFS. Indexed mode is the default, preserving explicit saved Indexed/Eager choices. Both modes hydrate compact license summaries, callsign-to-USI relationships and the callsign index into worker RAM. Eager explicitly warms a larger SQLite page cache for forensic work; it does not create a second callsign index. Progress, cancellation, estimated transition-peak admission and worker recycling keep this optional acceleration separate from evidence retention.

One owner holds the exclusive Web Lock for the active SQLite generation; follower tabs use coordinated requests. Updates stage and validate another generation before publication. See FCC data lifecycle for relay scope, source preservation and replacement, and operating controls for RAM behavior.

FAA aircraft data

The background aviation updater atomically publishes a versioned Pi-local dataset. The browser fetches ICAO-prefix shards on demand, persists matched metadata in IndexedDB and keeps resolved/no-match addresses in service RAM. Enrichment is optional to raw decoding and does not change protocol evidence. Generation provenance is not an effective-date filter: see the historical FAA limitation.

Map references

Natural Earth geometry, celestial catalogs, orbital elements, and geocoding indexes have explicit provenance and local generated artifacts. Their update cadence differs; none should become a hidden prerequisite for receiving RF.

Background job behavior

Updaters and migrations use bounded batches, resumable cursors, and atomic publication. Failed candidates do not replace the current valid generation. Workers publish compact keyed status at a human-scale cadence; they do not copy large archives into React state.