S1 Live Submission Preflight¶
Date created: 2026-05-06
This checklist is mandatory before wiring any live provider submitter for the S1 hybrid feedback job. It is deliberately manual because the final decision spends real QPU budget and changes the evidentiary status of the project.
Non-negotiable Rule¶
No S1 live job may be submitted unless every gate below is complete and recorded in a new session log. A dry-run package, capability probe, or valid credential is not sufficient by itself.
Required Artefacts¶
- [ ]
scpn-bench s1-feedback-readywas run immediately before submission. - [ ]
data/s1_feedback_loop/s1_feedback_preregistration_2026-05-06.jsonexists. - [ ]
data/s1_feedback_loop/s1_feedback_preregistration_2026-05-06.mdexists. - [ ]
data/s1_feedback_loop/s1_feedback_loop_latency_summary_2026-05-06.jsonexists. - [ ]
data/s1_feedback_loop/s1_feedback_analysis_summary_2026-05-06.jsonexists. - [ ] The hardware-job dossier embedded in the preregistration manifest was reviewed.
- [ ] The raw-count analysis schema was reviewed against the planned provider output.
Scientific Gates¶
- [ ] Purpose is unchanged: feedback-vs-matched-open-loop steering of
R_live. - [ ] Hypothesis is unchanged from the dossier.
- [ ] Falsification condition is unchanged from the dossier.
- [ ] Matched open-loop control arm is included.
- [ ] Positive, null, negative, and contradictory decision branches are accepted.
- [ ] Claim boundary is accepted: no quantum advantage, no backend-independent claim, no sub-microsecond feedback claim unless provider-side logic supports it.
Provider Capability Gates¶
- [ ] Live backend metadata was captured without submitting a job.
- [ ] Capability probe reports
readyfor the selected backend. - [ ] Backend supports required qubit count.
- [ ] Backend supports required shot count.
- [ ] Backend supports required circuit-batch count.
- [ ] Backend supports mid-circuit measurement.
- [ ] Backend supports conditional reset.
- [ ] Backend supports conditional control.
- [ ] Live transpilation was performed without submission.
- [ ] Live transpiled depth and operation counts were recorded.
- [ ] Transpiled payload still fits the scientific claim boundary.
Budget Gates¶
- [ ] Remaining QPU budget was checked.
- [ ] Requested S1 execution estimate was recorded.
- [ ] Queue/calibration uncertainty was recorded separately from execution estimate.
- [ ] Approval record
max_qpu_secondsis greater than or equal to the planned spend. - [ ] Approval record provider matches selected backend provider.
- [ ] Approval record package hash matches the exact preregistration manifest.
Data and Reproducibility Gates¶
- [ ] Raw-count output path was prepared.
- [ ] Job metadata path was prepared.
- [ ] SHA256 hashing plan was prepared.
- [ ] Analysis command was recorded:
python scripts/analyse_s1_feedback_hardware.py <raw-count-package.json>. - [ ] Failure handling was recorded: cancelled/failed jobs remain auditable until classified as superseded or resolved.
Approval Record¶
The live scheduler may only be wired after creating a HardwareApprovalRecord
with:
approved=True;- non-empty
approval_id; - named
approver; - exact preregistration package hash;
- selected provider;
- approved QPU-second ceiling;
- session-log reference in
notes.
Stop Conditions¶
Stop and do not submit if any of the following occurs:
- backend capability status is
blockedorunknown; - live transpilation changes the circuit beyond the preregistered claim boundary;
- matched open-loop control cannot be submitted in the same campaign;
- QPU budget approval is missing or lower than the planned spend;
- provider dry-run payload and live backend metadata disagree;
- raw-count archival path is not ready;
- session log cannot be written.
Post-run Requirement¶
Immediately after completion:
- write raw counts before analysis;
- write job IDs and backend metadata;
- hash raw-count files;
- run the preregistered analysis script;
- update the S1 session log and handover;
- do not alter the hypothesis or decision tree after seeing results.