Skip to content

QEC: compile one magic-state distillation factory and connect logical T consumption #487

Description

@arniber21

What to build

Compile one explicitly selected magic-state distillation protocol into a verified neutral-atom factory schedule and connect its output capacity to the logical T/Tdag consumption model delivered by #283.

This is a tracer-bullet factory, not a general factory optimizer. The implementation should choose and document one protocol, represent its logical blocks and acceptance behavior, allocate a bounded factory region, schedule production and measurement dependencies, and prevent logical T consumption before a state is available.

Design review is required for the protocol, fidelity/resource assumptions, and the boundary between compiler-analytic estimates and sampled validation.

Acceptance criteria

  • An ADR selects the initial distillation protocol and records its input/output assumptions, rounds, failure handling, and evidence limits.
  • The QEC workload represents factory initialization, distillation operations, measurements, accepted output capacity, and consumption dependencies explicitly.
  • One logical T workload compiles through factory production and consumption into a physical neutral-atom schedule.
  • Scheduling prevents early/double consumption and reports factory stalls or insufficient capacity with actionable diagnostics.
  • Factory atoms, zones, duration, measurements, peak demand, throughput, and magic-state inventory appear in resource reports.
  • The emitted QEC experiment artifact distinguishes compiler structure from sampled logical-error evidence.
  • Final physical schedules pass movement, zone, measurement, reset/reuse, and dependency verification.
  • Tests cover successful production/consumption, insufficient capacity, rejected/failed production metadata, and deterministic serialization.
  • Documentation explicitly avoids a threshold, calibrated-fidelity, or production-hardware claim.

Out of scope

  • Choosing the globally optimal distillation protocol.
  • General multi-factory placement and routing.
  • Hardware pulse generation or a real-time decoder.

Blocked by

None - can start after design review; #283 already delivered explicit logical T/Tdag/CCZ consumption metadata.

Related

Metadata

Metadata

Assignees

No one assigned

    Labels

    backendGeneral backend / compilation pipeline (not NA- or IBM-specific)compilerFrontend / MLIR passes, type system, language semanticsenhancementNew feature or requestneutral-atomNeutral-atom backend target (quon_na, quantum.na, AOD/schedule)ready-for-humanRequires human implementationresearchResearch or design exploration, not a straight implementation ticket

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions