Edukaizen

Menu
  • News
  • Hubbard 1D
    • Part 1: 1D Hubbard model
    • Part 2: Snake layout and fSWAP
    • Part 3: Qiskit and Fire Opal
    • Part 4: 120-qubit run
    • Part 5: Time-to-answer
    • Part 6: Tensor networks
    • Part 7: Majorana propagation
    • Part 8: Reading heatmaps
    • Part 9: Digital vs cold-atom labs
    • Part 10: Official Monoprop benchmark
  • Hubbard 2D
    • Part 1: 1D to 2D
    • Part 2: Cuprates
    • Part 3: 3×3
    • Part 4: Time
    • Part 5: 4×4
    • Part 6: 6×6 Fez
  • Hadron
    • Part 1: Hadron on a quantum processor
    • Part 2: Quarks and confinement
    • Part 3: SU(2) and LSH
    • Part 4: Hamiltonian and circuit
    • Part 5: Fire Opal
    • Part 6: Classical simulations
    • Part 7: Quantum advantage
  • Black Hole OLE
    • Part 1: What we ran
    • Part 2: How OLE works
    • Part 3: Fire Opal and Kingston
    • Part 4: The tensor-network challenge
    • Part 5: Hawking and scrambling
    • Part 6: What the result proves
    • Part 7: Local toy model
    • Part 8: QGSS26 compatibility
  • Random Graph
    • Start here
    • Part 1: Theory
    • Part 2: Circuit
    • Part 3: Qiskit
    • Part 4: Complexity
    • Part 5: Verification
    • Part 6: Workflow
    • Part 7: Conclusion
  • QOS QML
    • Tutorial: UMI counts to a four-qubit circuit
    • Part 1: The QML task
    • Part 2: QOS theory
    • Part 3: Gene expression to 40 qubits
    • Part 4: JAX to hardware
    • Part 5: Readout and classifier
    • Part 6: 40-qubit result
    • Part 7: Route to quantum advantage
    • Part 8: 60-qubit result
  • Floquet-Ising
    • Part 1: Floquet physics
    • Part 2: Ising cycle
    • Part 3: Two-qubit toy model
    • Part 4: Oscillation and entanglement
    • Part 5: Noise and error mitigation
    • Part 6: Toward 51 qubits
  • Work
    • Quantum Gold
      • Part 1: Why gold is a relativistic quantum problem
      • Part 2: Why the 2025 gold VQE study stalled
      • Part 3: From QE and spin–orbit coupling to Qiskit
      • Part 4: Twelve gold spinor modes on four qubits
      • Part 5: The 24-qubit route: an active window for transport
      • Part 6: 24 qubits on IBM and with Fire Opal
      • Part 7: The road to quantum advantage for gold
      • Part 8: 24 gold spinor modes on IBM with ZNE-PEA
    • HaPPY Gravity
      • Part 1: Gravity as a phase gate
      • Part 2: Bosons and convergence
      • Part 3: The dynamic HaPPY benchmark
      • Part 4: The N=145 classical audit
      • Part 5: MPS and Majorana baselines
      • Part 6: PEA/ZNE and the decisive test
    • Fibonacci Anyons
      • Part 1: Fusion and braiding
      • Part 2: The 3/5/9-qubit ladder
      • Part 3: Why nine qubits were too deep
      • Part 4: Structure-aware simplification
      • Part 5: IBM hardware diagnostic
      • Part 6: Results and open questions
  • Advantage List
Menu

Why the full nine-qubit circuit was too deep

Series home | Previous | Next | Code and evidence | Minimal-circuit paper

Nine qubits are not the problem by themselves. The obstacle is the number and structure of the gates produced when a hardware compiler expands each multi-controlled F-move and routes the result over a sparse superconducting-qubit layout.

A statistically significant contrast is not enough. If most probability has leaked out of the encoded fusion subspace, the surviving signal is no longer an interpretable implementation of the intended experiment, and it is not evidence of quantum advantage.

