Airline cross-Integrated Operations Management · v1.0 · 2026-05-07

The airline operating system, designed for any operator,
any jurisdiction.

One canonical record per real-world entity. Compartmentalised access at the data layer. Regulation, CBAs and FRMS encoded as data, not code. CRM, TEM and Human Factors as first-class design constraints — baked into the kernel, not bolted on.

34modules
P01–P10 spine · M01–M24 ops · M73–M84 ATC · P19–P20 IQ

6build phases
0 Foundation → 5 Productise · 36 mo to v1.0

€16–19Mgross to v1.0
~€10–13M net of SIFIDE II credit

€8–25Mnon-dilutive
Horizon · SESAR · EIC · PT2030 · SIFIDE

26source artefacts
doctrine · architecture · ATC · crew · funding

Architecture Read the doctrine

FIXM 4.3 AIXM 5.1.1/5.2 IWXXM v3+ ASTERIX cat-021/048/062/065 SWIM Yellow/Blue/Purple ARINC 858 ICAO Annex 19 EASA Reg 965/2012 14 CFR 117/121 WCAG 2.2 AA / AAA RFC 3161

What AXIOM is

An integrated operations spine for any airline, anywhere.

Today's airline runs ten or twelve systems that don't agree on anything: dispatch, crew, maintenance, safety, finance, comms, slots, traffic rights. Each carries its own copy of the truth. Each disagrees in subtle, billable ways. AXIOM replaces the patchwork with one canonical record per real-world entity, accessed only through compartmentalised, audited interfaces — and a regulatory engine in which every CBA, FTL rule and FRMS deviation is data, not code.

Single source of truth

One canonical record per aircraft tail, person, flight, route, ticket, MEL item, defect, duty, slot, ASA. References everywhere else. Direct DB access fails the build.

Compartmentalisation, not silos

Row- and column-level security at the data layer. Cross-department reads through published interfaces. Every cross-compartment query logged immutably.

Rules as data

EASA, FAA, TCCA, CASA, CAAS, ANAC, GACA, GCAA — plus every CBA, every FRMS deviation — encoded as time-bounded rule rows with provenance, not embedded in code.

Event-sourced audit

Append-only, hash-chained, externally anchored to RFC 3161. Any past flight cycle reproducible end-to-end in under ten minutes by a junior auditor.

Airline-agnostic by design

if operator == "MERIDIAN" in production code is a defect. Same binary deploys at any airline; configuration determines behaviour.

Buildable, sellable, defensible

€16–19M gross to v1.0 (~€10–13M net of SIFIDE II), 36 months, phased deployable increments every 6 months. Funded €8–25M non-dilutive.

The doctrine · AXM-ARCH-0001

Six binding principles. None of them are negotiable.

Every subsystem spec, every schema, every UI rule, every procurement decision must trace back to one of these. The Design Doctrine is the constitution of AXIOM.

01
CRM by design

Every operationally significant data point has ≥2 independent sources plus an arbitration mechanism. Disagreement is surfaced, never silently resolved. Single-source operation runs only as a degraded mode, with a persistent banner.
02
TEM by design

Before any code, three artefacts are required for every workflow: threat catalogue → trap/detection → recovery procedure. No feature ships without all three. The catalogue is versioned alongside the code.
03
Human factors by design

Build for the operator at the bottom of the performance curve, not the top. High-consequence actions never single-tap. Critical information persistent and pre-attentive. Multi-modal state — colour and icon and text. Bilingual UI (EN/PT min); ICAO phraseology canonical and un-translated.
04
No problem without a software solution

Every operational, regulatory, financial, HR or training problem lives in the issue ledger. Spreadsheet, email, paper workarounds carry mandatory closure dates. Workarounds without closure dates are uncommitted technical debt and are rejected.
05
Integration with compartmentalisation

Single source of truth + schema-on-write + role and attribute access. Each department owns, generates and consumes inside its compartment. Cross-department reads through published interfaces only. Row- and column-level security at the data layer, not the UI.
06
Airline-agnostic by design

No hardcoded reference to any operator, fleet, base, jurisdiction, language, currency or CBA. Operator behaviour is data-driven via configuration entities and the regulatory rule engine. The same binary, every airline.

