Prasad Patil
Notes from the lab · Nagpur, IN
2026-08-02· 5 min readquantumFQ-DOA

Hybrid vs. fully coherent: the coherence budget

The first DOA note ended on the trade: costs coherence, buys flexibility. This note is about the trade itself - where the coherence goes, and what the two architectures in the family do differently with it.

Both architectures answer the same problem - estimating a parameter with an oracle that can learn it mid-flight. The difference is where the learning happens, and that single choice decides the cost model.

HQ-DOA: learn between runs

HQ-DOA - Hybrid Quantum DOA - is the practical entry point. The quantum circuit runs a measurement; the classical side reads the outcome, updates its model of the parameter, and steers the next run's oracle accordingly. The oracle's parameters change between runs.

FQ-DOA: learn inside the evolution

FQ-DOA - Fully coherent - moves the feedback inside the quantum evolution. The oracle's adaptation is unitary; the state never leaves the coherent register to consult a classical model. The parameter and the oracle co-evolve within a single run.

The budget, as a table

HQ-DOAFQ-DOA
Where adaptation livesclassical, between runsunitary, inside a run
Granularityrun-levelshot-level
Coherence spent per adaptation≈ 0real, finite, counted
Drift toleranceslow driftfast drift
Today's NISQ feasibilitynowresearch frontier
Statuspublished (IEEE TIM 2026)under review (IEEE TETC)

Why "budget" is the right word

The reason I keep calling it a budget and not a trade-off is that a budget is something you can account for. In a fixed-oracle world, coherence decay is a nuisance to be minimized away. In the FQ-DOA world, coherence is denominated - you know how much the adaptation spends, you know how much the run can afford, and you can choose the operating point: more adaptation, less run length; or longer runs, slower adaptation.

That's the shift in mindset the framework pushes for, and it's the same mindset shift I've lived through in enterprise architecture. When you treat a legacy system's downtime budget as a resource to be managed rather than a failure to be avoided, migration strategy changes entirely - you stop asking "can we afford any downtime?" and start asking "what's the cheapest state change that gets us there?"

"You can't optimize what you refuse to measure - coherence included."

- a translation of a very long footnote in the FQ-DOA draft

The morphological edge case

The third line, QDOA, is the one that escapes both columns of the table. Morphological adaptation changes the oracle's structure, not just its parameters - a different operator shape entirely. It's the least mature and the most interesting: if parameter adaptation is the budget question, morphological adaptation is the design question, and it comes with the vocabulary problem I mentioned in the welcome note. You can't grep for a thing nobody has named.

Start from the beginning if you landed here first: what an adaptive oracle actually changes. The homepage's interactive head-to-head is the fastest way to feel the difference without the math.

All notes