{ "model": { "rank": 5220, "code": "thing-q245", "model_id": "vr.tr.raspberry-pi", "name": "Raspberry Pi", "purpose": "Enable an AI agent to recognise a Raspberry Pi computer, assess its configuration and operating condition, and determine compatible, safe actions for its intended workload.", "family": "Thing Registry", "category": "Physical world and living systems", "status": "research-draft", "kind": "thing", "plane": "PHY", "domain": "PHY.OBJ", "industry": "", "version": "", "url": "/models/thing/q245/", "tier": 2, "score": 69, "payload": { "layer": "wikidata", "aliases": [ "RP2040", "Raspberry Pi Model A", "Raspberry Pi Model B", "Raspberry Pi 2 Model B", "Raspberry Pi 1 Model B+", "Raspberry Pi Model A+", "Raspberry Pi Compute Module", "Raspberry Pi 3 Model B+", "Raspberry Pi 3 Model A+", "Compute Module 3 Lite" ], "aliasCount": 10, "merged": 10, "knownIn": 69, "facets": null, "markers": [], "lexicalClass": "", "senseRank": null, "alsoRegisteredAs": null, "source": { "dataset": "wikidata", "item": "Q245", "url": "https://www.wikidata.org/wiki/Q245", "license": "CC0 1.0" } }, "research": { "vercy": "1.0-draft", "publication": { "status": "research-draft", "adjudicationStatus": "unreviewed", "publishableCanonical": false, "generatedAt": "2026-09-09T21:55:05Z", "providers": [ "Codex" ], "breadth": "recalled by Codex without web access - no source was read", "missingProviders": [], "pass": 2, "cost": { "grok": { "seconds": 23, "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: 01a08829-db03-78d1-96a8-67030d7f07b2\n--------\nuser\nDescribe what is already known about one registered thing. Answer as JSON only, no prose around it.\n\nThing: Raspberry Pi\nSense to describe: (none recorded)\nDomain code: PHY.OBJ\nAlso known as: (none)\n\n\nContext for this batch of 1001 things:\n# Batch 005: 1001 re", "usd": 0, "recall": true }, "codex": { "seconds": 66.7, "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: 01a08829-dafc-71c0-924a-ba463295eaa6\n--------\nuser\nYou are drafting a Vercy meta-model for one registered thing. Answer as JSON only, no prose around it.\n\nThing: Raspberry Pi\nRegistry id: vr.tr.raspberry-pi\nPlane / domain: PHY / PHY.OBJ\nRegistry definition: (none recorded)\nNames folded into this entry: (none)\n" } } }, "metaModel": { "id": "THING-Q245", "registryId": "vr.tr.raspberry-pi", "name": "Raspberry Pi", "version": "0.1.0-research.1", "entryKind": "thing", "family": "Thing Registry", "domain": [ "PHY.OBJ" ], "status": "research-draft" }, "canonicalUrl": "https://ver.cy/models/thing/q245/", "model": { "registry_id": "vr.tr.raspberry-pi", "name": "Raspberry Pi", "purpose": "Enable an AI agent to recognise a Raspberry Pi computer, assess its configuration and operating condition, and determine compatible, safe actions for its intended workload.", "definition": "Raspberry Pi is a family of compact, Arm-based single-board computers and related compute modules designed for general-purpose computing, programming education and embedded applications, with specifications that vary by model.", "scope_statement": "This model owns the Raspberry Pi family of physical general-purpose computers in registry entry vr.tr.raspberry-pi, including single-board computers, keyboard-integrated computers and Compute Modules as variants within one kind; it records model-specific capabilities and unit state without treating the Raspberry Pi organisations or every Pi-branded product as the same thing.", "in_scope": [ "Identification of the board or module, product generation, hardware revision and installed memory", "Power, cooling, enclosure and carrier-board requirements for the identified variant", "Boot firmware, boot media, operating-system compatibility and recovery state", "Available ports, GPIO capabilities and attached peripheral compatibility", "Workload suitability, operating health and deployment readiness" ], "out_of_scope": [ "Raspberry Pi companies, charitable organisations and their governance", "Raspberry Pi Pico microcontroller boards and standalone microcontroller chips, provisionally treated as neighbouring kinds", "Operating systems and application software as independently maintained information products", "HATs, cameras, displays, power supplies and carrier boards as independently modelled accessories", "Complete robots, appliances or industrial installations that contain a Raspberry Pi" ], "distinguishing_features": [ "Establish Raspberry Pi product identity through consistent board markings, hardware identifiers and official product documentation; a similar connector layout or compatible operating system alone is insufficient.", "Distinguish the computer variants covered here from Pico-class microcontroller boards by the identified product family and its documented boot and software architecture.", "Distinguish a Compute Module from a standalone board by its documented carrier interface and dependence on a suitable carrier for exposed connections.", "Distinguish a Raspberry Pi component from a finished appliance by identifying the physical computer and the functions supplied by the surrounding system.", "Treat generation, memory option and board revision as variant attributes, and serial number and observed condition as attributes of an individual unit." ], "characteristics": [ { "name": "Product variant and board revision", "kind": "category", "unit_or_values": "Documented product designation, hardware revision and identification confidence", "why_it_matters": "Controls which specifications, firmware, accessories and recovery procedures apply." }, { "name": "Physical implementation", "kind": "category", "unit_or_values": "Single-board computer | keyboard-integrated computer | Compute Module; carrier required or integrated", "why_it_matters": "Determines installation boundaries, connector availability and enclosure requirements." }, { "name": "Processor and software architecture", "kind": "category", "unit_or_values": "SoC designation, supported instruction sets and installed operating-system architecture", "why_it_matters": "Determines whether an image or executable can run on the identified hardware." }, { "name": "Installed memory", "kind": "measurement", "unit_or_values": "MiB or GiB, distinguishing nominal capacity from operating-system-usable memory", "why_it_matters": "Constrains concurrent services, memory-intensive applications and image selection." }, { "name": "Power-path capability", "kind": "measurement", "unit_or_values": "Required and available V, A and W at the documented input, with cable and peripheral load identified", "why_it_matters": "Helps explain unstable operation and determines whether the complete setup has an adequate supply." }, { "name": "Boot configuration", "kind": "state", "unit_or_values": "Firmware version where applicable, supported and selected boot source, boot order and observed boot stage", "why_it_matters": "Separates unsupported boot choices from media, firmware and operating-system failures." }, { "name": "Storage configuration and condition", "kind": "state", "unit_or_values": "Media type, capacity in GB or GiB, free space, read/write status and observed errors", "why_it_matters": "Determines persistence, recovery options and risk when changing or interrupting the system." }, { "name": "Exposed interfaces", "kind": "category", "unit_or_values": "Variant-specific connector types, counts, supported protocols and occupied functions", "why_it_matters": "Prevents assumptions that every Raspberry Pi has the same ports or expansion capabilities." }, { "name": "Attached hardware", "kind": "relation", "unit_or_values": "Links to carrier, HAT, GPIO circuit, camera, display, storage, cooling and power-supply records", "why_it_matters": "Makes compatibility and electrical dependencies inspectable." }, { "name": "Thermal and supply health", "kind": "state", "unit_or_values": "Temperature in °C, available undervoltage or throttling indicators, observation time and workload", "why_it_matters": "Distinguishes satisfactory operation from performance constrained by cooling or power." }, { "name": "Physical fit", "kind": "measurement", "unit_or_values": "Board or assembly dimensions and mounting positions in mm, including connector and cooling clearance", "why_it_matters": "Determines whether a case, carrier or mounting arrangement fits the actual assembly." }, { "name": "Deployment trust state", "kind": "state", "unit_or_values": "Image provenance, update status, enabled remote services, credential provisioning and recovery readiness", "why_it_matters": "Determines whether the configured computer is ready for its intended network and maintenance conditions." } ], "affordances": [ "Identify the variant and select matching documentation, operating-system images and accessories.", "Prepare or replace boot media and configure supported boot paths while preserving required data.", "Connect compatible HATs, cameras, displays and GPIO circuits after checking electrical and software requirements.", "Measure supply and thermal behaviour under the intended workload and adjust cooling or load.", "Provision, update, diagnose and recover a deployed Raspberry Pi using methods supported by its variant.", "Integrate a board or Compute Module into a larger assembly with documented power, carrier and service dependencies." ] }, "sources": [], "structure": { "bundles": [ { "id": "product-identity-and-variant", "name": "Product identity and variant", "description": "Establish which Raspberry Pi computer is present and where its physical boundary lies.", "rationale": "Family resemblance conceals differences that change nearly every compatibility and maintenance decision.", "layers": [ { "id": "hardware-identification", "name": "Hardware identification", "description": "Reconcile physical markings with reported hardware identity.", "findings": [ { "id": "variant-evidence", "name": "Variant evidence", "description": "Record evidence for the product designation, board revision and memory option without assuming that an installed image identifies the board.", "questions": [ { "text": "Which Raspberry Pi product and revision do board markings and available hardware identifiers indicate?", "kind": "definition", "id": "variant-evidence-q01" }, { "text": "Which official identification reference was used, and do physical and software-reported identifiers agree?", "kind": "provenance", "id": "variant-evidence-q02" } ] } ] }, { "id": "assembly-boundary", "name": "Assembly boundary", "description": "Separate the computer variant from carriers, accessories and the host appliance.", "findings": [ { "id": "computer-and-carrier", "name": "Computer and carrier", "description": "Record whether usable interfaces belong to the Raspberry Pi itself, an integrated assembly or a separate Compute Module carrier.", "questions": [ { "text": "Is this a standalone board, keyboard-integrated computer or Compute Module requiring a carrier?", "kind": "boundary", "id": "computer-and-carrier-q01" }, { "text": "Which installed carrier or enclosure determines connector access, mounting and replacement compatibility?", "kind": "boundary", "id": "computer-and-carrier-q02" } ] } ] } ] }, { "id": "power-cooling-and-installation", "name": "Power, cooling and installation", "description": "Assess the power path and thermal environment of the complete Raspberry Pi assembly.", "rationale": "Supply limitations, peripheral demand and enclosure cooling can make a correctly configured Pi unreliable.", "layers": [ { "id": "power-path", "name": "Power path", "description": "Relate documented input requirements to the actual supply, cable and connected loads.", "findings": [ { "id": "supply-and-load-budget", "name": "Supply and load budget", "description": "Establish an evidence-based power budget that includes board demand, peripherals and the chosen input method.", "questions": [ { "text": "What input voltage, supply capability and connection or negotiation requirements are documented for this exact variant?", "kind": "measurement", "id": "supply-and-load-budget-q01" }, { "text": "Under peak intended load, what evidence shows that the supply and cable support the board and attached peripherals?", "kind": "measurement", "id": "supply-and-load-budget-q02" } ] } ] }, { "id": "thermal-and-mechanical-fit", "name": "Thermal and mechanical fit", "description": "Check cooling performance and physical installation against the intended workload.", "findings": [ { "id": "sustained-operation-envelope", "name": "Sustained operation envelope", "description": "Record temperature and performance observations together with cooling hardware, case geometry and ambient conditions.", "questions": [ { "text": "What temperatures and available throttling indicators are observed during a representative sustained workload?", "kind": "measurement", "id": "sustained-operation-envelope-q01" }, { "text": "What changes to the documented cooling or mounting arrangement are needed to maintain acceptable operation and connector clearance?", "kind": "action", "id": "sustained-operation-envelope-q02" } ] } ] } ] }, { "id": "boot-storage-and-recovery", "name": "Boot, storage and recovery", "description": "Trace the supported path from power-on through firmware and storage to a working operating system.", "rationale": "Raspberry Pi variants differ in boot facilities, and replaceable or embedded media creates distinct recovery constraints.", "layers": [ { "id": "boot-chain-compatibility", "name": "Boot-chain compatibility", "description": "Match firmware, boot source and operating-system image to the identified board.", "findings": [ { "id": "supported-startup-path", "name": "Supported startup path", "description": "Record the selected boot path and its prerequisites without assuming that all variants support identical media or firmware configuration.", "questions": [ { "text": "Which boot sources and firmware configuration mechanisms are supported by this variant, and which are currently selected?", "kind": "definition", "id": "supported-startup-path-q01" }, { "text": "What source establishes that the installed operating-system image supports this board and processor architecture?", "kind": "provenance", "id": "supported-startup-path-q02" } ] } ] }, { "id": "media-integrity-and-restoration", "name": "Media integrity and restoration", "description": "Assess persistence, failure evidence and practical restoration routes.", "findings": [ { "id": "recoverable-storage-state", "name": "Recoverable storage state", "description": "Identify the actual system and data media, their observed condition and the steps needed to restore service.", "questions": [ { "text": "Which media hold boot files, the operating system and persistent data, and what errors or capacity constraints are observed?", "kind": "measurement", "id": "recoverable-storage-state-q01" }, { "text": "How can this board or module be restored from verified media or backups, and what data must be preserved before that action?", "kind": "action", "id": "recoverable-storage-state-q02" } ] } ] } ] }, { "id": "gpio-and-peripheral-integration", "name": "GPIO and peripheral integration", "description": "Model the electrical, connector and software dependencies of Raspberry Pi expansion.", "rationale": "Physical connection alone does not establish compatibility, and pin assignments can conflict across attached hardware.", "layers": [ { "id": "gpio-electrical-contract", "name": "GPIO electrical contract", "description": "Make pin numbering, signal levels and shared functions explicit before connecting circuits.", "findings": [ { "id": "pin-use-and-protection", "name": "Pin use and protection", "description": "Record each connected circuit against the variant's documented header and electrical limits.", "questions": [ { "text": "Which physical pins and GPIO identifiers does the circuit use, and what signal levels and current limits apply?", "kind": "measurement", "id": "pin-use-and-protection-q01" }, { "text": "What level conversion, external driver, isolation or wiring change is required before this circuit may be connected or energised?", "kind": "action", "id": "pin-use-and-protection-q02" } ] } ] }, { "id": "accessory-and-interface-compatibility", "name": "Accessory and interface compatibility", "description": "Check connector variants, occupied resources and software enablement for expansion hardware.", "findings": [ { "id": "complete-peripheral-path", "name": "Complete peripheral path", "description": "Trace each HAT, camera, display or other peripheral through its connector, adapter, interface resources and required software.", "questions": [ { "text": "Which documented board and accessory revisions, cables and adapters establish compatibility for each attached device?", "kind": "provenance", "id": "complete-peripheral-path-q01" }, { "text": "Which pin functions, bus addresses, drivers or device-tree settings must be enabled or reconciled for these devices to operate together?", "kind": "action", "id": "complete-peripheral-path-q02" } ] } ] } ] }, { "id": "deployment-health-and-service", "name": "Deployment health and service", "description": "Determine whether a configured Raspberry Pi can deliver its assigned workload and remain maintainable.", "rationale": "A board that boots successfully may still lack adequate resources, trustworthy configuration or an accessible recovery route.", "layers": [ { "id": "workload-and-fault-evidence", "name": "Workload and fault evidence", "description": "Evaluate the deployed configuration using workload observations and variant-specific diagnostics.", "findings": [ { "id": "service-fitness", "name": "Service fitness", "description": "Connect observed failures or degraded performance to memory, storage, connectivity, power and thermal evidence.", "questions": [ { "text": "Under the intended workload, what memory use, storage latency, network performance and service interruptions are measured?", "kind": "measurement", "id": "service-fitness-q01" }, { "text": "Which available logs, diagnostic indicators or controlled checks distinguish media failure, supply problems, overheating and software faults?", "kind": "action", "id": "service-fitness-q02" } ] } ] }, { "id": "provisioning-and-deployment-constraints", "name": "Provisioning and deployment constraints", "description": "Record software provenance, remote maintenance access and evidence relevant to the intended installation.", "findings": [ { "id": "maintainable-deployment", "name": "Maintainable deployment", "description": "Establish an update and recovery route and identify which compliance evidence applies to the board versus the assembled product.", "questions": [ { "text": "What image source, update process, credentials and remote-access configuration are recorded, and how will access be recovered after an unsuccessful change?", "kind": "action", "id": "maintainable-deployment-q01" }, { "text": "Which official conformity documents, certification marks and installation restrictions apply to this variant and jurisdiction, and what remains the responsibility of the host assembly?", "kind": "boundary", "id": "maintainable-deployment-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 computer family, not a particular model or physical unit, and excludes Pico microcontroller boards.", "Dimensions, power requirements, memory, connectors, cooling needs and boot media must be checked against the specific model; Compute Modules have different integration requirements.", "These are recalled facts, not researched findings; model-specific conformity declarations and certification marks require verification." ], "questions": [ { "id": "evidence-confidence-notes-q01", "text": "Which of these check these first hold for the sense of Raspberry Pi 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": [ "Model A and A+ boards", "Model B and B+ boards", "Raspberry Pi Zero boards", "Raspberry Pi Compute Modules", "Keyboard-integrated Raspberry Pi computers" ], "questions": [ { "id": "evidence-kinds-q01", "text": "Which of these kinds and varieties hold for the sense of Raspberry Pi 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": "Raspberry Pi product naming", "value_or_pattern": "Raspberry Pi plus generation, form-factor designation and, where applicable, memory capacity", "note": "Identifies a product variant rather than an individual physical unit." }, { "scheme": "Raspberry Pi board revision codes", "value_or_pattern": "Hexadecimal revision code", "note": "Identifies hardware revision information; decoding depends on whether the code uses the older or newer scheme." } ], "questions": [ { "id": "evidence-identifiers-q01", "text": "Which of these identifiers and schemes hold for the sense of Raspberry Pi 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": [ "USB specifications - USB Implementers Forum; supported versions and connector roles depend on the model.", "IEEE 802.3 Ethernet standards - IEEE; applicable to models with Ethernet interfaces.", "IEEE 802.11 wireless LAN standards - IEEE; applicable to wireless-equipped models." ], "questions": [ { "id": "evidence-standards-and-regulation-q01", "text": "Which of these standards and regulation hold for the sense of Raspberry Pi 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": [ "Teaching programming, computing and electronics", "Prototyping embedded systems and sensor interfaces through GPIO", "Running small servers and network services", "Media playback and digital signage", "Industrial integration using Compute Modules and carrier boards" ], "questions": [ { "id": "evidence-real-world-use-q01", "text": "Which of these real-world use hold for the sense of Raspberry Pi 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": "Nominal external supply voltage for common standalone boards", "typical_range": "5", "unit": "V DC" }, { "quantity": "GPIO logic voltage", "typical_range": "3.3", "unit": "V" }, { "quantity": "Common Model B board footprint, excluding connector protrusions", "typical_range": "Approximately 85 × 56", "unit": "mm" }, { "quantity": "Zero-family board footprint", "typical_range": "Approximately 65 × 30", "unit": "mm" } ], "questions": [ { "id": "evidence-measurements-q01", "text": "Which of these typical measurements hold for the sense of Raspberry Pi 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": [ "Insufficient supply voltage or excessive cable voltage drop can cause instability, resets and peripheral failures.", "Interrupting power during storage writes can corrupt filesystems; flash storage can also wear out.", "Inadequate cooling under sustained load can cause thermal throttling.", "Applying 5 V to ordinary 3.3 V GPIO pins, shorting pins or drawing excessive current can damage hardware.", "Motors, relays and other substantial or inductive loads require suitable drivers and protection rather than direct GPIO connection." ], "questions": [ { "id": "evidence-failure-modes-and-hazards-q01", "text": "Which of these failure modes and hazards hold for the sense of Raspberry Pi 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": [ "Wireless channel availability and permitted operation depend on the configured country and local radio rules.", "Power adapters vary by mains plug and regional electrical approvals." ], "questions": [ { "id": "evidence-regional-variation-q01", "text": "Which of these regional variation hold for the sense of Raspberry Pi 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": "Single-board computer", "difference": "The broader hardware category; Raspberry Pi identifies a particular product family within it." }, { "name": "Raspberry Pi Pico", "difference": "A related microcontroller-board family intended primarily for firmware execution rather than the Linux-capable computer sense described here." }, { "name": "Raspberry Pi OS", "difference": "An operating-system distribution used on Raspberry Pi computers, rather than the hardware." }, { "name": "Raspberry Pi Foundation", "difference": "An educational organisation rather than a computer product family." } ], "questions": [ { "id": "evidence-neighbours-q01", "text": "Which of these neighbouring kinds and how to tell them apart hold for the sense of Raspberry Pi this model covers, and on what evidence?", "kind": "provenance" } ] } ] } ] } ] }, "openQuestions": [ "Does the registry intend Raspberry Pi to cover the computer family only, or also Pico-class microcontroller boards and other branded hardware?", "Does an existing Vercy world model already cover this concept or a parent computer kind that this entry should reference?", "Which official variant and revision references should anchor processor, memory, dimensions, power, thermal and boot-support records?", "Which peripheral compatibility claims require assembly-level testing beyond the published board and accessory documentation?", "Which jurisdiction-specific conformity records and environmental limits apply to each variant and to finished products incorporating it?" ], "statistics": { "bundles": 6, "layers": 11, "findings": 19, "questions": 29 } }, "draft": { "generator": "vr.draft.v3", "status": "draft-generated", "researched": false, "archetype": "unclassified", "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 Raspberry Pi, record what state it is in, and decide what may be done with it.", "whatItIs": "Enable an AI agent to recognise a Raspberry Pi computer, assess its configuration and operating condition, and determine compatible, safe actions for its intended workload.", "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: RP2040, Raspberry Pi Model A, Raspberry Pi Model B, Raspberry Pi 2 Model B, Raspberry Pi 1 Model B+, Raspberry Pi Model A+, Raspberry Pi Compute Module, Raspberry Pi 3 Model B+, Raspberry Pi 3 Model A+, Compute Module 3 Lite.", "10 finer distinctions are held as aliases rather than separate entries, because telling them apart needs a task that asks for it.", "Described in 69 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 Raspberry Pi, 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 and material. The registry holds no appearance data, so what a Raspberry Pi looks like has to come from research." ], "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": [ "RP2040", "Raspberry Pi Model A", "Raspberry Pi Model B", "Raspberry Pi 2 Model B", "Raspberry Pi 1 Model B+", "Raspberry Pi Model A+", "Raspberry Pi Compute Module", "Raspberry Pi 3 Model B+", "Raspberry Pi 3 Model A+", "Compute Module 3 Lite" ] } ], "standing": "Described in 69 Wikipedia languages, which measures how widely it is written about rather than how important or how common it is. 10 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 Raspberry Pi from another, and a Raspberry Pi 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 Raspberry Pi, 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 Raspberry Pi, 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 Raspberry Pi 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 Raspberry Pi, 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 Raspberry Pi, 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 Raspberry Pi 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 Raspberry Pi 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 Raspberry Pi, 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 Raspberry Pi, 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 Raspberry Pi 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 Raspberry Pi from the things most often confused with it.", "questions": [ { "id": "distinguishing-features-q01", "text": "What identifies and describes what distinguishes a Raspberry Pi, 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 Raspberry Pi, 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 Raspberry Pi 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 Raspberry Pi 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 Raspberry Pi, 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 Raspberry Pi, 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 Raspberry Pi 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 Raspberry Pi is built from and which parts are replaceable.", "questions": [ { "id": "parts-and-materials-q01", "text": "What identifies and describes the composition of a Raspberry Pi, 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 Raspberry Pi, 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 Raspberry Pi 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 Raspberry Pi is judged and by whom.", "questions": [ { "id": "condition-assessment-q01", "text": "What identifies and describes the condition of a Raspberry Pi, 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 Raspberry Pi, 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 Raspberry Pi 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 Raspberry Pi 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 Raspberry Pi is, and what that position is measured against.", "questions": [ { "id": "position-and-frame-q01", "text": "What identifies and describes the location of a Raspberry Pi, 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 Raspberry Pi, 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 Raspberry Pi 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 Raspberry Pi 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 Raspberry Pi, 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 Raspberry Pi, 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 Raspberry Pi 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 Raspberry Pi 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 Raspberry Pi between them.", "questions": [ { "id": "stages-and-transitions-q01", "text": "What identifies and describes the lifecycle of a Raspberry Pi, 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 Raspberry Pi, 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 Raspberry Pi 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 Raspberry Pi, how often and by whom.", "findings": [ { "id": "observation-record", "name": "Observation record", "description": "How an observation of a Raspberry Pi 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 Raspberry Pi, 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 Raspberry Pi, 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 Raspberry Pi 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 Raspberry Pi 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 Raspberry Pi is for, and what it is used for anyway.", "findings": [ { "id": "function-and-purpose", "name": "Function, purpose and misuse", "description": "The function a Raspberry Pi performs and the uses that fall outside it.", "questions": [ { "id": "function-and-purpose-q01", "text": "What identifies and describes the use of a Raspberry Pi, 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 Raspberry Pi, 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 Raspberry Pi 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 Raspberry Pi.", "findings": [ { "id": "procedures-and-skills", "name": "Procedures, skills and required tools", "description": "What an agent needs before it can act on a Raspberry Pi at all.", "questions": [ { "id": "procedures-and-skills-q01", "text": "What identifies and describes handling a Raspberry Pi, 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 Raspberry Pi, 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 Raspberry Pi is known, and what must it refuse?", "kind": "action", "answer_data": [ "permitted actions", "preconditions", "refusals", "escalation" ] } ] } ] } ] }, { "id": "provenance-and-evidence", "name": "Provenance, evidence and time", "description": "Where every claim about a Raspberry Pi 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 Raspberry Pi and how confident it is.", "questions": [ { "id": "claim-provenance-q01", "text": "What identifies and describes a claim about a Raspberry Pi, 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 Raspberry Pi, 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 Raspberry Pi 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 Raspberry Pi is retired without being erased.", "questions": [ { "id": "validity-and-supersession-q01", "text": "What identifies and describes the validity of a claim about a Raspberry Pi, 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 Raspberry Pi, 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 Raspberry Pi is known, and what must it refuse?", "kind": "action", "answer_data": [ "permitted actions", "preconditions", "refusals", "escalation" ] } ] } ] } ] } ] }, "statistics": { "bundles": 6, "layers": 13, "findings": 15, "questions": 45 } } } }