Quantum Error-Correction Proof Packets

Status

This page reports a bounded Project Telos preflight, not a quantum hardware claim. The evidence label is QEC_STABILIZER_FIXTURE_MATCH: a deterministic 3-qubit bit-flip repetition-code fixture declares logical states, stabilizers, syndrome bits, correction map, supported error model, and negative controls.

Fixture

Code

three_qubit_bit_flip_repetition_code, with logical states 000 and 111.

Stabilizers

Z0Z1 and Z1Z2.

Syndromes

MATCH. No-error and single Pauli-X errors recover the logical basis state for logical 0 and 1.

Rejected controls

Double-X error, phase error, missing stabilizer measurement, wrong syndrome map, and non-codeword input are rejected or marked UNVERIFIABLE.

Non-claims

No surface-code decoder, no hardware QEC, no fault-tolerant computation, no quantum advantage, no cryptographic security, and no BuildLang/buildc-native runtime receipt yet.

Why this matters

Quantum-computing claims are dense with hidden assumptions: code, gate set, error model, syndrome extraction, decoder, logical operator, noise model, resource estimate, hardware assumption, and classical baseline. A serious claim needs those assumptions carried as data, not buried in prose.

The current artifact is intentionally small. Its job is to prove the packet shape before stronger quantum claims are attempted.

Source leads

Surface and topological decoding

2605.17156v2 and 2512.07737v2 are metadata-only source leads.

Syndrome decoding

2207.05942v2, 2102.01984v1, and 2409.01440v3 pressure decoder and noise-model requirements.

Foundations

quant-ph/0602157v1 and 1810.01029v1 pressure code and simulation fields.

Hardware and compilation

Cat-qubit, atom-loss, and fault-tolerant circuit rows are source leads only; they do not promote hardware or compiler claims.

Algorithms and QML

Algorithm and hybrid-QML rows are requirements pressure for resource-estimation and advantage non-claim gates.

Toolchain map

Gather

Captures QEC, decoder, compiler, hardware, benchmark, and resource-estimation source receipts.

Index

Packages circuit specs, stabilizer tables, code distance, logical operators, decoder configs, and source refs.

Forum

Routes quantum claims through physics, formal methods, compiler, hardware, and verification lanes.

Crucible

Rejects quantum claims without supported error model, code distance, syndrome table, decoder verdicts, and negative controls.

Learn

Turns packets into exercises about stabilizers, syndromes, logical errors, unsupported error models, and overclaim boundaries.

BuildLang/buildc

Target runtime for typed Pauli operators, stabilizer groups, circuit IR, decoders, and resource estimates.

Telos

Binds source, circuit/code state, decoder output, verdict, and learning receipts into one proof-carrying packet.

Receipts

• Source ledger: demo/research/quantum-error-correction-source-receipts.json.
• Fixture CLI: demo/quantum-error-correction-proof-packet.mjs.
• Fixture output: quantum-error-correction-proof-packet-2026-07-02.json.
• Crucible verdict: MATCH 3 / DRIFT 0 / UNVERIFIABLE 0.
• Crucible run hash: 3d46985ec81ed6330bd38ee87f05a93814503dca286a74d2718ce02e24cca438.
• Crucible report hash: 1612e3007d41bde5f106aa2b4c99156ad0af131abf10a362315040080ee01872.
• Learn verdict: VERIFIED.
• Learn witness: 3093cea9b0746b052dba844a6745cdba1d11ae836be5468503af41f93c4702f3.

Next promotion target

The next public demo should be a BuildLang/buildc typed Pauli/stabilizer runtime for the same 3-qubit fixture, followed by a small surface-code syndrome fixture and a Clifford-circuit equivalence checker.

source receipts
-> typed Pauli operators
-> stabilizer code
-> syndrome table
-> correction map
-> negative controls
-> Crucible verdict
-> Learn prooflesson

Do not infer

• Do not infer that Telos implemented a surface-code decoder.
• Do not infer that the fixture proves hardware-level quantum error correction.
• Do not infer that the fixture establishes fault-tolerant quantum computing.
• Do not infer that the fixture validates quantum advantage or resource estimates.
• Do not infer that BuildLang/buildc already executes this quantum runtime.