Skip to content

NA loss recovery: compile one detected-loss reload-and-resume sequence #497

Description

@arniber21

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

  • The target model can declare atom reservoirs/reload zones, capacities, preparation time, and allowed transfer paths.
  • quantum.na/execution semantics represent atom-presence or loss-detection results, replacement initialization, role remapping, and resume/fail decisions explicitly.
  • One checked-in workload compiles a deterministic detected-loss branch through reload and continuation.
  • Scheduling respects readout/detection latency, reservoir capacity, zone constraints, movement legality, initialization, and classical dependencies.
  • The verifier rejects reuse of a lost atom, uninitialized replacement atoms, duplicate role ownership, illegal reservoir movement, and resume before remapping completes.
  • Reports distinguish analytic expected loss from observed/injected loss events and account for reload atoms, moves, transfers, latency, retries, and peak capacity.
  • Tests cover successful ancilla replacement, empty reservoir, unrecoverable data loss, repeated loss beyond policy, and deterministic no-loss execution.
  • The execution package/reference interpreter can exercise both no-loss and injected-loss branches.
  • Documentation states that this is compiler recovery scheduling, not a physical loss-detector or QEC threshold claim.

Out of scope

  • General optimal online remapping under arbitrary simultaneous losses.
  • Physical loss-detection pulse/camera implementation.
  • Statistical Monte Carlo validation of the analytic model.

Blocked by

Related

Metadata

Metadata

Assignees

No one assigned

    Labels

    backendGeneral backend / compilation pipeline (not NA- or IBM-specific)enhancementNew 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