T3QUBO-EGovernment & Public SectorFinance
Post-quantum cryptography migration planning
Plan the migration to PQC standards — NOT a QPU workload; listed for completeness as an advisory/defensive posture.
Sector
Cybersecurity / government
Likely buyer
CISOs; government security offices
Hardware gate
Not a QPU workload
Taxonomy
obsolescence-transition × hardening
No live demo yet — not a QPU workload — defensive posture, tracked as advisory. The paradigm-honest position: this use case is demonstrated with crossover analysis, not theater.
GTM talk track
'This one is NOT something you run on a QPU — it's the defensive homework quantum makes necessary. We flag it, we don't sell compute for it.'
OGSM — product operating frame
Objective
Route to advisory, not the compute pipeline.
Goals
- Correctly classify as non-QPU
Strategies
- Advise on PQC readiness
Measures
- N/A compute
OBR — outcome-based roadmap
| Horizon | Outcome we create | Buyer behavior change | Result we measure |
|---|---|---|---|
| Now | Advise on PQC posture | Prospect runs the emulated demo on their own instance data | Booked QPU-time evaluation or paid pilot |
| Next | Refer to specialists | Prospect co-designs a scoped benchmark against their incumbent solver | Documented crossover curve; expansion to production instances |
| Later | N/A | Prospect standardizes on the workflow or buys an on-prem system | Recurring QPU consumption / system sale; reference case |
Fit notes (honesty gate)
Explicitly not a compute use case — advisory only. Included so the portfolio is honest about what quantum is (and isn't) for.
Ready to run this on real hardware?
Emulation-verified today — the same program runs on a Pasqal QPU unchanged.