{ "model": { "rank": 3597, "code": "thing-q121117", "model_id": "vr.tr.supercomputer", "name": "supercomputer", "purpose": "Enable an AI agent to recognise a supercomputer, assess its computational readiness and constraints, and determine which workloads and operational actions it can support.", "family": "Thing Registry", "category": "Physical world and living systems", "status": "research-draft", "kind": "thing", "plane": "PHY", "domain": "PHY.OBJ", "industry": "", "version": "", "url": "/models/thing/q121117/", "tier": 2, "score": 84, "payload": { "layer": "wikidata", "aliases": [ "Intel iPSC", "Elbrus", "Cray Y-MP", "BullSequana", "Pratyush and Mihir", "M-10", "Quantum-centric supercomputing", "SGI Altix", "Cray XT5", "CDC 6500", "vector supercomputer", "ASC Purple", "CDC Cyber", "CDC STAR-100", "Cray XE6", "Cray XT3", "IBM Scalable POWERparallel", "Cray XK7", "Cray XT6", "Tsubame", "HPE SGI 8600", "Hitachi SR8000", "Hitachi SR2201", "Cray T3D", "Intel Paragon", "CDC 6600", "Jean Zay", "BESM", "Blue Gene", "CLUMEQ", "PS-2000", "PS-3000", "IBM 7030 Stretch", "Kraken", "CDC Cyber 70" ], "aliasCount": 35, "merged": 35, "knownIn": 84, "facets": null, "markers": [], "lexicalClass": "", "senseRank": null, "alsoRegisteredAs": null, "source": { "dataset": "wikidata", "item": "Q121117", "url": "https://www.wikidata.org/wiki/Q121117", "license": "CC0 1.0" } }, "research": { "vercy": "1.0-draft", "publication": { "status": "research-draft", "adjudicationStatus": "unreviewed", "publishableCanonical": false, "generatedAt": "2026-09-07T14:39:01Z", "providers": [ "Codex" ], "breadth": "recalled by Codex without web access - no source was read", "missingProviders": [], "pass": 2, "cost": { "grok": { "seconds": 27.7, "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: 01a07c4d-e454-7853-b6be-1de3d6f33848\n--------\nuser\nDescribe what is already known about one registered thing. Answer as JSON only, no prose around it.\n\nThing: supercomputer\nSense to describe: (none recorded)\nDomain code: PHY.OBJ\nAlso known as: (none)\n\n\nContext for this batch of 1001 things:\n# Batch 004: 1001 r", "usd": 0, "recall": true }, "codex": { "seconds": 66.9, "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: 01a07c4d-e44e-7402-b457-176001f9a119\n--------\nuser\nYou are drafting a Vercy meta-model for one registered thing. Answer as JSON only, no prose around it.\n\nThing: supercomputer\nRegistry id: vr.tr.supercomputer\nPlane / domain: PHY / PHY.OBJ\nRegistry definition: (none recorded)\nNames folded into this entry: (none" } } }, "metaModel": { "id": "THING-Q121117", "registryId": "vr.tr.supercomputer", "name": "supercomputer", "version": "0.1.0-research.1", "entryKind": "thing", "family": "Thing Registry", "domain": [ "PHY.OBJ" ], "status": "research-draft" }, "canonicalUrl": "https://ver.cy/models/thing/q121117/", "model": { "registry_id": "vr.tr.supercomputer", "name": "supercomputer", "purpose": "Enable an AI agent to recognise a supercomputer, assess its computational readiness and constraints, and determine which workloads and operational actions it can support.", "definition": "A supercomputer is a computing system designed to deliver exceptionally high computational performance relative to contemporary general-purpose computers, typically by coordinating large numbers of processors through high-performance interconnects.", "scope_statement": "This model owns the supercomputer as a kind of integrated physical computing system engineered for demanding computation through coordinated parallel resources, including its architecture, workload capabilities, operational states and infrastructure dependencies; particular designs and installed systems are instances.", "in_scope": [ "System boundaries across compute nodes, accelerators, interconnects and dedicated supporting resources", "Parallel execution capabilities and workload-dependent performance", "Memory, storage and data-movement constraints affecting computation", "Resource allocation, software compatibility and execution readiness", "Power, cooling, reliability and maintenance constraints on system operation" ], "out_of_scope": [ "Scientific validity and interpretation of simulations or analyses", "Individual processor, accelerator and storage-device designs", "General-purpose cloud service offerings and commercial pricing", "Data-centre buildings, utility networks and shared facility infrastructure", "Institutional governance and ownership of research data" ], "distinguishing_features": [ "Establish whether the system is engineered for demanding computation using coordinated parallel resources, rather than identifying it from processor count or marketing terminology alone.", "Distinguish a supercomputer from a single powerful workstation through its system architecture, resource coordination and intended workload scale.", "Distinguish an integrated computing system from loosely federated machines by examining interconnect coupling, scheduling and operational boundaries.", "Treat cluster architecture as compatible with being a supercomputer; assess computational capability and integration rather than making the labels mutually exclusive.", "Assess exceptional performance relative to a stated period and workload class, rather than imposing an unexplained permanent performance threshold." ], "characteristics": [ { "name": "Architectural configuration", "kind": "category", "unit_or_values": "Processor families, CPU-only or heterogeneous configuration, node classes and accelerator types", "why_it_matters": "Determines executable compatibility and the kinds of parallel work the system can support." }, { "name": "Installed and available compute resources", "kind": "measurement", "unit_or_values": "Counts of nodes, processor sockets, cores and accelerators, with installed and available counts separated", "why_it_matters": "Separates nominal system scale from resources currently usable for execution." }, { "name": "Measured computational performance", "kind": "measurement", "unit_or_values": "FLOP/s or workload-specific throughput and elapsed seconds, with precision, benchmark, configuration and date", "why_it_matters": "Supports meaningful capability comparisons without treating theoretical peak performance as achieved performance." }, { "name": "Memory capacity and accessibility", "kind": "measurement", "unit_or_values": "Bytes per memory tier and node, with sharing boundaries and usable capacity", "why_it_matters": "Determines whether a workload fits and how its data must be partitioned." }, { "name": "Interconnect capability", "kind": "measurement", "unit_or_values": "Bandwidth in bytes/s and latency in seconds, with topology, message size and measurement conditions", "why_it_matters": "Constrains communication-intensive parallel workloads and scaling." }, { "name": "Storage and checkpoint capability", "kind": "measurement", "unit_or_values": "Usable bytes, sustained read/write bytes/s and checkpoint or restart seconds under specified concurrency", "why_it_matters": "Determines data staging feasibility and recovery costs." }, { "name": "Operational readiness", "kind": "state", "unit_or_values": "Available, partially available, degraded, draining, maintenance, shut down or unknown, assessed by partition", "why_it_matters": "Prevents an agent from treating installed capacity as immediately schedulable." }, { "name": "Electrical demand", "kind": "measurement", "unit_or_values": "Watts at idle and specified loads, with measurement boundary and applicable power cap", "why_it_matters": "Constrains feasible operating configurations and energy assessment." }, { "name": "Cooling dependency", "kind": "relation", "unit_or_values": "Required cooling services and their documented temperature, flow and heat-removal limits", "why_it_matters": "Connects safe computational operation to facility services." }, { "name": "Execution environment", "kind": "relation", "unit_or_values": "Supported scheduler, operating environment, compilers, parallel runtimes, accelerator runtimes and versions", "why_it_matters": "Determines whether a workload can be built, admitted and executed correctly." } ], "affordances": [ "Match a workload's memory, communication, precision and accelerator requirements to suitable system partitions.", "Estimate usable scale and runtime from relevant measurements and scaling evidence.", "Prepare and submit authorised jobs within scheduler, allocation and power constraints.", "Assess whether degraded components permit continued execution, checkpointing or job rescheduling.", "Plan authorised draining, maintenance and return-to-service actions using documented dependencies and acceptance checks.", "Compare performance and energy measurements while preserving workload, date and system-boundary context." ] }, "sources": [], "structure": { "bundles": [ { "id": "system-identity-and-architecture", "name": "System identity and architecture", "description": "Establishes what constitutes the supercomputer and how its computing resources cooperate.", "rationale": "Neither a product name nor a collection of processors establishes the identity or capability of an integrated supercomputer.", "layers": [ { "id": "classification-and-boundary", "name": "Classification and boundary", "description": "Records the evidence for classification and the limits of the computing system.", "findings": [ { "id": "supercomputer-classification", "name": "Supercomputer classification", "description": "Records the intended workload class and contextual evidence supporting the designation without assuming a universal numerical cutoff.", "questions": [ { "text": "What computational role and architectural evidence distinguish this kind from a workstation, ordinary server cluster or distributed computing federation?", "kind": "definition", "id": "supercomputer-classification-q01" }, { "text": "Which compute partitions, interconnects, storage systems and management resources belong to the system, and which are shared external services?", "kind": "boundary", "id": "supercomputer-classification-q02" }, { "text": "Which dated technical documentation supports its classification and declared system boundary?", "kind": "provenance", "id": "supercomputer-classification-q03" } ] } ] }, { "id": "parallel-resource-organization", "name": "Parallel resource organization", "description": "Describes node heterogeneity, memory locality and communication structure.", "findings": [ { "id": "compute-and-memory-topology", "name": "Compute and memory topology", "description": "Captures how processors, accelerators and memory are connected and which resources a job can access together.", "questions": [ { "text": "Which node classes exist, and how many processors, accelerators and memory tiers does each provide?", "kind": "measurement", "id": "compute-and-memory-topology-q01" }, { "text": "Where are the memory-sharing and interconnect boundaries that require explicit communication or data transfer?", "kind": "boundary", "id": "compute-and-memory-topology-q02" } ] } ] } ] }, { "id": "workload-fit-and-performance", "name": "Workload fit and performance", "description": "Connects advertised computational capability to the demands and measured behaviour of actual workloads.", "rationale": "A single peak-performance number cannot establish whether a supercomputer suits a particular computation.", "layers": [ { "id": "execution-fit", "name": "Execution fit", "description": "Assesses resource and software compatibility before allocating substantial compute capacity.", "findings": [ { "id": "parallel-workload-compatibility", "name": "Parallel workload compatibility", "description": "Records the constraints determining whether and where a workload can execute.", "questions": [ { "text": "What memory per process, numerical precision, accelerator support and communication pattern does the proposed workload require?", "kind": "measurement", "id": "parallel-workload-compatibility-q01" }, { "text": "Which partition and supported compiler or runtime environment can satisfy those requirements?", "kind": "action", "id": "parallel-workload-compatibility-q02" } ] } ] }, { "id": "performance-evidence", "name": "Performance evidence", "description": "Preserves the conditions needed to interpret throughput, runtime and scaling measurements.", "findings": [ { "id": "sustained-performance-and-scaling", "name": "Sustained performance and scaling", "description": "Separates theoretical capability from observed results and identifies the scale at which additional resources remain useful.", "questions": [ { "text": "What sustained performance was measured, using which workload, input size, numerical precision, resource count and power setting?", "kind": "measurement", "id": "sustained-performance-and-scaling-q01" }, { "text": "How does runtime change as resource count increases, and does the evidence use a fixed problem size or a growing one?", "kind": "measurement", "id": "sustained-performance-and-scaling-q02" }, { "text": "Which reproducible report or execution record supports the result and identifies its date and configuration?", "kind": "provenance", "id": "sustained-performance-and-scaling-q03" } ] } ] } ] }, { "id": "data-and-job-operation", "name": "Data and job operation", "description": "Models the movement, admission and persistence of computational work across shared resources.", "rationale": "Usable supercomputer capacity depends on data access and scheduled availability as well as installed processors.", "layers": [ { "id": "data-paths-and-persistence", "name": "Data paths and persistence", "description": "Distinguishes working memory, temporary storage, checkpoint storage and external repositories.", "findings": [ { "id": "staging-and-checkpoint-path", "name": "Staging and checkpoint path", "description": "Records whether input staging, output collection and recovery data can be supported at the intended job scale.", "questions": [ { "text": "What usable capacity and sustained throughput are available along the job's staging and checkpoint paths under expected concurrent use?", "kind": "measurement", "id": "staging-and-checkpoint-path-q01" }, { "text": "Which storage locations persist after job completion or node failure, and which are temporary or subject to deletion policies?", "kind": "boundary", "id": "staging-and-checkpoint-path-q02" }, { "text": "How should the job stage data and write recoverable checkpoints within its storage quota and wall-time limit?", "kind": "action", "id": "staging-and-checkpoint-path-q03" } ] } ] }, { "id": "resource-admission", "name": "Resource admission", "description": "Connects available partitions to the permissions and scheduler rules governing execution.", "findings": [ { "id": "schedulable-job-allocation", "name": "Schedulable job allocation", "description": "Distinguishes installed, healthy, allocated and currently schedulable resources.", "questions": [ { "text": "Which healthy resources can be requested together, and what queue, reservation, allocation and wall-time rules apply?", "kind": "boundary", "id": "schedulable-job-allocation-q01" }, { "text": "What authorisation and scheduler request are required to submit, resize where supported, cancel or restart the job?", "kind": "action", "id": "schedulable-job-allocation-q02" } ] } ] } ] }, { "id": "power-thermal-and-reliability", "name": "Power, thermal limits and reliability", "description": "Determines whether the system can sustain computation safely and recover from faults.", "rationale": "Large parallel jobs depend on coordinated electrical, cooling and component health conditions across many resources.", "layers": [ { "id": "operating-envelope", "name": "Operating envelope", "description": "Records power and cooling limits alongside protective controls and applicable requirements.", "findings": [ { "id": "power-and-cooling-readiness", "name": "Power and cooling readiness", "description": "Connects permitted load to documented electrical and thermal limits at an explicit system boundary.", "questions": [ { "text": "What electrical demand and heat-removal requirement accompany the intended configuration and load, and where are they measured?", "kind": "measurement", "id": "power-and-cooling-readiness-q01" }, { "text": "Which documented thresholds and interlocks trigger throttling, job suspension or shutdown, and what actions may an agent initiate?", "kind": "action", "id": "power-and-cooling-readiness-q02" }, { "text": "Which manufacturer requirements and applicable electrical, cooling or safety standards govern this installation, with issuing bodies and editions recorded?", "kind": "provenance", "id": "power-and-cooling-readiness-q03" } ] } ] }, { "id": "faults-and-service", "name": "Faults and service", "description": "Assesses partial failure, recovery readiness and maintenance effects on running jobs.", "findings": [ { "id": "degraded-operation-and-recovery", "name": "Degraded operation and recovery", "description": "Records how component faults affect usable partitions and what evidence is required before returning resources to service.", "questions": [ { "text": "Which node, accelerator, memory, interconnect or storage faults are present, and what jobs or partitions do they affect?", "kind": "measurement", "id": "degraded-operation-and-recovery-q01" }, { "text": "When should affected resources be drained or isolated, and can impacted jobs restart from validated checkpoints?", "kind": "action", "id": "degraded-operation-and-recovery-q02" }, { "text": "What maintenance, consumable replacement where applicable, and acceptance checks are required before repaired resources rejoin the scheduler?", "kind": "action", "id": "degraded-operation-and-recovery-q03" } ] } ] } ] }, { "id": "evidence-and-external-alignment", "name": "Evidence and external alignment", "description": "What the world already says about this thing, gathered so the model can be checked against it.", "rationale": "A model that cannot be lined up against existing standards, identifiers and practice cannot be adopted by anyone who already uses them.", "layers": [ { "id": "reported-evidence", "name": "Reported evidence", "description": "Findings from the breadth pass, kept separate from the structural claims.", "findings": [ { "id": "evidence-confidence-notes", "name": "Check these first", "description": "Recalled without web access and unsourced; every item is a lead to verify.", "evidence": [ "This describes the equipment class, not a named installation, vendor product family, or individual machine.", "There is no timeless performance threshold defining a supercomputer; numerical capacity ranges and rankings require dated research.", "MPI and OpenMP are common programming specifications, not mandatory supercomputer certifications; equipment-safety applicability requires checking the installation and jurisdiction." ], "questions": [ { "id": "evidence-confidence-notes-q01", "text": "Which of these check these first hold for the sense of supercomputer this model covers, and on what evidence?", "kind": "provenance" } ] }, { "id": "evidence-kinds", "name": "Kinds and varieties", "description": "Recalled without web access and unsourced; every item is a lead to verify.", "evidence": [ "CPU-based massively parallel systems", "GPU-accelerated systems", "Vector supercomputers", "Special-purpose supercomputers" ], "questions": [ { "id": "evidence-kinds-q01", "text": "Which of these kinds and varieties hold for the sense of supercomputer this model covers, and on what evidence?", "kind": "provenance" } ] }, { "id": "evidence-standards-and-regulation", "name": "Standards and regulation", "description": "Recalled without web access and unsourced; every item is a lead to verify.", "evidence": [ "MPI Forum: Message Passing Interface specification for communication among parallel processes.", "OpenMP Architecture Review Board: OpenMP specification for shared-memory parallel programming and accelerator offloading.", "IEC 62368-1, issued by the International Electrotechnical Commission: safety requirements applicable to information and communication technology equipment." ], "questions": [ { "id": "evidence-standards-and-regulation-q01", "text": "Which of these standards and regulation hold for the sense of supercomputer this model covers, and on what evidence?", "kind": "provenance" } ] }, { "id": "evidence-real-world-use", "name": "Real-world use", "description": "Recalled without web access and unsourced; every item is a lead to verify.", "evidence": [ "Weather forecasting and climate simulation", "Computational fluid dynamics and engineering simulation", "Molecular dynamics and materials modelling", "Astrophysics and fundamental physics simulations", "Large-scale machine learning and scientific data analysis" ], "questions": [ { "id": "evidence-real-world-use-q01", "text": "Which of these real-world use hold for the sense of supercomputer this model covers, and on what evidence?", "kind": "provenance" } ] }, { "id": "evidence-measurements", "name": "Typical measurements", "description": "Recalled without web access and unsourced; every item is a lead to verify.", "evidence": [ { "quantity": "Floating-point computational throughput", "typical_range": "System-, precision-, and workload-dependent; distinguish theoretical peak from measured sustained performance", "unit": "FLOP/s" }, { "quantity": "Electrical power demand", "typical_range": "Large installations can require megawatts; distinguish computing equipment from total facility demand", "unit": "MW" }, { "quantity": "Application execution time", "typical_range": "Workload-dependent; compare the same problem and numerical requirements", "unit": "s" }, { "quantity": "Energy efficiency", "typical_range": "Benchmark-, numerical-precision-, and measurement-boundary-dependent", "unit": "FLOP/J" } ], "questions": [ { "id": "evidence-measurements-q01", "text": "Which of these typical measurements hold for the sense of supercomputer this model covers, and on what evidence?", "kind": "provenance" } ] }, { "id": "evidence-failure-modes-and-hazards", "name": "Failure modes and hazards", "description": "Recalled without web access and unsourced; every item is a lead to verify.", "evidence": [ "Processor, memory, or network failures can interrupt distributed jobs and require recovery from checkpoints.", "Cooling failures can cause thermal throttling, emergency shutdown, or equipment damage.", "Power interruptions or distribution faults can halt computation and damage equipment.", "Storage failures and silent data corruption can invalidate results unless detected through integrity checks and validation.", "High electrical fault energy and heavy equipment create maintenance hazards requiring appropriate isolation and handling procedures." ], "questions": [ { "id": "evidence-failure-modes-and-hazards-q01", "text": "Which of these failure modes and hazards hold for the sense of supercomputer this model covers, and on what evidence?", "kind": "provenance" } ] }, { "id": "evidence-regional-variation", "name": "Regional variation", "description": "Recalled without web access and unsourced; every item is a lead to verify.", "evidence": [ "Electricity prices, supply reliability, and climate influence location and cooling design.", "National export controls can affect access to advanced processors and interconnect technology.", "Electrical installation and building requirements depend on the jurisdiction hosting the facility." ], "questions": [ { "id": "evidence-regional-variation-q01", "text": "Which of these regional variation hold for the sense of supercomputer this model covers, and on what evidence?", "kind": "provenance" } ] }, { "id": "evidence-neighbours", "name": "Neighbouring kinds and how to tell them apart", "description": "Recalled without web access and unsourced; every item is a lead to verify.", "evidence": [ { "name": "computer cluster", "difference": "A cluster describes interconnected computers working together; only some clusters deliver performance that warrants classification as a supercomputer." }, { "name": "mainframe", "difference": "A mainframe primarily emphasizes reliable, high-volume transaction and data processing; a supercomputer primarily emphasizes computationally intensive workloads." }, { "name": "high-performance computing", "difference": "High-performance computing is a practice and field of computing; a supercomputer is a physical computing system used within it." }, { "name": "data centre", "difference": "A data centre is a facility housing computing infrastructure and may contain a supercomputer." }, { "name": "quantum computer", "difference": "A quantum computer operates on quantum states; supercomputer classification concerns computational performance and does not imply quantum operation." } ], "questions": [ { "id": "evidence-neighbours-q01", "text": "Which of these neighbouring kinds and how to tell them apart hold for the sense of supercomputer this model covers, and on what evidence?", "kind": "provenance" } ] } ] } ] } ] }, "openQuestions": [ "Which authoritative definition should anchor the registry entry, and how should classification account for changing computational capability over time?", "Where should the boundary fall for cloud-hosted HPC systems, federated resources and facilities with several independently scheduled partitions?", "Which benchmark families and workload measurements provide adequate evidence across simulation, data analysis and AI workloads without implying that their scores are interchangeable?", "Which electrical, thermal, electromagnetic and safety standards apply across the installations this model must cover, and which requirements belong solely to the facility model?", "What sourced capacity ranges, failure evidence and maintenance requirements are representative enough to include without presenting one architecture or generation as universal?" ], "statistics": { "bundles": 5, "layers": 9, "findings": 16, "questions": 29 } }, "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 supercomputer, record what state it is in, and decide what may be done with it.", "whatItIs": "Enable an AI agent to recognise a supercomputer, assess its computational readiness and constraints, and determine which workloads and operational actions it can support.", "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: Intel iPSC, Elbrus, Cray Y-MP, BullSequana, Pratyush and Mihir, M-10, Quantum-centric supercomputing, SGI Altix, Cray XT5, CDC 6500, vector supercomputer, ASC Purple.", "35 finer distinctions are held as aliases rather than separate entries, because telling them apart needs a task that asks for it.", "Described in 84 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 supercomputer, 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": [ "Intel iPSC", "Elbrus", "Cray Y-MP", "BullSequana", "Pratyush and Mihir", "M-10", "Quantum-centric supercomputing", "SGI Altix", "Cray XT5", "CDC 6500", "vector supercomputer", "ASC Purple" ] } ], "standing": "Described in 84 Wikipedia languages, which measures how widely it is written about rather than how important or how common it is. 35 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 supercomputer from another, and a supercomputer 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 supercomputer, 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 supercomputer, 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 supercomputer 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 supercomputer, 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 supercomputer, 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 supercomputer 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 supercomputer 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 supercomputer, 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 supercomputer, 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 supercomputer 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 supercomputer from the things most often confused with it.", "questions": [ { "id": "distinguishing-features-q01", "text": "What identifies and describes what distinguishes a supercomputer, 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 supercomputer, 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 supercomputer 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 supercomputer 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 supercomputer, 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 supercomputer, 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 supercomputer 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 supercomputer is built from and which parts are replaceable.", "questions": [ { "id": "parts-and-materials-q01", "text": "What identifies and describes the composition of a supercomputer, 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 supercomputer, 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 supercomputer 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 supercomputer is judged and by whom.", "questions": [ { "id": "condition-assessment-q01", "text": "What identifies and describes the condition of a supercomputer, 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 supercomputer, 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 supercomputer 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 supercomputer 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 supercomputer is, and what that position is measured against.", "questions": [ { "id": "position-and-frame-q01", "text": "What identifies and describes the location of a supercomputer, 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 supercomputer, 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 supercomputer 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 supercomputer 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 supercomputer, 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 supercomputer, 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 supercomputer 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 supercomputer 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 supercomputer between them.", "questions": [ { "id": "stages-and-transitions-q01", "text": "What identifies and describes the lifecycle of a supercomputer, 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 supercomputer, 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 supercomputer 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 supercomputer, how often and by whom.", "findings": [ { "id": "observation-record", "name": "Observation record", "description": "How an observation of a supercomputer 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 supercomputer, 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 supercomputer, 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 supercomputer 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 supercomputer 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 supercomputer 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 supercomputer, 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 supercomputer 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 supercomputer 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 supercomputer 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 supercomputer 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 supercomputer 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 supercomputer, 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 supercomputer 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 supercomputer and how confident it is.", "questions": [ { "id": "claim-provenance-q01", "text": "What identifies and describes a claim about a supercomputer, 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 supercomputer, 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 supercomputer 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 supercomputer is retired without being erased.", "questions": [ { "id": "validity-and-supersession-q01", "text": "What identifies and describes the validity of a claim about a supercomputer, 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 supercomputer, 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 supercomputer 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 } } } }