quantum computer
Enable an AI agent to recognise a physical quantum computer, assess its evidenced computational readiness and select workloads or interventions compatible with its capabilities and operating constraints.
Research draft, second pass
A second pass drafted this model: the structure a model of this thing needs, and what is known about it in the world. The line under this one says how the second half was obtained - researched against sources, or recalled without web access, in which case nothing here was read anywhere and every claim is a lead to verify. Unreviewed either way.
Researched by: Codex
Purpose and description
Enable an AI agent to recognise a physical quantum computer, assess its evidenced computational readiness and select workloads or interventions compatible with its capabilities and operating constraints.
It can be Match a proposed workload to the machine's computational model, usable resources and supported controls.; Prepare or translate an authorised workload into the accepted executable representation.; Submit permitted jobs and retrieve outcomes with execution and calibration provenance.; Request supported characterisation procedures and assess whether their results justify continued use.; Select an available configuration or request recalibration within the agent's authority.; Defer execution or escalate a fault when readiness evidence or operating constraints do not support the intended action..
Distinguishing features
Execution uses physical quantum degrees of freedom as computational resources; software that numerically imitates quantum evolution on classical hardware does not satisfy this test.
The system exposes a supported way to specify a computation and obtain its outcome, rather than only observing a quantum phenomenon.
Its principal computational function is distinguishable from measuring an external physical quantity or transporting quantum states.
Its declared boundary supplies or explicitly depends on preparation, control and readout capabilities; a processor chip alone does not establish a complete operable computer.
Its supported computational model is identified without assuming that every quantum computer accepts gate circuits or provides universal computation.
Scope
+ The system boundary linking quantum processing hardware, classical control and essential environmental support
+ The physical carriers of quantum information and the computational model they implement
+ Available quantum resources, supported operations and workload compatibility
+ Calibration, characterisation and evidence of computational performance
+ Operational readiness, execution access and restrictions on interventions
- Quantum algorithms and application problems as independently defined computational methods
- Classical quantum-circuit simulators and their host computers
- Standalone quantum sensors and quantum communication equipment
- Fabrication processes and individual components except as installed resources or dependencies
- Provider organisations, commercial contracts and facility management
- Quantum networks spanning independently operated computers
Characteristics
- Computational model
- Gate-based, annealing, analog, measurement-based or another evidenced model; multiple values permitted Determines which workload descriptions and computational operations are meaningful.
- Physical quantum implementation
- Recorded physical carrier and encoding, such as superconducting circuits, trapped ions, neutral atoms, photonic modes or spins Identifies implementation-specific controls, environmental requirements and failure modes.
- Usable quantum resource inventory
- Count of usable qubits, qudits, modes or other declared resources, with configuration and timestamp Separates installed resources from resources available for a particular execution.
- Interaction and addressing structure
- Supported interactions among identified resources, including direction, restrictions and reconfiguration conditions Constrains placement, routing and the computations the machine can implement.
- Characterised error behaviour
- Named error or fidelity metric with protocol, uncertainty, operating conditions and measurement date Supports workload-specific confidence without treating unlike measurements as interchangeable.
- Relevant timing limits
- Seconds for applicable coherence, operation, preparation, readout or evolution intervals, each with its definition Constrains executable sequences and helps estimate completion time.
- Error-management regime
- Documented use of suppression, mitigation, detection or correction; logical-resource claims require supporting evidence Distinguishes techniques that affect output interpretation and available computational resources.
- Computational readiness
- Uncharacterised, conditioning, calibrating, ready for a declared workload class, degraded, unavailable or maintenance Prevents hardware presence or remote reachability from being mistaken for readiness.
- Execution and intervention authority
- Links to authorised principals, permitted operations, access interfaces and applicable restrictions Determines whether an agent may submit jobs, change configurations or request specialist intervention.
Also called
Where this came from
wikidata · CC0 1.0
Drafted structure
Bundle to layer to finding to question, as the second pass will find it: 5 bundles · 10 layers · 10 findings · 20 questions.
Quantum system identity Establishes what physical system is being modelled and why it qualifies as a quantum computer.
An agent must distinguish a complete computing system from a simulator, an isolated processor and other quantum equipment.
Physical computation basis
Identifies the physical quantum resources and their computational role.
Quantum computation evidence
Records the evidence needed to establish physical quantum execution without assuming a particular architecture.
- Which physical degrees of freedom encode or carry the computational state, and how are they prepared, manipulated and measured? definition
- What inspected documentation or experimental evidence establishes that execution uses this hardware rather than a classical simulator? provenance
Installed system boundary
Separates the computer from its components, supporting equipment and access services.
Processor, control and support boundary
Records which quantum processors, controllers and essential support systems belong to this computer.
- Which processors, classical controllers, preparation and readout devices are included, and which environmental services are external dependencies? boundary
- What identifiers distinguish this physical installation and hardware revision from a provider endpoint that may route jobs to different machines? provenance
Computational capability Describes the computations the installed quantum hardware can express and support.
Resource counts alone cannot establish whether a workload is executable.
Computation and controls
Captures the accepted computational representation and available operations.
Supported computation contract
Records architecture-specific inputs and controls without imposing gate-based assumptions.
- Does the machine accept circuits, Hamiltonians, annealing schedules, measurement patterns or another representation, and what restrictions apply? definition
- Which operations, parameter ranges and conditional controls may an authorised workload request? action
Resource placement
Captures usable computational resources and the interactions available among them.
Usable resource and interaction map
Records the configuration against which workload size and placement must be checked.
- How many resources of each declared type are usable in the selected configuration, and which are excluded or reserved? measurement
- Which interaction, addressing, movement or embedding constraints determine whether the workload fits? boundary
Quantum performance evidence Connects capability claims to dated measurements and their limits of interpretation.
An agent needs evidence relevant to the intended workload rather than a single headline performance number.
Noise and calibration
Captures measured behaviour and the configuration for which it was characterised.
Characterisation validity
Records applicable error, timing and readout measurements together with their validity conditions.
- Which error, fidelity, timing and readout metrics have been measured, using what protocols and uncertainty estimates? measurement
- Which hardware configuration and calibration do those measurements describe, and what evidence or events would make them stale? provenance
Error management and results
Separates physical performance, error-management claims and demonstrated workload outcomes.
Supported result confidence
Records what evidence supports output quality and any claimed logical computation.
- What suppression, mitigation, detection or correction procedures were actually used, and what evidence supports any reported logical resources or logical error rates? provenance
- Which workload-level results support expected output quality, with what sampling, postselection, processing and comparison conditions? measurement
Quantum operating readiness Determines whether the quantum hardware and its dependencies can presently support the intended computation.
Quantum resources may be installed and reachable while environmental conditions, calibration or resource preparation prevent useful execution.
Operating envelope
Captures implementation-specific conditions required for stable operation.
Required physical conditions
Records applicable environmental and support requirements rather than assuming every implementation needs the same equipment.
- Which temperature, vacuum, optical, electromagnetic, vibration or supply conditions are required by this implementation? definition
- Which current observations establish that required conditions and support services are within their documented operating limits? measurement
Readiness and recovery
Connects observed machine state to permitted execution and recovery actions.
Workload readiness decision
Records whether a particular workload can run and what should happen when readiness fails.
- Are preparation, control, readout and required calibration currently adequate for the proposed workload, and which evidence supports that assessment? measurement
- Which conditions require deferring jobs, removing resources from use, requesting recalibration or escalating to an operator? action
Quantum execution and traceability Governs how an authorised workload reaches the hardware and how its outcomes remain interpretable.
Execution transformations, sampling choices and changing calibrations affect what an outcome means and whether it can be compared with another run.
Job admission
Captures access, translation and resource checks before execution.
Authorised executable workload
Records whether the agent can submit the proposed computation with suitable configuration and limits.
- Which interface and permissions allow this agent to submit workloads or change quantum control settings? action
- What compilation, routing, embedding or parameter validation is required, and what execution limits constrain the resulting job? boundary
Outcome interpretation
Links measured outputs to their physical execution and subsequent processing.
Reconstructable execution record
Records enough context to interpret stochastic outcomes and investigate discrepancies.
- Which machine identity, resource mapping, executable representation, calibration reference, execution time and sampling settings produced these outputs? provenance
- How are raw measurements distinguished from decoded, mitigated, postselected or aggregated outputs, including discarded samples and uncertainty? measurement
What the second pass must settle
- Does the registry intend this entry to include special-purpose analog quantum simulators and quantum annealers, and what boundary distinguishes them from noncomputational experimental apparatus?
- What minimum evidence should establish physical quantum computation for registration when internal hardware and characterisation data are inaccessible?
- When processors, controllers or quantum modules are replaced or reconfigured, which changes preserve the identity of the registered computer?
- Which architecture-specific characterisation methods and freshness criteria are sufficient for each intended workload class?
- What evidence threshold should support claims of usable logical resources, fault-tolerant operation or computational advantage?