Pulse and Runtime Registry Schemas — Operating Quantum Computers

This appendix provides draft schemas for registries introduced in Chapters 51 and 52.

I.1 Registry topology

Diagram loads as you read

I.1 Registry topology · Figure 1

View diagram source

flowchart TB
    RuntimeRegistry[Runtime contract registry] --> Program[Program artifacts]
    RuntimeRegistry --> Target[Target snapshots]
    RuntimeRegistry --> Mitigation[Mitigation policies]
    PulseRegistry[Pulse registry] --> Waveform[Waveform artifacts]
    PulseRegistry --> Validation[Validation runs]
    PulseRegistry --> Rollout[Rollout states]
    Target --> PulseRegistry
    Mitigation --> RuntimeRegistry

I.2 Runtime contract schema

Illustrative listing · yaml

runtime_contract_schema:
  required:
    - contract_id
    - created_at
    - workload_id
    - semantic_profile
    - program_ir
    - target
    - compilation
    - execution
    - evidence
  fields:
    contract_id: string
    created_at: timestamp
    workload_id: string
    semantic_profile: string
    program_ir:
      format: enum[qasm3, qir, qiskit, cirq, native, pulse_package]
      version: string
      artifact_hash: sha256
    target:
      provider: string
      backend: string
      target_snapshot_id: string
      required_features: list[string]
    compilation:
      compiler: string
      compiler_version: string
      optimization_goal: string
      compiled_artifact_hash: sha256
    execution:
      shots: integer
      seed_policy: string
      session_id: optional[string]
    evidence:
      package_id: string
      required_artifacts: list[string]

I.3 Runtime contract state machine

Diagram loads as you read

I.3 Runtime contract state machine · Figure 2

View diagram source

stateDiagram-v2
    [*] --> Draft
    Draft --> Preflighted
    Preflighted --> Admitted
    Preflighted --> Rejected
    Admitted --> Running
    Running --> Completed
    Running --> Failed
    Completed --> EvidenceComplete
    Completed --> EvidenceIncomplete
    EvidenceIncomplete --> Quarantined
    EvidenceComplete --> Archived

I.4 Pulse artifact schema

Illustrative listing · yaml

pulse_artifact_schema:
  required:
    - pulse_id
    - target_backend
    - target_qubits
    - waveform_family
    - parameters
    - safety_bounds
    - validation_status
    - rollout_state
  fields:
    pulse_id: string
    target_backend: string
    target_qubits: list[int]
    channels: list[string]
    waveform_family: string
    parameters:
      storage_uri: string
      parameters_hash: sha256
    safety_bounds:
      max_amplitude: float
      max_duration_dt: integer
      bandwidth_limit: string
      collision_domain: list[int]
    validation_status: enum[pending, passed, failed]
    validation:
      rb_result_id: optional[string]
      leakage_result_id: optional[string]
      crosstalk_result_id: optional[string]
    rollout_state: enum[candidate, canary, active, retired, revoked]

I.5 Pulse promotion workflow

Diagram loads as you read

I.5 Pulse promotion workflow · Figure 3

View diagram source

flowchart LR
    Candidate[Candidate pulse] --> Sim[Simulation check]
    Sim --> Safety[Safety bounds]
    Safety --> Cal[Calibration benchmark]
    Cal --> Neighbor[Neighbor impact]
    Neighbor --> Canary[Canary rollout]
    Canary --> Active[Active]
    Active --> Retire[Retire or rollback]

I.6 Evidence artifact schema

Illustrative listing · yaml

evidence_artifact_schema:
  package_id: string
  contract_id: string
  artifacts:
    raw_data:
      uri: string
      hash: sha256
    compiled_program:
      uri: string
      hash: sha256
    calibration_snapshot:
      uri: string
      hash: sha256
    target_snapshot:
      uri: string
      hash: sha256
    mitigation_metadata:
      uri: string
      hash: sha256
    analysis_pipeline:
      uri: string
      commit: git_sha
  retention:
    classification: exploratory | governed | regulated
    minimum_days: integer

I.7 Registry relationships

Diagram loads as you read

I.7 Registry relationships · Figure 4

View diagram source

classDiagram
    class RuntimeContract {
      contract_id
      workload_id
      target_snapshot_id
      evidence_package_id
    }
    class TargetSnapshot {
      target_snapshot_id
      backend
      operations
      timing
      calibration_age
    }
    class PulseArtifact {
      pulse_id
      qubits
      rollout_state
    }
    class EvidencePackage {
      package_id
      artifact_hashes
      retention_policy
    }
    RuntimeContract --> TargetSnapshot
    RuntimeContract --> EvidencePackage
    TargetSnapshot --> PulseArtifact

I.8 Minimal registry API

Illustrative listing · http

POST /runtime-contracts
GET /runtime-contracts/{contract_id}
POST /runtime-contracts/{contract_id}/preflight
POST /runtime-contracts/{contract_id}/admit
GET /evidence-packages/{package_id}
POST /pulse-artifacts
POST /pulse-artifacts/{pulse_id}/promote
POST /pulse-artifacts/{pulse_id}/rollback

I.9 Registry operating rules

no production execution without a runtime contract ID
no runtime contract without a target snapshot ID
no promoted pulse without validation artifacts
no published claim without an evidence package
no rollback without a known prior artifact

Diagram loads as you read

I.9 Registry operating rules · Figure 5

View diagram source

flowchart TD
    Rule[Registry rule] --> Contract[Contract required]
    Rule --> Snapshot[Snapshot required]
    Rule --> Validation[Validation required]
    Rule --> Evidence[Evidence required]
    Rule --> Rollback[Rollback required]