From a compact diagram to thousands of entangling gates

The generic all-to-all decomposition used about 1,476 CX gates for each braid-order arm. On a heavy-hex proxy, the best order arm reached 2,926 CX gates at depth 6,854. The primary phase-sensitive filter was worse: about 4,300 CX gates at depth 10,009.

This is the classic difference between logical circuit size and compiled hardware cost. A four-controlled arbitrary single-qubit unitary is a compact box on paper, but a generic synthesis knows nothing about the Fibonacci matrix, the reachable control patterns, or clean work qubits elsewhere in the register.

The preregistered readiness gate

The noise study froze three simultaneous conditions:

  • at least 80% probability of detecting the order contrast;
  • at most 10% leakage from the encoded fusion subspace;
  • at least 75% pass probability for the source-state filter.

Under mild one-qubit depolarizing noise, the contrast remained detectable with 128 shots, yet leakage was about 46%. Under mild two-qubit depolarizing noise, leakage rose to 61%. Mild thermal and combined proxies drove leakage to roughly 99%. More shots could estimate the damaged distribution more precisely, but could not restore the intended encoded state.

The verdict was therefore REVISE CIRCUIT/OBSERVABLE, not “run more shots.”

What mitigation did and did not do

Mitigation was audited rather than treated as a magic repair step.

Method Best observed effect Why it did not change readiness
M3 readout mitigation Restored readout-medium contrast from \(0.5562\) to \(0.6180\) The raw readout-only case already passed
PEA/ZNE Improved mild 1q and 2q contrast to \(0.5386\) and \(0.4715\) Variance grew by \(5.86\times\) and \(4.44\times\); raw leakage still failed
Bounded PEC estimate Conservative overhead \(11.77\times\) to \(19.14\times\) Exceeded the frozen \(5\times\) cap
Additional shots Increased detection power for attenuated contrasts Did not repair state leakage or filter failure

This does not mean the methods are useless. M3 correctly addresses measurement assignment error, and extrapolation can reduce bias in suitable observables. It means they cannot turn an excessively deep state-preparation circuit into faithful encoded dynamics merely by post-processing its output.

Fire Opal compatibility was a separate question

A later validate-only check submitted no shots and consumed no quantum time. Fire Opal accepted three ordered QASM payloads for ibm_fez, but the returned physical circuits were still deep: depth 1,665 with 598 two-qubit gates for the primary filter, and depth 1,219 with 441 two-qubit gates for each order arm.

That result established input and workflow compatibility, not hardware accuracy or mitigation benefit. No Fire Opal execution is part of the hardware result reported in this series.

The useful failure

The readiness failure localized the bottleneck. The Fibonacci algebra was not wrong; the generic synthesis was wasteful. The next design loop therefore targeted the internal identity of F, reachable control subspaces, adjacent cancellations, and finally the measured observable itself.

This is also why a qubit count cannot be used as a shortcut for complexity. A nine-qubit circuit may be too deep for current hardware, while a much larger but highly structured circuit could in principle be easier. Gate topology, entangling depth, idle time, error model, and the observable all matter.

Sources

  • Full hardware-readiness report
  • Fire Opal validate-only report
  • Mitigation and detection-power artifacts
Series home | Previous | Next | Code and evidence | Minimal-circuit paper

Recent Posts

  • Quantum computing-nieuws — 14 augustus 2026
  • IBM Quantum queues surge past 264,000 pending jobs
  • Quantum computing news — August 13, 2026
  • Quantum computing news — August 12, 2026
  • Quantum computing news — August 11, 2026

Recent Comments

No comments to show.

Archives

  • August 2026
  • July 2026
  • May 2026
  • March 2026
  • February 2026
  • September 2024

Categories

  • 10
  • Quantum Computing
  • Uncategorized
©2026 Edukaizen | Theme by SuperbThemes