Skip to content

Intelligence and maps roadmap

Status: WebSDR Phase 9A–E accepted; future geographic adapters and scan integration remain open. The celestial Globe extension was accepted 2026-09-30.

Scope, decisions and dependencies

Station intelligence owns capture-time/replay-idempotent learned evidence. FCC regulatory truth remains separate SQLite/OPFS data, with RAM-only compact enrichment. The operator approved this representation 2026-09-07 after the retained FCC benchmark. Chrome is the reference; Firefox is welcome but is not a Phase 9B release blocker. The dated import-start reset exception does not permit sustained RF degradation. Today's Indexed default respects explicit saved preferences.

Phase 9A was accepted 2026-09-06; 9B–D on 2026-09-07; the shared map on 2026-09-09. Map projection is a consumer of the shared service and selection, not a parallel station/geography store. Mailing-address geography is regulatory context, never proof of a transmitter or residence. Best Estimate retains both sources on disagreement. Reference time controls RF, orbital and celestial layers; hidden-view restoration catches up from a monotonic anchor, while paused history stays fixed. These constraints also apply to future aviation adapters.

The local basemap is geographic, not street navigation. Optional photography requires its selected Internet provider. Geocoder source coverage can be locality-only; updates stage atomically and retain last-good data. Orbital RF metadata is curated, not exhaustive. These are product limits, not reopened 9E gates. Current map architecture owns rendering, geocoder and pop-out behavior.

Acceptance criteria and open gates

These are retained acceptance records, not qualification of the current source. Checked items keep their recorded scope; implementation, qualification and operator acceptance are distinct. Later work does not close unchecked gates.

Phase 9 — Maps and Enrichment

Phase 9A — Contracts and Transport

  • [x] ~~Define provider-neutral contracts that keep station identity, regulatory identity, geographic assertions, decoded RF observations, and derived intelligence separate.~~
  • [x] ~~Preserve callsign reassignment and one-to-many callsign-to-FCC-USI relationships in the regulatory contracts.~~
  • [x] ~~Add role-aware FT8/FT4 station-observation normalization so a decoded grid is attributed to the transmitting station rather than merely the first token.~~
  • [x] ~~Define compact and full dossier projections over the same source data, without copying FCC records into station-observation objects.~~
  • [x] ~~Encode geographic provenance and precedence: explicit user location, trusted receiver configuration, decoded station grid, then clearly labelled approximate FCC-address and prefix/DXCC fallbacks as applicable.~~
  • [x] ~~Define Auto, Eager, and Indexed RAM-hydration policies. Keep the compact decode path storage-free and target effectively instantaneous, sub-millisecond hot-tier callsign enrichment.~~
  • [x] ~~Add a dedicated enrichment worker foundation and report IndexedDB, OPFS, origin quota, persistence, device-memory, and heap-limit capabilities where browsers expose them.~~
  • [x] ~~Add an explicit canonical-origin warning because browser durable storage is partitioned by origin; do not silently redirect valid appliance origins.~~
  • [x] ~~Add a narrowly allowlisted, single-transfer, bounded-backpressure FCC archive relay inside rfsentry-api. Support GET/HEAD and safe conditional or byte-range request headers without adding a daemon, cache, parser, arbitrary proxy target, receiver wake, or device authority.~~
  • [x] ~~Validate direct relay headers and a bounded partial transfer from the real RF Sentry browser origin in current Chrome. Retain Firefox validation as an explicit compatibility gate where no remote Firefox session is available.~~
  • [x] ~~Update architecture, operator, and implementation documentation, then obtain operator acceptance before committing Phase 9A.~~

