Open-instance verified benchmarks (Heron r2 · 156Q)

Five reproducible QPC-orchestrated workloads on the IBM Open plan (open-instance): labelled context layouts from 4 registers on one 156-qubit chip through 24 contexts across six cluster jobs (tier T4). Thirteen IBM Runtime jobs, 512 shots each, schema qpc_benchmark_v1.

Plain English

What this test is: Five labelled QPC workloads on IBM Open / Heron r2 156Q: from 4 registers on one chip up to 24 contexts in six cluster jobs (T01–T05).
Why we did it: Show the QPC orchestrator can plan, submit, and archive multi-context production jobs on a full Heron r2 layout.
What QPC computed: 13 IBM Runtime jobs · 512 shots each · schema qpc_benchmark_v1 · public job IDs in the table below.
Headline result: 13/13 jobs archived · scale ladder 4→24 contexts · reproducible JSON payloads.
What we claim: Orchestration and hardware reach at 156Q: co-resident contexts, cluster scale-out, auditable IBM IDs. Architecture-gap pages on the same fleet sit beside this ladder (coupling ablation, QQ, PFQM, KS).

What this page is

Orchestration and hardware-reach evidence. Real layouts, real IBM Heron r2 backends, verifiable job IDs, and standard JSON payloads. QPC plans and executes multi-context workloads on 156 qubits at increasing width and cluster depth.

Architecture metrics (bridge ICC, K-ablation, physical correlators) live on the linked pages below. This page is the scale ladder those jobs sit on.

Summary

Audit: Every job ID can be verified in the IBM Quantum console. Full JSON payloads ship with the licensed QPC buyer package.

Task	Tier	Layout	Backend	IBM job ID(s)
T01 · 4-context CO₂ (one submission)	T1	4×39Q = 156Q	ibm_fez	`d8atngdmdd1s73b8p4fg`
T02 · 12-context finance (one submission)	T2	12×13Q = 156Q	ibm_fez	`d8atp7h59p8c73blnl4g`
T03 · 6-context cluster	T3	2×(3×26Q)	ibm_marrakesh	`d8bjq6j8amns73bi9i00`, `d8bjq8c7avuc73dpo1f0`
T04 · 12-context finance cluster	T3	3×(4×13Q)	ibm_marrakesh	`d8bjqek7avuc73dpo1og`, `d8bjqg2jki0s73aq0nng`, `d8bjqhs7avuc73dpo1tg`
T05 · 24-context logistics	T4	6×(4×6Q)	ibm_marrakesh	six jobs · IDs in licensed JSON

What the runs establish

T01 and T02 · co-resident contexts, one circuit, one measurement

All labelled contexts share one IBM submission and one shot histogram on the full 156-qubit width. Genuine co-residence in a single run. A matched coupled vs decoupled control at identical width and shots is published for T03-class clusters. See Coupling ablation (bridge ICC + noise mitigation).

T03 and T04 · transjunction gates in-circuit

Cluster jobs include transjunction bridges between contexts inside each submission. The coupling ablation page reports ON vs OFF at 3×26Q on ibm_fez and ibm_marrakesh (1024 shots, bridge-local ICC with QPC readout mitigation).

T05 · hierarchical scale-out

Twenty-four labelled contexts executed as six cluster jobs with classical meta-merge: orchestration at hierarchical scale on Heron r2.

Across all tasks

Reproducible scripts, tier metadata, and noise-mitigation blocks in JSON (software layer).
Shannon entropy and unique outcomes confirm the circuits executed and produced diverse shots on hardware. Architecture discrimination uses the controlled pages linked below.

Architecture metrics on the same fleet

For reviewers and buyers who want the architecture gap beside the orchestrator ladder:

Coupling ablation (ON vs OFF) · bridge-local ICC + QPC readout mitigation; |Δ| > 0.05 on Fez and Marrakesh.
QPC-QQ pilot · K=1 vs K=4 control at matched resources; order-blind fit, held-out joints.
PFQM V3 on Heron · physical ZZ correlators (ICC, FSP) vs single-context baseline.
Kochen–Specker / Mermin–Peres (Fez) · contextuality witness with readout mitigation.

Open-instance verified benchmarks (Heron r2 · 156Q)

What this page is

Summary

What the runs establish

T01 and T02 · co-resident contexts, one circuit, one measurement

T03 and T04 · transjunction gates in-circuit

T05 · hierarchical scale-out

Across all tasks

Architecture metrics on the same fleet

Related pages