T1UD-MISDefense
Sensor & emitter placement (ISR)
Place sensors/emitters for maximum coverage without mutual interference — geometric coverage-conflict with a strong sovereign/on-prem buyer.
Sector
Defense ISR
Likely buyer
Defense primes; national security agencies
Hardware gate
Orion; sovereign/air-gapped deployment
Taxonomy
resource-constrained × enabling
Live demo — adiabatic sweep on 5 sensors
Ω 9.4 · δ ±12.6 rad/µs · 4000 ns · R_b 9.1 µmSensors interfere when co-located; maximize non-interfering coverage.
GTM talk track
'Geometry-native, and it runs air-gapped next to your own hardware — no hyperscaler in the loop.'
OGSM — product operating frame
Objective
Land a sovereign ISR placement pilot on air-gapped hardware.
Goals
- One agency runs a placement scenario in-enclave
Strategies
- Lead with sovereign deployment
- Map coverage-interference to geometry
Measures
- Coverage %
- Interference incidents avoided
OBR — outcome-based roadmap
| Horizon | Outcome we create | Buyer behavior change | Result we measure |
|---|---|---|---|
| Now | Agency runs placement on a scenario in-enclave | Prospect runs the emulated demo on their own instance data | Booked QPU-time evaluation or paid pilot |
| Next | Agency benchmarks an operational theater | Prospect co-designs a scoped benchmark against their incumbent solver | Documented crossover curve; expansion to production instances |
| Later | Agency procures an on-prem system | Prospect standardizes on the workflow or buys an on-prem system | Recurring QPU consumption / system sale; reference case |
Fit notes (honesty gate)
Native geometry + best sovereign-deployment alignment (room-temp rack, no cryoplant).
Ready to run this on real hardware?
Emulation-verified today — the same program runs on a Pasqal QPU unchanged.