Pilot record · reviewed 2026-08-20
QF-2048 Supply-chain Pilot Record
A public pilot-style route record that demonstrates brief, validation circuit, source, simulator baseline, route rationale, and reviewer packet without pretending the circuit solves the supply-chain problem.
- Qubits
- 8
- Operations
- 16
- Shots
- 4,096
Brief
Separate route validation from the future optimization claim.
brief.md
Validate
Exercise eight-qubit source, runner, counts, and export paths.
Qiskit + OpenQASM
Preflight
Hold hardware work until credentials, fit, budget, and baseline are reviewed.
route-rationale.md
Review
Share the fixture evidence while excluding private provider and billing data.
run trace + manifest
Workflow question
What this sample is testing.
Validate the eight-qubit author-to-simulator-to-evidence path before a supply-chain optimization team commits to problem encoding, provider access, or a hardware budget.
Route rationale
Seeded simulator route fixture first; optimization encoding and hardware route remain gated
Complete validation counts and trace ready for review without exposing credentials
Method
Use an eight-qubit GHZ-style validation circuit: apply H to q0, propagate entanglement through seven CNOT operations, and measure every qubit. This tests circuit size, source generation, runner routing, counts, and exports; it is not the eventual optimization model.
Run 4,096 shots on Qiskit Aer with simulator and transpiler seed 2048. Preserve the pilot brief, full source, route rationale, complete counts, trace, and the list of private fields excluded from review.
How to read the result
The stored ideal-simulator snapshot contains only 00000000 and 11111111, with 2,092 and 2,004 shots. That validates the seeded circuit fixture and evidence path.
A successful route fixture means the team can inspect how QFlow records a run. It says nothing yet about whether a supply-chain objective has been encoded well or whether a quantum method improves on a classical solver.
Measured distribution
Complete seeded count table
4,096 shots
Complete ideal-simulator distribution. Engine Qiskit Aer 0.17.0; simulator and transpiler seed 2048. This static public fixture is not a live provider run.
Proof boundary
- 01The circuit is deliberately a route-validation fixture and does not encode a supply-chain objective, constraints, cost Hamiltonian, or production dataset.
- 02The result is a seeded ideal simulation, not a provider hardware run, optimization benchmark, or claim of operational benefit.
- 03A real pilot must define the classical baseline, feasible-solution encoding, constraint penalties, dataset boundary, success metric, and hardware or simulator comparison before execution.
Generated representations
Inspect the source behind the counts.
The public code is a review fixture. Provider credentials, workspace members, billing context, and private notes stay excluded.
Qiskit circuit
from qiskit import QuantumCircuit
qc = QuantumCircuit(8, 8)
qc.h(0)
for target in range(1, 8):
qc.cx(target - 1, target)
qc.measure(range(8), range(8))OpenQASM circuit
OPENQASM 3;
include "stdgates.inc";
bit[8] c;
qubit[8] q;
h q[0];
cx q[0], q[1];
cx q[1], q[2];
cx q[2], q[3];
cx q[3], q[4];
cx q[4], q[5];
cx q[5], q[6];
cx q[6], q[7];
c[0] = measure q[0];
c[1] = measure q[1];
c[2] = measure q[2];
c[3] = measure q[3];
c[4] = measure q[4];
c[5] = measure q[5];
c[6] = measure q[6];
c[7] = measure q[7];Evidence manifest
{
"workflowId": "QF-2048",
"runner": "qiskit-aer",
"artifacts": [
"brief.md",
"generated-qiskit.py",
"route-rationale.md",
"counts.csv",
"run-trace.json"
],
"privateFieldsExcluded": [
"providerCredentialId",
"workspaceBilling",
"adminNotes",
"rawProviderResponse"
]
}What the reviewer receives
- brief.md
- generated-qiskit.py
- route-rationale.md
- counts.csv
- run-trace.json
Explicitly excluded
- providerCredentialId
- workspaceBilling
- adminNotes
- rawProviderResponse
Questions this record answers
Workflow FAQ
Does QF-2048 solve a supply-chain optimization problem?
No. This public record validates the workflow and evidence path with an eight-qubit circuit before a team defines the actual objective, constraints, encoding, and classical baseline.
Why use a validation circuit before a quantum optimization pilot?
It lets the team test source generation, simulator routing, exports, privacy boundaries, and review artifacts without confusing infrastructure readiness with algorithmic value.
What must a real supply-chain pilot add?
It must add a bounded dataset, objective and constraints, encoding, classical baseline, success metric, parameter or solver plan, provider budget, and a reviewable comparison.