QStrike · known gaps
QStrike known gaps: public evidence states the execution boundary and keeps buyer-specific evidence out of marketing. Encryption is not directly broken.
OPEN · PUBLIC
Commercial quantum-cloud execution demonstrates a bounded side-channel path; it does not directly break encryption or make a universal production-key claim.
Proof to change the status: Evidence changes the bounded claim without exposing customer data
BOUNDARY · PUBLIC
real commercial quantum-cloud services span four modalities and can represent up to 8 access services. Names identify commercial access context — not customer 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 commercial quantum-cloud runtime — not client evidence.