Atomx Component Map

Andi Lamprecht ·2026-05-11· 2 min read· Draft

Title

Context

Describe a high-level overview of ATOMx with examples.

Decision

Main ATOMx Components

Flight Authorization

This component handles the interaction between authorities and pilots via entities such as Airspaces, Flights Intents, and Flights.

ADR for Rules and Flight Authorization: <../adr-0130-atomx-approvals-4885839987/index.md>

Traffic Service

This component handles flight telemetry

ADR for Traffic Service: <../adr-0133-flight-traffic-exchange-architecture-proposal-and-design-details-4890722318/index.md>

Use Case Examples

Flight Authorization Use Cases

An Authority Creates An Airspace

Authorities create Airspaces by defining volumes of space and assigning rules to those volumes. Airspaces are later used for flight planning.

A Pilot Submits a Flight Intent

A flight intent is a proposed flight plan. The system finds all of the Airspaces that the flight path in the intent passes through and confirms that the flight conforms to all rules in all of the Airspaces intersected.

A Pilot Submits a Request for a Waiver

This section is speculative. A waiver request is processed by the Authority outside of ATOMx. Once the waiver is approved, the Authority can add it to our database so that we can verify that a pilot has permission to fly in areas covered by the waiver.

A Pilot Starts a Flight

A flight intent can be submitted in advance of the actual flight. In order to activate a flight, it needs to be checked against all of the airspaces it traverses in case there have been any changes.

Traffic Service Use Cases

The Traffic Service is about fusing various observations and distributing the fused data to various clients.

Observations Flow Through the System

Observations from various data sources flow into the Traffic System. The individual observations are combined by a fusion algorithm and written to a write-ahead-log. Various distribution clients subscribe to the log to receive the fused observations. These clients further distribute the data to various end client.

Consequences

What becomes easier or more difficult to do because of this change?

Alternatives Considered

List all alternatives you’ve considered and explain briefly why did you reject it.

Formal Impact

List any systems or services that are impacted by this architectural decision.