-
Notifications
You must be signed in to change notification settings - Fork 0
QEC: compile one magic-state distillation factory and connect logical T consumption #487
Copy link
Copy link
Open
Labels
backendGeneral backend / compilation pipeline (not NA- or IBM-specific)General backend / compilation pipeline (not NA- or IBM-specific)compilerFrontend / MLIR passes, type system, language semanticsFrontend / MLIR passes, type system, language semanticsenhancementNew feature or requestNew feature or requestneutral-atomNeutral-atom backend target (quon_na, quantum.na, AOD/schedule)Neutral-atom backend target (quon_na, quantum.na, AOD/schedule)ready-for-humanRequires human implementationRequires human implementationresearchResearch or design exploration, not a straight implementation ticketResearch or design exploration, not a straight implementation ticket
Description
Metadata
Metadata
Assignees
Labels
backendGeneral backend / compilation pipeline (not NA- or IBM-specific)General backend / compilation pipeline (not NA- or IBM-specific)compilerFrontend / MLIR passes, type system, language semanticsFrontend / MLIR passes, type system, language semanticsenhancementNew feature or requestNew feature or requestneutral-atomNeutral-atom backend target (quon_na, quantum.na, AOD/schedule)Neutral-atom backend target (quon_na, quantum.na, AOD/schedule)ready-for-humanRequires human implementationRequires human implementationresearchResearch or design exploration, not a straight implementation ticketResearch or design exploration, not a straight implementation ticket
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
Out of scope
Blocked by
None - can start after design review; #283 already delivered explicit logical T/Tdag/CCZ consumption metadata.
Related