Phase 9B — Corpus Benchmark and Data Plane

  • [x] ~~Before selecting an irreversible format, benchmark the current complete FCC archive in the real RF Sentry browser environment using SQLite/WASM + OPFS against OPFS + optimized RAM structures and, if still credible, chunked IndexedDB.~~
  • [x] ~~Measure first import, weekly rebuild, startup hydration, durable and peak storage, peak and steady RAM, compact lookup, full dossier assembly, historical/multi-USI traversal, search/filter performance, implementation complexity, and current Chrome/Firefox behavior.~~
  • [x] ~~Report benchmark evidence to the operator and confirm the durable FCC representation before implementing the importer.~~
  • [x] ~~Preserve every FCC archive file, record type, emitted field, relationship, schema revision, counts manifest, and source provenance. Retain original records or a demonstrably lossless representation.~~
  • [x] ~~Implement generation staging, complete validation, atomic activation, failure fallback to the prior valid generation, and safe old-generation pruning.~~
  • [x] ~~Keep normal decoder enrichment in RAM according to the selected Auto/Eager/Indexed policy; persistent storage must not enter the decode hot path.~~

Phase 9C — Station Intelligence

  • [x] ~~Maidenhead locator conversion for FT8 and related modes.~~
  • [x] ~~Persist validated decoded observations and learned station state in IndexedDB, including grid provenance/history, first/last heard, bands, frequencies, SNR, message references, receiver path, and capture time.~~
  • [x] ~~Add provider-neutral prefix/country/DXCC enrichment and leave extension points for future international callsign providers.~~
  • [x] ~~Build compact and forensic dossier loaders using the shared hot RAM tier, regulatory corpus, geographic assertions, and observation store.~~
  • [x] ~~Present inactive FCC records factually and conspicuously without making unsupported claims about legality or authorization.~~

Phase 9D — Investigation Experience

Phase 9D.0 — Shared Interaction and Query Contracts

  • [x] ~~Add one provider-neutral station/regulatory investigation-target and station-selection path shared by the rail, pop-out, dossier, search, and future map.~~
  • [x] ~~Add station-keyed RAM subscriptions, complete worker/IndexedDB heard- station search, stable capture-time history paging, and derived historical geography/distance projections without putting storage on decoder rows.~~
  • [x] ~~Complete the receiver/path location lifecycle with list, normalized Maidenhead or latitude/longitude entry, replace, remove, and explicit unknown state. Keep operator location separate.~~

Phase 9D.1 — Compact Live Enrichment

  • [x] ~~Add concise live FT8/FT4 transmitter enrichment while preserving exact decoded-message text, row density, selection/copy behavior, and RAM-only rendering.~~
  • [x] ~~Add protocol-aware From/To context, capture-time Rx→Tx and Tx↔To distances, and versioned show/hide/order/resize preferences in the pop-out; keep Message mandatory and destination-only enrichment ephemeral.~~
  • [x] ~~Add a bounded waterfall-rail station summary for situational awareness; show an unambiguous FCC licensee locality where useful while keeping deep history, regulatory records, source inspection, and search out of the rail.~~

Phase 9D.2 — FTx Investigation Workspace

  • [x] ~~Add a dedicated pop-out FTx workhorse with the full decoder stream and a resizable station dossier pane that shares lane, decoder, intelligence, and station selection state with the main application.~~
  • [x] ~~Organize overview, bounded capture-time RF history, geographic evidence, complete FCC/USI relationships, and safe raw/source inspection without collapsing observed, geographic, and regulatory identity.~~
  • [x] ~~Expose each retained FCC identity's complete EN-derived mailing address in the regulatory dossier while keeping it explicitly separate from decoded operating geography and preserving historical/multiple-USI associations.~~
  • [x] ~~Surface provider readiness/no-match/active/inactive/ambiguous semantics and retained-history completeness factually.~~

Phase 9D.3 — Forensic Search and Optional Export

  • [x] ~~Add explicit Heard Stations and FCC Corpus search scopes. Heard search must cover complete retained learned state regardless of RAM policy; FCC-only results must not manufacture observed station identities.~~
  • [x] ~~Add bounded scientific export only if it does not delay the core investigation experience; otherwise retain export as a documented follow-up.~~

