Data Contract and Conformance Templates — Operating Quantum Computers

This appendix provides starter templates for quantum data contracts, event envelopes, conformance suites, and scheduling policies.

Quantum data contract template

Diagram loads as you read

Quantum data contract template · Figure 1

View diagram source

flowchart TB
    Contract[Data contract] --> Meta[Metadata]
    Contract --> Schema[Schema]
    Contract --> Rules[Validation rules]
    Contract --> Owners[Owners]
    Contract --> Compatibility[Compatibility]
    Contract --> Examples[Examples]

Illustrative listing · yaml

contract:
  name: result_distribution
  version: 2.0.0
  owner: quantum-data-platform
  compatibility: backward-compatible-additive
  required_fields:
    - workload_id
    - run_id
    - target_id
    - circuit_manifest_id
    - shot_count
    - counts
    - calibration_snapshot_id
    - mitigation_policy
  retention:
    class: evidence
    minimum_years: 7

Event envelope template

Diagram loads as you read

Event envelope template · Figure 2

View diagram source

sequenceDiagram
    participant Service
    participant EventBus
    participant Consumer
    Service->>EventBus: publish event
    EventBus->>Consumer: deliver event
    Consumer-->>EventBus: acknowledge

Illustrative listing · json

{
  "specversion": "1.0",
  "type": "quantum.run.completed",
  "source": "quantum-platform/broker",
  "id": "evt-0001",
  "subject": "run/run-123",
  "time": "2026-04-19T00:00:00Z",
  "datacontenttype": "application/json",
  "data": {
    "workload_id": "workload-abc",
    "run_id": "run-123",
    "evidence_package_id": "evp-456"
  }
}

Conformance test manifest

Diagram loads as you read

Conformance test manifest · Figure 3

View diagram source

flowchart LR
    Manifest[Test manifest] --> API[API tests]
    Manifest --> Event[Event tests]
    Manifest --> Artifact[Artifact tests]
    Manifest --> Failure[Failure tests]
    Manifest --> Evidence[Evidence tests]

Illustrative listing · yaml

conformance_suite:
  id: provider-adapter-suite-v1
  adapter: provider-x
  tests:
    - id: submit-valid-workload
      type: positive
      expected: accepted
    - id: reject-missing-calibration-policy
      type: negative
      expected: rejected
    - id: cancel-queued-run
      type: lifecycle
      expected: cancelled_event_emitted
    - id: evidence-completeness
      type: evidence
      expected: all_required_artifacts_present

Scheduling policy template

Diagram loads as you read

Scheduling policy template · Figure 4

View diagram source

flowchart TB
    Policy[Scheduling policy] --> Classes[Service classes]
    Policy --> Budgets[Budgets]
    Policy --> Reservations[Reservations]
    Policy --> Stopping[Stopping rules]
    Policy --> Fairness[Fairness]

Illustrative listing · yaml

scheduling_policy:
  service_classes:
    research:
      max_daily_shots: 50000
      reservation_allowed: false
    benchmark:
      max_daily_shots: 250000
      reservation_allowed: true
      approval_required: benchmark-owner
    incident_response:
      priority: highest
      reservation_allowed: true
      approval_required: platform-lead
  stopping_rules:
    default_confidence_interval_width: 0.02
    max_retries: 2

Exit drill worksheet

Diagram loads as you read

Exit drill worksheet · Figure 5

View diagram source

stateDiagram-v2
    [*] --> Select
    Select --> Export
    Export --> ReTarget
    ReTarget --> Execute
    Execute --> Compare
    Compare --> Record
    Record --> [*]

Step	Evidence
select workload	workload contract
export artifacts	manifest bundle
map target	target-difference report
execute equivalent	run evidence
compare outputs	statistical comparison
record decision	portability decision record