We are building for the machine that does not exist yet.

Systems built so the cryptographic primitive is a swappable component: it can be replaced without rewriting what sits on top of it.

• Cryptography treated as a component, not an assumption
• The primitive replaceable without rewriting above it
• The preparation that survives a real migration deadline

Cryptography treated as a swappable component rather than a permanent assumption. Systems built so the primitive can be replaced without rewriting what sits on top — which is the only preparation for post-quantum cryptography that survives contact with a real migration deadline.

Optimisation problems written down in a form that names the solver explicitly. The classical solver runs them today, and the problem statement is already separable from the thing that solves it.

• The problem stated separately from the solver
• The classical solver runs it today
• A different class of hardware can be swapped in when it is worth using

Optimisation problems written down in a form that names the solver explicitly instead of burying it in application code. The classical solver runs today; when a different class of hardware becomes worth using, the problem statement is already separable from the thing that solves it.

Orchestration across classical and quantum resources so each part of a workload runs where it actually belongs, on the honest position that almost everything belongs on classical hardware today.

• Workloads split across classical and quantum resources
• Each part runs where it actually belongs
• The value is knowing precisely which parts will not, and why

Orchestration across classical and quantum resources where each part of a workload runs wherever it actually belongs. The honest position: almost everything belongs on classical hardware today, and the value of the work is knowing precisely which parts will not, and why.