Skip to main content
Introducing The Quantum Infrastructure Cloud Learn more
The stages and wiring of a dilution refrigerator, recoloured in violet.

Solutions · Hardware vendors

A published test
for quantum hardware.

ACOS-ISA is the conformance specification of the QCOS Compatible programme: one driver to write, eleven tests to run and a report your engineers and your buyers can read.

Why it exists

A buyer needs to compare backends without trusting anyone’s slide.

One published test specification

ACOS-ISA v1.0 states what a backend must declare and do, in eleven tests anyone can read before writing a line of driver code.

One driver to write

Implement a single QPUDriver class. Two methods are mandatory, and a reference simulator driver shows the whole contract.

One report to compare

The same tool, the same tests and the same report for every vendor, so a buyer reads like against like.

The driver

Two mandatory methods. Everything else is declared.

A driver says what the backend is and runs what it receives. ReferenceSimulatorDriver in the SDK is the full-contract template to start from.

Run the suite
pip install "qcos-driver-sdk[conformance]"

qcos-driver-cert acme_qcos_driver:AcmeDriver \
  --backend-id acme.lab1 \
  --output report.json
acme_qcos_driver.py
from qcos_driver_sdk import (
    BackendIdentity, DeviceCapabilities, HardwareSpec, QPUDriver,
)

class AcmeDriver(QPUDriver):
    targets = ("acme.lab1",)  # backend ids you serve

    def device_capabilities(self) -> DeviceCapabilities:
        return DeviceCapabilities(
            backend=BackendIdentity(id="acme.lab1", name="ACME Lab-1", provider="acme"),
            hardware=HardwareSpec(num_qubits=20, is_simulator=False),
        )

    def execute(self, circuit, shots=1024):
        ...  # circuit arrives as OpenQASM 2.0 text

ACOS-ISA v1.0

Eleven tests across five layers.

  1. 001

    Capabilities Contract

    The backend declares what it is.

  2. 002

    Native Gate Transpilation

    Circuits lower to the declared gate set.

  3. 003

    Bell State Execution

    A two-qubit entangled state.

  4. 004

    GHZ Correlation

    A four-qubit correlated state.

  5. 005

    Batch Execution Semantics

    Several circuits in one submission.

  6. 006

    Limits Enforcement

    Declared limits refuse what exceeds them.

  7. 007

    Job Cancellation

    May be declared absent; the result then reads compatible, not full.

  8. 008

    Error Taxonomy

    Failures use the published classes.

  9. 009

    Telemetry Minimum

    The minimum operating data is present.

  10. 010

    Evidence Bundle

    Checks the declaration, not a produced bundle.

  11. 011

    Declared Interface

    The interface matches the declaration.

Schema
Requests and responses match the published shapes.
Semantic
A declared capability behaves as declared.
Execution
Known circuits return the expected statistics.
Lifecycle
Submission, batching, limits, cancellation and errors.
Evidence
Part of the specification. No test covers it yet.

The path

From a driver to a report.

Coaxial lines and cold stages inside an open cryostat, recoloured in violet.
01

Write the driver on your own workstation

qcos-driver-sdk is for the vendor workstation or CI, never a QCOS server host. Your driver declares identity and capabilities, and executes what it is given.

An oscilloscope trace with rise and fall times annotated, recoloured in violet.
02

Run the eleven tests

qcos-driver-cert runs the suite against your driver and exits 0 only when a certificate is issued: full at eleven of eleven, or compatible when an optional capability is declared absent.

The plates of a cryostat with instruments in the background, recoloured in violet.
03

Keep the report

The certificate the command prints is local and self-hashed. It carries no QCOS signature and no evidence bundle, so read it as a test report for your own engineering and your buyers’ questions.

Where it stands

The limits, stated.

A conformance programme is worth what its limits are worth, so here they are. Evidence is the layer the suite has yet to reach.

  • No backends are listed in the registry yet
  • Issuing a signed certificate through the service is disabled while the suite is corrected
  • Certificates issued before that are not conformance evidence
  • The pulse-level and Pro tiers are not implemented in the tool

Read further.

Photographs, cropped and recoloured: “Quantum refrigerator at UCL” and “Dilution Refrigerator”, UCL Mathematical and Physical Sciences, CC BY 2.0; NIST and Txo, public domain; Erreja, Ordercrazy and Daderot, CC0. None shows SoftQuantus hardware or a listed vendor, and no partnership or endorsement is implied. ACME is a placeholder.