Skip to content
Leg 05 · Adopt · the experience

one report.one closed loop.

Follow one occurrence from the apron report to a signed, enforced closure. Every field carries its source, every gate must pass, and the operation organizes itself around the record. Then take the same path yourself: demo to production, with the design partner cohort.

The journey
9record doors
3field sources
3closure gates
2person sign-off
The report lands

One report. Three honest sources.

The reporter writes the narrative, the system adds weather and fleet, and eAvy proposes the ICAO category. Every value keeps its source and its confidence, and nothing is silently overwritten.

NORTHGALE AIR · SYNTHETIC OPERATION
OCC-2026-0042FILED · CLASSIFYING
Reporter narrative
Crew reported unusual vibration on approach, ILS RWY 25L. Stabilised at 1500ft AGL, monitored to touchdown, no further anomaly.
METAR at occurrenceSYS
VOMM 141330Z 28015KT 9999 FEW020 34/22 Q1008
ICAO classificationAI · 94%
Aircraft upset / Loss of control, in-flight (LOC-I)
Risk bandAI · 88%
4C · Tolerable, monitor
⌘K
Command palette
Jump to any record, module or action by name, from anywhere.
REF
The reference is the identity
Type a reference like OCC-2026-0042, in the {MOD}-{YYYY}-{NNNN} convention, and the record opens.
⌥Spc
Summon eAvy
The copilot opens beside the record, never in the way.
⌘J
My queue
The urgency-scored work list, one keystroke away.
Advance the stage
Move the record forward the moment its gate passes.
Driven from the keyboard

Command it from the keyboard.

Jump to any record by its reference, classify it, and advance the stage without reaching for the mouse. The command palette is the cockpit, and the reference is the identity.

The graph forms

The operation organizes itself.

The moment it is classified, the links form. The occurrence ties to the barrier it weakened, the finding it raised, the action that fixes it, and the look-alikes before it. The trail is the record.

23
View layers, one graph
1
System of record
0
Silos to reconcile
Record
Occurrence
weakened
Barrier
Record
Barrier
raised
Finding
Record
Finding
corrected by
Action
Record
Action
changed
Document
UNIVERSAL LINKS · the operation, self-organized
Report to closure

Watch it reach closure.

SMS · FILED
Occurrence reported from the apron
AIA · CLASSIFIED
eAvy drafts the ICAO category, a person validates
GRAPH · ORGANIZED
Links form to barriers, findings and look-alikes
BAR · RATED
Barriers rated, which held and which failed
CAP · PROVEN
Corrective action verified for effectiveness
SIGN · CLOSED
Two people sign, the loop is closed
NORTHGALE AIR · SYNTHETIC OPERATION
OCC-2026-0042CLOSED · LOCKED
Final classification
Aircraft upset / Loss of control, in-flight (LOC-I). Human-confirmed.
Barrier assessment
Rated on this event, two controls found degraded and corrected.
Effectiveness gate
Corrective action verified before the record could close.
Closure sign-off
OWNER + VERIFIER · TWO NAMES
Closure is earned

Three gates. No exceptions.

A record cannot close on a single click. Barriers must be assessed, the fix must be proven effective, and two people must sign. The workflow holds the line, so a closed record is a defensible one.

Barriers assessed. A record cannot advance until the barriers it touched are rated for health, not assumed intact.

Effectiveness proven. Every corrective action carries an effectiveness gate. The plan closes when the fix is verified, not when it is written.

Two people sign. Owner is not verifier, enforced by the workflow. Closure is a recorded, two-person act, never a single click.

The adoption path

From first look to production.

No big-bang migration. Each step has an exit, and each step earns the next.

Step 1 · DEMO
Bring a real scenario. Watch it move end to end.
Step 2 · SANDBOX
A bounded evaluation group, success criteria agreed up front.
Step 3 · PILOT
One operational domain live, with your data and your users.
Step 4 · PRODUCTION
Rollout by suite, with migration and training alongside.
Design partner cohort · open

Shape it before the market does.

A small cohort of operators adopting early, on founding terms, with a direct line to the build.

What partners get

A seat at the design table. Your workflows shape module priorities and the intake spine before the wider market sets them.

Founding terms, locked. Cohort pricing that survives the platform maturing past it.

The founder on the line. Direct access, not a ticket queue. Issues route to the person who can change the product.

What we ask

Real scenarios. Bring live occurrences, findings and audits, not toy data. The platform is proven on your operation.

A feedback cadence. A standing review where we watch your team work and fix what slows them down.

An honest verdict. If a gate fails your audit, say so on record. The product hardens on named objections.

One report. One closed loop.

Closure cannot be faked.Barriers assessed, effectiveness proven, two people sign. Enforced by the workflow.
Three sources on every field.Human, system and AI, each with its source and confidence, never silently overwritten.
One operation, one graph.The record ties to everything it touched, so the trail is the record.
01 WHY 02 THE SHIFT 03 PLATFORM 04 EVALUATE 05 ADOPT
Final leg
Ready when you are.

You have flown the route: the chain, the shift, the instrument, the evaluation, the experience. The walkthrough is where it becomes yours.