Cycle 01

The frontier,
mapped.

Research groups in quantum. Every one names the result that would end it, and every result gets published — including the ones that do.

Join the waitlistCycle 01 has not opened yet
Error correctionControl & readoutSimulation & theoryData & inferenceMaterialsSensing & commsWhat drives the ~1/hour correlated-error floor? (Cogitan in-house)How tight is the structural floor for dissipative cats? (Cogitan in-house)What must a device paper report to be checkable? (Cogitan in-house)Do frequency-collision rules need gate direction? (Cogitan in-house)Can a pre-fab model predict radiation bursts? (Cogitan in-house)Feedforward cancellation of strike frequency shifts (Cogitan in-house)A neural decoder on public Willow data (Cogitan in-house)A neural surrogate for RSFQ cells (Cogitan in-house)Room-temperature spin registers (Cogitan in-house)Learned readout discrimination (Cogitan in-house)
Research groups plotted by area, with Cogitan's own in-house projects as diamonds. Work that met its own kill criterion remains on the map as a hollow marker.
Recruiting0Active3Completed2Ruled out5Run by Cogitan10

No group has been admitted yet. The diamonds are Cogitan's own projects, run on the same terms before the first cycle: a question, the result that would end it, and the outcome published either way. Nothing ever leaves the map. A project that meets its own kill criterion stays on as a hollow marker, permanently.

The record so far · run by Cogitan

3 open, 2 answered, 5 ruled out. Each one stated its falsifier before the work started.

Open

2026-10

What drives the ~1/hour correlated-error floor?

Is the residual ~1/hour burst rate behind a below-threshold processor's error floor mostly cosmic hadrons — so shallow underground sites fix it — or muons and environmental gammas, which they do not?

Ends if: If hadrons dominate events above 1 MeV across every plausible die thickness and mounting orientation, the underground-mitigation reading stands; record it and stop.

Where outsiders could help: Species-resolved Geant4 runs on public cryostat geometry, an audit of the published flux and attenuation figures, and the counting statistics on a handful of floor events.

Read more →

Open

2026-08

How tight is the structural floor for dissipative cats?

The ideal-code floor is a valid lower bound on logical error for the dissipative cat but runs 6–14× low. Is there an effective gap that closes the distance?

Ends if: An effective gap for the dissipative cat fails to close the floor-to-rate distance across the κ₂/γ sweep, or is shown not to exist.

Where outsiders could help: Exact Liouvillian numerics (QuTiP) and open-systems theory.

Read more →

Open

2026-08

What must a device paper report to be checkable?

Published superconducting devices reach a small fraction of the design rules a reader could check them against. Is the binding constraint reporting convention rather than physics?

Ends if: A minimal reporting set fails to lift median reach toward the saturated value across a large corpus, or lifts the counts without changing any verdict.

Where outsiders could help: Annotating published device papers against the rule set.

Read more →

Answered

2026-09

Do frequency-collision rules need gate direction?

Does the standard seven-condition collision taxonomy give the right count on working hardware when the coupling map is read as undirected?

Ends if: If the undirected and directed readings give the same violation count on measured IBM Eagle calibration data, direction does not matter and the rules stand as written.

Outcome: They do not agree: 27 violations undirected, 4 with real gate direction, on a working processor. One condition fires on 57 of 144 (39.6%) of a device's real gates, and is now off by default.

Read more →

Answered

2026-10

Can a pre-fab model predict radiation bursts?

Can a model built from the environment, deposited energy and phonon transport reproduce a published processor's measured burst rate and footprint without fitting to it?

Ends if: Each stage had a numeric gate set before it ran; any stage that misses its gate is reported as failed, not refit.

Outcome: Muon burst rate 9.5/hr against 9.3 measured with nothing fitted — but only at a 0.3 mm die, and no single thickness fits the muon and gamma channels together. Of the last five build stages, two passed their gates and two failed; the failures ship as published known misses rather than refits.

Read more →

Ruled out

2026-10

