QStrike · known gaps
Current public QStrike gaps: zero connected quantum hardware, no live-hardware execution, modeled provider profiles, no client-key break claim, and buyer-specific evidence kept out of public marketing.
OPEN · PUBLIC
The public runtime reports zero hardware-backed runs and no live provider hardware. QStrike currently uses provider-calibrated modeled runtime evidence.
Proof to change the status: A tracked release demonstrates connected hardware, provenance, authorization, and public truth language without exposing customer data.
BOUNDARY · PUBLIC
6 provider-aligned modeled profiles span four modalities and can represent up to 8 access services. Names identify model context—not submitted jobs, credentials, access agreements, or endorsement.
Proof to change the status: No closure is implied; this distinction remains mandatory even if future live execution is introduced.
OUT OF SCOPE
QStrike does not claim to break RSA-2048, ECC-256, or client keys. Its bounded Shor demonstration uses N=143 as the 25-qubit implementation target. Future-machine resource estimates are planning inputs, not demonstrated breaks.
Proof to change the status: This is a permanent claim boundary unless independently reproducible evidence changes the state of the art.
CONTROLLED
Public artifacts use synthetic targets or method excerpts. Buyer-specific findings, references, environment details, and commercial evidence remain in controlled diligence.
Proof to change the status: Only explicit customer authorization can change an individual disclosure boundary.
The tracked public CBOM, detached checksum, methodology, and integrity boundary are the public evidence surface. They describe a synthetic target and modeled runtime—not client evidence.