2.1. Dataset and Prediction
Context
We used real indoor air-quality duplicate-sensor monitoring data organized as a forecasting dataset with a 30-minute window stride and a one-hour prediction horizon. The prediction task was binary event-onset forecasting: for each eligible time window, the response variable indicated whether a new air-quality event started within the next hour. In the repository, this target is recorded as event_onset_next_1h; in the frozen hardware subset, the corresponding column is y_event_onset_next_1h. Rows were eligible when this onset target was non-missing and the upstream future-label quality flag label_valid_1h was true. This flag is defined in the parent dataset builder and is not carried into the frozen-subset table (whose retained target column is y_event_onset_next_1h). In the parent dataset builder, event_onset_next_1h is assigned only to windows with event_now = 0. Together, the two eligibility conditions therefore exclude windows with an already active event and windows with invalid or boundary-purged future labels.
The parent event-onset dataset used a time-aware train/validation/external-test split. For the event_onset_next_1h target with the compact F_quantum_4 representation, the repository records 1,163 valid training rows, 471 validation rows, and 931 external-test rows, with 237, 124, and 213 positive cases, respectively. These full-split counts are reported only to define the prediction context; the quantum-hardware analysis described here was restricted to a pre-authorized frozen subset, described separately below.
The associated statevector reference metadata records the frozen subset as 16 training observation windows and 8 test observation windows. For this subset, the repository records 300 unique unordered kernel evaluations, including diagonal terms and 276 unique off-diagonal pairs. These counts define the hardware-kernel evaluation scope for the ZZ4 pilot.
The feature set was F_quantum_4, comprising four one-hour pollutant summary features: pm25_mean_last_1h, pm10_mean_last_1h, hcho_mean_last_1h, and tvoc_mean_last_1h. These inputs were processed under the repository’s train-only preprocessing policy: missing values were imputed from the training data, features were min-max scaled to , and values outside the training range in later splits were clipped.
The kernel used for the frozen subset was ZZ4, defined as a four-feature ZZ feature map applied to the scaled F_quantum_4 inputs. The statevector reference kernel was the squared-overlap quantum kernel [3,4], [11]. Accordingly, this experiment was framed as a statevector-to-hardware kernel-geometry distortion and survival analysis, not as a test of quantum advantage or hardware classifier superiority [8].
Reproducibility and artifact grounding. The public Wave 1 repository is available at a fixed commit (github.com/rsipakov/iaq-quantum-kernel-wave1-reproducibility, commit 6d14bca984486509b40850372f373c3499843dbc, release tag v1.2-wave1-manuscript); a permanent archival snapshot of this release is deposited at Zenodo (DOI 10.5281/zenodo.21332398). The repository is an artifact-level reproducibility package for the frozen ZZ4 hardware analysis. It contains the frozen subset, the statevector reference, the raw and reconstructed IBM Quantum result artifacts, and the audit and analysis scripts that reproduce the reported reconstruction, distortion, uncertainty, and shot-noise diagnostics. It does not rebuild the full upstream IAQ dataset and does not re-submit IBM Quantum jobs. The original numbered execution scripts retained in the repository are archival records from the source execution environment. They are not the supported reproduction path for the flat public package. Supplementary Note S1 provides the consolidated section-to-artifact map, including file paths, scripts, and checksum coverage for the Methods Sections 2.1–2.13 and the per-section artifact grounding for the Results Sections 3.1–3.7.
2.2. Frozen Subset
We selected a subset of observation windows from the duplicate-sensor indoor air-quality monitoring dataset and froze it before IBM hardware execution was authorized. Each window provides one scaled four-dimensional F_quantum_4 feature vector as input to the ZZ4 kernel. The subset, inclusion criteria, and acceptance thresholds used for compile-gate and stability checks were pre-specified and recorded in the freeze and execution artifacts; they were not modified after hardware results were obtained.
At the row level, the frozen subset comprises 16 training and 8 test windows drawn from the parent time-aware splits, balanced by construction in the signed labels (12 event-onset and 12 non-onset windows; 8 of 16 training and 4 of 8 test windows positive). The 24 windows span 2024-12-22 to 2026-04-20, with a median spacing of days between consecutive windows. Only two consecutive pairs lie 30 minutes apart, so at most two pairs of one-hour summary windows overlap in raw data. The full per-window ledger (row order, window end, split, and label) is reported in Supplementary Table S2.9. Dated, checksum-locked artifacts precede job creation (2026-05-09 08:42:04 UTC). The subset-stability record (05:35 UTC) set informal acceptance bands for the statevector effective rank () and uncentered alignment (), logged that both bands held across seven permutation seeds, and recorded that no alternative balanced subsets were evaluated. The scope-lock and authorization records (08:33 UTC) fixed the subset, kernel, feature set, and regimes. The public package records the resulting frozen rows and these dated freeze artifacts; it does not include the drawing procedure’s candidate-pool enumeration or selection seed.
Within the current pre-authorized scope, the frozen subset is not an adjustable analysis input. We did not add, remove, replace, reorder, or reweight any observation window after hardware execution authorization. This restriction applies in all cases: missing data, intermediate model behavior, hardware results, kernel distortion, diagnostic outcomes, reviewer preference, or downstream performance.
The current Wave 1 decision record states STOP_AFTER_WAVE1_REPORT_RESULTS. It allows only the frozen subset, blocks subset changes and threshold relaxation within the v9 scope, and requires a new decision record for any Wave 2 execution. The results reported here, therefore, apply only to this pre-authorized ZZ4 hardware pilot.
Extensions to additional regimes, sentinel-only follow-up runs, or larger subsets fall outside the present scope unless authorized by a new decision record, and may not retroactively alter the frozen subset, thresholds, or claims.
2.3. ZZ4 Quantum Feature
Map
The quantum-kernel component of the hardware pilot used a fixed four-dimensional, second-order Pauli-
Z (ZZ) feature map, denoted ZZ4. Its input was the train-only scaled
F_quantum_4 vector introduced above,
whose four components correspond, in this order, to
pm25_mean_last_1h,
pm10_mean_last_1h,
hcho_mean_last_1h and
tvoc_mean_last_1h. The tilde emphasizes that these are not raw pollutant readings but imputed, min-max scaled, and clipped values produced under the training-split preprocessing policy. No reliability, momentum, missingness, lag, or metadata features were supplied to ZZ4 in the hardware run.
Circuit definition. ZZ4 was implemented as Qiskit’s ZZFeatureMap on four qubits, one per feature. For an input vector
the circuit prepares
where
consists of two repetitions, each a layer of Hadamard gates followed by a data-encoding layer of single- and two-qubit
Z rotations. In the Qiskit ZZFeatureMap convention used here [3], the data map combines first-order terms
on qubit
k with second-order terms
on coupled pairs
, and the implementation used the default Qiskit scaling,
. Entanglement is linear (nearest-neighbor): only the adjacent feature qubits
carry ZZ couplings, so the map is not all-to-all. The configuration (feature dimension 4, linear entanglement, two repetitions,
) was fixed before hardware execution and was not re-tuned after observing statevector or IBM hardware outputs. The same configuration defines both the statevector reference and the hardware fidelity circuits; the hardware kernels are therefore empirical reconstructions of one fixed geometry, not separately parameterized kernels.
Statevector reference. The statevector reference kernel was the exact squared-fidelity kernel induced by this map,
For the frozen subset, this reference was computed for the 16 training windows, the 8 test windows, and the combined () set; the combined matrix served as the geometry baseline for the hardware distortion analysis. By construction, the statevector diagonal equals unity up to numerical precision. The hardware diagonal was retained as measured rather than forced to one. In the reported compiled artifacts, diagonal compute–uncompute circuits reduce to terminal measurement-only circuits; therefore, these entries primarily reflect preparation/reset, readout, and finite-shot effects rather than feature-map gate errors.
Hardware estimator. Each hardware kernel entry was estimated with a direct (compute–uncompute) fidelity circuit. For each pair
the operator
was applied to
and all four qubits were measured. In the noiseless limit, the probability of the all-zero outcome equals the squared overlap,
On IBM Quantum hardware, this probability was estimated from
SamplerV2 counts by the finite-shot estimator
where
denotes the pre-authorized execution regime,
is the observed all-zero count and
the observed shot count for the corresponding circuit. In an idealized fully depolarized four-qubit output distribution, the all-zero probability would approach the uniform floor
. Real hardware noise and finite-shot sampling do not follow this model exactly, but the limit illustrates why compute–uncompute kernel entries can develop a nonzero background and why noise drives measured overlaps toward a common value [6], [7]. We therefore interpret effective-rank and alignment changes as diagnostics of hardware distortion rather than as evidence of improved classification geometry.
The reported artifacts used a budget-safe execution with 1024 submitted shots per circuit for H0, H1, and H2, rather than the originally planned 4096. This shot count affects the statistical precision of but not the definition of the ZZ4 map or of the statevector reference kernel.
Matrix assembly. The frozen subset contains
observation windows, so the unordered pair inventory, including diagonal pairs, contains
ZZ4 kernel evaluations. These 300 pairs were evaluated in each of the three regimes, yielding 900 circuit–regime configurations. These are not 900 distinct logical circuit bodies: the regimes differ only in Sampler-level runtime options applied at execution time (
Section 2.5). In the executed runs, each unordered pair
with
was measured exactly once, with no directed or replicated observations. Symmetrization therefore reduced to mirroring the measured upper triangle,
, and the averaging rule for replicated entries was not used. Retrieved
SamplerV2 outputs were mapped back to the preserved circuit index, converted to all-zero probabilities, and assembled into one
hardware kernel matrix
per regime. The diagonal was not forced to one; it followed the measured-diagonal policy. We applied positive-semidefinite projection only as a diagnostic calculation and kept the uncorrected minimum eigenvalue in the metadata.
We thus treated the ZZ4 hardware kernels as empirical reconstructions of the same feature-map geometry defined by the statevector reference, not as separate learned kernels. The analysis endpoint was kernel survival and hardware-induced geometric distortion relative to . Accordingly, the ZZ4 pilot design does not support claims of quantum advantage, hardware classifier superiority, or readiness of the separate RMA feature-map family for hardware execution.
2.5. IBM Quantum Hardware
Protocol
Backend and primitive. The pilot was executed on the IBM Quantum backend ibm_fez, selected before submission from the pre-authorized candidate set {ibm_fez, ibm_marrakesh, ibm_kingston} under the rule that the package-selected backend is retained unless the live-metadata gate fails. A live snapshot taken immediately before submission identified ibm_fez as a 156-qubit, version-2 device reported operational, and the backend passed the live-metadata gate with no scope drift detected. The snapshot captured an operation set including cz, rz, sx, and x, together with a sampling period . The compiled circuits used cz as the recorded two-qubit operation after transpilation. Circuits were executed with the SamplerV2 sampler primitive of the Qiskit Runtime primitives framework [33] (Qiskit 2.4.1, qiskit-ibm-runtime 0.46.1) in backend job mode rather than in a Runtime session, so no session identifier is recorded for the three jobs.
Circuit construction and compilation. The submitted PUBs were the compute–uncompute fidelity circuits defined in
Section 2.3. The 300 pair-dependent logical circuit bodies were shared across regimes. The 900 inventory rows represent circuit–regime configurations, not 900 independently designed logical circuits, because dynamical decoupling and twirling are applied by the primitive at execution time rather than embedded in the submitted circuits. We confirmed the compile metrics by transpiling to
ibm_fez before submission. The post-transpilation values are a maximum compiled depth of 102, a maximum two-qubit-gate count of 22, and at most four active data qubits, with the circuits laid out on the 156-qubit device. The resource gate passed for every configuration. The frozen metadata artifacts store these resource metrics, the operation set, the sampling period, and the SDK versions. They do not include the physical-qubit layout, the transpilation seed, or a contemporaneous per-qubit calibration table (the archival submission script records
optimization_level=1). The archived circuit file (
circuits/zz4_wave1_circuits.qpy) preserves the 900 logical pair circuits rather than the compiled ISA circuits, so those execution-level details are recoverable only from the IBM Quantum job records (job identifiers in
Section 3.1), where account access allows.
Mitigation regimes. Three Sampler-level regimes were defined. The per-regime runtime-option records were SHA-256 locked, and the digests match across the runtime-options, backend-snapshot, and job-manifest artifacts. Regime H0 is the unmitigated baseline (dynamical decoupling off; gate and measurement twirling off). Regime H1 enables dynamical decoupling only [22], using an XX sequence with alap scheduling and middle extra-slack distribution, and no twirling. Regime H2 enables gate (Pauli) twirling only [24], with dynamical decoupling and measurement twirling off and the active-accum accumulation strategy. The auto randomization setting resolved at execution to 16 randomizations per circuit for all H2 PUBs. This pilot did not combine dynamical decoupling and gate twirling.
Shot budget. The locked plan specified 4096 shots per circuit. The reported execution used a budget-safe override of 1024 submitted shots per circuit for every regime, which affects only finite-shot precision and not the definitions of
Section 2.3. The retrieved counts confirm exactly 1024 observed shots per circuit in all three regimes. For the twirled regime
H2, the raw result metadata records 16 randomizations and 1024 observed shots per PUB (64 shots per randomization if allocated evenly). The analysis used the pooled 1024-shot count and did not model between-randomization variability. As a finite-shot reference, the per-entry binomial plug-in shot-noise scale is
This is a shot-noise scale, not a hardware-noise model, and it was not used as an uncertainty model in the present analysis. For H2, the shots are pooled across randomizations, so this expression does not capture between-randomization variability. Per-randomization counts were not persisted and cannot be recovered from the pooled counts, so the H2 dispersion across randomizations remains unquantified beyond this pooled binomial scale.
Submission and retrieval. We submitted one backend-mode job per regime, each covering all 300 pair circuits: d7vf6n3ack5s73bfc0eg (H0), d7vf8ocinasc738u1bhg (H1), and d7vfbsfmrars73d84u20 (H2). All three jobs completed with status DONE. The retrieval manifest records 300 PUB results per regime with no retrieval failure: 900 retrieved circuit–regime configurations in total.
Persisted artifacts. For each PUB, the raw result artifacts preserve the full count dictionary, the observed shot count, the regime label, the circuit-inventory and pair identifiers, the pair-inventory row, the kernel coordinates , and, for H2, the realized randomization count. The derived long-form table records, per regime and pair, the all-zero bit string, the all-zero count, the observed shots, and the raw finite-shot kernel value; the kernel manifest records one complete matrix per regime with no missing entries, the measured-diagonal policy, and positive-semidefinite metadata recorded for diagnostics only. The protocol thus produced three empirical ZZ4 reconstructions (H0, H1, and H2) of one fixed feature-map geometry. No RMA-family execution, Wave 2 execution, subset modification, or threshold relaxation was part of this protocol.
2.7. Kernel Reconstruction
Kernel reconstruction took place after IBM Quantum job retrieval and left the frozen subset, the pair inventory, the execution configurations, and the circuit definitions unchanged. For each artifact regime
, corresponding respectively to manuscript configurations
,
, and
, the retrieved
SamplerV2 payload contained 300 PUB results, one per frozen-subset pair (
Section 2.4).
The finite-shot estimator and the all-zero readout convention are defined in
Section 2.3. This section covers only the conversion of retrieved counts into matrix-valued kernels. As an operational definition, the empirical entry for the PUB at order
q in regime
r was formed from the raw count dictionary
and the observed shot count
as
The all-zero outcome was stored under the literal field all_zero_key with value 0000. Count keys were whitespace-normalized before matching the all-zero key, although this normalization was inert for the four-qubit single-register circuits. The observed shot count was read from each PUB; all reconstructed entries had 1024 observed shots.
Coordinates were recovered through the preserved circuit-index ledger, which maps each PUB order q to a unique upper-triangular pair . Each retrieved PUB also carried the coordinate and pair identifiers in its result metadata. An independent reconstruction audit (scripts/08b_audit_kernel_reconstruction.py; metadata/zz4_wave1_kernel_reconstruction _audit.json) checked these redundant identifiers against the circuit-index row at the same PUB order and found no coordinate or pair-identifier mismatch across all 900 retrieved circuit–regime configurations.
Reconstruction produced one long-form table (hardware_kernels/zz4_wave1_kernel_entries _long.csv) with one row per retrieved circuit–regime configuration (900 rows), recording the artifact regime, PUB order, circuit-inventory identifier, pair identifier, coordinates , all_zero_key, all-zero count, observed shots, and kernel_value_raw. This table provides the auditable link between the raw SamplerV2 count dictionaries and the matrix-valued hardware kernels.
Entries were accumulated by ordered coordinate under the symmetrization policy recorded in the kernel manifest as
average_duplicate_entries_then_mirror. Under this policy, duplicate observations of the same ordered
are averaged, directed entries
and
are averaged where both are present, and the result is mirrored. In the present execution, each unordered upper-triangular pair was measured exactly once and the lower triangle was unpopulated, so both averaging steps were inactive and symmetrization reduced to mirroring,
Diagonal entries were reconstructed from the same measured all-zero probabilities as off-diagonal entries and retained under the measured-diagonal policy, rather than overwritten by the noiseless value one. As a reconstruction quality check recorded in the audit artifact, the mean measured diagonal values were , , and for , , and , respectively. These values confirm that the diagonal entries are empirical hardware estimates, not imposed unit entries.
The final matrices were stored as CSV and NumPy arrays. The kernel manifest reports all three matrices present, each with 576 finite entries and no missing entries; no non-finite reconstructed entry was recorded.
Positive-semidefinite diagnostics were computed by a fixed routine. The routine applies a missing-value guard (inactive here, since all entries were finite), numerically symmetrizes the matrix, and computes its eigenvalues. Negative eigenvalues are clipped for diagnostic reporting only, and the uncorrected minimum eigenvalue is retained. All three uncorrected minima were positive, and the eigenvalue-clipping correction was numerically negligible:
Table 2.
Kernel-reconstruction PSD diagnostics. The Frobenius-norm correction values are kernel-manifest diagnostics, interpreted only at roundoff order of magnitude. The PSD conclusion rests on the positive uncorrected minimum eigenvalues.
Table 2.
Kernel-reconstruction PSD diagnostics. The Frobenius-norm correction values are kernel-manifest diagnostics, interpreted only at roundoff order of magnitude. The PSD conclusion rests on the positive uncorrected minimum eigenvalues.
| Configuration |
Regime |
Finite |
Missing |
before clip |
after clip |
PSD Frobenius (abs / rel) |
| M0 |
H0 |
576 |
0 |
|
|
|
| M1 |
H1 |
576 |
0 |
|
|
|
| M2 |
H2 |
576 |
0 |
|
|
|
Every uncorrected minimum eigenvalue is positive (Table 2), so the eigenvalue clip is inert and the PSD conclusion does not rest on the correction magnitudes. The PSD-correction Frobenius norms in Table 2 sit at the double-precision (float64) roundoff scale (); the order of magnitude is the reproducible content, and the last reported digits may depend on the BLAS/LAPACK backend used for the eigendecomposition.
For reference, the statevector kernel had ; comparative spectral interpretation is reported with the hardware-distortion results. Positive-semidefinite projection was therefore not used to replace any reported kernel. The unprojected measured-diagonal matrices remained the hardware kernels used in the subsequent distortion analysis.
2.8. Geometry and Distortion
Metrics
The distortion analysis compares each measured hardware kernel with the fixed statevector reference kernel of
Section 2.3. Let
denote the statevector ZZ4 kernel and let
denote the measured hardware kernel for manuscript configuration
, using the artifact-label alias of
Section 2.6. This subsection defines the metrics. Their values are reported in
Section 3.2.
Metric domains. Two metric families act on different parts of the kernel. The scalar agreement and entrywise-error metrics are evaluated on the off-diagonal set
so the measured diagonal does not enter these statistics. The matrix-level geometry metrics (CKA, effective rank, and centered KTA) are instead evaluated on the full symmetric
matrix and therefore include the measured, non-unit hardware diagonal. This domain split determines how each number should be read. The off-diagonal statistics capture the nontrivial pairwise-overlap geometry while still carrying hardware readout and finite-shot effects. The full-matrix statistics additionally fold in the diagonal background. The implementation uses the symmetric full off-diagonal mask
. Because the reconstructed matrices are symmetric, this duplicate-weighted representation of the 276 unique unordered off-diagonal pairs (
Section 2.1, 2.4) reproduces the descriptive correlations, the mean, median, and maximum absolute errors, the root-mean-squared error, and the off-diagonal variance that one copy of each pair would give. The directed and unique-pair representations agree to float64 machine precision. The correlation-test
p-value columns (
offdiag_spearman_pvalue,
offdiag_pearson_pvalue) are retained for schema compatibility but left unpopulated and are not used for any claim (rationale in
Section 2.13).
Rank-order and linear agreement. Rank-order preservation is quantified by the Spearman correlation between the off-diagonal entries of the statevector and hardware kernels, and linear agreement by the Pearson correlation,
Entrywise distortion. Entrywise distortion is summarized by the mean absolute error, root-mean-squared error, median absolute error, and maximum absolute error,
and the change in geometric spread by the off-diagonal variance difference
.
Spectral geometry. Spectral geometry is summarized by the effective rank. For a symmetric kernel
K with eigenvalues clipped at zero for this diagnostic only,
Alignment geometry. Global matrix-shape preservation is measured by CKA [27] and label geometry by the centered KTA [28], both with the centering matrix
and binary labels mapped to
,
:
Because both arguments of each alignment are double-centered, the reported is the Cortes-type centered alignment and is numerically identical to : CKA and KTA are the same functional evaluated against the statevector reference and against the label Gram matrix, respectively. The classical uncentered alignment is not used.
Diagonal and resampling policy. Because CKA, effective rank, and centered KTA retain the measured hardware diagonal, their sensitivity to the diagonal convention is assessed by recomputing with the diagonal forced to unity. That check still retains the diagonal component common to both kernels, so a diagonal-excluded (U-centered) CKA computed from the HSIC
1 estimator [34] is also reported (
Section 2.13, revision additions). These are sensitivity checks only, and the reported kernels retain the measured diagonal (values in
Section 3.2). Configuration differences in geometry preservation are assessed with the leave-one-window-out jackknife defined in
Section 2.13, which treats the
frozen windows as the resampling unit rather than the dependent off-diagonal entries. All metrics are post-reconstruction summaries of the three measured kernels; no threshold, subset membership, circuit definition, or reconstruction rule was changed during the distortion analysis, and the metrics were not used as optimization criteria.
2.12. Shot-Noise Reference-Scale
Decomposition
This subsection defines a post-reconstruction diagnostic that measures the off-diagonal hardware–statevector RMSE against a finite-shot reference scale. The calculation does not modify any kernel entry, subset member, circuit, backend choice, execution configuration, threshold, or claim boundary. The analysis is performed on the off-diagonal domain
of
Section 2.8 (
), so the measured diagonal does not enter. The resulting decompositions are reported in
Section 3.4.
Conservative global reference. As a single-number finite-shot reference at the executed shot count
, we use
denoted
rather than
to emphasize that it is not the sampling standard error of an individual kernel entry. In the persisted artifacts this quantity is recorded under the column
sigma_shot_global, retained under its original name. The compute–uncompute estimator
is a binomial estimator of the all-zero proportion (
Section 2.3), whose per-entry sampling standard error is bounded by
at
. The chosen reference exceeds this maximum per-entry binomial standard error by a factor of
; equivalently,
is twice the maximum per-entry shot variance
. It is therefore a deliberately conservative single-number variance-scale reference. It grants finite-shot sampling the maximal benefit of the doubt and is not the standard error of any one entry. For each artifact regime
r (manuscript configuration
m;
Section 2.6), the observed off-diagonal RMSE is decomposed in quadrature,
so the global shot share is a conservative upper reference for the finite-shot variance-scale contribution, not a probabilistic upper bound on the realized sampling error.
Matrix-aware plug-in reference. Because the reconstructed hardware probabilities are available, we also define an entry-resolved reference. For each off-diagonal reconstructed all-zero probability
, the per-entry binomial plug-in standard error is
which is the per-entry binomial plug-in scale
of
Section 2.5. The matrix-aware reference is its root mean square over
,
with
and the matrix-aware shot share defined by the same quadrature identity as above. Consistent with
Section 2.5, this plug-in is used only as a descriptive magnitude reference and not as an uncertainty or confidence-interval model; because the reconstructed matrices are symmetric, the directed off-diagonal average equals the average over the 276 unique unordered off-diagonal pairs.
Scope and caveats. Both decompositions are deterministic bookkeeping identities applied to the realized RMSE. They treat shot noise and residual hardware distortion as approximately separable in quadrature and are diagnostic, not a physical noise-model decomposition. Because
is a single-sample quantity that already contains one realization of finite-shot noise,
and
are point residuals rather than unbiased estimators of the systematic distortion. The matrix-aware variant is additionally a plug-in based on reconstructed rather than true probabilities; for the twirled
regime it uses the pooled 1024-shot all-zero probability and does not model between-randomization variability (
Section 2.5).
2.13. Statistical Analysis
All statistical analyses were performed after the frozen subset, pair inventory, hardware execution records, and reconstructed kernels had been fixed. No observation window, pair, circuit, execution configuration, reconstruction rule, threshold, or claim boundary was changed during statistical analysis. This subsection defines the statistical policy and estimators; the resulting standard errors, contrasts, and the permutation-reference values are reported in
Section 3.2 and 3.3.
The statistical unit for uncertainty assessment is the frozen observation window. Individual kernel entries are not treated as independent observations, because entries sharing an index come from the same underlying sample and the reconstructed matrices are symmetric. Consequently the 552 directed off-diagonal entries and the 276 unique unordered off-diagonal pairs (
Section 2.1, 2.4, 2.8) are used as deterministic domains for point-estimate summaries, not as independent sampling units. The conventional correlation-test
p-values associated with the off-diagonal Spearman and Pearson statistics are not used for any claim; in the supported direct workflow the corresponding columns (
offdiag_spearman_pvalue,
offdiag_pearson_pvalue) are retained for schema compatibility and left blank.
Window-level jackknife. Window-level uncertainty is estimated by the leave-one-window-out jackknife [35]. Let
denote a scalar statistic for execution configuration
. For each omitted window
, the statevector kernel, the hardware kernel, and the label vector are restricted to the remaining
windows and the statistic is recomputed as
. The jackknife standard error is
For paired contrasts between configurations
a and
b, the point contrast is
and the leave-one-window-out replicates are
. The contrast-scale uncertainty
follows the same formula, applied to
, so the within-window covariance between configurations is retained rather than assumed. The descriptive contrast ratio reported in the jackknife tables is
This ratio is used only as a scale-free robustness diagnostic; it is not treated as a normal-theory test statistic, is not converted into a p-value, and does not define statistical significance. Because the Spearman rank statistic and the absolute-error metrics are non-smooth functionals of the kernel entries, the delete-one-window jackknife is interpreted as a descriptive finite-sample stability probe rather than as a consistent or unbiased variance estimator.
Scope of the persisted jackknife. The persisted window-level jackknife covers Spearman, Pearson, MAE, CKA, and centered KTA. Spearman, Pearson, and MAE are recomputed on the off-diagonal domain of each leave-one-window-out submatrix; CKA and centered KTA are recomputed on the full centered submatrices, retaining the measured-diagonal policy for the hardware kernels. Median and maximum absolute error, off-diagonal variance, and effective rank are reported as point estimates only — no window-level jackknife and no paired contrast is persisted for them — so no inferential comparison is reported for these quantities; this is one reason the median absolute error, for which the delete-one jackknife is least reliable, is not jackknifed. No jackknife for RMSE is persisted in the frozen package either; a leave-one-window-out RMSE probe with paired contrasts was added at revision (revision additions below; Supplementary Table S2.7) under the same deletion-sensitivity reading — RMSE is a smooth functional of the kernel entries, so the deletion probe is better behaved for it than for the rank-order and absolute-error metrics.
No bootstrap intervals. No entrywise-pair bootstrap confidence intervals are reported. A bootstrap that resamples off-diagonal entries or unordered pairs would ignore the dependence induced by shared sample indices and would understate uncertainty at the window scale. Uncertainty statements in this hardware analysis are therefore limited to leave-one-window-out jackknife standard errors and descriptive paired contrast ratios: the frozen-package persisted analyses and the explicitly post hoc U-centered CKA, RMSE, and probes described below.
Statevector label-permutation reference. A label-permutation analysis is used only as a statevector label-alignment reference, not as a hardware-configuration selection test. The frozen
labels are permuted and the ZZ4 statevector label alignment is evaluated with
permutations. For manuscript reporting,
scripts/09e_label_permutation_reference.py regenerates the reference in-package with a fixed reference seed. The script recomputes the observed alignment, regenerates the permutation null, and reports an explicit upper-tail probability
together with two named symmetric two-sided conventions,
(absolute deviation from the null mean) and
. The table follows the historical row labels: the
CKA row denotes the centered label alignment, which in manuscript notation is
whereas the companion
KTA row denotes the uncentered classical alignment retained for provenance. The historical source-derived table reports a single field
p_perm_two_sided, whose value corresponds numerically to the upper-tail exceedance probability rather than to a symmetric two-sided
p-value. The in-package regeneration therefore preserves the source field for provenance and removes the report-level ambiguity by explicitly naming
p_upper_tail,
p_two_sided_centered, and
p_two_sided_2min. No hardware-regime label-permutation
p-values for
,
, or
are persisted in the frozen package; per-regime references were added at revision (revision additions below;
Section 3.3.3). The observed-versus-null values and the conclusion are reported in
Section 3.3.
Multiple comparisons. The pre-specified paired hardware contrasts are , , and , reported as descriptive jackknife contrasts for Spearman, Pearson, MAE, CKA, and centered KTA only. Because no formal p-values are generated for these hardware contrasts, no Holm–Bonferroni correction is applied. The statevector permutation diagnostic is a single reference calculation and is not pooled with the descriptive hardware-contrast ratios into a family of confirmatory tests. The revision references below (per-regime permutation references, the resampling null, the split-preserving variant, and the comparator-kernel references) are likewise descriptive references reported without family-wise adjustment; none is used as a confirmatory test.
Recorded directional expectations E1–E4. The Results reference four directional expectations, E1–E4, recorded in the project’s research-question record, a manuscript-side document maintained alongside RQ1–RQ4; they are reproduced verbatim here.
E1. “The Wave 1 protocol is expected to yield complete, finite, auditable 24×24 hardware-kernel reconstructions for all three configurations. PSD diagnostics will be reported on the uncorrected measured matrices, and geometry comparisons will be performed without PSD correction if no correction is required. At least one configuration is expected to preserve centered statevector geometry at a high descriptive level while still showing nonzero entrywise distortion.”
E2. “Gate twirling is expected to show the lowest observed hardware-vs-statevector distortion, while dynamical decoupling alone is not expected to be robustly distinguishable from baseline at the N=24 leave-one-window-out scale. Because configurations were executed as single, non-interleaved jobs, any ordering is descriptive of these jobs on ibm_fez and not a causal estimate of mitigation efficacy.”
E3. “The observed RMSE is expected to exceed both finite-shot reference scales in every configuration, so residual hardware distortion—not finite-shot sampling alone—will dominate the discrepancy even for the best-preserving configuration. For the twirled configuration, the reference calculation does not capture between-randomization variability because the 1024 shots are pooled across 16 randomizations.”
E4. “The ZZ4 statevector kernel is not expected to align with the labels above the permutation reference; therefore, the experiment is not expected to support any IAQ forecasting claim. Any hardware KTA exceeding the statevector KTA will be interpreted as consistent with non-affine, label-correlated distortion rather than supervised improvement. This interpretation is algebraically motivated by the removal of affine/depolarizing components under centering, but it is not validated by a hardware-regime permutation null in Wave 1.”
Two transparency notes bound the status of this record. First, its wording refers to the realized execution (single non-interleaved jobs and 1024-shot pooling across 16 randomizations), so it is not an independently timestamped pre-execution registration. The expectations are accordingly cited in this manuscript as
recorded rather than as formally pre-registered. The independently dated, checksummed pre-execution artifacts of
Section 2.2 fix the subset, regimes, scope exclusions, and diagnostic bands, but they do not contain these directional statements. Second, E4’s recorded reading (“label-correlated”) predates the revision attribution of
Section 3.3.3, which identifies the uplift as normalization-associated, with the full-numerator decrease carried mainly by the measured diagonal, and E4’s final clause records the pre-revision absence of hardware-regime permutation references, which the revision adds.
Revision additions (post hoc). We added six diagnostics at manuscript revision in response to peer review. None is pre-specified, and none modifies a frozen artifact. All are computed from the released v1.2 package artifacts (the three hardware kernels, the statevector reference, the frozen labels, and the scaled inputs), deterministically or under fixed, documented seeds. (i) A diagonal-excluded (U-centered) CKA computed from the HSIC
1 estimator [34], reported alongside the unit-diagonal sensitivity because forcing the diagonal to one retains the diagonal component common to both kernels rather than removing it. HSIC
1 removes self-interaction terms through diagonal-zeroed Gram matrices, together with the U-statistic correction to the row-sum and normalization terms. The normalized ratio is reported as a descriptive diagonal-excluded variant, not as an unbiased estimator of a population CKA. The exact estimator is reproduced alongside Supplementary Table S2.5. (ii) A numerator–denominator attribution of the centered alignment: with balanced labels each
splits exactly into a numerator factor
and a normalization factor
(
Section 2.10, 2.11). (iii) A count-level finite-shot resampling reference: every kernel entry is resampled as an independent binomial proportion at the executed
shots around either the statevector probabilities (the no-hardware-distortion counterfactual) or the measured hardware probabilities, with
replicates. For
H2, both variants use the pooled 1024-shot probabilities and therefore do not identify the unpersisted between-randomization dispersion (
Section 2.5). (iv) Per-regime label-permutation references for the three hardware kernels, computed with the same
scheme as the statevector reference. These are label-alignment references, not configuration-contrast tests, and the policy above of reporting no formal hardware-contrast
p-values is unchanged. (v) A split-preserving permutation variant that permutes labels separately within the 16 training windows and within the 8 test windows, as an exchangeability robustness check on the otherwise unrestricted permutation scheme. (vi) Two classical comparator kernels on the same scaled inputs and labels (the linear kernel
, where the rows of
X are the
scaled feature vectors of
Section 2.3, and an RBF kernel
on the pairwise squared Euclidean distances
of those rows, at the median-heuristic bandwidth
with the median taken over the
unordered pairs), evaluated with the same centered alignment and permutation scheme. In addition, leave-one-window-out jackknives for U-centered CKA, RMSE, and the single-regime uplift
were computed under the deletion-sensitivity reading above. All revision quantities are reported in
Section 3.2–3.4 and Supplementary Tables S2.5–S2.9.
Interpretation boundary. We interpret all statistical outputs as fixed-subset, post-reconstruction diagnostics. They support statements about kernel-geometry survival, hardware-induced distortion, and window-level robustness at the frozen scale. They do not support claims of classifier accuracy, improved prediction, hardware classifier superiority, or quantum advantage.
Use of generative AI tools. Generative AI tools were used during the preparation of this paper: Claude (Anthropic) assisted with the preparation and quality review of the figure-rendering scripts and with readability editing and proofreading of the text; Perplexity was used to verify literature references; and OpenAI Codex was used for an independent audit of the public reproducibility package. These tools were not used to design the study, select or freeze the analysis subset, execute the hardware jobs, choose the statistical methodology, or produce any reported quantity. All reported quantities of the present analysis are generated by the persisted pipeline of the public reproducibility package and its revision-diagnostics release (
Section 2.1; Code availability; Supplementary Note S1) and can be regenerated from them independently of any AI assistance. All AI-assisted output was reviewed and verified by the author before incorporation.