{ "model": { "rank": 1686, "code": "thing-q4439", "model_id": "vr.tr.hard-disk", "name": "hard disk", "purpose": "Enable an AI agent to recognise a hard disk drive, assess its compatibility, condition and data exposure, and decide whether it may be connected, used, recovered, sanitised or retired.", "family": "Thing Registry", "category": "Physical world and living systems", "status": "research-draft", "kind": "thing", "plane": "PHY", "domain": "PHY.OBJ", "industry": "", "version": "", "url": "/models/thing/q4439/", "tier": 2, "score": 132, "payload": { "layer": "wikidata", "aliases": [ "WD Black", "RAM drive", "Seagate Medalist", "HP Kittyhawk", "PlayStation 2 Hard Disk Drive", "REV", "Quantum Fireball", "Microdrive", "removable hard drive", "ST3000DM001", "Seagate Barracuda", "Apple ProFile", "ST-412", "Quantum Bigfoot", "SATA hard disk drives", "Seagate ST1", "Seagate Barracuda Compute 2TB" ], "aliasCount": 17, "merged": 17, "knownIn": 132, "facets": null, "markers": [], "lexicalClass": "", "senseRank": null, "alsoRegisteredAs": null, "source": { "dataset": "wikidata", "item": "Q4439", "url": "https://www.wikidata.org/wiki/Q4439", "license": "CC0 1.0" } }, "research": { "vercy": "1.0-draft", "publication": { "status": "research-draft", "adjudicationStatus": "unreviewed", "publishableCanonical": false, "generatedAt": "2026-09-06T21:38:17Z", "providers": [ "Codex" ], "missingProviders": [ "Grok" ], "pass": 2, "cost": { "grok": { "usd": null, "turns": null, "seconds": 2.3, "error": "Error: Internal error: {\n \"message\": \"API error (status 402 Payment Required): Grok Build usage balance exhausted\",\n \"http_status\": 402\n}", "retried": true }, "codex": { "seconds": 64.7, "error": "Reading additional input from stdin...\nOpenAI Codex v0.153.3\n--------\nworkdir: R:\\02_PROJECTS\\02_Meta_Models_Platforms\\Ver.cy\\current\\thing-registry-backlog\nmodel: gpt-6-astra\nprovider: openai\napproval: never\nsandbox: read-only\nreasoning effort: none\nreasoning summaries: none\nsession id: 01a078a7-6d4d-76a0-b674-8cd52d083aa9\n--------\nuser\nYou are drafting a Vercy meta-model for one registered thing. Answer as JSON only, no prose around it.\n\nThing: hard disk\nRegistry id: vr.tr.hard-disk\nPlane / domain: PHY / PHY.OBJ\nRegistry definition: (none recorded)\nNames folded into this entry: (none)\n\nA Ver" } } }, "metaModel": { "id": "THING-Q4439", "registryId": "vr.tr.hard-disk", "name": "hard disk", "version": "0.1.0-research.1", "entryKind": "thing", "family": "Thing Registry", "domain": [ "PHY.OBJ" ], "status": "research-draft" }, "canonicalUrl": "https://ver.cy/models/thing/q4439/", "model": { "registry_id": "vr.tr.hard-disk", "name": "hard disk", "purpose": "Enable an AI agent to recognise a hard disk drive, assess its compatibility, condition and data exposure, and decide whether it may be connected, used, recovered, sanitised or retired.", "definition": "", "scope_statement": "This model owns an individual hard disk drive as a physical magnetic storage device, including its recording assembly, integrated electronics, interfaces, operating constraints and observable condition; interpreting the registry term as a complete drive rather than a bare platter remains provisional.", "in_scope": [ "Drive identity and evidence that its recording medium is rotating magnetic platters", "Physical, electrical and command-interface compatibility", "Addressable capacity, sector presentation and recording behaviour", "Mechanical condition, diagnostic evidence and read/write reliability", "Drive-level access restrictions, data exposure and lifecycle actions" ], "out_of_scope": [ "Filesystem, partition and file semantics, owned by logical storage models", "RAID membership policy, redundancy and array reconstruction, owned by storage-array models", "External enclosure, USB bridge and host-controller design, owned by their device models", "Meaning, ownership and retention policy of stored information, owned by information and governance models", "Host operating-system configuration and application performance, owned by host and workload models" ], "distinguishing_features": [ "Identify rotating magnetic platters and a head-positioning mechanism through reliable product identification or existing inspection evidence; an SSD lacks this recording mechanism.", "Distinguish the complete drive, with recording assembly and control electronics, from a bare magnetic platter or replacement circuit board.", "Distinguish an HDD inside an external enclosure from the enclosure and bridge that expose it to the host; a USB connection alone does not identify the internal medium.", "Confirm that the device uses magnetic disks rather than a removable optical disc or magnetic tape; a drive letter or block-device interface alone is insufficient.", "For a hybrid drive, establish whether rotating magnetic media provide persistent bulk storage and record any flash component separately." ], "characteristics": [ { "name": "Drive identity", "kind": "category", "unit_or_values": "Manufacturer, model, serial number and firmware revision; unknown or conflicting evidence allowed", "why_it_matters": "Connects observations, specifications and action history to the correct physical drive." }, { "name": "Recording architecture", "kind": "category", "unit_or_values": "Conventional magnetic recording, shingled magnetic recording with management mode, other documented architecture, or unknown", "why_it_matters": "Affects host compatibility, sustained-write behaviour and permissible command assumptions." }, { "name": "Physical envelope", "kind": "measurement", "unit_or_values": "Width, depth and height in mm; mass in g", "why_it_matters": "Determines whether a particular bay or enclosure can accommodate the drive." }, { "name": "Connection and power requirements", "kind": "category", "unit_or_values": "Observed connector, documented protocol, required supply rails and startup demand", "why_it_matters": "Prevents connections based only on connector resemblance and supports safe power provisioning." }, { "name": "Exposed capacity", "kind": "measurement", "unit_or_values": "Addressable logical-block count and calculated bytes, with observation path and timestamp", "why_it_matters": "Separates host-visible capacity from label claims and detects presentation changes." }, { "name": "Sector presentation", "kind": "measurement", "unit_or_values": "Logical and reported physical sector sizes in bytes", "why_it_matters": "Affects alignment, imaging, migration and compatibility." }, { "name": "Rotational speed", "kind": "measurement", "unit_or_values": "rpm, supported by device or manufacturer evidence; unknown permitted", "why_it_matters": "Helps interpret expected latency and mechanical operating behaviour." }, { "name": "Mechanical operating state", "kind": "state", "unit_or_values": "Unpowered, starting, spinning, standby, failing to spin, abnormal behaviour, or unknown", "why_it_matters": "Guides whether further power cycles or access attempts are appropriate." }, { "name": "Media and diagnostic condition", "kind": "state", "unit_or_values": "Timestamped errors, diagnostic results and counter trends with vendor-specific interpretation", "why_it_matters": "Supports evidence-based decisions without treating one health flag as proof of reliability." }, { "name": "Operating temperature", "kind": "measurement", "unit_or_values": "Degrees Celsius, sensor source and timestamp", "why_it_matters": "Allows comparison with documented limits and investigation of thermal problems." }, { "name": "Connection path", "kind": "relation", "unit_or_values": "Host, controller, bridge, enclosure and physical port through which the drive is observed", "why_it_matters": "Separates drive faults from power, transport and command-translation faults." }, { "name": "Access and sanitisation state", "kind": "state", "unit_or_values": "Reported lock and encryption states, sanitisation method, completion evidence and verification limits", "why_it_matters": "Constrains access, recovery, reuse and transfer decisions." } ], "affordances": [ "Identify and interrogate the drive through a compatible connection while recording the observation path.", "Mount, power and operate the drive within its documented mechanical, electrical and environmental limits.", "Read or image addressable sectors, choosing an access strategy appropriate to the condition and recovery priority.", "Write, overwrite or run diagnostic operations when authorised and justified by the drive's condition.", "Isolate suspected drive failures from enclosure, cable, controller and power faults.", "Sanitise, reuse, transfer or retire the drive using a supported method and explicit completion evidence." ] }, "sources": [], "structure": { "bundles": [ { "id": "drive-identity-and-boundary", "name": "Drive identity and boundary", "description": "Establishes which physical magnetic storage device is being modelled and separates it from surrounding storage components.", "rationale": "Host-visible names and enclosure labels can conceal the underlying drive or incorrectly identify the object being acted upon.", "layers": [ { "id": "recording-device-identification", "name": "Recording device identification", "description": "Determines whether the object is a complete HDD and identifies its recording architecture.", "findings": [ { "id": "magnetic-drive-evidence", "name": "Magnetic drive evidence", "description": "Records evidence for a rotating magnetic recording assembly and any hybrid storage components.", "questions": [ { "text": "What evidence identifies this object as a complete hard disk drive rather than an SSD, bare platter or external enclosure?", "kind": "definition", "id": "magnetic-drive-evidence-q01" }, { "text": "Which label, device response or manufacturer document establishes its recording architecture?", "kind": "provenance", "id": "magnetic-drive-evidence-q02" } ] } ] }, { "id": "physical-and-reported-identity", "name": "Physical and reported identity", "description": "Reconciles the drive's physical markings with identities exposed through its connection path.", "findings": [ { "id": "identity-reconciliation", "name": "Identity reconciliation", "description": "Associates model, serial and firmware evidence with the physical drive while preserving discrepancies.", "questions": [ { "text": "Do the physical label and device-reported model and serial number agree, and when were they observed?", "kind": "provenance", "id": "identity-reconciliation-q01" }, { "text": "Which reported identifiers belong to the drive, and which belong to a bridge, enclosure or logical volume?", "kind": "boundary", "id": "identity-reconciliation-q02" } ] } ] } ] }, { "id": "installation-and-operating-envelope", "name": "Installation and operating envelope", "description": "Captures the conditions required to connect, mount and operate this drive.", "rationale": "An HDD needs suitable startup power and mechanical support as well as a compatible data interface.", "layers": [ { "id": "connection-and-power", "name": "Connection and power", "description": "Establishes electrical and protocol compatibility across the actual connection path.", "findings": [ { "id": "supported-connection-path", "name": "Supported connection path", "description": "Records connectors, protocol, power requirements and intermediary devices affecting access.", "questions": [ { "text": "Which data protocol, connectors, supply rails and startup power requirements are documented for this drive?", "kind": "definition", "id": "supported-connection-path-q01" }, { "text": "Can the proposed host, adapter and power supply meet those requirements and pass the commands needed for the intended action?", "kind": "action", "id": "supported-connection-path-q02" } ] } ] }, { "id": "mechanical-and-thermal-conditions", "name": "Mechanical and thermal conditions", "description": "Relates installation and handling to the drive's documented operating limits.", "findings": [ { "id": "installation-suitability", "name": "Installation suitability", "description": "Assesses fit, mounting, cooling and exposure to shock or vibration.", "questions": [ { "text": "What are the drive's dimensions, mounting requirements and documented operating and non-operating environmental limits?", "kind": "measurement", "id": "installation-suitability-q01" }, { "text": "Does the proposed installation or transport method satisfy those limits for the drive's powered or unpowered state?", "kind": "action", "id": "installation-suitability-q02" } ] } ] } ] }, { "id": "media-presentation-and-io-behaviour", "name": "Media presentation and I/O behaviour", "description": "Describes the storage the drive exposes and the recording behaviours relevant to using it.", "rationale": "Capacity alone does not establish whether an HDD can support a host's addressing assumptions or intended write pattern.", "layers": [ { "id": "addressable-media", "name": "Addressable media", "description": "Records host-visible capacity and sector geometry without owning partitions or filesystems.", "findings": [ { "id": "capacity-and-sector-evidence", "name": "Capacity and sector evidence", "description": "Captures measured block presentation and discrepancies across labels or connection paths.", "questions": [ { "text": "How many logical blocks are exposed, and what logical and physical sector sizes does the drive report?", "kind": "measurement", "id": "capacity-and-sector-evidence-q01" }, { "text": "Are capacity discrepancies attributable to units, drive configuration, inaccessible regions or an intermediary device, and what remains unexplained?", "kind": "boundary", "id": "capacity-and-sector-evidence-q02" } ] } ] }, { "id": "recording-and-write-semantics", "name": "Recording and write semantics", "description": "Captures recording constraints, caching and completion behaviour relevant to actual workloads.", "findings": [ { "id": "workload-and-persistence-constraints", "name": "Workload and persistence constraints", "description": "Connects documented drive behaviour to write compatibility and evidence of durable completion.", "questions": [ { "text": "What evidence establishes conventional or shingled recording, any host-managed zones, and the supported cache and flush behaviour?", "kind": "provenance", "id": "workload-and-persistence-constraints-q01" }, { "text": "What must the host do for the intended write pattern and durability requirement, given the drive and connection path?", "kind": "action", "id": "workload-and-persistence-constraints-q02" } ] } ] } ] }, { "id": "condition-and-recovery-triage", "name": "Condition and recovery triage", "description": "Combines mechanical symptoms, diagnostic history and access results to guide further interaction.", "rationale": "Repeated tests or power cycles may consume a failing drive's remaining opportunity for recovery.", "layers": [ { "id": "condition-evidence", "name": "Condition evidence", "description": "Records observed symptoms and diagnostic trends with their interpretation limits.", "findings": [ { "id": "mechanical-and-media-observations", "name": "Mechanical and media observations", "description": "Preserves startup behaviour, abnormal sounds, read failures and health telemetry as distinct observations.", "questions": [ { "text": "What startup behaviour, abnormal sounds, temperatures, read errors and diagnostic results have been observed, and how have they changed?", "kind": "measurement", "id": "mechanical-and-media-observations-q01" }, { "text": "Which diagnostic meanings are documented for this model and firmware, and which interpretations remain uncertain?", "kind": "provenance", "id": "mechanical-and-media-observations-q02" } ] } ] }, { "id": "fault-isolation-and-access-strategy", "name": "Fault isolation and access strategy", "description": "Separates likely drive faults from connection faults and selects a justified next operation.", "findings": [ { "id": "least-damaging-next-access", "name": "Least damaging next access", "description": "Records recovery priorities, existing copies, stop conditions and the justification for further access.", "questions": [ { "text": "What evidence separates media or mechanical failure from cable, controller, bridge or power faults?", "kind": "boundary", "id": "least-damaging-next-access-q01" }, { "text": "Given the symptoms, data-recovery priority and available copies, should access stop, proceed with controlled imaging, or move to specialist recovery?", "kind": "action", "id": "least-damaging-next-access-q02" } ] } ] } ] }, { "id": "access-control-and-disposition", "name": "Access control and disposition", "description": "Records drive-level access restrictions and evidence needed for sanitisation, transfer or retirement.", "rationale": "A drive can be unreadable yet retain data, and a reported erase completion may not establish the required sanitisation outcome.", "layers": [ { "id": "drive-level-access-state", "name": "Drive-level access state", "description": "Identifies device locks and encryption boundaries without storing credentials in the model.", "findings": [ { "id": "locks-and-encryption-boundaries", "name": "Locks and encryption boundaries", "description": "Distinguishes drive-enforced restrictions from enclosure or host encryption and records authorised access paths.", "questions": [ { "text": "Which locks or encryption mechanisms are evidenced, and are they enforced by the drive, enclosure or host?", "kind": "boundary", "id": "locks-and-encryption-boundaries-q01" }, { "text": "What authorised credential or key-management reference is needed for access, and what consequences would unlocking, resetting or key removal have?", "kind": "action", "id": "locks-and-encryption-boundaries-q02" } ] } ] }, { "id": "sanitisation-and-release", "name": "Sanitisation and release", "description": "Connects the intended disposition to supported sanitisation methods and verifiable outcomes.", "findings": [ { "id": "disposition-evidence", "name": "Disposition evidence", "description": "Records method support, execution results, coverage limits and the basis for releasing or retiring the drive.", "questions": [ { "text": "Which sanitisation methods are supported through this connection path, and what evidence establishes their coverage of remapped or otherwise inaccessible media?", "kind": "provenance", "id": "disposition-evidence-q01" }, { "text": "What authorisation, completion and verification evidence is required before this drive may be reused, transferred or destroyed?", "kind": "action", "id": "disposition-evidence-q02" } ] } ] } ] } ] }, "openQuestions": [ "Does the registry intend 'hard disk' to mean the complete HDD, the magnetic recording medium, or both, and is an existing world model already authoritative for that concept?", "Should hybrid drives fall wholly within this entry or be represented through a relationship to a separate flash-storage component model?", "Which manufacturer and protocol sources are needed to interpret recording mode, diagnostic attributes and command support without unreliable inference from model names?", "What evidence is sufficient to distinguish drive failure from connection-path failure while limiting further stress on a drive containing the only available copy of data?", "Which sanitisation assurance requirements apply to each disposition, and how should unavailable evidence about inaccessible media or encryption keys constrain release?" ], "statistics": { "bundles": 5, "layers": 10, "findings": 10, "questions": 20 } }, "draft": { "generator": "vr.draft.v3", "status": "draft-generated", "researched": false, "archetype": "device, machine or tool", "method": "Written from the archetype playbook - what this kind of thing needs beyond identity and provenance - and from the structure that recurred across 6,333 models already researched by two engines. Applied to this entry by rule. No source was read for this thing and no claim here is researched. This entry carries no facets of its own, so they were inferred from its domain - a guess about a whole domain applied to one thing.", "facetsInferred": true, "nextPass": "A researcher replaces this draft with a sourced specification. Treat every sentence below as a proposal to argue with.", "purpose": "Give an agent a durable, checkable way to recognise a hard disk, record what state it is in, and decide what may be done with it.", "whatItIs": "Enable an AI agent to recognise a hard disk drive, assess its compatibility, condition and data exposure, and decide whether it may be connected, used, recovered, sanitised or retired.", "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: WD Black, RAM drive, Seagate Medalist, HP Kittyhawk, PlayStation 2 Hard Disk Drive, REV, Quantum Fireball, Microdrive, removable hard drive, ST3000DM001, Seagate Barracuda, Apple ProFile.", "17 finer distinctions are held as aliases rather than separate entries, because telling them apart needs a task that asks for it.", "Described in 132 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 hard disk, 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": [ "WD Black", "RAM drive", "Seagate Medalist", "HP Kittyhawk", "PlayStation 2 Hard Disk Drive", "REV", "Quantum Fireball", "Microdrive", "removable hard drive", "ST3000DM001", "Seagate Barracuda", "Apple ProFile" ] } ], "standing": "Described in 132 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 hard disk from another, and a hard disk 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 hard disk, 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 hard disk, 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 hard disk 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 hard disk, 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 hard disk, 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 hard disk 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 hard disk 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 hard disk, 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 hard disk, 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 hard disk 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 hard disk from the things most often confused with it.", "questions": [ { "id": "distinguishing-features-q01", "text": "What identifies and describes what distinguishes a hard disk, 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 hard disk, 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 hard disk 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 hard disk 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 hard disk, 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 hard disk, 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 hard disk 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 hard disk is built from and which parts are replaceable.", "questions": [ { "id": "parts-and-materials-q01", "text": "What identifies and describes the composition of a hard disk, 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 hard disk, 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 hard disk 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 hard disk is judged and by whom.", "questions": [ { "id": "condition-assessment-q01", "text": "What identifies and describes the condition of a hard disk, 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 hard disk, 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 hard disk 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 hard disk 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 hard disk is, and what that position is measured against.", "questions": [ { "id": "position-and-frame-q01", "text": "What identifies and describes the location of a hard disk, 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 hard disk, 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 hard disk 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 hard disk 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 hard disk, 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 hard disk, 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 hard disk 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 hard disk 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 hard disk between them.", "questions": [ { "id": "stages-and-transitions-q01", "text": "What identifies and describes the lifecycle of a hard disk, 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 hard disk, 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 hard disk 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 hard disk, how often and by whom.", "findings": [ { "id": "observation-record", "name": "Observation record", "description": "How an observation of a hard disk 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 hard disk, 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 hard disk, 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 hard disk 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 hard disk 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 hard disk 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 hard disk, 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 hard disk 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 hard disk 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 hard disk 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 hard disk 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 hard disk 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 hard disk, 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 hard disk 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 hard disk and how confident it is.", "questions": [ { "id": "claim-provenance-q01", "text": "What identifies and describes a claim about a hard disk, 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 hard disk, 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 hard disk 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 hard disk is retired without being erased.", "questions": [ { "id": "validity-and-supersession-q01", "text": "What identifies and describes the validity of a claim about a hard disk, 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 hard disk, 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 hard disk 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 } } } }