T1–T2UD-MISAviationDefense
Air-traffic / UTM corridor & slot allocation
Assign flight corridors and time slots so separation minima are never violated — exclusion radii are literally blockade radii.
Sector
Aviation / unmanned traffic management
Likely buyer
ANSPs; UTM providers; drone-fleet operators
Hardware gate
Orion; dense airspace → larger/weighted
Taxonomy
fragility-reliability × hardening
Live demo — adiabatic sweep on 6 slots
Ω 9.4 · δ ±12.6 rad/µs · 4000 ns · R_b 9.1 µmFlight slots conflict when separation minima overlap; find the largest simultaneously-safe set.
GTM talk track
'Separation minima are exclusion zones. Exclusion zones are what blockade physically enforces.'
OGSM — product operating frame
Objective
Demonstrate conflict-free slot allocation under separation constraints.
Goals
- One UTM provider runs a corridor scenario
Strategies
- Map separation minima to blockade radius
Measures
- Conflicts avoided
- Airspace utilization
OBR — outcome-based roadmap
| Horizon | Outcome we create | Buyer behavior change | Result we measure |
|---|---|---|---|
| Now | Provider sees conflict-free slotting on a scenario | Prospect runs the emulated demo on their own instance data | Booked QPU-time evaluation or paid pilot |
| Next | Provider benchmarks a dense airspace | Prospect co-designs a scoped benchmark against their incumbent solver | Documented crossover curve; expansion to production instances |
| Later | Provider integrates into UTM stack | Prospect standardizes on the workflow or buys an on-prem system | Recurring QPU consumption / system sale; reference case |
Fit notes (honesty gate)
Separation minima are exclusion radii — native. Safety-critical framing (hardening).
Ready to run this on real hardware?
Emulation-verified today — the same program runs on a Pasqal QPU unchanged.