English Specification Overview¶
This page is the entry point for the English repository-native specification of the QOS-oriented UQCI framework, hosted by Quantum-Punk as an open-source draft specification and reference implementation project.
Architectural Summary¶
The specification is organized around four stable doctrinal points:
- QOS is the runtime, systems, and orchestration layer
- UQCI is the canonical protocol layer
- OpenQASM is the compatibility and exchange layer
DeviceSpec,CalSet,Manifest, andBundleremain normative sidecar artifacts
The canonical source of truth is always the UQCI IR. OpenQASM exports are compatibility artifacts rather than the sole internal representation.
How To Read This Draft¶
Recommended reading paths:
- architecture and semantics: chapters 01 to 05
- artifact and execution contracts: chapters 06 to 10
- compatibility and lowering: chapters 11 to 12
- implementation and release structure: chapters 13 to 17
- stable terminology: chapter 18
Companion repository documents:
- Repository Structure
- OpenQASM Compatibility Bridge
- Backend Extension Guide
- Additional Extension Types
- Development Roadmap
- Terminology Index
Hosting Context¶
The Quantum-Punk organization serves as the open-source host for this
repository and its surrounding ecosystem work. In this context, Quantum-Punk
should be understood as the project host and collaboration container, not as a
formal standards body.
Chapter Directory¶
- Introduction
- Positioning of QOS / UQCI / OpenQASM
- Layered Architecture
- Canonical UQCI Model
- Execution Bundle Model
- JSON Schema Requirements
- DeviceSpec
- CalSet
- Driver API
- RunResult / ValidationReport
- OpenQASM Compatibility Profiles
- Lowering Rules
- Python Skeleton
- Backend Directory Structure
- Mock Backend Strategy
- Non-Goals
- Roadmap
- Glossary
Editorial Status¶
The Markdown chapters are now the preferred repository-native working form of the specification. The Word documents under docs/reference/ remain important reference inputs, but future editorial work should primarily happen in this Markdown set.