Tie-breaker order

Safety · ethics · law Accuracy Privacy Completeness Brevity

Architecture · v1.0 canonical

34 modules. One spine. One canonical record per entity.

A platform spine of 10 services (P01–P10), 24 operational and governance modules (M01–M24), an ATC/ANSP integration family (M73–M84) and two AXIOM-IQ analytics extensions (P19, P20). All on the same event-sourced canonical store; all reachable only through audited interfaces.

PresentationWeb (React) · Mobile (iOS/Android/Flutter) · EFB (iPad-class) · Voice/CPDLC · BI dashboards

Experience servicesTask orchestration · Notifications · Search · Decision-support overlays · Workflow / BPMN engine

Domain subsystems · M01–M24, M73–M84DISPATCH · OPS · CREW · TECH · CABIN · COMM · SMS · FIN · M73–M84 ATC integration

Cross-cutting enginesRegulatory rules · CBA engine · HF model · TEM library · CRM framework · Fatigue model (FRMS) · Workflow

Platform core · P01–P10Identity · Time · Data · Bus · Audit · Rules · Doc · UI · Observability · Analytics · Units · KMS

Data fabricEvent store · Operational stores · Analytics lake · Document store · KV · Search index

InfrastructureKubernetes · Multi-region · Multi-cloud-capable · Air-gapped option for security-sensitive operators

Platform spine · P01–P10

P01

IDENTITY

OIDC + SAML SSO · SCIM · FIDO2/WebAuthn · ABAC · MFA · break-glass · dual-auth.

P02

TIME

Canonical UTC · multi-source arbitration · σ tracking · leap-second smear · UTC↔local projections.

P03

DATA

Canonical entity store · schema-on-write · versioned schemas · projections · MDM.

P04

BUS

Kafka or NATS JetStream · CDC · idempotent writes · exactly-once semantics.

P05

AUDIT

Append-only · hash-chained · RFC 3161 anchored · query log · compliance exports.

P06

RULES

Versioned regulatory + contractual rule library · evaluation engine · effective-date tracking.

P07

DOC

Document control · IDs · revisions · supersession · e-signatures · ARINC 858.

P08

UI

Design Spec v2.1 · component library · WCAG 2.2 AA (AAA on safety-critical) · fatigue-aware densities.

P09

OBSERVE

Distributed tracing · structured logs · metrics per SLO · OCC/MCC/NCC/SOC dashboards · RUM.

P10

ANALYTICS

Read-only projection of P03 · data warehouse · BI · ML/forecast services.

Operational & governance · M01–M24

M01

Network & schedule

Long-range planning, slots strategy, network shape.

M02

Revenue mgmt & pricing

Yield, fare construction, RBD, group pricing.

M03

Sales & distribution

NDC + GDS + direct, agency, interline.

M04

Loyalty

Programme tiers, accrual, redemption, partner equivalencies.

M05

Customer service

Care, EU 261, irrops accommodation, voucher engine.

M06

Ancillary

Bags, seats, lounges, upgrades, ground product.

M07

Crew resources

Rostering, FTL, currency, training, FRMS.

M08

Aircraft resources

Tail planning, lease/own, configuration, lifing.

M09

Engineering & CAMO

AD/SB compliance, MEL, work packs, defect history.

M10

Maintenance ops

Hangar floor, line maintenance, parts, ATA Spec 2000.

M11

Flight production

OFP, fuel, alternates, ETOPS/EDTO, briefings.

M12

Network ops control

NOCC: irrops, recovery, watch-keeping.

M13

Ground production

Stand, GSE, fueler, de-ice, turnaround.

M14

Cargo

AWB, ULD, dangerous goods, ONE Record.

M15

Cabin operations

Service standards, cabin defects, retail, special handling.

M16

Operational comms

ATC, datalink, ACARS, ops messaging.

M17

Safety mgmt (SMS)

Hazard, risk, FDM, voluntary reports — just-culture by architecture.

M18

Security (AVSEC)

NCASP, vetting, threat intel, PII firewall.

M19

Quality & compliance

IOSA, ISAGO, IS-BAO; closed-loop training intelligence.

