Quantum systems will support regulated research, customer claims, security programs, and contractual services. When a result is challenged, the organization must produce records that are complete, interpretable, and defensible.
A histogram is not a computation record. It is only one artifact.
View diagram source
flowchart LR
Run[Quantum run] --> Records[Records]
Records --> Retention[Retention policy]
Records --> Audit[Audit request]
Records --> Discovery[Discovery request]
Audit --> Packet[Audit packet]
Discovery --> LegalReview[Legal review]Record classes
| Record class | Examples |
|---|---|
| workload | objective, contract, claim boundary |
| transformation | circuit hash, compiler version, optimization profile |
| execution | provider job, shots, queue timestamps, runtime options |
| physical context | target snapshot, calibration epoch, benchmark canary |
| governance | admission decision, approvals, policy bundle |
| interpretation | post-processing, statistics, reviewer decision |
View diagram source
flowchart TB
Result[Result] --> Execution[Execution context]
Execution --> Transformation[Transformation lineage]
Transformation --> Physical[Physical context]
Physical --> Governance[Governance records]
Governance --> Interpretation[Interpretation records]
Interpretation --> Defensible[Defensible record]Legal hold
A legal hold freezes deletion or alteration of relevant records.
View diagram source
sequenceDiagram
participant Legal
participant Records
participant Broker
participant Archive
participant Provider
Legal->>Records: issue hold scope
Records->>Broker: freeze matching workload records
Records->>Archive: lock evidence packages
Records->>Provider: request preservation if available
Provider-->>Records: preservation confirmationThe scope should include workload IDs, claim IDs, incident IDs, provider job IDs, customer IDs, target IDs, and time windows.
Audit packets
Audit packets should be generated from structured records, not screenshots. OSCAL can help represent control and assessment information, while NIST SP 800-53 supplies a common control vocabulary. [R169] [R170]
View diagram source
flowchart LR
Scope[Audit scope] --> Query[Record query]
Query --> Builder[Packet builder]
Builder --> Controls[Control mapping]
Builder --> Evidence[Evidence artifacts]
Builder --> Exceptions[Exceptions]
Controls --> Reviewer[Reviewer]
Evidence --> Reviewer
Exceptions --> ReviewerIntegrity and chain of custody
View diagram source
flowchart TB
Artifact[Artifact] --> Hash[Hash]
Hash --> Manifest[Manifest]
Manifest --> Signature[Signature]
Signature --> Archive[Immutable archive]
Archive --> Verification[Verification]Verifiable credentials and attestations can express issuer-backed claims and evidence relationships. They help most when combined with retention, access control, and clear review authority. [R176] [R178]
Retention classes
| Class | Examples |
|---|---|
| ephemeral | failed exploratory simulator runs |
| standard | internal benchmark results |
| extended | claim-grade evidence |
| hold | incident, dispute, legal, or audit scope |
| regulated | jurisdiction- or customer-specific records |
View diagram source
stateDiagram-v2
[*] --> Created
Created --> Active
Active --> Archived
Active --> Hold
Hold --> Archived
Archived --> DeletedAudit-readiness questions
A platform is audit-ready when it can answer:
- Which workloads produced this claim?
- Which policies allowed those workloads to run?
- Which target and calibration state were used?
- Which compiler and mitigation profile affected the result?
- Which exceptions were approved?
- Which records were retained, deleted, archived, or placed on hold?
Operating rule
Design records before the first serious dispute. Quantum evidence is expensive to reconstruct and sometimes impossible to recreate.