{ "model": { "rank": 5564, "code": "thing-q183484", "model_id": "vr.tr.graphics-processing-unit", "name": "graphics processing unit", "purpose": "Let an agent explain GPUs, relay architecture, history, uses and policy debates from computer architecture and industry sources with positions attributed, flag product and bridge chip aliases, and distinguish GPUs from CPUs, systems on chips, AI accelerators such as TPUs, graphics cards as boards and FPGAs, without purchase or investment advice.", "family": "Thing Registry", "category": "Physical world and living systems", "status": "research-draft", "kind": "thing", "plane": "PHY", "domain": "PHY.OBJ", "industry": "", "version": "", "url": "/models/thing/q183484/", "tier": 2, "score": 66, "payload": { "layer": "wikidata", "aliases": [ "ATI Rialto", "Qualcomm Snapdragon 670", "Snapdragon 480 Plus 5G", "Qualcomm Snapdragon 820", "Qualcomm Snapdragon 660", "Qualcomm Snapdragon 630", "Qualcomm Snapdragon 425", "Qualcomm Snapdragon 435", "Qualcomm Snapdragon S1 MSM7225A", "RCP", "Radeon", "PowerVR SGX543MP2", "PowerVR SGX543MP4", "PowerVR SGX543MP3", "PowerVR SGX554MP4", "PowerVR G6430", "PowerVR GX6650", "RIVA TNT2", "GeForce 3 series", "Adreno 509", "Standard Television Interface Chip", "Ardeno 630", "Adreno 305", "Adreno 650", "Intel Arc", "GA102", "Mali-400 MP", "Adreno 618", "Asahi Kasei AK8000", "Adreno 610", "Mali-400 MP1", "Mali-400 MP2", "Vivante GC7000UL", "PowerVR SGX544MP2", "Nvidia Titan", "ATI Xenos", "Mali-G52", "Imagination PowerVR GX6250", "Imagination PowerVR GX6450", "PowerVR Series 7XT GT7600" ], "aliasCount": 105, "merged": 105, "knownIn": 66, "facets": null, "markers": [], "lexicalClass": "", "senseRank": null, "alsoRegisteredAs": null, "source": { "dataset": "wikidata", "item": "Q183484", "url": "https://www.wikidata.org/wiki/Q183484", "license": "CC0 1.0" } }, "research": { "vercy": "1.0-draft", "publication": { "status": "research-draft", "adjudicationStatus": "unreviewed", "publishableCanonical": false, "generatedAt": "2026-09-13T23:16:03Z", "providers": [ "Claude" ], "breadth": "written by Claude from model knowledge without web access - no source was read, every claim is a lead to verify", "pass": 2, "wave": 4, "engine": "claude" }, "metaModel": { "id": "THING-Q183484", "registryId": "vr.tr.graphics-processing-unit", "name": "graphics processing unit", "version": "0.2.0-wave.4", "entryKind": "thing", "family": "Thing Registry", "domain": [ "PHY.OBJ" ], "status": "research-draft" }, "canonicalUrl": "https://ver.cy/models/thing/q183484/", "model": { "registry_id": "vr.tr.graphics-processing-unit", "name": "graphics processing unit", "purpose": "Let an agent explain GPUs, relay architecture, history, uses and policy debates from computer architecture and industry sources with positions attributed, flag product and bridge chip aliases, and distinguish GPUs from CPUs, systems on chips, AI accelerators such as TPUs, graphics cards as boards and FPGAs, without purchase or investment advice.", "definition": "A specialised processor designed to accelerate rendering of images and to perform many calculations in parallel, originating in graphics accelerators of the 1980s and 1990s, with Nvidia marketing the GeForce 256 as the first GPU in 1999, now used as discrete graphics cards, integrated GPUs within CPUs and mobile system-on-chip designs, and widely applied to general-purpose computing, scientific simulation, cryptocurrency mining and training artificial intelligence models; the registry aliases name Qualcomm Snapdragon system-on-chip products, which contain Adreno GPUs but are whole chips and instances, and the ATI Rialto, a PCI Express bridge chip, which appear misfiled. GPU export controls and supply constraints are subjects of policy debate, attributed.", "what_it_is_for": "Parallel computation and graphics rendering.", "affordances": [ "explain architecture and history", "relay uses in graphics and AI", "present policy debates with attribution", "flag product aliases" ], "distinguishing_features": [ "Massive parallelism", "High memory bandwidth", "Graphics and compute", "Strategic technology" ], "appearance": "Chips on graphics cards with heatsinks and fans, or regions within CPUs and mobile chips.", "visual_identification": [ "Parallel processor for graphics and compute", "ATI Rialto, Qualcomm Snapdragon 670, Snapdragon 480 Plus 5G, Qualcomm Snapdragon 820, Qualcomm Snapdragon 660, Qualcomm Snapdragon 630", "CPUs handle general sequential work; SoCs combine many components; TPUs are dedicated AI accelerators; graphics cards are boards; FPGAs are reconfigurable" ], "physical_properties": [ { "quantity": "GeForce 256 marketed as GPU", "typical_range": "1999", "unit": "year", "note": "Nvidia" }, { "quantity": "CUDA released", "typical_range": "2007", "unit": "year", "note": "general-purpose GPU computing" }, { "quantity": "US AI chip export controls", "typical_range": "from 2022", "unit": "note", "note": "check current rules" } ], "families_and_kinds": [ "discrete GPUs", "integrated GPUs", "mobile GPUs in SoCs", "data centre GPUs", "workstation GPUs" ], "related_models": [ { "relation": "is a kind of", "target": "coprocessor", "why": "in registry terms" }, { "relation": "is programmed with", "target": "CUDA", "why": "among others" }, { "relation": "is contrasted with", "target": "central processing unit", "why": "" }, { "relation": "is contrasted with", "target": "system on a chip", "why": "Snapdragon aliases" } ], "identifiers": [], "standards_and_regulation": [ "US and allied export controls on advanced chips", "Graphics APIs such as Vulkan, DirectX and OpenGL" ], "failure_modes_and_hazards": [ "Treating SoC products as GPUs", "Giving investment or purchase advice", "Partisan framing of export controls" ], "in_scope": [], "out_of_scope": [], "characteristics": [] }, "sources": [], "structure": { "bundles": [ { "id": "understand", "name": "Understand", "description": "What a GPU is.", "rationale": "Definition.", "layers": [ { "id": "definition", "name": "Definition", "description": "Definition.", "findings": [ { "id": "definition-finding", "name": "Definition", "description": "Definition.", "questions": [ { "text": "What is a GPU, and how does it differ from CPUs, SoCs, TPUs, graphics cards and FPGAs?", "kind": "definition" }, { "text": "Is the question about gaming, AI computing, buying hardware or policy?", "kind": "boundary" } ] } ] }, { "id": "aliases", "name": "Aliases", "description": "Product aliases.", "findings": [ { "id": "aliases-finding", "name": "Aliases", "description": "Aliases.", "questions": [ { "text": "What are the Snapdragon chips and ATI Rialto, and why are they not GPU kinds?", "kind": "definition" }, { "text": "Which entry fits the specific product?", "kind": "action" } ] } ] } ] }, { "id": "architecture", "name": "Architecture", "description": "Architecture.", "rationale": "Science.", "layers": [ { "id": "parallel", "name": "Parallelism", "description": "Parallel design.", "findings": [ { "id": "parallel-finding", "name": "Parallelism", "description": "Parallelism.", "questions": [ { "text": "Why are GPUs good at parallel workloads such as matrix operations?", "kind": "provenance" }, { "text": "Which references are standard?", "kind": "provenance" } ] } ] }, { "id": "memory", "name": "Memory", "description": "Memory and bandwidth.", "findings": [ { "id": "memory-finding", "name": "Memory", "description": "Memory.", "questions": [ { "text": "How do GDDR and high-bandwidth memory affect GPU performance?", "kind": "provenance" }, { "text": "Which sources are cited?", "kind": "provenance" } ] } ] } ] }, { "id": "uses", "name": "Uses", "description": "Uses.", "rationale": "Sources.", "layers": [ { "id": "graphics", "name": "Graphics", "description": "Rendering.", "findings": [ { "id": "graphics-finding", "name": "Graphics", "description": "Graphics.", "questions": [ { "text": "How do GPUs render 3D graphics through pipelines and shaders?", "kind": "provenance" }, { "text": "Which entry fits graphics pipeline?", "kind": "action" } ] } ] }, { "id": "ai", "name": "AI", "description": "AI training.", "findings": [ { "id": "ai-finding", "name": "AI", "description": "AI.", "questions": [ { "text": "Why did GPUs become central to deep learning after 2012?", "kind": "provenance" }, { "text": "Which entry fits deep learning?", "kind": "action" } ] } ] } ] }, { "id": "context", "name": "Context", "description": "Policy and industry.", "rationale": "Attribution.", "layers": [ { "id": "exports", "name": "Export controls", "description": "Export controls.", "findings": [ { "id": "exports-finding", "name": "Export controls", "description": "Export controls.", "questions": [ { "text": "What do governments, companies and analysts argue about GPU export controls, with positions attributed?", "kind": "provenance" }, { "text": "Is the presentation neutral and current?", "kind": "boundary" } ] } ] }, { "id": "mining", "name": "Mining", "description": "Cryptocurrency mining.", "findings": [ { "id": "mining-finding", "name": "Mining", "description": "Mining.", "questions": [ { "text": "How did cryptocurrency mining affect GPU supply, as reported?", "kind": "provenance" }, { "text": "Which entry fits cryptocurrency mining?", "kind": "action" } ] } ] } ] } ] }, "openQuestions": [ "The registry aliases for Snapdragon products and ATI Rialto should be moved to their own entries", "Should data centre GPUs be a separate entry?", "How should export control rules be kept current?" ], "statistics": { "bundles": 4, "layers": 8, "findings": 8, "questions": 16 } }, "draft": { "generator": "vr.draft.v3", "status": "draft-generated", "researched": false, "archetype": "unit, quantity or measure", "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 graphics processing unit, record what state it is in, and decide what may be done with it.", "whatItIs": "Let an agent explain GPUs, relay architecture, history, uses and policy debates from computer architecture and industry sources with positions attributed, flag product and bridge chip aliases, and distinguish GPUs from CPUs, systems on chips, AI accelerators such as TPUs, graphics cards as boards and FPGAs, without purchase or investment advice.", "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: ATI Rialto, Qualcomm Snapdragon 670, Snapdragon 480 Plus 5G, Qualcomm Snapdragon 820, Qualcomm Snapdragon 660, Qualcomm Snapdragon 630, Qualcomm Snapdragon 425, Qualcomm Snapdragon 435, Qualcomm Snapdragon S1 MSM7225A, RCP, Radeon, PowerVR SGX543MP2.", "105 finer distinctions are held as aliases rather than separate entries, because telling them apart needs a task that asks for it.", "Described in 66 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 graphics processing unit, 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": [ "Nothing to see: a unit is a convention. What is seen is an instrument reading in it." ], "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": [ "ATI Rialto", "Qualcomm Snapdragon 670", "Snapdragon 480 Plus 5G", "Qualcomm Snapdragon 820", "Qualcomm Snapdragon 660", "Qualcomm Snapdragon 630", "Qualcomm Snapdragon 425", "Qualcomm Snapdragon 435", "Qualcomm Snapdragon S1 MSM7225A", "RCP", "Radeon", "PowerVR SGX543MP2" ] } ], "standing": "Described in 66 Wikipedia languages, which measures how widely it is written about rather than how important or how common it is. 105 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 graphics processing unit from another, and a graphics processing unit 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 graphics processing unit, 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 graphics processing unit, 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 graphics processing unit 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 graphics processing unit, 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 graphics processing unit, 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 graphics processing unit 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 graphics processing unit 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 graphics processing unit, 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 graphics processing unit, 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 graphics processing unit 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 graphics processing unit from the things most often confused with it.", "questions": [ { "id": "distinguishing-features-q01", "text": "What identifies and describes what distinguishes a graphics processing unit, 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 graphics processing unit, 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 graphics processing unit 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 graphics processing unit 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 graphics processing unit, 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 graphics processing unit, 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 graphics processing unit 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 graphics processing unit is built from and which parts are replaceable.", "questions": [ { "id": "parts-and-materials-q01", "text": "What identifies and describes the composition of a graphics processing unit, 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 graphics processing unit, 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 graphics processing unit 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 graphics processing unit is judged and by whom.", "questions": [ { "id": "condition-assessment-q01", "text": "What identifies and describes the condition of a graphics processing unit, 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 graphics processing unit, 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 graphics processing unit 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 graphics processing unit 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 graphics processing unit is, and what that position is measured against.", "questions": [ { "id": "position-and-frame-q01", "text": "What identifies and describes the location of a graphics processing unit, 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 graphics processing unit, 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 graphics processing unit 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 graphics processing unit 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 graphics processing unit, 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 graphics processing unit, 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 graphics processing unit 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 graphics processing unit 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 graphics processing unit between them.", "questions": [ { "id": "stages-and-transitions-q01", "text": "What identifies and describes the lifecycle of a graphics processing unit, 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 graphics processing unit, 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 graphics processing unit 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 graphics processing unit, how often and by whom.", "findings": [ { "id": "observation-record", "name": "Observation record", "description": "How an observation of a graphics processing unit 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 graphics processing unit, 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 graphics processing unit, 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 graphics processing unit is known, and what must it refuse?", "kind": "action", "answer_data": [ "permitted actions", "preconditions", "refusals", "escalation" ] } ] } ] } ] }, { "id": "use-and-operation", "name": "Use and operation", "description": "What can be done with a graphics processing unit and what it takes to do it.", "rationale": "An agent that can recognise a thing but not act on it has only half a model.", "layers": [ { "id": "intended-use", "name": "Intended use and function", "description": "What a graphics processing unit is for, and what it is used for anyway.", "findings": [ { "id": "function-and-purpose", "name": "Function, purpose and misuse", "description": "The function a graphics processing unit performs and the uses that fall outside it.", "questions": [ { "id": "function-and-purpose-q01", "text": "What identifies and describes the use of a graphics processing unit, and in what units or vocabulary?", "kind": "definition", "answer_data": [ "identifiers", "types and classes", "values with units", "explicit unknowns" ] }, { "id": "function-and-purpose-q02", "text": "Who or what asserted this about the use of a graphics processing unit, by which method, and when was it true?", "kind": "provenance", "answer_data": [ "authority", "method", "evidence", "event time", "knowledge time" ] }, { "id": "function-and-purpose-q03", "text": "What may an agent decide or do once the use of a graphics processing unit is known, and what must it refuse?", "kind": "action", "answer_data": [ "permitted actions", "preconditions", "refusals", "escalation" ] } ] } ] }, { "id": "handling-and-procedure", "name": "Handling and procedure", "description": "The steps, skills and tools involved in using a graphics processing unit.", "findings": [ { "id": "procedures-and-skills", "name": "Procedures, skills and required tools", "description": "What an agent needs before it can act on a graphics processing unit at all.", "questions": [ { "id": "procedures-and-skills-q01", "text": "What identifies and describes handling a graphics processing unit, and in what units or vocabulary?", "kind": "definition", "answer_data": [ "identifiers", "types and classes", "values with units", "explicit unknowns" ] }, { "id": "procedures-and-skills-q02", "text": "Who or what asserted this about handling a graphics processing unit, by which method, and when was it true?", "kind": "provenance", "answer_data": [ "authority", "method", "evidence", "event time", "knowledge time" ] }, { "id": "procedures-and-skills-q03", "text": "What may an agent decide or do once handling a graphics processing unit is known, and what must it refuse?", "kind": "action", "answer_data": [ "permitted actions", "preconditions", "refusals", "escalation" ] } ] } ] } ] }, { "id": "definition-and-realisation", "name": "Definition, dimension and realisation", "description": "What graphics processing unit is defined as and how it is realised in practice.", "rationale": "A unit is not the quantity it measures, and its definition has a history that older data still depends on.", "layers": [ { "id": "definition", "name": "Definition and dimension", "description": "The defining relation and the quantity it measures.", "findings": [ { "id": "definition-record", "name": "Definition, body and date", "description": "What defines it now, and what defined it before.", "questions": [ { "id": "definition-record-q01", "text": "How is graphics processing unit defined, by which body, and since when?", "kind": "definition" }, { "id": "definition-record-q02", "text": "What was the previous definition, and what data still depends on it?", "kind": "provenance" } ] } ] }, { "id": "conversion", "name": "Conversion and compatibility", "description": "Relations to other units, exact or approximate.", "findings": [ { "id": "conversion-record", "name": "Conversions and their exactness", "description": "Factors, and whether each is exact by definition.", "questions": [ { "id": "conversion-record-q01", "text": "What conversions relate graphics processing unit to other units, and which are exact by definition?", "kind": "measurement" }, { "id": "conversion-record-q02", "text": "Where does rounding a conversion change a decision, and how should that be recorded?", "kind": "action" } ] } ] } ] }, { "id": "provenance-and-evidence", "name": "Provenance, evidence and time", "description": "Where every claim about a graphics processing unit 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 graphics processing unit and how confident it is.", "questions": [ { "id": "claim-provenance-q01", "text": "What identifies and describes a claim about a graphics processing unit, 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 graphics processing unit, 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 graphics processing unit 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 graphics processing unit is retired without being erased.", "questions": [ { "id": "validity-and-supersession-q01", "text": "What identifies and describes the validity of a claim about a graphics processing unit, 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 graphics processing unit, 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 graphics processing unit is known, and what must it refuse?", "kind": "action", "answer_data": [ "permitted actions", "preconditions", "refusals", "escalation" ] } ] } ] } ] } ] }, "statistics": { "bundles": 7, "layers": 15, "findings": 17, "questions": 49 } } } }