M20

Training & standards

Competencies, recurrent, examiner calibration.

M21

HR & people

Code of Employment, payroll integration, mental-health firewall.

M22

Finance & accounting

Books, IFRS 16 lease, tax, BSP/CASS, IATA SIS.

M23

Procurement & contracts

Vendor lifecycle, hotel/handling/fuel/catering contracts.

M24

IT & infrastructure

Connectivity, devices, EFB fleet, sovereign-cloud topology.

ATC / ANSP integration · M73–M84 FF-ICE/R1 mandatory in EU 1 Jan 2026 · CP1 AF6 31 Dec 2027

M73

Strategic TBO Negotiator

GUFI assignment, eFPL, PFP submission, trial loops, planning-status feedback.

M74

Tactical NM/CFMU Connector

NM B2B P/S · CTOT (-5/+10) · DPI/FUM A-CDM · slot improvement feedback.

M75

Trajectory Cost Optimiser

Multi-objective: fuel + time + contrail + noise + EU261 + crew + FDM + hedge. Pareto front.

M76

Remote Tower Consumer

RTC service registry per EUROCAE ED-240B, multi-aerodrome.

M77

Mission Trajectory

State, military, HEMS, eVTOL · iOAT FPL · VPA/DMA · EUROAT.

M78

iCWP Controller WP

STCA · MSAW · DAIW · MTCD · MONA · SWIM-native.

M79

AMAN/DMAN/SMAN

E-AMAN/XMAN to 350 NM · TSAT/TTOT A-CDM · ADS-C/EPP downlink.

M80

AIM/SWIM Service Bus

AIXM 5.1.1/5.2 · FIXM 4.3 · IWXXM v3+ · ASTERIX cat-021/048/062/065.

M81

Surveillance Fusion

PSR + SSR Mode S + ADS-B v2 + MLAT/WAM + ADS-C + GNSS interference detection.

M82

Remote/Digital Tower

EUROCAE ED-240B · multi-aerodrome per EASA Issue 3 · contingency model.

M83

Flight Object Manager

SESAR FOI · GUFI lifecycle · role-scoped views · FF-ICE diff/version. Sits on P04.

M84

CPDLC/ADS-C Gateway

ATN-B1/B2 · FANS-1/A · VDL Mode 2 · AeroMACS · SATCOM Iris · PBCS · ED-137 voice.

AXIOM-IQ analytics · P19–P20

P19

Trajectory Causal Engine

Counterfactuals over accept/reject decisions and downstream outcomes. Feeds M75 weights and M73 strategy.

P20

Federated Privacy-Preserving Insights

Differential-privacy aggregations · MPC for cross-tenant benchmarks · no leakage of competitor intent.

Ten cardinal rules of the build

One canonical record per real-world entity.
Events, not polling.
Idempotent writes.
Graceful degradation with explicit staleness.
Read-through, write-through.
Offline-capable for safety-critical roles.
Audit by default.
Time is UTC operationally.
Units explicit. No bare numbers in safety-critical fields.
Air-gapped where required, without forking.

CI-enforced architectural invariants

Subsystems write through AXIOM-CORE APIs only. Direct DB access fails the build.
Every API call carries actor, purpose, authorisation context, jurisdiction context.
Every write produces an event before any projection update.
Reads are projection-based and ABAC-filtered at the projection boundary, not the UI.
Reference data is versioned and time-aware. Past flights audited under rules in force at the time.

POST /axiom/v1/flights/{flightId}/loadsheet/final M13 · dual-auth

X-AXIOM-Actor:          user:op_lc_lis_421
X-AXIOM-Auth-Context:   role=load_controller; station=LPPT; jurisdiction=PT
X-AXIOM-Purpose:        dispatch_release_loadsheet_final
X-AXIOM-Trace-Id:       01HX...
Idempotency-Key:        lpa-lhr-2026-05-04-tp342-final-1

