IQM Resonance · Garnet · Full device width

QPC Runs on IQM

QPC-HTD-20Q. Quantum Polycontextural HPC Threat Detection on every line of IQM’s 20-qubit Garnet processor. A structured, real-world-scale workload: named infrastructure roles, multi-layer security contexts, and a verifiable Resonance job identity.

✓ 20 / 20 QUBITS · GARNET CAPACITY ✓ PRODUCTION JSON + JOB UUID

20
Qubits engaged
Full Garnet width
1,024
Hardware shots
Raw measurement statistics
19.09
θ · cascade band (H₉₀)
Systemic energy percentile
6.50
Threat index R
Coupled stress on network edges

What this test is

QPC-HTD-20Q maps a credible HPC / cyber-resilience story onto Garnet’s full quantum register: one qubit per named node, one Hamiltonian, four polycontextural prelude layers, then QAOA.

Architecture in one glance

What it is designed to prove

For IQM customers and partners: breadth, semantics, and auditability on Nordic superconducting hardware, at the advertised 20-qubit width.

QPC expresses domain-structured workloads that look like what enterprises argue about: cascades, correlated failures, tiered infrastructure. It runs them at the top of Garnet’s advertised qubit count.

Results. Garnet hardware.

Figures below are taken from the canonical run saved as evidence bundle (NDA) (provider: IQM, quantum computer: garnet).

019d779f…
Job ID (UUID)
5.87 s
Wall time (this run)
10.06%
Share ≥ θ (≈ decile)
1.95 – 42.99
H range over samples

How to read the headline metrics

Each shot samples a 20-bit stress pattern across the facility map. We compute classical energy H from that pattern under the threat model. θ is the 90th percentile of H across all 1,024 samples: a high-stress cascade band for this model. The fraction of samples with H ≥ θ is ≈ 10% by construction: a well-formed distribution check on the sampled energies.

R (systemic threat index) aggregates weighted co-stress on high-risk edges: how often critical pairs (compute–storage, gateway–login, and so on) light up together in the data. That is the hook for ranking hot spots and comparing scenarios, runs, or mitigation strategies. Output an IQM sales engineer can place in front of an HPC or national-lab stakeholder.

Top stress concentrations (high‑H configurations)

When samples land in the top energy decile, these nodes appear most often. The quantum run is telling a coherent infrastructure story.

RANK 1
Compute-Cluster-D
Compute tier
RANK 2
Parallel-FS-Primary
Storage
RANK 3
Parallel-FS-Backup
Storage

Verification table

FieldValue
ExperimentQPC-HTD-20Q
BackendIQMBackend (Garnet)
Job ID019d779f-de19-7da3-b178-42f760654c8c
Qubits20 (full width)
Shots1024
QAOA layers p2
θ (90th percentile H)19.091
P(H ≥ θ)0.100586
R6.503379
H mean (sampled)12.038
Wall time (s)5.874
Artifactevidence bundle (NDA)

Queue latency varies by Resonance load. Execution time in the JSON is wall-clock for that submission. The job UUID ties results to IQM’s ledger.

QPC and IQM. What compatibility means.

Platform compatibility: QPC workloads execute on IQM’s cloud and silicon the same way customers already run Qiskit jobs, with a concrete, checkable run (HTD-20Q) and a Resonance UUID.

Technical compatibility (what is proven)

Why IQM and its customers should care

COMPATIBILITY ON GARNET · TECHNICAL + STRATEGIC

One framework, multiple hardware families

Cross-platform runs are the practical definition of “compatible”: the same algorithmic ideas must compile and execute wherever the customer’s contract points.

Quantum Polycontextural Computing is a universal computation layer across these families. IQM is the Nordic superconducting reference implementation.