Platform / Radio & telemetry

Downlink frames, captured & signed.

SatNOGS-style telemetry downlink frames ingested as representative/synthetic inputs - the raw hex frame is stored verbatim and frame-byte counted (not demodulated or FEC-decoded), then normalised into one canonical JSON product, cryptographically signed and hash-chained. GNSS deframing, FEC and RINEX output are roadmap, not built.

InputsSatNOGS-style telemetry frame (hex); sourced synthetic, replayed or live OutputsCanonical JSON product, GeoJSON, JSON Schema StackStandard open-source, geospatial database (in-request normalisation, no queue)

One contract for downlink frames, not glue code per station.

A ground-station network aggregating downlink from many radios and stations gets a different native frame shape from each - so integration cost scales with sources and every new feed is bespoke parser glue. The radio lane collapses that: it ingests SatNOGS-style telemetry downlink frames as representative/synthetic inputs - the raw hex frame is stored verbatim and frame-byte counted (not demodulated, deframed or FEC-decoded) - then normalises each one into the same canonical JSON product and signs it into the same tamper-evident, append-only chain of custody as every other source, so downstream tooling and the public verifier read one shape. GNSS observation handling is roadmap. There is no live feed connector yet - inputs are tagged by how each was sourced: synthetic, replayed or live.

[ Where we start ]

Level Zero starts at the frame: an SDR or modem produces a downlink frame; Level Zero stores that hex frame verbatim, counts its bytes, records source and quality metadata, and normalises it into the canonical product - all on plain Node, with no heavyweight DSP tooling to operate. Demodulation, deframing and FEC decoding are not performed; they sit upstream or on the roadmap.

Frame capture

A downlink frame is ingested as representative/synthetic input. Level Zero stores the raw hex frame verbatim, computes a frame-byte count, and records its source metadata. AX.25/CCSDS deframing, FCS/CRC verification and Reed-Solomon FEC are not performed in this demonstrator - they are upstream or roadmap.

  • Frame: SatNOGS-style telemetry frame stored as raw hex, frame-byte counted.
  • Provenance: Ed25519 signature and hash-chained, append-only chain of custody.
  • Sourcing: synthetic, replayed or live (no live connector yet).

Canonical normalisation

The frame is normalised into one canonical JSON product with a UTC timestamp, source block, GeoJSON geometry, machine-readable quality flags and a 0.0-1.0 confidence, validated against a published JSON Schema. Bit-level telemetry field decoding via descriptors is roadmap; the demonstrator does not parse frame payloads into typed fields.

GNSS normalisation (roadmap)

Roadmap. GNSS observation handling - converting receiver logs into a RINEX-style normalised store with IGS-style QC - is a planned extension of the canonical-product pipeline. It is not built in the current TRL-4 demonstrator, which emits canonical JSON + GeoJSON only.

Delivery

Canonical products are reachable over the documented REST API - product and feed endpoints, the schema, a public verifier and its published trust anchor. There is no published SDK yet; a generic signed outbound-webhooks module exists at the platform level but is not wired to Level Zero, and a streaming (WebSocket) surface is roadmap. See REST API.

[ Ready to integrate ]