{
  "zfw_kg":               138420,
  "tow_kg":               174900,
  "ldw_kg":               142200,
  "cg_pct_mac_zfw":       24.7,
  "cg_pct_mac_to":        25.3,
  "fuel_block_kg":        36480,
  "fuel_taxi_kg":         180,
  "fuel_density_kg_per_l": 0.795,
  "doc_id":               "MG-OPS-LS-0001-v3.4",
  "computed_against_afm_rev": "A20N-AFM-2025-09",
  "dual_auth_pending":    true
}

ABAC check → AXIOM-RULE check (PT regulatory parameters in force) → emits OPS.LoadSheet.Final.Submitted → notifies dispatcher and PIC for dual-auth → on second auth, emits OPS.LoadSheet.Final.Released. Both events are AXIOM-LOG-anchored.

Foundational data services

The substrate: time, units, airports, fleet, trajectory, slots.

Every operational module sits on six foundational data services. Each is small, opinionated and uncompromising. The rest of AXIOM inherits their guarantees.

AXIOM-CORE/TIME

AXM-ARCH-0002 · v0.3

Canonical UTC, ISO 8601 with explicit Z, nanosecond hardware precision (microsecond minimum acceptable). A four-tier source hierarchy with σ uncertainty tracked on every record. Leap-second policy: 24-hour symmetric smear, never a step. Records are immutable; corrections are new records linked to the original.

Tier 1 GNSS multi-constellation with spoof-detection · Tier 2 NTS quorum (≥6 sources) · Tier 3 PTP local · Tier 4 offline TCXO/OCXO with reported drift
σ thresholds: ≤100 ms normal · 100 ms–1 s caution · 1 s–10 s alert · >10 s operational mode refused
Coverage explicit: Sub-Saharan Africa + MENA degraded · polar relaxed quorum · cloud cross-validated
>50 ms divergence between Tier 1 and Tier 2 quarantines Tier 1

Operation class	Tolerance
Flight recorder ingest	1 ms
ATC clearance	100 ms
Slot management · OFP filing · FTL boundary · dispatch release	1 s
General state change	10 s
Personal scheduling	60 s
Historical reporting	5 min

AXIOM-CORE/UNITS

Quantities, never bare numbers.

SI canonical with ICAO Annex 5 exceptions (ft, kt, NM, °C). Fuel mass canonical post-uplift; volume only at uplift, with both density and temperature recorded. Role-scoped display: active value bold + adjacent conversion in regular weight, identical font size. Colour-blind safety encoded by weight, not hue.

Quantity bus envelope · axiom.core.units.*

{
  "magnitude_SI": 0.795,
  "unit_id":      "kg/L",
  "canonical":    "density_kg_per_litre",
  "module":       "M13",
  "source":       "FUELER:UPLIFT-7724",
  "captured_at":  "2026-05-04T05:32:11.082Z",
  "provenance":   "sample, certified, op_fuel_lis_19"
}

Crew & HR substrate

Three layers, one rule engine, regulator-grade audit.

Every roster, every pay statement, every currency check passes through the same evaluator. The binding rule cites itself on the line.

Layer 1

Regulator prescriptive baseline

Hard ceilings from CAAs. Cannot exceed except via Layer 3.

EASA Reg 965/2012 Annex III Subpart FTL
UK CAA · 14 CFR Part 117/121 · Transport Canada CARs Subpart 700
CASA · ANAC-BR · ANAC-PT · JCAB · CAAC · CAA Israel · GACA · GCAA · CAAS

Layer 2

CBA & enterprise overlay

Per-AOC, per-crew-group. Stored as structured data, not PDFs. May only be more restrictive than Layer 1.

Examples: AE PGA/SPAC (BTE 33/2009) · AE PGA-SIPLA (BTE 47/2018) · UPA23
Snap-up clauses ingested via SEC filings, union bulletins, bilateral treaties
Two-person rule (CFO + Chief Pilot) gates propagation

Layer 3

FRMS deviations

Operator-approved Fatigue Risk Management System with safety case. Bounded deviations from Layer 1 limits, only with regulator approval, only for specific operations.

Rule evaluation result AUTHORISED

L1 floor14 CFR §117.21 · max 10h FDP, 2 pilots, 0500 acclimOK

L2 CBACBA-UPA23-DUTYRIG-DAY · min 10h actual rest before reduced restOK

L3 FRMSnot invoked—

