Decision Records and Review Templates — Operating Quantum Computers

This appendix provides copy-paste templates for the governance mechanisms described throughout the book. They are deliberately plain Markdown/YAML so they can live in a repository, issue tracker, or documentation site.

C.1 Architecture decision record

Illustrative listing · yaml

architecture_decision_record:
  id: ADR-0000
  title: string
  status: proposed|accepted|superseded|rejected
  date: date
  owners:
    - string
  context: |
    What problem forced this decision?
  decision: |
    What are we choosing?
  alternatives:
    - option: string
      reason_rejected: string
  consequences:
    positive:
      - string
    negative:
      - string
    risks:
      - string
  review_date: date

Diagram loads as you read

C.1 Architecture decision record · Figure 1

View diagram source

flowchart LR
    Context[Context] --> Decision[Decision]
    Alternatives[Alternatives] --> Decision
    Decision --> Consequences[Consequences]
    Consequences --> Review[Review date]

C.2 Experiment proposal

Illustrative listing · yaml

experiment_proposal:
  id: EXP-0000
  title: string
  owner: string
  purpose: exploratory|publication|production
  decision_question: string
  success_threshold: string
  classical_baseline:
    method: string
    artifact_uri: string|null
  quantum_method:
    algorithm: string
    encoding: string
    target_candidates:
      - string
  resource_estimate:
    qubits: int|null
    shots: int|null
    estimated_cost: float|null
  risk:
    statistical: string
    hardware: string
    security: string
    cost: string
  stop_conditions:
    - string

Diagram loads as you read

C.2 Experiment proposal · Figure 2

View diagram source

flowchart TB
    Proposal[Proposal] --> Baseline[Baseline]
    Proposal --> Method[Quantum method]
    Proposal --> Estimate[Resource estimate]
    Proposal --> Risk[Risk]
    Risk --> Approval[Approval]

C.3 Publication claim review

Illustrative listing · yaml

publication_claim_review:
  claim_id: string
  proposed_claim: string
  audience: internal|customer|public|academic
  evidence_bundle: uri
  baseline: uri
  uncertainty_report: uri
  limitations: |
    State what the result does not show.
  reviewers:
    technical: string
    statistical: string
    product: string
    legal_or_compliance: string|null
  decision: approved|revise|rejected

Diagram loads as you read

C.3 Publication claim review · Figure 3

View diagram source

flowchart LR
    Claim[Claim] --> Evidence[Evidence]
    Evidence --> Review[Review]
    Review --> Approved[Approved]
    Review --> Revise[Revise]
    Review --> Rejected[Rejected]

C.4 Target onboarding review

Illustrative listing · yaml

target_onboarding_review:
  target_id: string
  provider: string
  modality: superconducting|trapped_ion|photonic|neutral_atom|annealing|simulator|other
  access_model: cloud|reservation|dedicated|on_prem
  supported_operations:
    - string
  limits:
    max_shots: int|null
    max_circuits: int|null
    max_runtime: string|null
  metadata_available:
    calibration_snapshot: true
    backend_properties: true
    raw_results: true
    queue_metadata: true
  conformance_tests:
    status: pass|partial|fail
    report_uri: string
  security_review:
    status: pass|partial|fail
    notes: string
  decision: onboard|pilot|reject

Diagram loads as you read

C.4 Target onboarding review · Figure 4

View diagram source

flowchart TB
    Target[Candidate target] --> Capability[Capability review]
    Target --> Security[Security review]
    Target --> Conformance[Conformance tests]
    Capability --> Decision[Onboarding decision]
    Security --> Decision
    Conformance --> Decision

C.5 Incident review template

Illustrative listing · yaml

incident_review:
  incident_id: string
  severity: sev1|sev2|sev3|sev4
  summary: string
  impact:
    users: int|null
    workloads: int|null
    reports_blocked: int|null
  timeline:
    - timestamp: timestamp
      event: string
  root_causes:
    - string
  contributing_factors:
    - string
  detection:
    how_detected: string
    detection_gap: string|null
  resolution: string
  followups:
    - owner: string
      action: string
      due: date

Diagram loads as you read

C.5 Incident review template · Figure 5

View diagram source

sequenceDiagram
    participant Detect as Detection
    participant Triage
    participant Mitigate
    participant Review
    participant Improve
    Detect->>Triage: alert or report
    Triage->>Mitigate: identify mitigation
    Mitigate->>Review: stabilize and document
    Review->>Improve: assign followups

C.6 Vendor review template

Illustrative listing · yaml

vendor_review:
  vendor: string
  period: string
  targets_reviewed:
    - string
  utilization:
    jobs: int
    spend: float|null
    reservation_hours: float|null
  quality:
    benchmark_report_uri: string
    incidents: int
    metadata_completeness: float|null
  support:
    tickets_opened: int
    response_quality: string
  roadmap_changes:
    - string
  risks:
    - string
  decisions:
    - renew|expand|remediate|exit|monitor

Diagram loads as you read

C.6 Vendor review template · Figure 6

View diagram source

flowchart LR
    Utilization[Utilization] --> QBR[Vendor review]
    Quality[Quality] --> QBR
    Support[Support] --> QBR
    Roadmap[Roadmap] --> QBR
    Risks[Risks] --> QBR
    QBR --> Decision[Decision]