A maturity map for public quantum-defense programs

Public programs often use broad language about research, resilience, or future capability. A maturity map keeps the discussion specific. Start at research: a laboratory effort may investigate a measurement method or component. A prototype may show an integrated design. A demonstration may show behavior in a defined environment. A procurement action may fund development or acquire a capability. Operational use requires public evidence of a system being employed for its intended mission, not merely described as relevant.

Ask for the setting

For each claimed test, identify who ran it, where it occurred, what system was measured, what the reference or baseline was, and which result was actually reported. A sensor reading is not necessarily navigation accuracy; a lab demonstration is not necessarily a field result.

Preserve the evidence gap

Many defense details are not public. That limitation should narrow an article, not invite conjecture. A responsible report can explain that an award exists and that performance details are unavailable without implying a hidden success or failure. The point of this map is not to rank programs. It is to help readers describe publicly documented maturity without converting intent into proof.