-
Notifications
You must be signed in to change notification settings - Fork 0
NA loss recovery: compile one detected-loss reload-and-resume sequence #497
Copy link
Copy link
Open
Labels
backendGeneral backend / compilation pipeline (not NA- or IBM-specific)General backend / compilation pipeline (not NA- or IBM-specific)enhancementNew 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)enhancementNew 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 detected atom-loss event into an explicit reservoir reload, replacement initialization, remapping, and verified resume sequence on a zoned neutral-atom target.
Issue #310 models analytic loss probability but deliberately excludes observed loss and replacement. This tracer bullet should introduce the minimum execution semantics necessary to react to a known loss without pretending to solve general online remapping: one workload reaches a detection point, receives a deterministic loss result, replaces the affected ancilla/data role according to a reviewed policy, and continues or fails safely.
Design review is required for atom identity versus logical role, branch semantics, and which losses are recoverable in the first slice.
Acceptance criteria
quantum.na/execution semantics represent atom-presence or loss-detection results, replacement initialization, role remapping, and resume/fail decisions explicitly.Out of scope
Blocked by
Related