{ "model": { "rank": 4218, "code": "thing-q4308", "model_id": "vr.tr.graphics-card", "name": "graphics card", "purpose": "Enable an AI agent to recognise a graphics card, assess its suitability and operating condition, and determine compatible, safe installation, configuration and service actions.", "family": "Thing Registry", "category": "Physical world and living systems", "status": "research-draft", "kind": "thing", "plane": "PHY", "domain": "PHY.OBJ", "industry": "", "version": "", "url": "/models/thing/q4308/", "tier": 2, "score": 77, "payload": { "layer": "wikidata", "aliases": [ "Innosilicon Fantasy One Type A", "Innosilicon Fantasy One Type B", "GeForce GTS 250", "shader core", "mobile graphics card", "desktop graphics card", "S3 Graphics DeltaChrome S8", "VDP", "Voodoo 5", "Voodoo2", "Voodoo3", "IBM 8514", "IBM Image Adapter/A", "Matrox Millennium", "Matrox Mystique", "Matrox G400", "AMD Radeon 760M" ], "aliasCount": 17, "merged": 17, "knownIn": 77, "facets": null, "markers": [], "lexicalClass": "", "senseRank": null, "alsoRegisteredAs": null, "source": { "dataset": "wikidata", "item": "Q4308", "url": "https://www.wikidata.org/wiki/Q4308", "license": "CC0 1.0" } }, "research": { "vercy": "1.0-draft", "publication": { "status": "research-draft", "adjudicationStatus": "unreviewed", "publishableCanonical": false, "generatedAt": "2026-09-09T19:44:25Z", "providers": [ "Codex" ], "breadth": "recalled by Codex without web access - no source was read", "missingProviders": [], "pass": 2, "cost": { "grok": { "seconds": 22.4, "error": "Reading additional input from stdin...\nOpenAI Codex v0.153.4\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: 01a087b2-2b6b-7ba0-bfdd-860058c09f7d\n--------\nuser\nDescribe what is already known about one registered thing. Answer as JSON only, no prose around it.\n\nThing: graphics card\nSense to describe: (none recorded)\nDomain code: PHY.OBJ\nAlso known as: (none)\n\n\nContext for this batch of 695 things:\n# Batch 004: 1001 re", "usd": 0, "recall": true }, "codex": { "seconds": 69.8, "error": "Reading additional input from stdin...\nOpenAI Codex v0.153.4\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: 01a087b2-2b60-7962-9839-dd8c1dfecf24\n--------\nuser\nYou are drafting a Vercy meta-model for one registered thing. Answer as JSON only, no prose around it.\n\nThing: graphics card\nRegistry id: vr.tr.graphics-card\nPlane / domain: PHY / PHY.OBJ\nRegistry definition: (none recorded)\nNames folded into this entry: (none" } } }, "metaModel": { "id": "THING-Q4308", "registryId": "vr.tr.graphics-card", "name": "graphics card", "version": "0.1.0-research.1", "entryKind": "thing", "family": "Thing Registry", "domain": [ "PHY.OBJ" ], "status": "research-draft" }, "canonicalUrl": "https://ver.cy/models/thing/q4308/", "model": { "registry_id": "vr.tr.graphics-card", "name": "graphics card", "purpose": "Enable an AI agent to recognise a graphics card, assess its suitability and operating condition, and determine compatible, safe installation, configuration and service actions.", "definition": "A graphics card is a circuit-board assembly containing a graphics processing unit, usually dedicated graphics memory, and supporting power and interface circuitry, used to render images and commonly to drive displays or perform parallel computation.", "scope_statement": "This model owns the graphics card as a physical graphics-processing board assembly, including its processing devices, onboard memory where present, board interfaces, power delivery, firmware and fitted cooling; it defines what to record about the kind while keeping product specifications and individual-unit observations distinct.", "in_scope": [ "Graphics-processing board identity, assembly boundaries and hardware revision", "Graphics execution, video processing and supported display-output capabilities", "Onboard graphics memory, host interface and installation requirements", "Board power delivery, cooling, operating states and telemetry", "Firmware and driver compatibility, faults, maintenance and service constraints" ], "out_of_scope": [ "A GPU semiconductor considered independently of its graphics-card assembly", "Integrated graphics embedded in a host processor or motherboard", "The complete computer, its operating system and its general power supply", "Monitors, display cables and external graphics enclosures as separate products", "Applications, graphics APIs and rendered media as independent information objects", "Dedicated compute accelerators whose classification as graphics cards has not been established" ], "distinguishing_features": [ "Identify a physical board assembly carrying graphics-processing hardware; a bare GPU package is a component rather than the card.", "Establish that the board executes graphics workloads; video connectors alone do not distinguish a graphics card from a passive adapter or capture card.", "Distinguish graphics generation and rendering from video capture: accepting a video signal is not sufficient evidence that a board is a graphics card.", "Identify the board's connection to its host and its assembly boundary; graphics integrated into a host processor do not become a graphics card merely because the computer has display outputs.", "Check graphics capability separately from physical display connectors, since connector presence alone cannot settle the classification of headless or specialised boards." ], "characteristics": [ { "name": "Board identity and revision", "kind": "category", "unit_or_values": "Board manufacturer, product designation, part number and hardware revision; unknown where unverified", "why_it_matters": "Cards using the same GPU can differ in dimensions, cooling, connectors, firmware and power requirements." }, { "name": "Graphics processor configuration", "kind": "relation", "unit_or_values": "Installed GPU identity or identities, architecture and enabled capabilities", "why_it_matters": "Connects the assembly to its processing components without treating the GPU name as a complete card specification." }, { "name": "Onboard graphics memory", "kind": "measurement", "unit_or_values": "Capacity in GiB with original manufacturer units retained; memory type and interface width in bits", "why_it_matters": "Constrains workload residency and helps distinguish memory exhaustion from other performance limits." }, { "name": "Host interface", "kind": "category", "unit_or_values": "Interface family, connector form, supported link generation and electrical lane width", "why_it_matters": "Determines host compatibility and separates physical connector fit from negotiated link capability." }, { "name": "Installed link state", "kind": "state", "unit_or_values": "Detected or undetected; negotiated link generation and lane width under stated load", "why_it_matters": "Reveals installation or link limitations that a product specification alone cannot show." }, { "name": "Installation envelope", "kind": "measurement", "unit_or_values": "Length, height and thickness in mm; occupied expansion slots; required connector and airflow clearance", "why_it_matters": "Determines whether the complete fitted assembly can be installed and adequately cooled." }, { "name": "Display and video capabilities", "kind": "category", "unit_or_values": "Connector inventory, simultaneous-display constraints, supported signal modes and codec encode/decode capabilities", "why_it_matters": "Separates rendering, display transport and media-processing capabilities that are often incorrectly treated as interchangeable." }, { "name": "Board power requirements", "kind": "measurement", "unit_or_values": "Documented board power and configurable limits in W; required supply connections and ratings", "why_it_matters": "Supports power budgeting and connection checks without confusing board consumption with a whole-system supply recommendation." }, { "name": "Thermal observations", "kind": "measurement", "unit_or_values": "Available sensor temperatures in °C, fan speeds in rpm and workload, ambient and sampling conditions", "why_it_matters": "Makes cooling assessment meaningful while preserving differences between GPU, hotspot and memory sensors." }, { "name": "Operating condition", "kind": "state", "unit_or_values": "Unpowered, initialising, idle, active, throttled, faulted or unknown, with supporting observations", "why_it_matters": "Guides diagnosis and prevents absence of display output from being equated automatically with complete board failure." }, { "name": "Software and firmware compatibility", "kind": "relation", "unit_or_values": "Board firmware version, host firmware requirements, supported operating systems, drivers and exposed graphics or compute features", "why_it_matters": "Determines which hardware functions the installed software stack can actually use." } ], "affordances": [ "Match a card to a host, enclosure, power supply and display arrangement using verified board-specific requirements.", "Install, remove or reseat the assembly using documented isolation, handling and connector procedures.", "Select compatible drivers and supported firmware, then verify device detection and required graphics features.", "Configure supported display modes, cooling controls and power limits within documented operating constraints.", "Run bounded graphics, memory and media-processing checks while observing temperatures, errors and throttling.", "Inspect and service cooling or connections, or refer the card for repair when evidence exceeds the available diagnostic or service scope." ] }, "sources": [], "structure": { "bundles": [ { "id": "graphics-card-identity", "name": "Graphics card identity", "description": "Establish what physical assembly is being modelled and what makes it a graphics card.", "rationale": "A GPU name, a board product and an installed unit provide different evidence and must not be conflated.", "layers": [ { "id": "assembly-boundary", "name": "Assembly boundary", "description": "Identify the graphics board and distinguish it from adjacent graphics-related components.", "findings": [ { "id": "graphics-board-classification", "name": "Graphics board classification", "description": "Record the evidence that the assembly performs graphics processing and the boundary around its fitted components.", "questions": [ { "text": "What establishes that this is a graphics-processing board rather than a bare GPU, integrated graphics implementation, capture card or passive display adapter?", "kind": "definition", "id": "graphics-board-classification-q01" }, { "text": "Which memory devices, cooling parts, brackets and power-delivery components belong to the card assembly, and which belong to its host or enclosure?", "kind": "boundary", "id": "graphics-board-classification-q02" } ] } ] }, { "id": "board-variant-provenance", "name": "Board variant provenance", "description": "Separate processor-family information from evidence for the exact board variant.", "findings": [ { "id": "board-specific-identification", "name": "Board-specific identification", "description": "Capture identifiers and their evidence so that specifications are applied to the correct board and revision.", "questions": [ { "text": "Which labels, device identifiers and manufacturer records establish the board manufacturer, part number and hardware revision?", "kind": "provenance", "id": "board-specific-identification-q01" }, { "text": "Which claimed specifications are verified for this board revision, and which describe only its GPU family or a reference design?", "kind": "boundary", "id": "board-specific-identification-q02" } ] } ] } ] }, { "id": "host-and-display-integration", "name": "Host and display integration", "description": "Describe the physical, electrical and display connections needed to use the card.", "rationale": "A card may fit a connector yet fail installation, link negotiation or the intended display configuration.", "layers": [ { "id": "host-fit-and-link", "name": "Host fit and link", "description": "Assess the board's installation envelope and connection to the host.", "findings": [ { "id": "installation-and-link-compatibility", "name": "Installation and link compatibility", "description": "Record mechanical clearance, host-interface requirements and observed link operation separately.", "questions": [ { "text": "What are the card's installed dimensions in mm, slot occupancy, retention needs and clearances for power cables and cooling airflow?", "kind": "measurement", "id": "installation-and-link-compatibility-q01" }, { "text": "What host interface does the board require, and what link generation and width does the installed system actually negotiate under load?", "kind": "measurement", "id": "installation-and-link-compatibility-q02" } ] } ] }, { "id": "display-signal-path", "name": "Display signal path", "description": "Describe outputs and the end-to-end conditions for the required display modes.", "findings": [ { "id": "usable-display-configurations", "name": "Usable display configurations", "description": "Record connector capabilities and shared limits without assuming that connector shape guarantees a signal mode.", "questions": [ { "text": "Which physical outputs and documented interface capabilities does this board provide, including limits on simultaneous displays or shared resources?", "kind": "provenance", "id": "usable-display-configurations-q01" }, { "text": "Can the complete card, adapter, cable and display path support the requested resolution, refresh rate, colour depth and compression settings?", "kind": "action", "id": "usable-display-configurations-q02" } ] } ] } ] }, { "id": "graphics-execution-and-memory", "name": "Graphics execution and memory", "description": "Connect graphics and media workloads to the card's processing capabilities and memory resources.", "rationale": "Suitability depends on supported operations, available memory and workload-specific behaviour rather than a single performance label.", "layers": [ { "id": "execution-capabilities", "name": "Execution capabilities", "description": "Determine which graphics, compute and media operations the installed card can expose.", "findings": [ { "id": "available-processing-features", "name": "Available processing features", "description": "Separate hardware capability from features enabled by the driver, operating system and application.", "questions": [ { "text": "Which required graphics features, compute functions and video codec profiles are supported by the exact card and installed software stack?", "kind": "provenance", "id": "available-processing-features-q01" }, { "text": "Which representative workload can verify the required rendering, encoding or decoding function, and what output or error would establish success or failure?", "kind": "action", "id": "available-processing-features-q02" } ] } ] }, { "id": "graphics-memory-resources", "name": "Graphics memory resources", "description": "Describe onboard memory and distinguish it from host memory made available to graphics workloads.", "findings": [ { "id": "memory-capacity-and-pressure", "name": "Memory capacity and pressure", "description": "Record physical memory resources and observed workload pressure without treating shared host memory as equivalent onboard capacity.", "questions": [ { "text": "What onboard memory capacity, type and interface width are verified, and how are dedicated, shared and currently available memory reported?", "kind": "measurement", "id": "memory-capacity-and-pressure-q01" }, { "text": "Under the intended workload, what evidence distinguishes memory exhaustion or transfer pressure from processing limits, thermal throttling or a software fault?", "kind": "measurement", "id": "memory-capacity-and-pressure-q02" } ] } ] } ] }, { "id": "board-power-and-cooling", "name": "Board power and cooling", "description": "Establish the electrical supply and heat-removal conditions required by the board.", "rationale": "Power connection mistakes and inadequate cooling can prevent reliable operation even when host and graphics capabilities match.", "layers": [ { "id": "power-delivery", "name": "Power delivery", "description": "Assess slot power, auxiliary connections and board-specific power constraints.", "findings": [ { "id": "supply-and-connector-requirements", "name": "Supply and connector requirements", "description": "Record documented power needs and the compatibility of the actual supply connections.", "questions": [ { "text": "What board power limits and auxiliary connector requirements are documented for this revision, and how do they differ from the recommended whole-system supply rating?", "kind": "provenance", "id": "supply-and-connector-requirements-q01" }, { "text": "What checks establish that the supply, modular cables or adapters, connector seating and cable routing meet the card and supply manufacturers' requirements before energising?", "kind": "action", "id": "supply-and-connector-requirements-q02" } ] } ] }, { "id": "thermal-operation", "name": "Thermal operation", "description": "Relate the fitted cooler and environmental conditions to sensor readings and performance limits.", "findings": [ { "id": "cooling-effectiveness-and-throttling", "name": "Cooling effectiveness and throttling", "description": "Assess cooling using identified sensors and documented controls rather than an assumed universal temperature threshold.", "questions": [ { "text": "Which GPU, hotspot, memory and fan measurements are available, and what values occur under a stated workload, ambient temperature and duration?", "kind": "measurement", "id": "cooling-effectiveness-and-throttling-q01" }, { "text": "Which documented thermal limits, fan-stop behaviours and throttle indicators determine whether to continue operation, reduce load or shut down?", "kind": "action", "id": "cooling-effectiveness-and-throttling-q02" } ] } ] } ] }, { "id": "configuration-diagnosis-and-service", "name": "Configuration, diagnosis and service", "description": "Guide software configuration, fault isolation and maintenance for the graphics-card assembly.", "rationale": "Missing output, rendering faults and unstable operation require evidence that separates card faults from host, display and software failures.", "layers": [ { "id": "firmware-and-driver-state", "name": "Firmware and driver state", "description": "Establish the configuration needed to initialise the board and expose its supported functions.", "findings": [ { "id": "supported-configuration-and-recovery", "name": "Supported configuration and recovery", "description": "Record firmware and driver provenance, compatibility and available recovery procedures.", "questions": [ { "text": "Which board firmware, host firmware settings, operating system and driver versions are installed, and what authoritative records establish their compatibility?", "kind": "provenance", "id": "supported-configuration-and-recovery-q01" }, { "text": "For a proposed driver or firmware change, what board-specific procedure, prerequisites and rollback or recovery route are documented?", "kind": "action", "id": "supported-configuration-and-recovery-q02" } ] } ] }, { "id": "fault-isolation-and-maintenance", "name": "Fault isolation and maintenance", "description": "Turn symptoms and inspection results into bounded diagnostic and service decisions.", "findings": [ { "id": "diagnostic-evidence-and-service-boundary", "name": "Diagnostic evidence and service boundary", "description": "Distinguish suspected board failures from surrounding-system faults and identify justified maintenance actions.", "questions": [ { "text": "What controlled checks distinguish no-display, artefact, reset or slowdown symptoms caused by the card from those caused by the monitor, cable, host, power supply or software?", "kind": "action", "id": "diagnostic-evidence-and-service-boundary-q01" }, { "text": "Which cleaning, fan replacement or thermal-interface service actions are documented for this assembly, and what isolation, electrostatic handling and stop conditions apply?", "kind": "action", "id": "diagnostic-evidence-and-service-boundary-q02" } ] } ] } ] }, { "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 hardware category, not a particular product line or individual unit; terminology sometimes uses 'graphics card' loosely for integrated graphics.", "Measurement ranges are approximate recall-based examples, not verified market limits; memory capacity, power and dimensions vary substantially by generation and application.", "Researchers should check interface versions, connector requirements, supported software and jurisdiction-specific compliance for each product; no sources were consulted." ], "questions": [ { "id": "evidence-confidence-notes-q01", "text": "Which of these check these first hold for the sense of graphics card 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": [ "Consumer gaming graphics card", "Professional workstation graphics card", "Low-profile graphics card", "Passively cooled graphics card", "External graphics card assembly" ], "questions": [ { "id": "evidence-kinds-q01", "text": "Which of these kinds and varieties hold for the sense of graphics card this model covers, and on what evidence?", "kind": "provenance" } ] }, { "id": "evidence-identifiers", "name": "Identifiers and schemes", "description": "Recalled without web access and unsourced; every item is a lead to verify.", "evidence": [ { "scheme": "PCI vendor ID and device ID", "value_or_pattern": "16-bit vendor ID paired with a 16-bit device ID, commonly written as four hexadecimal digits each", "note": "Identifies the enumerated PCI device type rather than an individual card; PCI-SIG assigns vendor IDs and vendors assign device IDs." }, { "scheme": "Manufacturer part number and serial number", "value_or_pattern": "Manufacturer-specific alphanumeric strings", "note": "Part numbers distinguish board products or revisions; serial numbers identify individual units." } ], "questions": [ { "id": "evidence-identifiers-q01", "text": "Which of these identifiers and schemes hold for the sense of graphics card 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": [ "PCI Express Base Specification and Card Electromechanical Specification - PCI-SIG; define host interfaces and relevant add-in card requirements.", "DisplayPort Standard - Video Electronics Standards Association (VESA); applies to cards implementing DisplayPort outputs.", "HDMI Specification - HDMI Founders and HDMI Forum; applies to cards implementing HDMI outputs." ], "questions": [ { "id": "evidence-standards-and-regulation-q01", "text": "Which of these standards and regulation hold for the sense of graphics card 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": [ "Rendering interactive graphics for games and visualization.", "Driving one or more monitors.", "Accelerating CAD, animation and digital content creation.", "Accelerating supported video decoding and encoding.", "Running supported parallel workloads such as machine learning and scientific computation." ], "questions": [ { "id": "evidence-real-world-use-q01", "text": "Which of these real-world use hold for the sense of graphics card 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": "Dedicated graphics memory capacity", "typical_range": "Approximately 4-24 for many consumer discrete cards; other products fall outside this range", "unit": "GB" }, { "quantity": "Board power under load", "typical_range": "Approximately 30-450 across many desktop products; high-power products can exceed this", "unit": "W" }, { "quantity": "Board assembly length", "typical_range": "Approximately 150-350 for many desktop add-in cards", "unit": "mm" }, { "quantity": "Installed thickness", "typical_range": "Approximately 1-4", "unit": "expansion-slot widths" } ], "questions": [ { "id": "evidence-measurements-q01", "text": "Which of these typical measurements hold for the sense of graphics card 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": [ "Fan failure, dust accumulation or degraded thermal interfaces can cause overheating, throttling or shutdown.", "Graphics memory or processor faults can produce visual artifacts, application crashes or loss of display output.", "Inadequate power delivery or poorly seated power connectors can cause instability and localized overheating.", "Electrostatic discharge or mechanical damage during handling can permanently damage components.", "Heavy cooling assemblies can strain the circuit board and host connector if inadequately supported." ], "questions": [ { "id": "evidence-failure-modes-and-hazards-q01", "text": "Which of these failure modes and hazards hold for the sense of graphics card 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": "graphics processing unit", "difference": "The GPU is the processing component; the graphics card is the board assembly incorporating it." }, { "name": "integrated graphics", "difference": "Integrated graphics resides within a processor or system chipset rather than on a separate graphics card." }, { "name": "compute accelerator card", "difference": "A compute accelerator primarily serves computation and may lack display outputs or graphics functionality; some graphics cards also perform this role." }, { "name": "video capture card", "difference": "A capture card primarily receives and digitizes external video rather than rendering computer-generated graphics." }, { "name": "external GPU enclosure", "difference": "The enclosure supplies housing, power and a host connection for a graphics card; it is not necessarily supplied with the card itself." } ], "questions": [ { "id": "evidence-neighbours-q01", "text": "Which of these neighbouring kinds and how to tell them apart hold for the sense of graphics card this model covers, and on what evidence?", "kind": "provenance" } ] } ] } ] } ] }, "openQuestions": [ "Does the registry intend graphics card to include removable laptop graphics modules, historical display adapters and headless graphics boards, and where is its boundary with dedicated compute accelerators?", "Which existing Vercy models already own GPU components, expansion cards, display interfaces or graphics accelerators, and should this entry reference an existing publication?", "Which primary manufacturer and standards-body sources establish applicable interface, electrical safety, electromagnetic compatibility and certification requirements, including their jurisdiction and revision?", "Which representative board classes should establish useful capacity, dimension and power ranges without implying that a contemporary desktop card defines the entire kind?", "Which diagnostic observations reliably separate memory faults, GPU faults, power instability and software errors, and which conclusions require specialist testing?" ], "statistics": { "bundles": 6, "layers": 11, "findings": 18, "questions": 28 } }, "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 graphics card, record what state it is in, and decide what may be done with it.", "whatItIs": "Enable an AI agent to recognise a graphics card, assess its suitability and operating condition, and determine compatible, safe installation, configuration and service actions.", "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: Innosilicon Fantasy One Type A, Innosilicon Fantasy One Type B, GeForce GTS 250, shader core, mobile graphics card, desktop graphics card, S3 Graphics DeltaChrome S8, VDP, Voodoo 5, Voodoo2, Voodoo3, IBM 8514.", "17 finer distinctions are held as aliases rather than separate entries, because telling them apart needs a task that asks for it.", "Described in 77 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 card, 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": [ "Innosilicon Fantasy One Type A", "Innosilicon Fantasy One Type B", "GeForce GTS 250", "shader core", "mobile graphics card", "desktop graphics card", "S3 Graphics DeltaChrome S8", "VDP", "Voodoo 5", "Voodoo2", "Voodoo3", "IBM 8514" ] } ], "standing": "Described in 77 Wikipedia languages, which measures how widely it is written about rather than how important or how common it is. 17 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 card from another, and a graphics card 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 card, 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 card, 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 card 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 card, 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 card, 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 card 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 card 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 card, 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 card, 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 card 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 card from the things most often confused with it.", "questions": [ { "id": "distinguishing-features-q01", "text": "What identifies and describes what distinguishes a graphics card, 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 card, 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 card 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 card 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 card, 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 card, 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 card 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 card is built from and which parts are replaceable.", "questions": [ { "id": "parts-and-materials-q01", "text": "What identifies and describes the composition of a graphics card, 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 card, 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 card 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 card is judged and by whom.", "questions": [ { "id": "condition-assessment-q01", "text": "What identifies and describes the condition of a graphics card, 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 card, 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 card 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 card 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 card is, and what that position is measured against.", "questions": [ { "id": "position-and-frame-q01", "text": "What identifies and describes the location of a graphics card, 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 card, 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 card 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 card 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 card, 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 card, 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 card 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 card 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 card between them.", "questions": [ { "id": "stages-and-transitions-q01", "text": "What identifies and describes the lifecycle of a graphics card, 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 card, 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 card 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 card, how often and by whom.", "findings": [ { "id": "observation-record", "name": "Observation record", "description": "How an observation of a graphics card 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 card, 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 card, 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 card 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 graphics card 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 graphics card 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 graphics card, 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 graphics card 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 graphics card 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 graphics card 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 graphics card 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 graphics card 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 graphics card, 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 graphics card 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 card and how confident it is.", "questions": [ { "id": "claim-provenance-q01", "text": "What identifies and describes a claim about a graphics card, 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 card, 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 card 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 card is retired without being erased.", "questions": [ { "id": "validity-and-supersession-q01", "text": "What identifies and describes the validity of a claim about a graphics card, 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 card, 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 card 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 } } } }