Spoofable tracks shouldn't quietly become ground truth.
ADS-B and AIS can be forged, and a lone track promoted into a decision with no record of why it was trusted contaminates everything downstream. The live-tracking lane makes that trust explicit and machine-readable: it ingests ADS-B-style track state - position, course and speed - as representative/synthetic input, normalises it into the canonical product with a GeoJSON geometry, and auto-sets a spoofable quality flag because these signals are forgeable. That flag directly reduces the corroboration score, so a spoofable source can contextualise but never dominate a candidate - and the reasoning is inspectable. The signed record shares the same tamper-evident, append-only chain of custody and independent public verifier as every other source. There is no live feed connector yet, and KML/CCSDS/SensorML interchange is roadmap.
CCSDS interchange
Roadmap. CCSDS navigation-message interchange (OEM/OMM/AEM/TDM) is a planned extension. The current demonstrator normalises track state into the canonical JSON product and does not yet read or write CCSDS messages.
| Message | Purpose |
|---|---|
| OEM · Orbit Ephemeris | Time-tagged state vectors for trajectories. |
| OMM · Orbit Mean-Element | Mean orbital elements at an epoch. |
| AEM · Attitude Ephemeris | Time-tagged attitude representations (quaternion, Euler, DCM). |
| TDM · Tracking Data | Range, Doppler, angles and other tracking observables. |
Ships & drones
Live-tracking inputs are normalised to the canonical product and flagged spoofable:
- ADS-B / AIS-style track state - position, course and speed normalised into the canonical product, with a spoofable quality flag because these signals are forgeable.
- NMEA 0183, MAVLink - parsing of marine and drone telemetry formats is roadmap, not built in this demonstrator.
Each live-tracking input collapses to one canonical JSON product, so downstream consumers and the public verifier treat every record identically, whatever its source.
Track building
Each track-state record becomes a canonical product with a GeoJSON Point geometry and properties (a UTC timestamp, source, quality flags, confidence). Spatial queries run in a geospatial database - the same 75 km / 30 min spatial gate that powers corroboration candidates. KML export and orbit propagation are roadmap.
Delivery
Canonical products and corroboration candidates are retrievable over the documented REST API - product and feed endpoints, corroboration events, a GeoJSON corroboration feed, a public verifier and its published trust anchor. There is no published SDK yet, and the generic signed outbound-webhooks module is not wired to Level Zero. See REST API.