:3004 · in development

MRO / Aviation

Work orders, fleet registry, component lifecycle, life-limited parts tracking, EASA Form 1 / FAA 8130-3 certificate generation. Coming Q3 2026.

Open admin →API referenceArchitecture

Autonomous capabilities

01
Fleet registry + component genealogy
02
Work order state machine
03
Life-limited parts tracking
04
Certificate of Release generation (EASA Form 1, FAA 8130-3)
05
AD/SB compliance tracking
06
Tool calibration registry

Live event stream

Real-time tail of the kernel event bus for this vertical. Hash-chained, immutable, public via Evidence API.

events.live · mrotail -f
$ subscribing…

Agent handoff

Stateless edge functions. Coordination via the database event bus, not RPC.

01work-order-agent
02parts-agent
03compliance-agent
04release-cert-agent
Use cases

Where this lands

Life-limited parts tracking

Per-serial cycle/hour tracking. Alerts at 30%, 15%, 5% remaining. Stops AOG before it happens.

0 LLP overrun
AD/SB compliance

Airworthiness Directives + Service Bulletins ingested from EASA/FAA feeds. Compliance status per tail and component.

100% AD coverage
EASA Form 1 / FAA 8130-3

Certificate of Release autogenerated when work order completes evidence requirements. Signed and hash-chained.

< 60s issuance
Tool calibration registry

Every torque wrench, every gauge, every test rig. Calibration lapses gate the work order, not vice versa.

0 expired-tool releases
Under the hood

How it maps to the kernel

Same Postgres-source-of-truth, same hash-chained audit, same agent runtime — sliced by aggregate. Each vertical is a config of tables + agents + /v1/* endpoints, not a fork of the kernel.

Database tables
  • ontology_object_types (item_master, supplier_certification)
  • audit_events
  • outbox
Agents wired
  • orchestrator
  • supplier-kyc
/v1/* endpoints
  • GET /v1/ontology/object-types
  • POST /v1/tenant/ontology/actions
  • GET /v1/lineage/{type}/{id}
Try it

Open the live admin

The same kernel that runs in this preview is the kernel you self-host. Every link below is wired to a real route — the data is seeded, the agents respond, and the audit chain is verifiable.

admin
MRO module (preview)
Work orders, fleet registry, certificate-of-release flow. Q3 2026.
Open →
docs
Architecture
How a new vertical is a config of tables + agents + endpoints, not a fork.
Open →
FAQ

Common questions

Why "in development"?+

We are working with two pilot Part-145 operators to refine the work-order state machine and certificate-of-release flow. Public release Q3 2026.

Will you support FAA + EASA?+

Yes — both, day one. The certificate templates are operator-overridable.

Can we tie in our parts marketplace?+

Yes — same RFQ engine as P2P, same dispute arbitration. Reuses 80% of the kernel.

Migration from Trax / AMOS?+

Tooling for both planned. We are not asking operators to abandon a working AMOS install — the kernel becomes the agent layer over it.

mro · go-live

Pilot in 28 days. White-label in 42.

Sovereign deployment. Scoped engagement. Invitation-only pilot cohort for Q3 2026.

Strategic inquiry →Try the admin

Other verticals

:3000
Procure-to-Pay
Requisition through payment, autonomous.
:3001
Treasury & Revenue
GAAP ledger, marketplace, satellite spawning.
:3002
ClinKernel
GxP-compliant pharma & clinical workflows.
:3003
Telecom Expense Management
Carrier invoice audit, contract optimization.