01 Introduction¶

Purpose¶

This chapter introduces the repository-native specification for the QOS-oriented UQCI framework. It translates the reference Word drafts into a maintainable Markdown form suitable for open-source development, review, and incremental implementation while preserving publication-ready structure and standards-oriented terminology.

Document Status¶

Status: Draft v0.1
Language: English
Role: repository-native normative chapter

This repository-native specification is an implementable draft. It does not claim formal adoption by any standards body.

Scope¶

This specification addresses the following concerns:

universal quantum control semantics across heterogeneous backend families
program interoperability across toolchains and runtime environments
bundle-based execution delivery with normative sidecar artifacts
a standards-friendly path from draft specification to runnable reference implementation

The immediate focus of v0.1 is architectural clarity, machine-readable artifacts, compatibility export, and reference implementation structure. It is not a claim of complete runtime or hardware standardization.

Intended Audience¶

The intended audience includes:

quantum operating system and orchestration teams
compiler and control-software teams
backend and hardware vendors
quantum cloud platforms and simulator implementers
standards and interoperability contributors

Normative Position¶

The reference Word drafts make a central point that remains normative here: the objective is not to force all quantum technologies into one physical control channel. The objective is to standardize control semantics, program interchange, and execution packaging while preserving the physical differences among hardware families.

This repository therefore defines a layered architecture in which:

QOS provides the runtime and systems viewpoint
UQCI provides the canonical protocol semantics
OpenQASM provides a compatibility and exchange surface
backend modules preserve technology-specific realization

Naming Background¶

The naming model inherited from the reference drafts is intentionally layered:

QOS expresses the runtime, systems, and orchestration viewpoint
UQCI names the canonical protocol and semantic core
OpenQASM Compatibility Profile names the exchange and interoperability binding

This structure is important because it keeps UQCI independent and device-agnostic while still making OpenQASM compatibility explicit. In other words, the compatibility profile is attached to the protocol; it does not replace the protocol.

The Word drafts also use a public-facing specification identity comparable to a QOS-1 world-standard draft. This repository does not need to repeat that branding on every page, but it preserves the same architectural doctrine.

Repository-Native Form¶

In the imported materials, the Word documents serve as the source drafts. In this repository, the Markdown chapters under docs/spec/en/ and docs/spec/zh-CN/ become the preferred working form for ongoing specification maintenance.

That editorial transition has two practical consequences:

normative ideas are preserved, but long code and schema listings should be summarized in prose where appropriate and backed by repository files
implementation-aligned documents such as schemas/, examples/, and source modules become first-class companions to the specification

Relationship To The Repository¶

This chapter should be read together with the repository overview, architecture notes, and the later specification chapters. It establishes the scope and editorial stance for the remainder of the English specification.