Phase 9D.4 — Acceptance and Handoff

  • [x] ~~Validate compact density, cross-view selection, dossiers, receiver- specific distance/bearing, international geography continuity, reload, history completeness, safe corpus rendering, and active RF operation in the reference Chrome environment.~~
  • [x] ~~Document the accepted selection, station, geographic, regulatory, query, UI-extension, and performance interfaces as a Phase 9E map-agent handoff.~~

Phase 9E — Interactive Map

  • [x] ~~Add a first-class, protocol-neutral RF intelligence map in a dedicated pop-out workspace. Reuse the shared station-selection, dossier, station-intelligence, receiver-location, and capture-time evidence paths.~~
  • [x] ~~Provide MapLibre-backed 2D Mercator and globe views, locally served light/dark geographic basemaps, state/province and country boundaries, locality labels, persisted camera/settings, and a retained WebGL2 RF overlay outside the React render loop.~~
  • [x] ~~Project learned stations and configured receivers from RAM snapshots and station-keyed deltas. Show categorical geographic precision, independently toggleable Maidenhead cells/grid, recency, distance/bearing, and map-to-dossier or dossier/decode-to-map selection.~~
  • [x] ~~Keep observed RF geography distinct from regulatory/home geography. Implement provenance-bearing Best Estimate behavior that may refine a decoded grid with a regulatory point inside it, retains both sources on disagreement, and exposes coarse-only evidence honestly.~~
  • [x] ~~Add local-first U.S. FCC-address geocoding with Census TIGER/Line, ZCTA, place, and state tiers; browser-worker resolution, persistent IndexedDB result caching, RAM reuse, dataset-version invalidation, and explicit exact/interpolated/postal/locality precision. Never represent a PO box as a residence point.~~
  • [x] ~~Render directional heard Tx→receiver and decoded Tx→addressed relationships as separate event roles without manufacturing destination observations. Keep relationship distances as endpoint great-circle facts, not modeled propagation paths.~~
  • [x] ~~Add reference-time-driven day/night, dense terminator, and greyline layers plus locally cached satellite/space-asset positions, altitude, ground tracks, receiver-relative range/azimuth/elevation, AOS/culmination/ LOS pass prediction, curated RF metadata, Doppler, and corrected expected frequency.~~
  • [x] ~~Bind station visibility, geography, relationships, receiver effective intervals, solar layers, orbital position, passes, and Doppler to the IQ timeshift cursor so rewinding produces a strict as-of-capture view.~~
  • [x] ~~Keep core geographic, MapLibre, geocoder, and orbital assets local to the appliance. Use low-priority atomic background updaters for Census and CelesTrak data, retain the last valid artifacts on failure, and make photographic satellite imagery an explicit optional Internet-backed enhancement.~~
  • [x] ~~Retain cross-origin isolation with COEP: credentialless, narrowly pin optional map providers in CSP, isolate map faults from the receiver, throttle hidden animation, recover WebGL context, and preserve realtime DSP/audio/waterfall/decoder/timeshift priority.~~
  • [x] ~~Reconcile operator and engineering documentation and validate the accepted map, security headers, local assets, geocoder/orbital updaters, temporal semantics, and existing SDR paths in the reference Chrome environment and full repository gate.~~

Post-9E geographic extensions

  • [ ] APRS station and object positions.
  • [ ] Add the protocol-neutral aircraft and aviation-ground-station adapters defined by Phase 10; do not make ADS-B a one-off map implementation.
  • [ ] AIS vessels.
  • [ ] Radiosondes.
  • [ ] Optional frequency, repeater, station, and service databases.
  • [ ] Reuse the existing local HF propagation cache where useful without adding status-page network requests.
  • [ ] Connect geographic decoder outputs to automatic scan results when deferred Phase 4 scanning resumes.