{ "model": { "rank": 5766, "code": "thing-q176555", "model_id": "vr.tr.quantum-computer", "name": "quantum computer", "purpose": "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.", "family": "Thing Registry", "category": "Physical world and living systems", "status": "research-draft", "kind": "thing", "plane": "PHY", "domain": "PHY.OBJ", "industry": "", "version": "", "url": "/models/thing/q176555/", "tier": 2, "score": 65, "payload": { "layer": "wikidata", "aliases": [ "IBM Heron", "IBM Q System Two", "Neutral atom quantum computer", "Gottesman–Kitaev–Preskill code", "Cat qubit quantum computer", "D-Wave 2X", "D-Wave One", "D-Wave Advantage", "D-Wave Advantage2", "Euro-Q-Exa", "D-Wave Two", "counterfactual quantum computation", "D-Wave 2000Q", "black hole computer", "IBM Q System One", "Kane quantum computer", "one-way quantum computer", "topological quantum computer", "trapped ion quantum computer", "nuclear magnetic resonance quantum computer", "liquid state nuclear magnetic resonance quantum computer" ], "aliasCount": 21, "merged": 21, "knownIn": 65, "facets": null, "markers": [], "lexicalClass": "", "senseRank": null, "alsoRegisteredAs": null, "source": { "dataset": "wikidata", "item": "Q176555", "url": "https://www.wikidata.org/wiki/Q176555", "license": "CC0 1.0" } }, "research": { "vercy": "1.0-draft", "publication": { "status": "research-draft", "adjudicationStatus": "unreviewed", "publishableCanonical": false, "generatedAt": "2026-09-07T09:14:59Z", "providers": [ "Codex" ], "missingProviders": [ "Grok" ], "pass": 2, "cost": { "grok": { "usd": null, "turns": null, "seconds": 9.4, "error": "Error: Internal error: {\n \"message\": \"API error (status 402 Payment Required): Grok Build usage balance exhausted\",\n \"http_status\": 402\n}", "retried": true }, "codex": { "seconds": 92.1, "error": "Reading additional input from stdin...\nOpenAI Codex v0.153.3\n--------\nworkdir: R:\\02_PROJECTS\\02_Meta_Models_Platforms\\Ver.cy\\current\\thing-registry-backlog\nmodel: gpt-6-astra\nprovider: openai\napproval: never\nsandbox: read-only\nreasoning effort: none\nreasoning summaries: none\nsession id: 01a07b24-dad0-74b2-a368-723e70e0b8df\n--------\nuser\nYou are drafting a Vercy meta-model for one registered thing. Answer as JSON only, no prose around it.\n\nThing: quantum computer\nRegistry id: vr.tr.quantum-computer\nPlane / domain: PHY / PHY.OBJ\nRegistry definition: (none recorded)\nNames folded into this entry:" } } }, "metaModel": { "id": "THING-Q176555", "registryId": "vr.tr.quantum-computer", "name": "quantum computer", "version": "0.1.0-research.1", "entryKind": "thing", "family": "Thing Registry", "domain": [ "PHY.OBJ" ], "status": "research-draft" }, "canonicalUrl": "https://ver.cy/models/thing/q176555/", "model": { "registry_id": "vr.tr.quantum-computer", "name": "quantum computer", "purpose": "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.", "definition": "", "scope_statement": "This model owns the identity, physical quantum computing resources, supported computational operations, measured performance, operating state and permitted use of one quantum computer, including the classical control and environmental dependencies required to operate it.", "in_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" ], "out_of_scope": [ "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" ], "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." ], "characteristics": [ { "name": "Computational model", "kind": "category", "unit_or_values": "Gate-based, annealing, analog, measurement-based or another evidenced model; multiple values permitted", "why_it_matters": "Determines which workload descriptions and computational operations are meaningful." }, { "name": "Physical quantum implementation", "kind": "category", "unit_or_values": "Recorded physical carrier and encoding, such as superconducting circuits, trapped ions, neutral atoms, photonic modes or spins", "why_it_matters": "Identifies implementation-specific controls, environmental requirements and failure modes." }, { "name": "Usable quantum resource inventory", "kind": "measurement", "unit_or_values": "Count of usable qubits, qudits, modes or other declared resources, with configuration and timestamp", "why_it_matters": "Separates installed resources from resources available for a particular execution." }, { "name": "Interaction and addressing structure", "kind": "relation", "unit_or_values": "Supported interactions among identified resources, including direction, restrictions and reconfiguration conditions", "why_it_matters": "Constrains placement, routing and the computations the machine can implement." }, { "name": "Characterised error behaviour", "kind": "measurement", "unit_or_values": "Named error or fidelity metric with protocol, uncertainty, operating conditions and measurement date", "why_it_matters": "Supports workload-specific confidence without treating unlike measurements as interchangeable." }, { "name": "Relevant timing limits", "kind": "measurement", "unit_or_values": "Seconds for applicable coherence, operation, preparation, readout or evolution intervals, each with its definition", "why_it_matters": "Constrains executable sequences and helps estimate completion time." }, { "name": "Error-management regime", "kind": "category", "unit_or_values": "Documented use of suppression, mitigation, detection or correction; logical-resource claims require supporting evidence", "why_it_matters": "Distinguishes techniques that affect output interpretation and available computational resources." }, { "name": "Computational readiness", "kind": "state", "unit_or_values": "Uncharacterised, conditioning, calibrating, ready for a declared workload class, degraded, unavailable or maintenance", "why_it_matters": "Prevents hardware presence or remote reachability from being mistaken for readiness." }, { "name": "Execution and intervention authority", "kind": "relation", "unit_or_values": "Links to authorised principals, permitted operations, access interfaces and applicable restrictions", "why_it_matters": "Determines whether an agent may submit jobs, change configurations or request specialist intervention." } ], "affordances": [ "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." ] }, "sources": [], "structure": { "bundles": [ { "id": "quantum-system-identity", "name": "Quantum system identity", "description": "Establishes what physical system is being modelled and why it qualifies as a quantum computer.", "rationale": "An agent must distinguish a complete computing system from a simulator, an isolated processor and other quantum equipment.", "layers": [ { "id": "physical-computation-basis", "name": "Physical computation basis", "description": "Identifies the physical quantum resources and their computational role.", "findings": [ { "id": "quantum-computation-evidence", "name": "Quantum computation evidence", "description": "Records the evidence needed to establish physical quantum execution without assuming a particular architecture.", "questions": [ { "text": "Which physical degrees of freedom encode or carry the computational state, and how are they prepared, manipulated and measured?", "kind": "definition", "id": "quantum-computation-evidence-q01" }, { "text": "What inspected documentation or experimental evidence establishes that execution uses this hardware rather than a classical simulator?", "kind": "provenance", "id": "quantum-computation-evidence-q02" } ] } ] }, { "id": "installed-system-boundary", "name": "Installed system boundary", "description": "Separates the computer from its components, supporting equipment and access services.", "findings": [ { "id": "processor-control-support-boundary", "name": "Processor, control and support boundary", "description": "Records which quantum processors, controllers and essential support systems belong to this computer.", "questions": [ { "text": "Which processors, classical controllers, preparation and readout devices are included, and which environmental services are external dependencies?", "kind": "boundary", "id": "processor-control-support-boundary-q01" }, { "text": "What identifiers distinguish this physical installation and hardware revision from a provider endpoint that may route jobs to different machines?", "kind": "provenance", "id": "processor-control-support-boundary-q02" } ] } ] } ] }, { "id": "computational-capability", "name": "Computational capability", "description": "Describes the computations the installed quantum hardware can express and support.", "rationale": "Resource counts alone cannot establish whether a workload is executable.", "layers": [ { "id": "computation-and-controls", "name": "Computation and controls", "description": "Captures the accepted computational representation and available operations.", "findings": [ { "id": "supported-computation-contract", "name": "Supported computation contract", "description": "Records architecture-specific inputs and controls without imposing gate-based assumptions.", "questions": [ { "text": "Does the machine accept circuits, Hamiltonians, annealing schedules, measurement patterns or another representation, and what restrictions apply?", "kind": "definition", "id": "supported-computation-contract-q01" }, { "text": "Which operations, parameter ranges and conditional controls may an authorised workload request?", "kind": "action", "id": "supported-computation-contract-q02" } ] } ] }, { "id": "resource-placement", "name": "Resource placement", "description": "Captures usable computational resources and the interactions available among them.", "findings": [ { "id": "usable-resource-and-interaction-map", "name": "Usable resource and interaction map", "description": "Records the configuration against which workload size and placement must be checked.", "questions": [ { "text": "How many resources of each declared type are usable in the selected configuration, and which are excluded or reserved?", "kind": "measurement", "id": "usable-resource-and-interaction-map-q01" }, { "text": "Which interaction, addressing, movement or embedding constraints determine whether the workload fits?", "kind": "boundary", "id": "usable-resource-and-interaction-map-q02" } ] } ] } ] }, { "id": "quantum-performance-evidence", "name": "Quantum performance evidence", "description": "Connects capability claims to dated measurements and their limits of interpretation.", "rationale": "An agent needs evidence relevant to the intended workload rather than a single headline performance number.", "layers": [ { "id": "noise-and-calibration", "name": "Noise and calibration", "description": "Captures measured behaviour and the configuration for which it was characterised.", "findings": [ { "id": "characterisation-validity", "name": "Characterisation validity", "description": "Records applicable error, timing and readout measurements together with their validity conditions.", "questions": [ { "text": "Which error, fidelity, timing and readout metrics have been measured, using what protocols and uncertainty estimates?", "kind": "measurement", "id": "characterisation-validity-q01" }, { "text": "Which hardware configuration and calibration do those measurements describe, and what evidence or events would make them stale?", "kind": "provenance", "id": "characterisation-validity-q02" } ] } ] }, { "id": "error-management-and-results", "name": "Error management and results", "description": "Separates physical performance, error-management claims and demonstrated workload outcomes.", "findings": [ { "id": "supported-result-confidence", "name": "Supported result confidence", "description": "Records what evidence supports output quality and any claimed logical computation.", "questions": [ { "text": "What suppression, mitigation, detection or correction procedures were actually used, and what evidence supports any reported logical resources or logical error rates?", "kind": "provenance", "id": "supported-result-confidence-q01" }, { "text": "Which workload-level results support expected output quality, with what sampling, postselection, processing and comparison conditions?", "kind": "measurement", "id": "supported-result-confidence-q02" } ] } ] } ] }, { "id": "quantum-operating-readiness", "name": "Quantum operating readiness", "description": "Determines whether the quantum hardware and its dependencies can presently support the intended computation.", "rationale": "Quantum resources may be installed and reachable while environmental conditions, calibration or resource preparation prevent useful execution.", "layers": [ { "id": "operating-envelope", "name": "Operating envelope", "description": "Captures implementation-specific conditions required for stable operation.", "findings": [ { "id": "required-physical-conditions", "name": "Required physical conditions", "description": "Records applicable environmental and support requirements rather than assuming every implementation needs the same equipment.", "questions": [ { "text": "Which temperature, vacuum, optical, electromagnetic, vibration or supply conditions are required by this implementation?", "kind": "definition", "id": "required-physical-conditions-q01" }, { "text": "Which current observations establish that required conditions and support services are within their documented operating limits?", "kind": "measurement", "id": "required-physical-conditions-q02" } ] } ] }, { "id": "readiness-and-recovery", "name": "Readiness and recovery", "description": "Connects observed machine state to permitted execution and recovery actions.", "findings": [ { "id": "workload-readiness-decision", "name": "Workload readiness decision", "description": "Records whether a particular workload can run and what should happen when readiness fails.", "questions": [ { "text": "Are preparation, control, readout and required calibration currently adequate for the proposed workload, and which evidence supports that assessment?", "kind": "measurement", "id": "workload-readiness-decision-q01" }, { "text": "Which conditions require deferring jobs, removing resources from use, requesting recalibration or escalating to an operator?", "kind": "action", "id": "workload-readiness-decision-q02" } ] } ] } ] }, { "id": "quantum-execution-and-traceability", "name": "Quantum execution and traceability", "description": "Governs how an authorised workload reaches the hardware and how its outcomes remain interpretable.", "rationale": "Execution transformations, sampling choices and changing calibrations affect what an outcome means and whether it can be compared with another run.", "layers": [ { "id": "job-admission", "name": "Job admission", "description": "Captures access, translation and resource checks before execution.", "findings": [ { "id": "authorised-executable-workload", "name": "Authorised executable workload", "description": "Records whether the agent can submit the proposed computation with suitable configuration and limits.", "questions": [ { "text": "Which interface and permissions allow this agent to submit workloads or change quantum control settings?", "kind": "action", "id": "authorised-executable-workload-q01" }, { "text": "What compilation, routing, embedding or parameter validation is required, and what execution limits constrain the resulting job?", "kind": "boundary", "id": "authorised-executable-workload-q02" } ] } ] }, { "id": "outcome-interpretation", "name": "Outcome interpretation", "description": "Links measured outputs to their physical execution and subsequent processing.", "findings": [ { "id": "reconstructable-execution-record", "name": "Reconstructable execution record", "description": "Records enough context to interpret stochastic outcomes and investigate discrepancies.", "questions": [ { "text": "Which machine identity, resource mapping, executable representation, calibration reference, execution time and sampling settings produced these outputs?", "kind": "provenance", "id": "reconstructable-execution-record-q01" }, { "text": "How are raw measurements distinguished from decoded, mitigated, postselected or aggregated outputs, including discarded samples and uncertainty?", "kind": "measurement", "id": "reconstructable-execution-record-q02" } ] } ] } ] } ] }, "openQuestions": [ "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?" ], "statistics": { "bundles": 5, "layers": 10, "findings": 10, "questions": 20 } }, "draft": { "generator": "vr.draft.v3", "status": "draft-generated", "researched": false, "archetype": "device, machine or tool", "method": "Written from the archetype playbook - what this kind of thing needs beyond identity and provenance - and from the structure that recurred across 6,333 models already researched by two engines. Applied to this entry by rule. No source was read for this thing and no claim here is researched. This entry carries no facets of its own, so they were inferred from its domain - a guess about a whole domain applied to one thing.", "facetsInferred": true, "nextPass": "A researcher replaces this draft with a sourced specification. Treat every sentence below as a proposal to argue with.", "purpose": "Give an agent a durable, checkable way to recognise a quantum computer, record what state it is in, and decide what may be done with it.", "whatItIs": "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.", "characteristics": { "substance": "material", "origin": "manufactured", "agency": "inert", "mobility": "varies" }, "whatYouCanDoWithIt": [ "observed and measured" ], "distinguishingFeatures": [ "Names folded into this entry, which a task may need to split apart again: IBM Heron, IBM Q System Two, Neutral atom quantum computer, Gottesman–Kitaev–Preskill code, Cat qubit quantum computer, D-Wave 2X, D-Wave One, D-Wave Advantage, D-Wave Advantage2, Euro-Q-Exa, D-Wave Two, counterfactual quantum computation.", "21 finer distinctions are held as aliases rather than separate entries, because telling them apart needs a task that asks for it.", "Described in 65 Wikipedia languages, which is a measure of how widely the thing is known, not of how important it is." ], "openQuestionsForResearch": [ "Which of the bundles below does a real task actually need, and which are ceremony?", "What does this thing have that the facets do not capture at all?", "Which neighbouring kind is most often confused with a quantum computer, and on what evidence are they told apart?" ], "whatItIsMadeOf": "matter you can touch", "physicalCharacter": [ "Mobility varies between examples.", "Does nothing on its own; everything it does, something else did to it.", "These come from the domain this entry sits in rather than from the entry itself, so treat them as a first guess about the whole domain applied to one thing." ], "whatCanBeDoneWithIt": [ "observe it, measure it, record its state" ], "howItIsRecognised": [ "Recognised by form, by the arrangement of its controls, and by markings - a plate, a model number, a certification mark. Form alone rarely separates two models that do very different things." ], "relatedModels": [ { "relation": "covers", "note": "Finer kinds folded into this entry because telling them apart needs a task that asks for it. Each is a model waiting to be split out when one does.", "targets": [ "IBM Heron", "IBM Q System Two", "Neutral atom quantum computer", "Gottesman–Kitaev–Preskill code", "Cat qubit quantum computer", "D-Wave 2X", "D-Wave One", "D-Wave Advantage", "D-Wave Advantage2", "Euro-Q-Exa", "D-Wave Two", "counterfactual quantum computation" ] } ], "standing": "Described in 65 Wikipedia languages, which measures how widely it is written about rather than how important or how common it is. 21 finer distinctions are held inside this entry as names rather than as separate models.", "structure": { "bundles": [ { "id": "identity-and-classification", "name": "Identity, naming and classification", "description": "How an agent tells one quantum computer from another, and a quantum computer from things that resemble it.", "rationale": "Recognition comes before every other claim. Without stable identity nothing else in the model can be trusted to be about the same thing twice.", "layers": [ { "id": "naming-and-identifiers", "name": "Names and identifiers", "description": "The names this thing goes by and the identifiers that survive translation and time.", "findings": [ { "id": "preferred-name-and-aliases", "name": "Preferred name, aliases and local names", "description": "Which name to use, which names mean the same thing, and which merely sound similar.", "questions": [ { "id": "preferred-name-and-aliases-q01", "text": "What identifies and describes the name of a quantum computer, and in what units or vocabulary?", "kind": "definition", "answer_data": [ "identifiers", "types and classes", "values with units", "explicit unknowns" ] }, { "id": "preferred-name-and-aliases-q02", "text": "Who or what asserted this about the name of a quantum computer, by which method, and when was it true?", "kind": "provenance", "answer_data": [ "authority", "method", "evidence", "event time", "knowledge time" ] }, { "id": "preferred-name-and-aliases-q03", "text": "What may an agent decide or do once the name of a quantum computer is known, and what must it refuse?", "kind": "action", "answer_data": [ "permitted actions", "preconditions", "refusals", "escalation" ] } ] }, { "id": "stable-identifiers", "name": "Stable identifiers and external keys", "description": "Identifiers that keep pointing at this kind of thing across systems and languages.", "questions": [ { "id": "stable-identifiers-q01", "text": "What identifies and describes an identifier for a quantum computer, and in what units or vocabulary?", "kind": "definition", "answer_data": [ "identifiers", "types and classes", "values with units", "explicit unknowns" ] }, { "id": "stable-identifiers-q02", "text": "Who or what asserted this about an identifier for a quantum computer, by which method, and when was it true?", "kind": "provenance", "answer_data": [ "authority", "method", "evidence", "event time", "knowledge time" ] }, { "id": "stable-identifiers-q03", "text": "What may an agent decide or do once an identifier for a quantum computer is known, and what must it refuse?", "kind": "action", "answer_data": [ "permitted actions", "preconditions", "refusals", "escalation" ] } ] } ] }, { "id": "classification-and-granularity", "name": "Classification and granularity", "description": "Where a quantum computer sits among kinds, and how finely a task needs to cut it.", "findings": [ { "id": "kind-and-parents", "name": "Kind, parents and neighbouring kinds", "description": "The classes this thing belongs to and the ones it is next to.", "questions": [ { "id": "kind-and-parents-q01", "text": "What identifies and describes the kind of a quantum computer, and in what units or vocabulary?", "kind": "definition", "answer_data": [ "identifiers", "types and classes", "values with units", "explicit unknowns" ] }, { "id": "kind-and-parents-q02", "text": "Who or what asserted this about the kind of a quantum computer, by which method, and when was it true?", "kind": "provenance", "answer_data": [ "authority", "method", "evidence", "event time", "knowledge time" ] }, { "id": "kind-and-parents-q03", "text": "What may an agent decide or do once the kind of a quantum computer is known, and what must it refuse?", "kind": "action", "answer_data": [ "permitted actions", "preconditions", "refusals", "escalation" ] } ] }, { "id": "distinguishing-features", "name": "Distinguishing features", "description": "What separates a quantum computer from the things most often confused with it.", "questions": [ { "id": "distinguishing-features-q01", "text": "What identifies and describes what distinguishes a quantum computer, and in what units or vocabulary?", "kind": "definition", "answer_data": [ "identifiers", "types and classes", "values with units", "explicit unknowns" ] }, { "id": "distinguishing-features-q02", "text": "Who or what asserted this about what distinguishes a quantum computer, by which method, and when was it true?", "kind": "provenance", "answer_data": [ "authority", "method", "evidence", "event time", "knowledge time" ] }, { "id": "distinguishing-features-q03", "text": "What may an agent decide or do once what distinguishes a quantum computer is known, and what must it refuse?", "kind": "action", "answer_data": [ "permitted actions", "preconditions", "refusals", "escalation" ] } ] } ] } ] }, { "id": "form-and-composition", "name": "Form, composition and condition", "description": "What a quantum computer is made of, what shape and size it takes, and what state it is in.", "rationale": "A physical thing can be measured, and a model that cannot record its measurements cannot support any decision that depends on them.", "layers": [ { "id": "form-and-dimensions", "name": "Form and dimensions", "description": "Shape, size, mass and the ranges these take across examples.", "findings": [ { "id": "measurable-dimensions", "name": "Measurable dimensions and their units", "description": "The quantities worth recording and the units they are recorded in.", "questions": [ { "id": "measurable-dimensions-q01", "text": "What identifies and describes the dimensions of a quantum computer, and in what units or vocabulary?", "kind": "definition", "answer_data": [ "identifiers", "types and classes", "values with units", "explicit unknowns" ] }, { "id": "measurable-dimensions-q02", "text": "Who or what asserted this about the dimensions of a quantum computer, by which method, and when was it true?", "kind": "provenance", "answer_data": [ "authority", "method", "evidence", "event time", "knowledge time" ] }, { "id": "measurable-dimensions-q03", "text": "What may an agent decide or do once the dimensions of a quantum computer is known, and what must it refuse?", "kind": "action", "answer_data": [ "permitted actions", "preconditions", "refusals", "escalation" ] } ] } ] }, { "id": "material-and-composition", "name": "Material and composition", "description": "Materials, parts and how they are put together.", "findings": [ { "id": "parts-and-materials", "name": "Parts and materials", "description": "What a quantum computer is built from and which parts are replaceable.", "questions": [ { "id": "parts-and-materials-q01", "text": "What identifies and describes the composition of a quantum computer, and in what units or vocabulary?", "kind": "definition", "answer_data": [ "identifiers", "types and classes", "values with units", "explicit unknowns" ] }, { "id": "parts-and-materials-q02", "text": "Who or what asserted this about the composition of a quantum computer, by which method, and when was it true?", "kind": "provenance", "answer_data": [ "authority", "method", "evidence", "event time", "knowledge time" ] }, { "id": "parts-and-materials-q03", "text": "What may an agent decide or do once the composition of a quantum computer is known, and what must it refuse?", "kind": "action", "answer_data": [ "permitted actions", "preconditions", "refusals", "escalation" ] } ] } ] }, { "id": "condition-and-integrity", "name": "Condition and integrity", "description": "Wear, damage, health and the difference between working and broken.", "findings": [ { "id": "condition-assessment", "name": "Condition, damage and health", "description": "How the condition of a quantum computer is judged and by whom.", "questions": [ { "id": "condition-assessment-q01", "text": "What identifies and describes the condition of a quantum computer, and in what units or vocabulary?", "kind": "definition", "answer_data": [ "identifiers", "types and classes", "values with units", "explicit unknowns" ] }, { "id": "condition-assessment-q02", "text": "Who or what asserted this about the condition of a quantum computer, by which method, and when was it true?", "kind": "provenance", "answer_data": [ "authority", "method", "evidence", "event time", "knowledge time" ] }, { "id": "condition-assessment-q03", "text": "What may an agent decide or do once the condition of a quantum computer is known, and what must it refuse?", "kind": "action", "answer_data": [ "permitted actions", "preconditions", "refusals", "escalation" ] } ] } ] } ] }, { "id": "place-and-movement", "name": "Place and movement", "description": "Where a quantum computer is, how it got there and where it may go (varies).", "rationale": "A thing that can move needs its position recorded with a time, or every later claim about it is about a place it has left.", "layers": [ { "id": "location-and-placement", "name": "Location and placement", "description": "Position, containment and the reference frame the position is given in.", "findings": [ { "id": "position-and-frame", "name": "Position, container and reference frame", "description": "Where a quantum computer is, and what that position is measured against.", "questions": [ { "id": "position-and-frame-q01", "text": "What identifies and describes the location of a quantum computer, and in what units or vocabulary?", "kind": "definition", "answer_data": [ "identifiers", "types and classes", "values with units", "explicit unknowns" ] }, { "id": "position-and-frame-q02", "text": "Who or what asserted this about the location of a quantum computer, by which method, and when was it true?", "kind": "provenance", "answer_data": [ "authority", "method", "evidence", "event time", "knowledge time" ] }, { "id": "position-and-frame-q03", "text": "What may an agent decide or do once the location of a quantum computer is known, and what must it refuse?", "kind": "action", "answer_data": [ "permitted actions", "preconditions", "refusals", "escalation" ] } ] } ] }, { "id": "movement-and-transfer", "name": "Movement and transfer", "description": "How a quantum computer is carried, installed or relocated.", "findings": [ { "id": "movement-events", "name": "Movement events and constraints", "description": "What counts as a movement, what records it and what limits it.", "questions": [ { "id": "movement-events-q01", "text": "What identifies and describes the movement of a quantum computer, and in what units or vocabulary?", "kind": "definition", "answer_data": [ "identifiers", "types and classes", "values with units", "explicit unknowns" ] }, { "id": "movement-events-q02", "text": "Who or what asserted this about the movement of a quantum computer, by which method, and when was it true?", "kind": "provenance", "answer_data": [ "authority", "method", "evidence", "event time", "knowledge time" ] }, { "id": "movement-events-q03", "text": "What may an agent decide or do once the movement of a quantum computer is known, and what must it refuse?", "kind": "action", "answer_data": [ "permitted actions", "preconditions", "refusals", "escalation" ] } ] } ] } ] }, { "id": "state-and-lifecycle", "name": "State and lifecycle", "description": "The states a quantum computer passes through and the events that move it between them.", "rationale": "Most decisions about a thing depend on what state it is in now, which is a claim with a time on it, not a property.", "layers": [ { "id": "lifecycle-stages", "name": "Lifecycle stages", "description": "From coming into existence to ceasing to be one of these.", "findings": [ { "id": "stages-and-transitions", "name": "Stages and transitions", "description": "The stages worth naming and what moves a quantum computer between them.", "questions": [ { "id": "stages-and-transitions-q01", "text": "What identifies and describes the lifecycle of a quantum computer, and in what units or vocabulary?", "kind": "definition", "answer_data": [ "identifiers", "types and classes", "values with units", "explicit unknowns" ] }, { "id": "stages-and-transitions-q02", "text": "Who or what asserted this about the lifecycle of a quantum computer, by which method, and when was it true?", "kind": "provenance", "answer_data": [ "authority", "method", "evidence", "event time", "knowledge time" ] }, { "id": "stages-and-transitions-q03", "text": "What may an agent decide or do once the lifecycle of a quantum computer is known, and what must it refuse?", "kind": "action", "answer_data": [ "permitted actions", "preconditions", "refusals", "escalation" ] } ] } ] }, { "id": "observations-and-status", "name": "Observations and current status", "description": "What is observed about a quantum computer, how often and by whom.", "findings": [ { "id": "observation-record", "name": "Observation record", "description": "How an observation of a quantum computer is recorded so that it can be superseded rather than overwritten.", "questions": [ { "id": "observation-record-q01", "text": "What identifies and describes an observation of a quantum computer, and in what units or vocabulary?", "kind": "definition", "answer_data": [ "identifiers", "types and classes", "values with units", "explicit unknowns" ] }, { "id": "observation-record-q02", "text": "Who or what asserted this about an observation of a quantum computer, by which method, and when was it true?", "kind": "provenance", "answer_data": [ "authority", "method", "evidence", "event time", "knowledge time" ] }, { "id": "observation-record-q03", "text": "What may an agent decide or do once an observation of a quantum computer is known, and what must it refuse?", "kind": "action", "answer_data": [ "permitted actions", "preconditions", "refusals", "escalation" ] } ] } ] } ] }, { "id": "function-and-principle", "name": "Function and operating principle", "description": "What quantum computer is for and how it achieves it.", "rationale": "Two devices with the same name can work on different principles, and the principle is what predicts failure and constrains use.", "layers": [ { "id": "intended-function", "name": "Intended function", "description": "The job it does, and the jobs it is used for anyway.", "findings": [ { "id": "function-record", "name": "Function, principle and variants", "description": "What it does, how, and which variants do it differently.", "questions": [ { "id": "function-record-q01", "text": "What function does quantum computer perform, on what operating principle, and which variants differ in that principle?", "kind": "definition" }, { "id": "function-record-q02", "text": "What use falls outside the intended function but happens in practice?", "kind": "boundary" } ] } ] }, { "id": "capacity-and-rating", "name": "Capacity and rating", "description": "The numbers that say what it can do and where it stops.", "findings": [ { "id": "ratings", "name": "Ratings and their conditions", "description": "Rated capacity, power, throughput and the conditions each assumes.", "questions": [ { "id": "ratings-q01", "text": "What ratings characterise quantum computer, in what units, and under what stated conditions?", "kind": "measurement" }, { "id": "ratings-q02", "text": "What happens beyond the rating - degradation, refusal, damage - and how is that detected?", "kind": "action" } ] } ] } ] }, { "id": "operation-and-state", "name": "Operation, controls and state", "description": "How quantum computer is operated and what state it is in right now.", "rationale": "An agent acting on a device needs its current state and the controls that change it, not just its specification.", "layers": [ { "id": "controls-and-modes", "name": "Controls and modes", "description": "What can be set, what that changes, and what is interlocked.", "findings": [ { "id": "control-surface", "name": "Control surface and interlocks", "description": "The settings available and the conditions that block them.", "questions": [ { "id": "control-surface-q01", "text": "What controls and modes does quantum computer have, and what does each change?", "kind": "definition" }, { "id": "control-surface-q02", "text": "Which actions are interlocked or forbidden in which state, and what must be true before acting?", "kind": "action" } ] } ] }, { "id": "condition-and-maintenance", "name": "Condition and maintenance", "description": "Wear, service intervals, consumables and the line between working and broken.", "findings": [ { "id": "service-record", "name": "Condition, service and consumables", "description": "What is consumed, what is serviced, and how condition is judged.", "questions": [ { "id": "service-record-q01", "text": "What consumables and service does quantum computer need, at what interval, and on whose authority?", "kind": "measurement" }, { "id": "service-record-q02", "text": "What evidence separates a unit that is working from one that is out of service?", "kind": "boundary" } ] } ] } ] }, { "id": "kind-model-unit", "name": "Kind, model and unit", "description": "Whether a claim about quantum computer is about the kind, a product line, or one physical unit.", "rationale": "This is the boundary most often got wrong for made things, and getting it wrong mixes a catalogue entry with the machine in the yard.", "layers": [ { "id": "level-of-reference", "name": "Level of reference", "description": "The three levels and what belongs at each.", "findings": [ { "id": "level-rules", "name": "What belongs to kind, model and unit", "description": "Which properties are shared by all of them and which are not.", "questions": [ { "id": "level-rules-q01", "text": "Which facts about quantum computer hold for every one of them, which for a model, and which only for one unit?", "kind": "boundary" }, { "id": "level-rules-q02", "text": "What identifies an individual unit, and what should an agent do when it has only the kind?", "kind": "action" } ] } ] }, { "id": "standards-and-conformity", "name": "Standards and conformity", "description": "The standards a working example must meet and who attests it.", "findings": [ { "id": "conformity", "name": "Standards, marks and attestation", "description": "Which standard applies, who certifies, and what the mark means.", "questions": [ { "id": "conformity-q01", "text": "Which standards govern quantum computer, issued by whom, and what does conformity actually assert?", "kind": "provenance" }, { "id": "conformity-q02", "text": "What may an agent conclude from a certification mark, and what may it not?", "kind": "boundary" } ] } ] } ] }, { "id": "provenance-and-evidence", "name": "Provenance, evidence and time", "description": "Where every claim about a quantum computer came from and when it held.", "rationale": "A claim without a source and a time cannot be superseded, only overwritten, and an agent that overwrites loses the ability to explain itself.", "layers": [ { "id": "source-and-authority", "name": "Source and authority", "description": "Who said it, on what evidence, and how strongly.", "findings": [ { "id": "claim-provenance", "name": "Claim provenance and confidence", "description": "The authority behind each claim about a quantum computer and how confident it is.", "questions": [ { "id": "claim-provenance-q01", "text": "What identifies and describes a claim about a quantum computer, and in what units or vocabulary?", "kind": "definition", "answer_data": [ "identifiers", "types and classes", "values with units", "explicit unknowns" ] }, { "id": "claim-provenance-q02", "text": "Who or what asserted this about a claim about a quantum computer, by which method, and when was it true?", "kind": "provenance", "answer_data": [ "authority", "method", "evidence", "event time", "knowledge time" ] }, { "id": "claim-provenance-q03", "text": "What may an agent decide or do once a claim about a quantum computer is known, and what must it refuse?", "kind": "action", "answer_data": [ "permitted actions", "preconditions", "refusals", "escalation" ] } ] } ] }, { "id": "time-and-versions", "name": "Time, versions and supersession", "description": "When a claim was true, when it was learnt, and what replaced it.", "findings": [ { "id": "validity-and-supersession", "name": "Validity period and supersession", "description": "How an old claim about a quantum computer is retired without being erased.", "questions": [ { "id": "validity-and-supersession-q01", "text": "What identifies and describes the validity of a claim about a quantum computer, and in what units or vocabulary?", "kind": "definition", "answer_data": [ "identifiers", "types and classes", "values with units", "explicit unknowns" ] }, { "id": "validity-and-supersession-q02", "text": "Who or what asserted this about the validity of a claim about a quantum computer, by which method, and when was it true?", "kind": "provenance", "answer_data": [ "authority", "method", "evidence", "event time", "knowledge time" ] }, { "id": "validity-and-supersession-q03", "text": "What may an agent decide or do once the validity of a claim about a quantum computer is known, and what must it refuse?", "kind": "action", "answer_data": [ "permitted actions", "preconditions", "refusals", "escalation" ] } ] } ] } ] } ] }, "statistics": { "bundles": 8, "layers": 17, "findings": 19, "questions": 51 } } } }