Pith Number

pith:TYCCYR4J

pith:2026:TYCCYR4JFVXZ3RJZPEQPCWZXNW

not attested not anchored not stored refs pending

Quantum-HPC Software Stacks and the openQSE Reference Architecture: A Survey

Aleksander Wennersteen, Alex Chernoguzov, Amir Shehata, Andrea Delgado, Brian Austin, Christian Ortiz Pauyac, Ermal Rrapaj, Guen Prawiroatmodjo, Jeffery Heckey, Jiri Schindler, Josh Moles, Katherine Klymko, Kevin Kissell, Laura Schulz, Lee James O'Riordan, Lukas Burgholzer, Martin Schulz, Miwako Tsuji, Sebastian Stern, Spencer Churchill, Thomas Naughton, Tom Beck, Travis Humble, Tyler Takeshita, Yasuko Eckert

A survey of nine quantum-HPC stacks identifies recurring patterns and proposes layer boundaries for interoperability and future-proofing.

arxiv:2604.20912 v2 · 2026-04-22 · quant-ph · cs.DC · cs.ET · cs.SE

Open paper page JSON Open Graph Bundle Merged state Verified badge What is a Pith Number?

Add to your LaTeX paper

\usepackage{pith}
\pithnumber{TYCCYR4JFVXZ3RJZPEQPCWZXNW}

Prints a linked badge after your title and injects PDF metadata. Compiles on arXiv. Learn more · Embed verified badge

Record completeness

1 Bitcoin timestamp

2 Internet Archive

3 Author claim open · sign in to claim

4 Citations open

5 Replications open

✓ Portable graph bundle live · download bundle · merged state

The bundle contains the canonical record plus signed events. A mirror can host it anywhere and recompute the same current state with the deterministic merge algorithm.

Claims

C1strongest claim

we propose the open quantum-HPC software ecosystem (openQSE) reference architecture as a first step toward unifying the state-of-the-practice. openQSE defines a set of layer boundaries that allow different implementations to interoperate while preserving deployment flexibility, and is structured to support both current noisy intermediate-scale quantum (NISQ) workloads and future fault-tolerant quantum computing (FTQC) systems without changes to upper-layer application interfaces.

C2weakest assumption

The common design patterns and requirements identified from the nine production stacks are representative enough to define stable layer boundaries that will actually enable broad interoperability across vendors and will require no upper-layer changes when moving to fault-tolerant quantum systems.

C3one line summary

A survey of nine QHPC stacks identifies common patterns and proposes the openQSE reference architecture to unify interfaces for interoperability in quantum-HPC environments.

Receipt and verification

First computed	2026-06-19T16:09:58.407985Z
Builder	pith-number-builder-2026-05-17-v1
Signature	Pith Ed25519 (`pith-v1-2026-05`) · public key
Schema	pith-number/v1.0

Canonical hash

9e042c47892d6f9dc5397920f15b376db0b20a28f5b32c1eb0103d1634ca3baa

Aliases

arxiv: 2604.20912 · arxiv_version: 2604.20912v2 · doi: 10.48550/arxiv.2604.20912 · pith_short_12: TYCCYR4JFVXZ · pith_short_16: TYCCYR4JFVXZ3RJZ · pith_short_8: TYCCYR4J

Agent API

Resolver JSON Graph JSON Events JSON Schema Signing key

Verify this Pith Number yourself

curl -sH 'Accept: application/ld+json' https://pith.science/pith/TYCCYR4JFVXZ3RJZPEQPCWZXNW \
  | jq -c '.canonical_record' \
  | python3 -c "import sys,json,hashlib; b=json.dumps(json.loads(sys.stdin.read()), sort_keys=True, separators=(',',':'), ensure_ascii=False).encode(); print(hashlib.sha256(b).hexdigest())"
# expect: 9e042c47892d6f9dc5397920f15b376db0b20a28f5b32c1eb0103d1634ca3baa

Canonical record JSON

{
  "metadata": {
    "abstract_canon_sha256": "fb31898196d05f7f8410845077f03e1ca7d12464efbef896930514f5738ec5fc",
    "cross_cats_sorted": [
      "cs.DC",
      "cs.ET",
      "cs.SE"
    ],
    "license": "http://creativecommons.org/licenses/by/4.0/",
    "primary_cat": "quant-ph",
    "submitted_at": "2026-04-22T01:56:58Z",
    "title_canon_sha256": "53505ed1d7cfe88a754e3107eac78b7cfd375b705f14cfb2435f4ab9b8cee99c"
  },
  "schema_version": "1.0",
  "source": {
    "id": "2604.20912",
    "kind": "arxiv",
    "version": 2
  }
}