Currencyline check 2026-04-12 · valid through 2026-10-12OK

MedicalClass 1 valid through 2026-12-03 · >30 days marginOK

Binding: most restrictive of Layer 1 ∩ Layer 2. Decision logged with rule citations. Pay statement cites rule_id on every line.

What this stack does that no incumbent does

Closed loop with all operational sources. FDM, voluntary reports, line check, manual changes, fleet reliability, network data, customer feedback all feed training.
Adaptive recurrent within the regulatory floor. Each pilot's annual programme individualised inside FAR/EASA minima.
Examiner calibration as a managed function. Inter-rater reliability, bias and drift continuously monitored.
Just culture by data architecture. Identity projections, access gates, audit logging — not a memo that gets ignored.
Cross-jurisdictional currency engine. Same calculator handles EASA + FAA + national rules per strictest applicable.
CBA as executable data. New CBA versions ingested in days, not months. Snap-up auto-triggered on counterparty events.
Mental health as a flight-safety control. Confidentiality firewall decouples help-seeking from Loss-of-Licence. Six paid mental-health days/yr.

Regulatory engagement

Influence by reference implementation, not by lobbying.

Don't dilute existing safety SARPs. Don't push AXIOM-specific formats over recognised standards. Don't pick public fights with chart vendors before the renderer is at parity. Don't claim regulator-grade data until externally audited. Influence accrues from running the fleet, publishing structured data, and proving outcomes.

Engine 1

Structured operational data out

Every AXIOM tenant exports FIXM, AIXM 5.1, IWXXM, SWIM-compliant flight plans, dispatch releases, OFPs, fuel performance, FOQA summaries, de-identified SMS reports, turnaround events, slot utilisation and environmental telemetry.

Regulators have never had clean, comparable, structured data across operators at operations speed. AXIOM tenants supplying it become the dataset of record.

Cost · Low
Risk · Standards drift

Engine 2

Reference implementation for emerging markets

AXIOM-LITE configuration packs for sub-50-aircraft carriers in capacity-constrained CAA jurisdictions. SMS, FDM, dispatch, AIM ingest, CORSIA reporting.

Small operators run spreadsheets, paper or expensive legacy. Their CAAs lack oversight tools. AXIOM becomes operator backbone and CAA visibility tool — natural channel via ICAO No Country Left Behind.

Cost · Low marginal
Risk · Pricing must not exclude

Engine 3 · recommended

Performance-Based Equivalence Engine

AXIOM continuously computes operator performance against safety, fuel and environmental targets. Where evidence materially exceeds the prescriptive standard, AXIOM produces a regulator-grade equivalence dossier for filing under EASA SPA, FAA OpSpec or national equivalent.

This is how PBR finally happens at scale. Regulators wanted operator equivalence cases for 20 years. The bottleneck was data quality and presentation. AXIOM closes it.

Cost · Higher
Risk · Acceptance jurisdiction-by-jurisdiction

Recommended path: Engines 1 + 3 combined; subsidise Engine 2. Engine 1 yields the data feedstock that makes Engine 3 credible. Engine 2 delivers political cover and seeds revenue.

Funding · MG-FIN-001

€8–25M, non-dilutive, in 24 months.

Map subsystem development into the priorities of EU, national and international research and innovation programs. Layer with tax credits and customer prepayments. Take grant tranches, never the equity tranches.

Programme	Band	Posture	Notes
Horizon Europe / SESAR3 JU	€1–6M / project	Non-dilutive	FF-ICE, CP1 AF6 momentum is a tailwind
Clean Aviation JU	€1–4M	Non-dilutive	Sustainability and emissions tooling
EIC Accelerator (grant tranche only)	up to €2.5M	Non-dilutive	Submit only after MVP + ≥3 paying customers · once-only · first viable cut-off 2 Sep 2026
EU Innovation Fund	mid-7 to 8-fig	Non-dilutive	Decarbonisation case
PT2030 (PRR-successor)	€2–8M	Non-dilutive	Requires PT consortium anchor (OGMA, TAP M&E, NAV PT, ANA)
SIFIDE II R&D tax credit	~30% of qual. R&D	Non-dilutive	Largest single shelter; bank line possible against receivable
Belgian R&D wage exemption	up to ~80% of wage tax	Non-dilutive	Triggered if ≥3 BE engineers expected
Irish R&D refundable credit	25% refundable	Non-dilutive	Pre-profit-friendly
Israeli IIA	up to 50%	Royalty-bearing, not equity	Activated if any IL technical capability accessible
EDF (defence module carve-out)	7–8-fig	Optional · FDI-screened	Segregate from civil if used
Customer prepayments	low-7-fig	Non-dilutive (commercial)	Attached to Phase-1 design partners
SIFIDE-receivable bank line	€0.5–2M bridge	Debt	Cash-flow gap protection

