D5 Flight Ops · PHASE-2 M6

Two-gate release control

Dispatch release is split into an operational readiness gate and a governance evidence gate. A flight does not move to production release until both gates are closed against auditable evidence.

1 blocked
Dispatch boardAction queue
Ready0

Both gates closed; dispatcher release action still explicit

Watch2

One gate has open evidence or acknowledgement work

Blocked1

Production mutation prevented by unresolved gate state

D5 Flight Ops

Operational release gate

watch

Release can proceed only after crew, tech, weather/slot and captain/EFB checks agree.

Crew legality clearRequiredP05:dispatch.release.two_gate.operational
Aircraft tech state currentRequiredP05:dispatch.release.two_gate.operational
Slot/weather/NOTAM acceptedRequiredP05:dispatch.release.two_gate.operational
Captain handoff acknowledgedRequiredP05:dispatch.release.two_gate.operational

P05/P06/P07

Governance evidence gate

blocked

Production mutation remains blocked until policy, signature and append-before-publish evidence are present.

P06 policy decision attachedRequiredP05:dispatch.release.two_gate.governance
P07 signed release artifactRequiredP05:dispatch.release.two_gate.governance
P05 append confirmedRequiredP05:dispatch.release.two_gate.governance
P04 publish authorizedRequiredP05:dispatch.release.two_gate.governance

Active releases

Operational gate + governance gate

sandbox proof data
FlightAircraftOperational gateGovernance gateBlocker / noteEvidence
AX 104
LHR -> JFK		G-AXOAwatchblockedSlot revision requires captain/EFB re-acknowledgement before governance evidence can close.DR-2026-05-17-104
AX 238
MAN -> AMS		G-AXOBreadywatchP07 signed release artifact pending.DR-2026-05-17-238
AX 771
EDI -> LHR		G-AXOCreadyreadyNo active blocker; release still requires explicit dispatcher action.DR-2026-05-17-771
Two-gate release | AXIOM