SPDX-License-Identifier: AGPL-3.0-or-later

Commercial license available

© Concepts 1996–2026 Miroslav Šotek. All rights reserved.

© Code 2020–2026 Miroslav Šotek. All rights reserved.

ORCID: 0009-0009-3560-0851

Contact: www.anulum.li | protoscience@anulum.li

scpn-quantum-control — Methodology and evidence governance

Methodology and Evidence Governance

This is the single entry point for the project's evidence-governance material. You do not need to read it to run the examples — start with Onboarding and the Example Gallery. Read this page when you need to understand what a result in this repository is allowed to claim and how a claim is promoted from simulation to hardware evidence. The deep registers, ledgers, and contracts are linked below rather than inlined, so each stays the authoritative source for its own scope.

Why this layer exists

A useful result here is not just a plot or a notebook output. It is a result with its inputs, code path, dependency context, claim class, and promotion rule recorded. The governance layer separates four altitudes of confidence so that a fast simulation result is never read as a hardware claim:

• simulation science — fast iteration on the statevector simulator;
• method verification — reproducible checks, classical baselines, and preregistered replay;
• hardware evidence — claims backed by raw-count artefacts on real devices;
• commercial readiness — stable facades, release gates, and deployment boundaries.

Higher-cost routes carry a higher evidence burden. The rest of this page is a map to where each rule and record lives.

Claim classes and boundaries

• Results & Claims — the claim matrix and what each class permits.
• Claim Boundary: SCPN/FIM — a worked claim boundary for one experiment family.
• Classical Irreproducibility — why classical references are part of the evidence, not a footnote.
• Licensing FAQ and Core Package Boundary — what is in scope for the stable surface versus the research workbench.

Hardware evidence

• Hardware Status Ledger — the promotion state of every hardware claim.
• Hardware Result Packs and the Release Checklist — the raw-count-backed artefacts and how they are promoted.
• IBM Guide — running on real devices.

Runtime contracts

• QPU Data Artifact — the typed, hash-bound input contract.
• Pipeline Runtime Contract and QPU Compute Unit.
• QPU Provider Readiness — fail-closed provider boundaries.

Validation protocols and readiness

• Protocol: SCPN/FIM Validation.
• Methods Benchmark Dashboard and the Classical Baselines they compare against.
• Campaign readiness indices: S1 Feedback, S1 Live Submission Preflight, Hybrid Feedback Loop S1, S2 Scaling, and S3 Design.