Build plan · 36 months to v1.0

Six phases. Each ends with a deployable, audited increment.

Total planning cost (±35%): USD 20–36M / €16–19M gross over 4 years, fully loaded. SIFIDE II nets €10–13M.

0months 0–6$2.5–4M

Foundation

AXIOM-CORE, IDENTITY, LOG, RULES, UI, DOC, OBSERVE, LINK framework, KMS. Reference data.

Nothing else builds honestly.

1months 6–18$6–10M

Operate

DISPATCH, CREW, TECH, SMS. Connectors: weather, NOTAM, ATC slots, ACARS/datalink, FDM.

AOC-critical.

2months 12–24$4–7M

Sell & serve

COMM, CUST, OPS, CABIN. NDC/GDS, DCS, BSP/CASS, baggage, IATA SIS settlement.

Revenue + customer experience.

3months 18–30$3–5M

Run business

FIN, HR, PROC, LEGAL, QA. Tax engine, IFRS 16 lease accounting, payroll connectors.

Internal back office.

4months 24–42$3–6M

Harden & extend

SEC (AVSEC), CYBER, ENV, TRAIN, ERP. SOC 2 Type II, NIS2, Annex 17/19 evidence.

Hardening + regulatory.

5months 36–48$2–4M

Productise

Multi-tenant configuration tooling. Partner programme. Onboarding playbook.

Sellable asset · ≥1 third-party AOC by close.

Kill criteria

Phase 0 cannot demonstrate reproducibility → stop, rebuild.
Target jurisdiction cannot be configured without core engineering → redesign.
Integration costs exceed 35% over two phases → boundary wrong; redesign.
Phase-1 dispatch latency or availability misses >2× for 60 days → re-architect before Phase 2.
Externally-anchored audit gap in production → halt releases until root cause closed.

Measurable success

Any past flight cycle reproducible <10 min by a junior auditor.
Every recurrent regulator pack generated by AXIOM with zero manual data entry.
Zero side-spreadsheets in active ops across in-scope subsystems.
New jurisdiction onboarded <4 weeks once connector library covers.
Any subsystem redeployable without taking another down (proven by chaos tests).
≥1 third-party AOC running AXIOM by Phase 5 close, onboarding spend within ±20% of plan.

Adversarial CI tests · must fail = pass

Try to write AXIOM-LOG outside the API.
Try to read another tenant's data with valid creds in wrong context.
Try to forge an event with a valid signature.
Try to bypass dual-auth via API while it is enforced in UI.
Try to roll back time on a regulator submission.
Try to delete a safety report.
Try to access a privileged-class record via an indirect projection.

Source artefacts

26 documents converged into one masterplan.

Doctrine, architecture (v0.1, v0.2, v1.0), six substrates, ATC/ANSP integration, slots and traffic rights, training, the CBA encoder, the Meridian Code of Employment, regulatory engagement, non-dilutive funding, hub-site network analysis, and competitive position.

