Qubit Isolation Zones
The Isolation module provides logical partitioning of qubit registers across different security domains. In multi-tenant or classified environments, isolation zones enforce that circuits from different projects or classification levels never share physical qubits, prevent crosstalk leakage, and produce per-zone audit trails.Use Cases
- Multi-tenant QPU time-sharing: Ensure organisation A’s qubits are physically separate from organisation B’s
- Classified research: Separate SECRET and UNCLASSIFIED workloads on the same QPU
- Lab partitioning: Allocate dedicated qubit regions to different research groups
- Compliance: Satisfy FIPS 140-3 and NIST SP 800-175B physical isolation requirements
List Zones
Allocate a Zone
Returns the allocated
zone_id used for isolated execution. Inspect zones with GET /api/v1/isolation/zones and GET /api/v1/isolation/zones/{zone_id}; release one with DELETE /api/v1/isolation/zones/{zone_id}.
For fault-tolerant logical zones (QEC-encoded), use POST /api/v1/qec/isolation/zones with code_id and n_logical_qubits.
Execute Inside a Zone
generate_evidence: true the run produces a per-zone evidence record, retrievable at GET /api/v1/isolation/evidence/{evidence_id}.