Provides guidance for decoding Stim-derived detector models and sampled trajectories with ldpc-based baseline decoders, starting with a narrow BPOSD lane and explicit compatibility checks.
Use this skill when a task needs a concrete baseline decoding workflow over registered QEC artifacts:
DetectorModelBundle plus matching TrajectoryBundle,Use this skill for the initial decoder lane when the workflow is:
Stim detector models,ldpc parity-check view,Prefer future lomatching, mle-decoder, or benchmark workflows when the task needs correlated decoding, exact baselines, richer runtime comparisons, or multi-decoder sweeps.
Prefer when the main problem is backend selection across graphlike matching, color-code, hypergraph, erasure-aware, or search-based decoder families.
choosing-qec-decodersDo not describe this lane as "the decoder abstraction" for the whole repo. It is the first executable decoder slice, not the universal decoder interface.
Expected inputs:
DetectorModelBundle,TrajectoryBundle,Expected outputs:
DecoderResult.Assumptions to make explicit:
research-state.yaml and confirm the current decoder-lane assumptions.servers/contracts/qec_decoders_mcp.yaml for the intended tool surface.DecoderResult artifacts instead of returning shot-level payloads inline.Before closing work:
ldpc baseline lane, not a repo-wide decoder truth.Problem: the detector-model and trajectory bundles do not share the same source circuit.
Fix: stop and rebuild one of the inputs instead of decoding across incompatible artifacts.
Problem: the decode path silently assumes graphlike detector-model structure.
Fix: record whether undecomposed hyperedges are allowed and keep the default strict unless the task explicitly needs otherwise.
Problem: one successful BPOSD run gets described like a full decoder evaluation pipeline.
Fix: keep the summary narrow and record what still needs a benchmark lane, transport binding, or multi-decoder comparison.