T1UD-MISAerospace & SpaceDefense
Satellite mission planning & tasking
Select the largest set of imaging/observation tasks that don't conflict on slew, footprint, or resource windows. Framed and solved as MIS on Pasqal hardware by Thales.
Sector
Earth observation / space operations
Likely buyer
EO satellite operators; defense space agencies
Named precedent
Thales × Pasqal — satellite planning as MIS
Hardware gate
Orion today; large constellations → bigger registers / weighted (Vela)
Taxonomy
throughput-limited × accelerating
Live demo — adiabatic sweep on 5 tasks
Ω 9.4 · δ ±12.6 rad/µs · 4000 ns · R_b 9.1 µmFive imaging tasks; conflicting slew/footprint windows link them. Weighted by mission value — the largest-value non-conflicting set wins.
Weighted instance: site values map to per-atom detuning — on hardware this needs Vela-class local addressing. Emulated exactly here.
GTM talk track
'Thales already framed this exactly as MIS and ran it on neutral atoms. Your tasking conflicts are geometric — slew windows and footprints — which is the one problem shape this hardware was born for.'
OGSM — product operating frame
Objective
Convert the Thales-validated framing into a booked operator benchmark.
Goals
- One EO operator runs a real tasking window
- Reaction-time delta documented
Strategies
- Lead with the Thales precedent
- Map slew/footprint conflicts to geometry
- Show weighted tasking as the Vela upgrade
Measures
- Tasks scheduled per orbit
- Replan latency
OBR — outcome-based roadmap
| Horizon | Outcome we create | Buyer behavior change | Result we measure |
|---|---|---|---|
| Now | Operator schedules a sample tasking window | Prospect runs the emulated demo on their own instance data | Booked QPU-time evaluation or paid pilot |
| Next | Operator benchmarks a full constellation day | Prospect co-designs a scoped benchmark against their incumbent solver | Documented crossover curve; expansion to production instances |
| Later | Operator adopts for operational replanning | Prospect standardizes on the workflow or buys an on-prem system | Recurring QPU consumption / system sale; reference case |
Fit notes (honesty gate)
Strongest lead cluster: public precedent de-risks the framing; constellation growth makes the pain rising and budgeted.
Ready to run this on real hardware?
Emulation-verified today — the same program runs on a Pasqal QPU unchanged.