Skip to content
Open navigation
Sign inRequest a demo
Evidence · review packet

Evidence that holds up in review.

Keep the circuit, generated source, route context, run result, and share-safe artifacts together in one readable workflow record.

View sample packetReview integrations
An evidence trace connecting a quantum workflow, verification layers, measured states, and a protected review packet
Evidence trace · public-safe example
Ready for review

Review packet snapshot

Bell State

QF-SAMPLE-BELL

2

qubits

4,096

shots

5

artifacts

Measured states4,096 shots
112,072 (50.6%)
002,024 (49.4%)
Circuit, source, route, counts, trace, and manifest stay attached.tokens excluded

What travels with a run

One packet, four useful answers.

Reviewers can follow what was built, how it ran, what came back, and what is safe to share without searching through separate tools.

Evidence packet / sample

Bell State

Ready for review
QF-SAMPLE-BELL

Runner

qiskit-aer

Qubits

2

Shots

4,096

Artifacts

5

Run result

completed

Complete 4,096-shot 00/11 distribution in a reviewer-safe result packet

Measured states4,096 shots
112,072 (50.6%)
002,024 (49.4%)

Included artifacts

  • Generated source
  • Counts and exports
  • Run trace
  • Share-safe link

Provider tokens and workspace-only fields stay private.

How it stays connected

One record from first brief to reviewer link.

The packet follows the workflow, so the result never loses its context or its boundaries.

A left-to-right evidence trace connecting workflow input, verification layers, measured results, and a review packet
traceable by design

Evidence sequence

Context travels with the result.

The visual record connects the original workflow, verification steps, measured output, and the packet a reviewer can safely open.

01 / workflow scope02 / source and route03 / result and trace04 / approved share
01

Capture

Start with scope, ownership, and a circuit that can be traced.

Brief
Canvas
02

Prepare

Keep generated source and provider rationale beside the workflow.

Code
Provider preflight
03

Run

Record the route, result, and execution state as one timeline.

Run
Results
04

Share

Package only the artifacts that are safe and useful to review.

Evidence packet
Approved share

Inspect the output

A sample packet you can actually read.

This Bell State example keeps the useful technical detail visible while excluding provider credentials, billing records, and internal notes.

Measured states4,096 shots
112,072 (50.6%)
002,024 (49.4%)

Public packet contents

Source, result, and manifest

read-only sample

generated-qiskit.py

from qiskit import QuantumCircuit

qc = QuantumCircuit(2, 2)
qc.h(0)
qc.cx(0, 1)
qc.measure([0, 1], [0, 1])

generated-openqasm.qasm

OPENQASM 3;
include "stdgates.inc";
bit[2] c;
qubit[2] q;
h q[0];
cx q[0], q[1];
c[0] = measure q[0];
c[1] = measure q[1];

evidence-manifest.json

{
  "workflowId": "QF-SAMPLE-BELL",
  "runner": "qiskit-aer",
  "artifacts": [
    "generated-qiskit.py",
    "generated-openqasm.qasm",
    "counts.json",
    "counts.csv",
    "trace.json"
  ],
  "privateFieldsExcluded": [
    "providerCredentialId",
    "userEmail",
    "billingState",
    "adminNotes"
  ]
}

Private / public boundary

Share evidence. Keep operations private.

A good evidence packet is explicit about what a reviewer can inspect and what remains role-gated.

Private

Operational data stays inside authenticated workspaces.

  • provider tokens
  • billing state
  • draft notes
  • admin records
  • raw credentials

Shareable

Reviewers receive only the proof needed to inspect a result.

  • result page
  • counts
  • certificate
  • reviewer link
  • artifact manifest

Next step

Start with a public sample packet.

See the evidence first, then choose the route your team needs.

View sample workflows