Standards & Compliance Posture
Read this first. This page describes design posture and alignment, not certified conformance. FlightStudio is built to interoperate with recognized UTM standards, and much of the relevant logic is implemented in code. However, no regulatory certification is claimed, and formal conformance must be validated with the relevant regulator or standards body and proven by conformance testing against a reference system. Where automated tests exist, they are described honestly below — including their current limitations.
Summary
| Standard / framework | Implementation | Verification today | Posture |
|---|---|---|---|
| ASTM F3411 — Remote ID & tracking | [Beta] — Net-RID Service Provider ISA lifecycle, Display Provider display_data, broadcast RID ingestion, RID DSS client (SP registration + DP area discovery) in traffic-ingest |
ISA-store behavioral tests in CI + reference-DSS round-trip verified (InterUSS core-service v0.22.0, 2026-06-10): ISA put/get/area-search/update/delete with version concurrency + stale-version rejection, via scripts/run_dss_conformance.py |
Round-trip conformant vs the reference implementation; external DP peer + uss_qualifier suite still open |
| ASTM F3548 — USS interoperability & strategic coordination | [Beta] — 4D operational-intent model, strategic deconfliction engine, DSS client (registration, peer sync, subscriptions) in flight-planning |
Behavioral deconfliction tests in CI + reference-DSS round-trip verified (InterUSS core-service v0.22.0, 2026-06-10): op-intent create/get/query/update/delete with OVN concurrency + stale-OVN rejection + subscriptions, via scripts/run_dss_conformance.py |
Round-trip conformant vs the reference implementation (self-hosted sandbox); remote-peer / uss_qualifier validation still open |
| EUROCAE ED-269 — UAS geofencing | [Beta] — geofence lifecycle state machine, schedules, activation/deactivation, breach policies, altitude/time validity, authority provenance, schema validation gate on import in geo-airspace |
Lifecycle state machine + schema validator + parser (unit conversion, geometry, restriction mapping) behaviorally tested in CI; imports skip non-conformant zones with precise reasons and require provenance | Schema-conformance enforced at the import boundary; live breach-geometry (PostGIS) covered by the stack harness |
| JARUS SORA 2.5 — risk assessment | [Beta] — GRC/ARC/SAIL calculators, SAIL matrix (Table 4), 24 OSOs, TMPR validator in sora-engine |
A few spot-check assertions via the live harness; matrix not exhaustively validated | Strongest implementation; needs exhaustive matrix tests |
| EASA U-space (EU 2021/664) — common information & USSP coordination | [Beta] — all four mandatory U-space services have a formal surface (see coverage matrix below), CISP/FIMS zone sync, authority workflows, conformance→FIMS broadcast | Traffic-information proximity/shaping + FIMS-broadcast decision behaviorally tested in CI; CISP client never validated against a live CIS | Mandatory-service coverage complete in-platform; certified CIS interop requires regulatory engagement |
| FAA LAANC — controlled-airspace authorization | [Preview] — "LAANC-like" authorization workflow in authorization-broker |
Structural tests | Workflow analog, not an actual FAA LAANC integration |
U-space mandatory services coverage (EU 2021/664)
The four services every U-space airspace must provide, and where FlightStudio implements them:
| Mandatory service | Article | Implementation | Status |
|---|---|---|---|
| Network identification | Art. 8 | traffic-ingest — F3411 Net-RID SP/DP + RID DSS client (reference round-trip verified) |
[Beta] |
| Geo-awareness | Art. 9 | geo-airspace — ED-269 geozones with schema-validated import, TFRs, NOTAMs, vector tiles |
[Beta] |
| UAS flight authorisation | Art. 10 | flight-planning + authorization-broker — submission, approval workbench, conditional approvals, evidence ledger |
[Beta] |
| Traffic information | Art. 11 | traffic-ingest — GET /api/v1/uspace/traffic-information (proximate conspicuous traffic from fused ADS-B + Remote ID, nearest-first, SI units; decision support, not separation) |
[Beta] |
Supporting USSP obligations: conformance monitoring (flights-ops) now
broadcasts in-flight non-conformance to the FIMS gateway as compliance
evidence (fims_broadcast.py, best-effort, never blocks the safety path).
What "implemented" vs "verified" means here
- Implemented means the domain logic exists in code and runs (e.g. the SORA 2.5 SAIL matrix, the 4D deconfliction geometry, the ED-269 lifecycle state machine). The service catalog cites the source.
- Verified distinguishes two test layers, because they give very different
assurance:
- Structural ("contract") tests assert that code contains the expected classes, routes, and fields. They catch accidental deletion/rename but do not prove the algorithm is correct.
- Runtime conformance harness (
tests/compliance/test_astm_compliance.py) exercises live endpoints (RID ISA lifecycle, intent flows, geofence validation). It is real, but it skips when no stack is running and is not yet run in CI — so it currently provides assurance only when executed deliberately against a running stack.
See development/testing.md for the full test strategy and the plan to close these gaps.
Honest gaps to certified conformance
These are the work items between today's alignment and defensible conformance claims. They are tracked in the roadmap:
- Behavioral tests for safety-critical math — exhaustive SORA SAIL matrix, F3548 conflict/buffer geometry, and ED-269 lifecycle/breach transitions.
- Run the conformance harness in CI against a live stack — so F3411/F3548 are actually exercised on every change rather than skipped.
- External interop conformance — ✅ F3548 operational-intent exchange
and ✅ F3411 ISA registration/discovery are validated against the
self-hosted InterUSS reference DSS (
scripts/run_dss_conformance.py, see the validation playbook). Still open: a live external DP/SP peer and the full InterUSSuss_qualifiersuite. - Schema conformance — ✅ ED-269 zone documents are validated against the structural rules at the import boundary (identifier/country/restriction/ geometry/limits/applicability/provenance; non-conformant zones rejected with reasons); RID DSS payloads are validated by the reference implementation's parsing in the round-trip. Remaining: official published JSON-schema files as the validation source of truth.
- Regulatory engagement — any LAANC or EASA U-space CIS claim requires the actual integration and the relevant authority's acceptance.
Claim tables (per-capability, evidence-linked)
The tender-grade detail behind the summary: each row is a specific, checkable claim with its evidence in this repository. Claim levels:
- Verified vs reference — proven against the InterUSS reference
implementation via
scripts/run_dss_conformance.py(dated runs). - Verified in CI — behavioral tests assert the logic on every build.
- Implemented — real code, exercised via the live-stack harness only.
- Open — known gap, tracked on the roadmap.
ASTM F3548-21 — strategic coordination
| Capability | Claim | Evidence |
|---|---|---|
| Operational-intent reference create/get/query/delete (DSS) | Verified vs reference (core-service v0.22.0, 2026-06-10) | tests/conformance/test_f3548_dss_roundtrip.py |
| OVN optimistic concurrency incl. stale-OVN rejection | Verified vs reference | same round-trip |
| Subscription put/get/delete | Verified vs reference | same round-trip |
| OAuth2 client-credentials USS↔DSS auth (RFC 6749 + sandbox dialect) | Verified vs reference | services/flight-planning/app/services/dss_client.py |
| 4D deconfliction screening (temporal → horizontal → vertical, VLOS/BVLOS buffers) | Verified in CI | tests/test_f3548_deconfliction_contracts.py |
| DSS coordination evidence (attempts, digests, correlation IDs) | Verified in CI | tests/test_dss_interoperability_contracts.py |
| Conformance monitoring (corridor/vertical/temporal/lost-link) | Verified in CI (engine) + Implemented (live geometry) | tests/test_telemetry_conformance_engine_contracts.py |
| Multi-USS conflict negotiation with a live peer USS | Open | roadmap (out-of-repo: needs a partner USS) |
ASTM F3411-22a — network Remote ID
| Capability | Claim | Evidence |
|---|---|---|
| ISA registration / update / delete in the DSS (SP role) | Verified vs reference (2026-06-10) | tests/conformance/test_f3411_rid_dss_roundtrip.py |
| ISA discovery by area polygon (DP role) | Verified vs reference | same round-trip |
| ISA version concurrency incl. stale-version rejection | Verified vs reference | same round-trip |
| Local ISA store lifecycle + TTL bounds | Verified in CI | tests/test_f3411_rid_isa_store_contracts.py |
| SP flights / DP display_data endpoints | Implemented | services/traffic-ingest/app/routes/rid_sp.py |
| Broadcast RID ingestion normalization (field aliases, unit conversions, timestamp dialects, dedup) | Verified in CI (2026-06-10) | tests/test_broadcast_rid_ed269_gap_contracts.py |
uss_qualifier DSS-probing suite (official InterUSS harness, F3411 v19+v22a + F3548 DSS requirements) |
Verified 2026-06-10 — PASS, zero failed checks above Low severity; 5 DatastoreAccess scenarios skip by design (need direct CockroachDB access). The timing-sensitive expired-ISA check flaked in one earlier local run (clock granularity) — rerun if seen | make uss-qualifier → ops/conformance/qualifier-reports/ (report.json + sequence + per-participant requirements) |
uss_qualifier SP/DP qualification (netrid suites) |
Open — requires the ASTM RID test injection APIs on traffic-ingest | roadmap Phase 13 remainder |
EUROCAE ED-269 — UAS geographical zones
| Capability | Claim | Evidence |
|---|---|---|
| Schema validation gate on import (identifier/country/restriction/geometry/limits/applicability) | Verified in CI | tests/test_ed269_schema_conformance_contracts.py |
| Official EUROCAE JSON-schema gate (authoritative when a licence holder installs the schema file; ED-269 material is not redistributable) | Verified in CI (hook + ordering; stand-in schema) | tests/test_broadcast_rid_ed269_gap_contracts.py · install: services/geo-airspace/schemas/ed269/README.md |
| Authority provenance required on zone data | Verified in CI | same |
| Lifecycle state machine (draft→…→withdrawn, schedules) | Verified in CI | tests/test_ed269_geofence_lifecycle_contracts.py |
| Unit conversion (FT/FL→m), polygon closure, restriction mapping | Verified in CI | tests/test_ed269_schema_conformance_contracts.py |
Breach detection geometry (PostGIS ST_Contains) |
Implemented (live-stack harness) | services/geo-airspace/app/routes/geofence_engine.py |
| Official published JSON-schema files as validation source | Open | roadmap |
JARUS SORA 2.5 — risk assessment
| Capability | Claim | Evidence |
|---|---|---|
| Full SAIL matrix (Table 4, all GRC×ARC cells) | Verified in CI (exhaustive) | tests/test_sora_sail_matrix_contracts.py |
| GRC / ARC calculators, 24 OSOs, TMPR validation | Implemented | services/sora-engine/app/services/ |
| SORA gate inside preflight go/no-go | Verified in CI (wiring) | services/flights-ops/app/services/preflight_engine.py |
EU 2021/664 — U-space
| Capability | Claim | Evidence |
|---|---|---|
| Four mandatory services (Art. 8–11) have formal surfaces | Verified in CI (traffic-information core) + Implemented | coverage matrix above |
| Conformance → FIMS broadcast (IN_FLIGHT evidence) | Verified in CI (decision/shape) | tests/test_uspace_traffic_information_contracts.py |
| CISP/FIMS zone sync client | Implemented (live CIS validation Open) | services/flight-planning/app/services/cisp_client.py |
| USSP certification | Open (regulatory engagement) | business plan |
Compliance evidence
FlightStudio does produce the evidence that regulated operations require, today:
- Every state-changing action is intended to write audit evidence (actor,
tenant, project, correlation ID, source service) via
audit-log. authorization-brokerexports hash-linked evidence bundles spanning approval requests, authority decisions, telemetry, Remote ID, conformance, operator actions, admin changes, DSS interop, and authorization packages.
This makes operations auditable; it does not by itself constitute certified compliance.