01AXIOM Non-Dilutive Funding Plan: €8–25M Strategy GuideMG-FIN-001
02M19 Training & Standards Module: Airline Competency FrameworkMG-MOD-M19 v0.1
03AXIOM System Design Charter v0.2 — Architecture SpecAXM-ARCH-0001 v0.2
04Units of Measurement Subsystem SpecificationAXIOM-CORE/UNITS
05AXIOM Master Architecture Specification v0.2MG-SYS-0001 v0.2
06AXIOM ATC/ANSP Integration Architecture 2025–2026 StrategyMG-AXIOM-ATC-001
07AXIOM Architecture Overview & DesignAXM-ARCH-0000 v0.1
08AXIOM-CORE/TIME: Airline Time & Date Service v0.3AXM-ARCH-0002 v0.3
09Aviation Regulatory Gap Analysis: Reference ImplementationMG-AXIOM-REG-001 v0.1
10Airline Fleet Data Report: 527 Aircraft / 37 Operators— substrate
11OpenSky Fleet Loader (code)— substrate
12Aviation Regulator Modernization: Bridging Dated StandardsMG-AXIOM-007 v0.1
13Airport Master Data SpecificationMG-AXIOM-AIRPORT-001
14Airport Data Ingest Pipeline (Python ETL)— substrate
15Hub Site Alternatives: European Airport Comparative Analysis— network
16Slot Coordination & Traffic Rights: Operational Reference— substrate
17AXIOM Master Architectural Specification v1.0MG-AXIOM-ARCH-0001 v1.0
18Aviation Regulatory Modernization: Standards Reform StrategyMG-AXIOM-REG-001 v1.0
19AXIOM Complete System Design Spec— architecture
20AXIOM Design Doctrine v0.1MG-AXIOM-ARCH-0001 v0.1
21AXIOM Architecture v0.1— architecture
22CBA Encoding Specification for Crew ManagementMG-AXIOM-CBA-001 v0.1
23AXIOM Master Architectural Specification v0.1— architecture
24Meridian Code of Employment v2.0 — HR CBA Template— template
25AXIOM Training Framework: Competency ModelMG-AXIOM-TRN-0001 v0.1
26AXIOM Architecture, Cost & Competitive AnalysisMG-AXIOM-001

The unifying loop Funding → development → operating scale → structured operational data + compliance evidence → regulatory credibility → working-group seats and PBR equivalence → standards evolution → policy tailwinds → higher funding success → faster maturation → more customer adoption → more regulatory influence.

The airline operating system, designed for any operator,any jurisdiction.

An integrated operations spine for any airline, anywhere.

Single source of truth

Compartmentalisation, not silos

Rules as data

Event-sourced audit

Airline-agnostic by design

Buildable, sellable, defensible

Six binding principles. None of them are negotiable.

CRM by design

TEM by design

Human factors by design

No problem without a software solution

Integration with compartmentalisation

Airline-agnostic by design

34 modules. One spine. One canonical record per entity.

Platform spine · P01–P10

IDENTITY

TIME

DATA

BUS

AUDIT

RULES

DOC

UI

OBSERVE

ANALYTICS

Operational & governance · M01–M24

Network & schedule

Revenue mgmt & pricing

Sales & distribution

Loyalty

Customer service

Ancillary

Crew resources

Aircraft resources

Engineering & CAMO

Maintenance ops

Flight production

Network ops control

Ground production

Cargo

Cabin operations

Operational comms

Safety mgmt (SMS)

Security (AVSEC)

Quality & compliance

Training & standards

HR & people

Finance & accounting

Procurement & contracts

IT & infrastructure

ATC / ANSP integration · M73–M84 FF-ICE/R1 mandatory in EU 1 Jan 2026 · CP1 AF6 31 Dec 2027

Strategic TBO Negotiator

Tactical NM/CFMU Connector

Trajectory Cost Optimiser

Remote Tower Consumer

Mission Trajectory

iCWP Controller WP

AMAN/DMAN/SMAN

AIM/SWIM Service Bus

Surveillance Fusion

Remote/Digital Tower

Flight Object Manager

CPDLC/ADS-C Gateway

AXIOM-IQ analytics · P19–P20

Trajectory Causal Engine

Federated Privacy-Preserving Insights

Ten cardinal rules of the build

CI-enforced architectural invariants

The substrate: time, units, airports, fleet, trajectory, slots.

AXIOM-CORE/TIME

AXIOM-CORE/UNITS

Airport master data

Aircraft fleet master data

ATC / ANSP integration · the trajectory spine

Slots & traffic rights · the two-gate check

Slot

Traffic rights

Three layers, one rule engine, regulator-grade audit.

The airline operating system, designed for any operator,
any jurisdiction.