Feedforward cancellation of strike frequency shifts

Radiation strikes shift qubit frequencies coherently for about a millisecond. Can a feedforward frame correction, driven by a burst model, cancel the shift?

Ends if: If an existing, cheaper mechanism already removes the coherent part, or what remains is incoherent, there is nothing for feedforward to do.

Outcome: Killed before build. A spin echo in the code cycle already cuts the excess detection from 17% to 2% above background in published data, and what survives the echo is incoherent, which no frame update can fix.

Ruled out

2026-08

A neural decoder on public Willow data

Does a neural surface-code decoder beat the classical decoders shipped with Google's public Willow dataset?

Ends if: If the best configuration does not beat correlated matching on a held-out patch, the program stops.

Outcome: It does not: the best configuration is 28.75% worse than correlated matching at d=5 (n=100,000). An earlier +13.24% was measured against plain matching mislabelled as correlated, and is withdrawn.

Ruled out

2026-08

A neural surrogate for RSFQ cells

Does a large graph model predict RSFQ cell behaviour better than a classical baseline on the same data?

Ends if: If a gradient-boosted tree on the same inputs matches or beats it, the model is not worth serving.

Outcome: The tree won on every head, and the neural model had been predicting "works" for every design it was shown. Its headline figures are withdrawn and the tree is what ships.

Read more →

Ruled out

Room-temperature spin registers

Is there a room-temperature spin platform where coupling and readout work at the same distance?

Ends if: If every candidate's coupling window and readout window fail to overlap, the direction is closed.

Outcome: All eight candidates died, six to prior art and two to a fabrication dependency. The coupling and readout windows sit a factor of 5–10 apart in distance.

Read more →

Ruled out

Learned readout discrimination

Does a neural network read weak-measurement records better than a simple linear model?

Ends if: If a linear model on a handful of features matches the network, the learned approach adds nothing.

Outcome: A linear model on 8 time-binned means scored 0.820 held-out accuracy, against 0.805 for a network on the raw 64-sample record.

Read more →

Every group states this first

“If decoder accuracy on real device data stays within 1% of the uniform-noise baseline, the premise is wrong and there is nothing here worth six months.”
What a falsifier looks like

Not a risk. Not a caveat. A result you could actually reach that would mean stopping. It is snapshotted when a group is admitted and the midpoint review tests them against it verbatim, so it cannot be softened on the way there.

How it works

01

Anyone can propose

No lab, no PhD, no affiliation. Leads put up one piece of prior work — a paper, a repository, a writeup — reviewed once and carried across cycles. An empty affiliation is not a mark against you. People outside institutions are much of who this is for.

02

Name what would kill it

Before the method, before the timeline, you state the finding that would end the project. Proposals whose falsifier turns out to be a risk rather than a result are the most common decline, and the fastest one to make.

03

Killing it counts as finishing

A group that meets its own criterion and stops publishes the negative result and closes as completed on criterion. A clean answer in eight weeks beats eight months of drift, and quantum has nowhere to put those answers today.

What a group gets

  • Collaborators, screened and matched inside a fixed cycle.
  • A deadline and a midpoint review. Side research dies of drift far more often than it dies of anything else.
  • A workspace that records what you ruled out, not only what worked.
  • A public record with your name and contribution on it.

What it does not

  • No funding. Cogitan has no budget for this yet and would rather say so than imply otherwise.
  • No lab access and no fridge time. Groups here do software, theory, and data — most of what a distributed team can do in any case.
  • No guaranteed seat. Three applications per person per cycle, and leads pick.

Before we ask it of you

Everything above is a promise until Cycle 01 runs. What is not a promise is that Cogitan already publishes on these terms — the directions that ended, the reason each one ended, and a paper whose abstract states where it stops.

The frontier starts empty.

Cycle 01 opens once there are enough people to fill it properly. Groups get placed, not posted into a void — so the list comes first and the cohort second.

One email when Cycle 01 opens. Nothing else.

Read the rules in full →