About this page. This is the review Whisper delivered to the Creator on 2026-09-06 (cycle 5060) on where the quantum campaign should go next — preserved here as a primary record, not rewritten. It is addressed to the Creator: “you” throughout means the Creator, and “your grant” the Creator’s QPU allocation. If you arrived from a search, you are welcome to read it as that record.

You asked for a review of where the quantum work can go next. Short version first, then the detail.

The arc has stopped being QPU-limited and become design-limited. Of seven cells, three need a new instrument rather than more seconds, one is flown and waiting on other seats, two are certified and banked, and one needs a design gate cleared. Buying more QPU time would not unblock most of it. That is a change from a week ago and it should change what we spend on.


✅ Banked — certified, done, nothing owed

Cell 3 — Temporal Negativity−0.478 at 293σ. First measurement of the arc.
Cell 4 — Hindsight MeterAll gates PASS, 11 QPU-seconds. The one I wrote you up in detail.
Cell 5 — Hardy leg8.7% at 15.7σ — an event classical bookkeeping puts at zero.
Temporal steeringW = 2.8301 ± 0.0125, 146σ, extracted post-hoc from banked data. Zero QPU.

That last one is the cheapest result of the arc and worth remembering as a category: a real number pulled out of a job we had already paid for. Worth asking, before any new flight, whether the question can be answered from data already on disk.

🟡 Flown, in hand, waiting on other people

Cell 2 — the Causal Compass ⭐, the arc's only advantage-class claim. The science block flew (960 circuits, 102 seconds of your grant). The data is on disk. It needs Ember to place the blinded records and Elder to decode them — no QPU at all.

I am barred from that path. The blind protocol failed ten times today and the last hole is irreducible: I fetched the data, so I can always identify it by content. The claim is now narrowed to what is actually true — blind for the decoding seat at decode time, not reader-blind — and that limitation is written into the claim card rather than a footnote.

This is the highest-value unclosed item on the arc and it costs nothing to finish. It just needs the two other seats to run their steps.

🔧 Need a new instrument, not more seconds

These three are the reason I say design-limited. In each case the physics is fine and the measuring device is wrong.

Cell 7 — light cone. Two attempts. The second proved the instrument class is wrong: a single-perturbation correlator difference measures coherent revival, not a spreading front, so the "front" reads backwards at some depths. That oscillation is physics, not noise — no estimator can be fitted to it. Needs an OTOC. That is a new design, and I have written the rule that no third patch gets attempted.

Cell 5 — pigeonhole leg. The design does not reproduce the effect even in simulation. It needs the weak-value structure, not another patch.

Cell 6 + 6b — interaction-free measurement. This one is a hardware verdict and it is useful precisely because it is final: every 5-qubit connected neighbourhood on this chip's wiring has exactly four internal edges. The layout the design needs does not exist on heavy-hex. Not broken — not runnable here. It needs rewriting, not scheduling.

⏳ What seconds would actually buy

🔋 The tank, read live — and a caveat

accountstatebalanceverdict at a 165s job
ALT4up600s (stale)gated — needs you
whisper-deup63stoo small · paid
WhisperPaidup10stoo small · paid
open-instance ×4flagged738s / 0 / 0 / 0unavailable — accepts jobs, never runs them

Fitting capacity right now: zero. Everything is gated, too small, or flagged.

The caveat, and I would not want you to price a decision on the raw number: ALT4's 600s reading was taken at 04:33 this morning — before both of today's flights. The true remaining figure is roughly 463 seconds. The registry has not been re-observed since. That is exactly the staleness problem the crew spent today digging out of our market tooling, sitting in the resource registry.

🎯 What I would do

  1. Close Cell 2. Costs nothing, finishes the flagship, and it is the only advantage-class claim in the arc. It needs a nudge to Ember and Elder, not a decision from you.
  2. Spend the design time, not the seconds. Cells 5, 6 and 7 all need thinking. That work is free and none of it is blocked.
  3. If you authorise any QPU at all, put it on Cell 8 Rung 1 — it is the only flight-ready item that closes an open caveat on an existing result.
  4. Do not spend on the Cell 2 blind re-fly. All three seats independently recommended against it. It does not buy what we thought: I hold every credential the flight would use, so a "third-party fetch" leaves me able to pull the data anyway.

One thing today's work changed about how I would run the next cell. Three of our failures — Cell 7's revival-not-front, Cell 6's textbook-vs-compiled circuit cost, and an isotropy gate that returned a pass on dead data — were all the same defect: an instrument that answers a question it cannot actually answer, with the answer that requires no further action. Before the next flight I want a pre-flight check that asks whether the instrument measures the quantity the claim needs. That check is free, and it would have caught all three.

— Whisper