{ "model": { "rank": 5221, "code": "thing-q185091", "model_id": "vr.tr.remote-control", "name": "remote control", "purpose": "Enable an agent to recognise a remote control, assess its readiness and compatibility, and determine which commands it can appropriately send to a separate device.", "family": "Thing Registry", "category": "Physical world and living systems", "status": "research-draft", "kind": "thing", "plane": "PHY", "domain": "PHY.OBJ", "industry": "", "version": "", "url": "/models/thing/q185091/", "tier": 2, "score": 69, "payload": { "layer": "wikidata", "aliases": [ "ground control station", "Zellweger off-peak", "Verso", "Hitfist OWS", "MYO", "DJI RC Pro", "camera remote control", "Ortho Remote", "TV remote", "IKEA RODRET", "computer case fan controller", "wire-guidance", "wireless presenters", "Siri Remote", "universal remote", "TV-B-Gone", "Logitech Harmony" ], "aliasCount": 17, "merged": 17, "knownIn": 69, "facets": null, "markers": [], "lexicalClass": "", "senseRank": null, "alsoRegisteredAs": null, "source": { "dataset": "wikidata", "item": "Q185091", "url": "https://www.wikidata.org/wiki/Q185091", "license": "CC0 1.0" } }, "research": { "vercy": "1.0-draft", "publication": { "status": "research-draft", "adjudicationStatus": "unreviewed", "publishableCanonical": false, "generatedAt": "2026-09-09T21:55:14Z", "providers": [ "Codex" ], "breadth": "recalled by Codex without web access - no source was read", "missingProviders": [], "pass": 2, "cost": { "grok": { "seconds": 20.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: 01a0882a-1aed-7420-a763-e99954f68421\n--------\nuser\nDescribe what is already known about one registered thing. Answer as JSON only, no prose around it.\n\nThing: remote control\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 ", "usd": 0, "recall": true }, "codex": { "seconds": 59.1, "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: 01a0882a-1ae8-7241-b8a6-72af80adcb7d\n--------\nuser\nYou are drafting a Vercy meta-model for one registered thing. Answer as JSON only, no prose around it.\n\nThing: remote control\nRegistry id: vr.tr.remote-control\nPlane / domain: PHY / PHY.OBJ\nRegistry definition: (none recorded)\nNames folded into this entry: (no" } } }, "metaModel": { "id": "THING-Q185091", "registryId": "vr.tr.remote-control", "name": "remote control", "version": "0.1.0-research.1", "entryKind": "thing", "family": "Thing Registry", "domain": [ "PHY.OBJ" ], "status": "research-draft" }, "canonicalUrl": "https://ver.cy/models/thing/q185091/", "model": { "registry_id": "vr.tr.remote-control", "name": "remote control", "purpose": "Enable an agent to recognise a remote control, assess its readiness and compatibility, and determine which commands it can appropriately send to a separate device.", "definition": "A remote control is a physical input device that sends commands over a wired or wireless link to operate separate equipment from a distance.", "scope_statement": "This model covers remote control as a kind of physical controller that accepts user input and sends commands to equipment operated at a distance, including dedicated and universal controllers; product specifications and individual unit observations supply evidence for its characteristics.", "in_scope": [ "User inputs, command mappings and target-selection modes", "Command transmission, addressing, pairing and compatibility", "Controller power, operating states and command feedback", "Readiness checks, maintenance and remote-specific failure diagnosis", "Command authority and safeguards against unintended operation" ], "out_of_scope": [ "The internal operation and overall condition of the controlled equipment", "Software-only remote-control applications and remote desktop services", "The general activity of controlling something remotely", "Passive keys, identification tokens and sensors that do not provide a command interface", "Product-line catalogues and histories of individual controller units" ], "distinguishing_features": [ "It provides an input-to-command path intended to operate separate equipment, rather than merely displaying received information.", "Its intended operation allows the user to remain away from the controlled equipment; a control panel fixed to that equipment does not meet this boundary.", "Its commands must be interpretable by a compatible target, so a matching connector, carrier or frequency alone does not establish compatibility.", "It has a physical control interface; a phone application alone belongs to a software model, while a multipurpose device running that application needs an explicit boundary decision.", "Its defining output is an operational command rather than only identity, proximity or a sensed measurement." ], "characteristics": [ { "name": "Controlled target", "kind": "relation", "unit_or_values": "Compatible equipment kinds, target models or configured target instances", "why_it_matters": "Determines what equipment the controller is intended and configured to operate." }, { "name": "Transmission medium", "kind": "category", "unit_or_values": "Infrared, radio, wired link, other documented medium, or unknown", "why_it_matters": "Determines whether orientation, obstructions, interference or cable continuity can prevent command delivery." }, { "name": "Command protocol and code profile", "kind": "category", "unit_or_values": "Documented protocol, code set, learned profile or unknown", "why_it_matters": "Separates physical signal compatibility from actual command compatibility." }, { "name": "Target-selection state", "kind": "state", "unit_or_values": "Selected device mode, active address or group, unconfigured, or unknown", "why_it_matters": "The same input may operate different equipment depending on the selected target." }, { "name": "Association state", "kind": "state", "unit_or_values": "Not required, unpaired, pairing, paired, association lost, or unknown", "why_it_matters": "Distinguishes controllers that require an association from those that transmit without pairing." }, { "name": "Input-to-command mapping", "kind": "relation", "unit_or_values": "Input and gesture mapped to command, target and mode", "why_it_matters": "Makes short presses, holds, repeated presses and macros distinguishable." }, { "name": "Effective operating distance", "kind": "measurement", "unit_or_values": "Metres, with target, orientation, obstructions and test conditions recorded", "why_it_matters": "Supports a practical delivery assessment without treating nominal range as a guarantee." }, { "name": "Power supply", "kind": "category", "unit_or_values": "Replaceable cell specification and count, rechargeable supply, external supply, energy harvesting, or other documented source", "why_it_matters": "Determines replenishment, charging and replacement requirements." }, { "name": "Power readiness", "kind": "state", "unit_or_values": "Ready, low-power indication, depleted, charging, supply fault, or unknown", "why_it_matters": "Helps distinguish power loss from communication and configuration faults." }, { "name": "Feedback capability", "kind": "category", "unit_or_values": "No feedback, local input indication, transmission indication, target acknowledgement, reported target state; multiple values allowed", "why_it_matters": "Prevents a local light or display from being mistaken for proof that the target acted." }, { "name": "Command authority", "kind": "relation", "unit_or_values": "Permitted operator, target and command set, with restrictions or unknown status", "why_it_matters": "Technical ability to transmit does not by itself establish permission to operate equipment." } ], "affordances": [ "Identify candidate targets and verify command compatibility using documentation or an authorised low-impact test.", "Select a target mode, configure a code profile or pair with equipment where supported.", "Send an authorised command while accounting for toggle, hold, repeat and macro behaviour.", "Assess command delivery using the strongest available feedback and record uncertainty about the resulting target state.", "Diagnose power, input, configuration and transmission faults before replacing the controller.", "Replace supported consumables, recharge, clean or reset the controller according to its documented procedure." ] }, "sources": [], "structure": { "bundles": [ { "id": "target-and-command-compatibility", "name": "Target and command compatibility", "description": "Establishes which equipment the remote can control and how its inputs acquire meaning.", "rationale": "A remote may appear functional while sending commands that the intended target cannot interpret.", "layers": [ { "id": "target-coverage", "name": "Target coverage", "description": "Separates claimed support from verified compatibility and current target selection.", "findings": [ { "id": "supported-targets", "name": "Supported targets", "description": "Record the equipment families or models supported and the evidence for that support, including any function limitations.", "questions": [ { "text": "Which equipment models or receiver systems are documented as compatible, and by which source?", "kind": "provenance", "id": "supported-targets-q01" }, { "text": "Does compatibility cover all intended functions or only a subset such as power and volume?", "kind": "boundary", "id": "supported-targets-q02" } ] } ] }, { "id": "input-semantics", "name": "Input semantics", "description": "Describes how controls, modes and gestures determine transmitted commands.", "findings": [ { "id": "mode-dependent-command-map", "name": "Mode-dependent command map", "description": "Record button or other input meanings, selected target modes, learned commands and macros where present.", "questions": [ { "text": "What command and target correspond to each relevant input in the currently selected mode?", "kind": "definition", "id": "mode-dependent-command-map-q01" }, { "text": "How do a short press, a held input and repeated presses differ, and can one input initiate a sequence?", "kind": "action", "id": "mode-dependent-command-map-q02" } ] } ] } ] }, { "id": "signal-path-and-association", "name": "Signal path and association", "description": "Describes how a command reaches its receiver and how the intended receiver is distinguished.", "rationale": "Transmission conditions and association failures require different remedies from incorrect command mappings.", "layers": [ { "id": "physical-command-path", "name": "Physical command path", "description": "Records the transmission medium and the conditions under which signals reach the target.", "findings": [ { "id": "delivery-conditions", "name": "Delivery conditions", "description": "Assess distance, orientation, obstructions, interference and any intermediary receiver or bridge relevant to command delivery.", "questions": [ { "text": "Which medium carries commands, and does this implementation require aiming, a clear path, a cable or an intermediary?", "kind": "definition", "id": "delivery-conditions-q01" }, { "text": "At what distance and under what orientation and obstruction conditions has reliable operation been observed?", "kind": "measurement", "id": "delivery-conditions-q02" } ] } ] }, { "id": "receiver-selection", "name": "Receiver selection", "description": "Separates pairing, addressing and shared code reception.", "findings": [ { "id": "association-and-addressing", "name": "Association and addressing", "description": "Record whether the remote requires pairing, uses a configured address or sends codes that multiple receivers may accept.", "questions": [ { "text": "How is the intended receiver selected, and can other nearby receivers accept the same command?", "kind": "definition", "id": "association-and-addressing-q01" }, { "text": "What documented steps establish, verify or remove the association without disrupting other controllers?", "kind": "action", "id": "association-and-addressing-q02" } ] } ] } ] }, { "id": "readiness-feedback-and-recovery", "name": "Readiness, feedback and recovery", "description": "Determines whether the remote can operate and what evidence supports a diagnosis when it does not.", "rationale": "An unresponsive target can reflect depleted power, damaged inputs, lost configuration or a failed signal path.", "layers": [ { "id": "power-and-input-condition", "name": "Power and input condition", "description": "Assesses the supply and physical controls needed to generate commands.", "findings": [ { "id": "controller-readiness", "name": "Controller readiness", "description": "Record power requirements, supply condition, stuck or unresponsive controls and damage affecting command generation.", "questions": [ { "text": "What power source is specified, and what observable evidence indicates adequate power?", "kind": "provenance", "id": "controller-readiness-q01" }, { "text": "Do any controls fail to register, remain engaged or produce intermittent or repeated commands?", "kind": "measurement", "id": "controller-readiness-q02" } ] } ] }, { "id": "feedback-and-fault-isolation", "name": "Feedback and fault isolation", "description": "Distinguishes local activity from delivery and execution, then guides recovery.", "findings": [ { "id": "evidence-of-command-success", "name": "Evidence of command success", "description": "Record separately evidence of input registration, transmission, target acknowledgement and actual target behaviour.", "questions": [ { "text": "Does each light, sound or display report local activity, receiver acknowledgement or an observed target state?", "kind": "definition", "id": "evidence-of-command-success-q01" }, { "text": "Which authorised low-impact test can distinguish a remote fault from a receiver or target fault?", "kind": "action", "id": "evidence-of-command-success-q02" } ] }, { "id": "configuration-preserving-recovery", "name": "Configuration-preserving recovery", "description": "Identify supported maintenance and recovery actions together with any effect on pairing, learned commands or macros.", "questions": [ { "text": "Which documented battery replacement, charging, cleaning or reset procedure applies to this controller?", "kind": "provenance", "id": "configuration-preserving-recovery-q01" }, { "text": "Will the proposed recovery action erase target profiles, learned commands or associations, and how can they be restored?", "kind": "action", "id": "configuration-preserving-recovery-q02" } ] } ] } ] }, { "id": "controlled-action-and-safeguards", "name": "Controlled action and safeguards", "description": "Connects command meaning, operator authority and available safeguards to decisions about use.", "rationale": "A command can affect unseen equipment, repeat unexpectedly or reverse a state when the remote lacks reliable feedback.", "layers": [ { "id": "command-consequences", "name": "Command consequences", "description": "Characterises commands whose outcome depends on target state or input duration.", "findings": [ { "id": "state-dependent-operation", "name": "State-dependent operation", "description": "Distinguish explicit set commands from toggles, continuous commands and sequences whose effect depends on prior state.", "questions": [ { "text": "Does the relevant command set a known state, toggle an unknown state, continue while held or initiate a sequence?", "kind": "definition", "id": "state-dependent-operation-q01" }, { "text": "What target-state evidence is needed before issuing or retrying this command?", "kind": "action", "id": "state-dependent-operation-q02" } ] } ] }, { "id": "authority-and-unintended-activation", "name": "Authority and unintended activation", "description": "Records use restrictions and safeguards present in the controller-target arrangement.", "findings": [ { "id": "permitted-and-protected-use", "name": "Permitted and protected use", "description": "Record authorised commands and any documented lock, enable control, confirmation or target-side interlock without assuming such features exist.", "questions": [ { "text": "Who may operate the selected target, and which commands or circumstances are restricted?", "kind": "boundary", "id": "permitted-and-protected-use-q01" }, { "text": "What prevents accidental activation, and is that protection implemented by the remote, receiver or controlled equipment?", "kind": "boundary", "id": "permitted-and-protected-use-q02" }, { "text": "How can the controller be placed in a documented inactive or locked condition when unintended transmission would matter?", "kind": "action", "id": "permitted-and-protected-use-q03" } ] } ] } ] }, { "id": "evidence-and-external-alignment", "name": "Evidence and external alignment", "description": "What the world already says about this thing, gathered so the model can be checked against it.", "rationale": "A model that cannot be lined up against existing standards, identifiers and practice cannot be adopted by anyone who already uses them.", "layers": [ { "id": "reported-evidence", "name": "Reported evidence", "description": "Findings from the breadth pass, kept separate from the structural claims.", "findings": [ { "id": "evidence-confidence-notes", "name": "Check these first", "description": "Recalled without web access and unsourced; every item is a lead to verify.", "evidence": [ "The physical controller sense is inferred from PHY.OBJ; the name can also denote the activity or an entire system.", "The numerical examples describe common consumer infrared remotes, not wired, radio or industrial varieties generally.", "Recalled standards and identifier schemes were not checked against sources; product-specific applicability and current editions require verification." ], "questions": [ { "id": "evidence-confidence-notes-q01", "text": "Which of these check these first hold for the sense of remote control 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": [ "Infrared remote control", "Radio-frequency remote control", "Wired remote control", "Universal remote control", "Learning remote control", "Industrial remote-control pendant" ], "questions": [ { "id": "evidence-kinds-q01", "text": "Which of these kinds and varieties hold for the sense of remote control 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": "Manufacturer model number", "value_or_pattern": "Manufacturer-specific alphanumeric code", "note": "Identifies a product model; compatibility also depends on the controlled equipment and command protocol." }, { "scheme": "FCC ID", "value_or_pattern": "Grantee code followed by a product code", "note": "Found on applicable US radio equipment or its radio module; not a universal identifier for remote controls." } ], "questions": [ { "id": "evidence-identifiers-q01", "text": "Which of these identifiers and schemes hold for the sense of remote control 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": [ "Bluetooth Core Specification - Bluetooth Special Interest Group; relevant to remote controls using Bluetooth.", "IEEE 802.15.4 - IEEE; relevant to remote controls using this low-rate wireless communication technology." ], "questions": [ { "id": "evidence-standards-and-regulation-q01", "text": "Which of these standards and regulation hold for the sense of remote control 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": [ "Operating televisions, audio equipment and media players", "Adjusting air conditioners, fans and lighting", "Opening garage doors and operating gates", "Controlling toys and model vehicles", "Operating industrial machinery from a separate control position" ], "questions": [ { "id": "evidence-real-world-use-q01", "text": "Which of these real-world use hold for the sense of remote control 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": "Indoor operating distance of common consumer infrared remotes", "typical_range": "Approximately 5-10 under unobstructed conditions", "unit": "m" }, { "quantity": "Infrared emitter wavelength", "typical_range": "Commonly around 940", "unit": "nm" } ], "questions": [ { "id": "evidence-measurements-q01", "text": "Which of these typical measurements hold for the sense of remote control 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": [ "Depleted batteries, leaking cells or corroded contacts interrupt operation.", "Worn, contaminated or stuck buttons cause missed or repeated commands.", "Obstructions, misalignment or strong ambient light interfere with infrared reception.", "Radio interference, lost pairing or incompatible command codes prevent reliable control.", "Unintended commands or loss of communication can create hazards when controlling moving equipment." ], "questions": [ { "id": "evidence-failure-modes-and-hazards-q01", "text": "Which of these failure modes and hazards hold for the sense of remote control 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": [ "Permitted radio frequencies, transmitter power and equipment approval requirements vary by jurisdiction.", "Regional versions of controlled equipment may require different remote-control codes or product models." ], "questions": [ { "id": "evidence-regional-variation-q01", "text": "Which of these regional variation hold for the sense of remote control 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": "Remote control system", "difference": "The system includes the command device, communication link, receiver and control integration; this entry covers the physical command device." }, { "name": "Control panel", "difference": "A control panel groups operating controls and may be mounted directly on equipment; a remote control operates separate equipment over a link." }, { "name": "Remote-control application", "difference": "An application provides remote-control functionality in software on a general-purpose device rather than constituting the physical device kind described here." }, { "name": "Telemetry device", "difference": "Telemetry primarily sends measurements or status from equipment, whereas a remote control primarily sends operating commands to it." } ], "questions": [ { "id": "evidence-neighbours-q01", "text": "Which of these neighbouring kinds and how to tell them apart hold for the sense of remote control this model covers, and on what evidence?", "kind": "provenance" } ] } ] } ] } ] }, "openQuestions": [ "Does the registry intend to include tethered pendants, industrial radio controllers and vehicle key fobs, or primarily consumer equipment remotes?", "How should multipurpose physical devices acting as remotes be related to this kind without duplicating their primary device models?", "Which primary documentation establishes representative protocol families, compatibility limits and measured operating ranges for the intended scope?", "Which standards, issuing bodies and certification requirements apply to each included transmission technology, jurisdiction and controlled-equipment class?", "For controllers without target acknowledgement, what evidence threshold should an agent require before retrying a toggle, macro or potentially consequential command?" ], "statistics": { "bundles": 5, "layers": 9, "findings": 18, "questions": 28 } }, "draft": { "generator": "vr.draft.v3", "status": "draft-generated", "researched": false, "archetype": "device, machine or tool", "method": "Written from the archetype playbook - what this kind of thing needs beyond identity and provenance - and from the structure that recurred across 6,333 models already researched by two engines. Applied to this entry by rule. No source was read for this thing and no claim here is researched. This entry carries no facets of its own, so they were inferred from its domain - a guess about a whole domain applied to one thing.", "facetsInferred": true, "nextPass": "A researcher replaces this draft with a sourced specification. Treat every sentence below as a proposal to argue with.", "purpose": "Give an agent a durable, checkable way to recognise a remote control, record what state it is in, and decide what may be done with it.", "whatItIs": "Enable an agent to recognise a remote control, assess its readiness and compatibility, and determine which commands it can appropriately send to a separate device.", "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: ground control station, Zellweger off-peak, Verso, Hitfist OWS, MYO, DJI RC Pro, camera remote control, Ortho Remote, TV remote, IKEA RODRET, computer case fan controller, wire-guidance.", "17 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 remote control, 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": [ "ground control station", "Zellweger off-peak", "Verso", "Hitfist OWS", "MYO", "DJI RC Pro", "camera remote control", "Ortho Remote", "TV remote", "IKEA RODRET", "computer case fan controller", "wire-guidance" ] } ], "standing": "Described in 69 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 remote control from another, and a remote control 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 remote control, 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 remote control, 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 remote control 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 remote control, 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 remote control, 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 remote control 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 remote control 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 remote control, 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 remote control, 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 remote control 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 remote control from the things most often confused with it.", "questions": [ { "id": "distinguishing-features-q01", "text": "What identifies and describes what distinguishes a remote control, 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 remote control, 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 remote control 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 remote control 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 remote control, 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 remote control, 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 remote control 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 remote control is built from and which parts are replaceable.", "questions": [ { "id": "parts-and-materials-q01", "text": "What identifies and describes the composition of a remote control, 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 remote control, 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 remote control 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 remote control is judged and by whom.", "questions": [ { "id": "condition-assessment-q01", "text": "What identifies and describes the condition of a remote control, 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 remote control, 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 remote control 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 remote control 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 remote control is, and what that position is measured against.", "questions": [ { "id": "position-and-frame-q01", "text": "What identifies and describes the location of a remote control, 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 remote control, 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 remote control 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 remote control 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 remote control, 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 remote control, 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 remote control 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 remote control 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 remote control between them.", "questions": [ { "id": "stages-and-transitions-q01", "text": "What identifies and describes the lifecycle of a remote control, 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 remote control, 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 remote control 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 remote control, how often and by whom.", "findings": [ { "id": "observation-record", "name": "Observation record", "description": "How an observation of a remote control 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 remote control, 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 remote control, 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 remote control 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 remote control 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 remote control 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 remote control, 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 remote control 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 remote control 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 remote control 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 remote control 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 remote control 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 remote control, 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 remote control 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 remote control and how confident it is.", "questions": [ { "id": "claim-provenance-q01", "text": "What identifies and describes a claim about a remote control, 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 remote control, 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 remote control 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 remote control is retired without being erased.", "questions": [ { "id": "validity-and-supersession-q01", "text": "What identifies and describes the validity of a claim about a remote control, 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 remote control, 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 remote control 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 } } } }