{ "model": { "rank": 3787, "code": "thing-q165970", "model_id": "vr.tr.touchscreen", "name": "touchscreen", "purpose": "Enable an agent to recognise a touchscreen, assess its display and touch-input condition, and determine which interactions, adjustments and maintenance actions are appropriate.", "family": "Thing Registry", "category": "Physical world and living systems", "status": "research-draft", "kind": "thing", "plane": "PHY", "domain": "PHY.OBJ", "industry": "", "version": "", "url": "/models/thing/q165970/", "tier": 2, "score": 82, "payload": { "layer": "wikidata", "aliases": [ "Force Touch", "resistive touchscreen" ], "aliasCount": 2, "merged": 2, "knownIn": 82, "facets": null, "markers": [], "lexicalClass": "", "senseRank": null, "alsoRegisteredAs": null, "source": { "dataset": "wikidata", "item": "Q165970", "url": "https://www.wikidata.org/wiki/Q165970", "license": "CC0 1.0" } }, "research": { "vercy": "1.0-draft", "publication": { "status": "research-draft", "adjudicationStatus": "unreviewed", "publishableCanonical": false, "generatedAt": "2026-09-07T15:09:31Z", "providers": [ "Codex" ], "breadth": "recalled by Codex without web access - no source was read", "missingProviders": [], "pass": 2, "cost": { "grok": { "seconds": 24.8, "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: 01a07c69-9abd-77f1-84be-46764b1e55e6\n--------\nuser\nDescribe what is already known about one registered thing. Answer as JSON only, no prose around it.\n\nThing: touchscreen\nSense to describe: (none recorded)\nDomain code: PHY.OBJ\nAlso known as: (none)\n\n\nContext for this batch of 801 things:\n# Batch 004: 1001 regi", "usd": 0, "recall": true }, "codex": { "seconds": 81.2, "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: 01a07c69-9ac2-78a1-9518-0571eb4afaba\n--------\nuser\nYou are drafting a Vercy meta-model for one registered thing. Answer as JSON only, no prose around it.\n\nThing: touchscreen\nRegistry id: vr.tr.touchscreen\nPlane / domain: PHY / PHY.OBJ\nRegistry definition: (none recorded)\nNames folded into this entry: (none)\n\n\n" } } }, "metaModel": { "id": "THING-Q165970", "registryId": "vr.tr.touchscreen", "name": "touchscreen", "version": "0.1.0-research.1", "entryKind": "thing", "family": "Thing Registry", "domain": [ "PHY.OBJ" ], "status": "research-draft" }, "canonicalUrl": "https://ver.cy/models/thing/q165970/", "model": { "registry_id": "vr.tr.touchscreen", "name": "touchscreen", "purpose": "Enable an agent to recognise a touchscreen, assess its display and touch-input condition, and determine which interactions, adjustments and maintenance actions are appropriate.", "definition": "A touchscreen is an electronic display assembly with a touch-sensitive surface that detects contact positions, allowing a user to provide input directly at locations on the displayed interface.", "scope_statement": "This model owns touchscreen as a physical device kind combining a visual display with spatially registered touch sensing at its viewing surface, including integrated assemblies and display-mounted touch overlays, while separating kind-level properties from product specifications and individual-unit observations.", "in_scope": [ "The relationship between the visible display area and the touch-sensitive area", "Touch-sensing principles, controller behaviour and supported contact types", "Optical, dimensional and touch-input performance characteristics", "Power, host connections, coordinate mapping and operating states", "Surface condition, environmental compatibility, maintenance and interaction hazards" ], "out_of_scope": [ "The complete phone, tablet, kiosk or machine containing the touchscreen", "Application workflows, interface content and gesture meanings assigned by software", "Touchpads and other touch-input surfaces without a spatially corresponding display", "Displays without touch sensing", "Styluses, gloves and cleaning products as independently modelled things", "Product-line identity and individual-unit histories except as linked specifications and observations" ], "distinguishing_features": [ "A visible display and a touch-sensing region correspond spatially, allowing input at the location of displayed content.", "Contact at the viewing surface produces position-related input, distinguishing a touchscreen from a display controlled solely by separate buttons or a pointer.", "Its sensing region supports positional interaction across an area rather than only fixed touch-sensitive switches.", "The assembly remains a touchscreen when installed inside a larger device; the enclosing device and its application are separate modelling subjects.", "A touch overlay qualifies within this scope when associated with the display it serves; an unattached sensor panel alone is a component." ], "characteristics": [ { "name": "Touch-sensing principle", "kind": "category", "unit_or_values": "resistive; surface capacitive; projected capacitive; infrared; surface acoustic wave; other; unknown", "why_it_matters": "Helps establish compatible contacts, environmental sensitivities and diagnostic methods." }, { "name": "Assembly relationship", "kind": "relation", "unit_or_values": "touch sensor, display, cover surface, controller and host component links", "why_it_matters": "Locates responsibility for faults and establishes which parts can be serviced separately." }, { "name": "Display and touch-active dimensions", "kind": "measurement", "unit_or_values": "width and height in mm for each area; display diagonal in inches where specified", "why_it_matters": "Reveals inactive margins and supports installation and coordinate-registration checks." }, { "name": "Display resolution and touch reporting resolution", "kind": "measurement", "unit_or_values": "display width × height in pixels; reported touch-coordinate ranges in controller units", "why_it_matters": "Separates image detail from input-coordinate granularity; neither alone establishes touch accuracy." }, { "name": "Touch position error", "kind": "measurement", "unit_or_values": "mm, with test locations, contact tool, calibration and operating conditions", "why_it_matters": "Determines whether reported contacts reliably correspond to intended targets." }, { "name": "Concurrent contact capacity", "kind": "measurement", "unit_or_values": "number of independently reported contacts under a stated configuration", "why_it_matters": "Constrains simultaneous interactions and helps distinguish hardware capability from host restrictions." }, { "name": "Contact compatibility", "kind": "category", "unit_or_values": "bare finger; specified gloves; passive stylus; specified active stylus; unsupported; unverified", "why_it_matters": "Prevents assuming that every touchscreen accepts the same input tools." }, { "name": "Touch reporting latency", "kind": "measurement", "unit_or_values": "ms from defined physical contact onset to a defined controller or host event", "why_it_matters": "Supports responsiveness assessment without conflating sensing delay with application rendering delay." }, { "name": "Display visibility", "kind": "measurement", "unit_or_values": "luminance in cd/m² and contrast under specified ambient illumination and viewing angle", "why_it_matters": "Determines whether users can see the targets they are expected to touch." }, { "name": "Input and display operating state", "kind": "state", "unit_or_values": "display active, dimmed or off; touch enabled, disabled, waking or faulted; host connected or disconnected", "why_it_matters": "An apparently dark or frozen screen may still accept touch input." }, { "name": "Host and power connections", "kind": "relation", "unit_or_values": "video interface, touch-data interface and power-supply links with specified electrical requirements", "why_it_matters": "Display, touch and power faults can originate in different connections." }, { "name": "Surface and assembly condition", "kind": "state", "unit_or_values": "intact; contaminated; scratched; cracked; delaminating; intermittently responsive; unassessed", "why_it_matters": "Relates visible damage and contamination to usability, maintenance and safe handling." } ], "affordances": [ "Inspect the viewing surface and compare touch-active coverage with displayed content.", "Test contact detection, positional registration, edge response and simultaneous contacts.", "Check supported fingers, gloves and styluses against documented compatibility.", "Adjust supported calibration, orientation, sensitivity or input-enable settings through authorised controls.", "Isolate display, sensing, controller and host-connection faults using supported diagnostics.", "Disable input for approved cleaning or arrange repair when surface damage or unreliable sensing warrants it." ] }, "sources": [], "structure": { "bundles": [ { "id": "display-touch-identity", "name": "Display and touch identity", "description": "Establishes the combined display-and-input function and the physical assembly to which observations apply.", "rationale": "Touchscreens are easily confused with their host devices, standalone displays and touch-sensor components.", "layers": [ { "id": "functional-boundary", "name": "Functional boundary", "description": "Identifies the defining relationship between displayed content and sensed contact.", "findings": [ { "id": "spatially-corresponding-input", "name": "Spatially corresponding input", "description": "Record whether contact positions on the viewing surface map to locations in the associated display.", "questions": [ { "text": "Which visible display region corresponds to the touch-sensing region?", "kind": "definition", "id": "spatially-corresponding-input-q01" }, { "text": "Is the subject a complete touchscreen assembly, an installed overlay or a standalone component requiring a linked display?", "kind": "boundary", "id": "spatially-corresponding-input-q02" } ] } ] }, { "id": "assembly-composition", "name": "Assembly composition", "description": "Separates the sensor, display, cover surface and controller within the host installation.", "findings": [ { "id": "component-and-host-links", "name": "Component and host links", "description": "Record component relationships and distinguish documented product construction from observations of a particular installation.", "questions": [ { "text": "Which documentation identifies the sensor, display, controller and cover construction?", "kind": "provenance", "id": "component-and-host-links-q01" }, { "text": "Which components belong to the touchscreen assembly, and which belong to its host device?", "kind": "boundary", "id": "component-and-host-links-q02" } ] } ] } ] }, { "id": "contact-sensing", "name": "Contact sensing", "description": "Describes how the surface detects contacts and which input tools and contact patterns it supports.", "rationale": "Sensing technology and controller configuration determine whether an intended touch can be recognised.", "layers": [ { "id": "sensing-and-contact-tools", "name": "Sensing and contact tools", "description": "Connects the sensing mechanism to documented finger, glove and stylus compatibility.", "findings": [ { "id": "supported-contact-conditions", "name": "Supported contact conditions", "description": "Record the sensing principle and verified contact-tool combinations without generalising compatibility across technologies.", "questions": [ { "text": "What sensing principle is documented for this touchscreen?", "kind": "definition", "id": "supported-contact-conditions-q01" }, { "text": "Which fingers, glove types and stylus models have documented or tested support, and under what conditions?", "kind": "provenance", "id": "supported-contact-conditions-q02" } ] } ] }, { "id": "contact-discrimination", "name": "Contact discrimination", "description": "Addresses simultaneous contacts, tracking continuity and rejection of unintended contacts.", "findings": [ { "id": "contact-tracking-and-rejection", "name": "Contact tracking and rejection", "description": "Record concurrent-contact capability and any verified handling of palms, nearby contacts or surface moisture.", "questions": [ { "text": "How many contacts remain independently tracked during the specified test, including near edges and near each other?", "kind": "measurement", "id": "contact-tracking-and-rejection-q01" }, { "text": "Which supported settings affect palm or unintended-contact rejection, and when may they be changed?", "kind": "action", "id": "contact-tracking-and-rejection-q02" } ] } ] } ] }, { "id": "visual-touch-registration", "name": "Visual and touch registration", "description": "Covers target visibility, coordinate alignment and the performance of contact reporting.", "rationale": "Successful touchscreen interaction requires both a readable target and a sufficiently accurate, timely input location.", "layers": [ { "id": "viewing-conditions", "name": "Viewing conditions", "description": "Records how the display, cover surface and ambient conditions affect visible touch targets.", "findings": [ { "id": "target-visibility", "name": "Target visibility", "description": "Record display geometry and visibility under stated lighting and viewing conditions, including reflections or apparent displacement through the cover.", "questions": [ { "text": "What are the display dimensions, pixel resolution and touch-active dimensions?", "kind": "measurement", "id": "target-visibility-q01" }, { "text": "Under the intended illumination and viewing angles, how readable are targets and how apparent is any separation between the contact surface and image?", "kind": "measurement", "id": "target-visibility-q02" } ] } ] }, { "id": "coordinate-and-time-performance", "name": "Coordinate and time performance", "description": "Separates coordinate range, positional error, repeatability and reporting delay.", "findings": [ { "id": "registered-contact-performance", "name": "Registered contact performance", "description": "Record measured input performance with explicit endpoints and conditions, including orientation and calibration state.", "questions": [ { "text": "What positional error and repeatability are measured at the centre, edges and corners after the supported mapping procedure?", "kind": "measurement", "id": "registered-contact-performance-q01" }, { "text": "What touch-reporting latency is measured, and where do its timing boundaries begin and end?", "kind": "measurement", "id": "registered-contact-performance-q02" }, { "text": "Which calibration or coordinate-mapping procedure is supported after rotation, replacement or host reconfiguration?", "kind": "action", "id": "registered-contact-performance-q03" } ] } ] } ] }, { "id": "host-integration-and-states", "name": "Host integration and states", "description": "Records the connections and operating states that make displayed output and touch input available.", "rationale": "A working image does not establish working touch input, and an inactive image does not establish disabled input.", "layers": [ { "id": "connection-paths", "name": "Connection paths", "description": "Identifies video, touch-data and power paths and their host dependencies.", "findings": [ { "id": "interface-dependencies", "name": "Interface dependencies", "description": "Record connection requirements and the controller, firmware or driver dependencies needed for supported operation.", "questions": [ { "text": "Which interfaces carry video, touch reports and power, and what electrical requirements are documented?", "kind": "provenance", "id": "interface-dependencies-q01" }, { "text": "Which touch capabilities are supplied by the assembly, and which depend on host drivers or application interpretation?", "kind": "boundary", "id": "interface-dependencies-q02" } ] } ] }, { "id": "input-state-control", "name": "Input state control", "description": "Distinguishes display activity, touch availability, wake behaviour and loss of communication.", "findings": [ { "id": "observable-and-commanded-states", "name": "Observable and commanded states", "description": "Record independently observable display and input states and supported transitions between them.", "questions": [ { "text": "Does touch remain active or trigger wake-up while the display is dimmed, blank or asleep?", "kind": "measurement", "id": "observable-and-commanded-states-q01" }, { "text": "How can an agent disable touch input and verify that contacts no longer generate host actions?", "kind": "action", "id": "observable-and-commanded-states-q02" } ] } ] } ] }, { "id": "surface-environment-and-service", "name": "Surface, environment and service", "description": "Connects physical condition and exposure to reliable interaction, cleaning and repair decisions.", "rationale": "The same surface must remain viewable, touch-responsive and safe to contact throughout use and maintenance.", "layers": [ { "id": "exposure-and-protection", "name": "Exposure and protection", "description": "Records the tested operating environment and the exact assembly boundary covered by protection claims.", "findings": [ { "id": "environmental-operating-envelope", "name": "Environmental operating envelope", "description": "Record documented temperature, moisture and interference limits, and attach standards or certification evidence only to the configuration it covers.", "questions": [ { "text": "What operating limits and touch-performance conditions are documented for temperature, humidity, water on the surface and electromagnetic interference?", "kind": "provenance", "id": "environmental-operating-envelope-q01" }, { "text": "Which standards, issuing bodies, editions and test records support protection claims, and do those claims cover the front surface, complete module or installed host?", "kind": "boundary", "id": "environmental-operating-envelope-q02" } ] } ] }, { "id": "condition-and-maintenance", "name": "Condition and maintenance", "description": "Relates physical damage and input symptoms to supported cleaning, diagnosis and service actions.", "findings": [ { "id": "surface-fault-response", "name": "Surface fault response", "description": "Record contamination, cracks, delamination, dead regions and unintended input, together with evidence supporting the next action.", "questions": [ { "text": "Which cleaning materials, methods and surface protectors are approved for the cover and its coatings?", "kind": "action", "id": "surface-fault-response-q01" }, { "text": "Which observations require input isolation, withdrawal from use or replacement, and what supported checks distinguish surface faults from controller or host faults?", "kind": "action", "id": "surface-fault-response-q02" } ] } ] } ] }, { "id": "evidence-and-external-alignment", "name": "Evidence and external alignment", "description": "What the world already says about this thing, gathered so the model can be checked against it.", "rationale": "A model that cannot be lined up against existing standards, identifiers and practice cannot be adopted by anyone who already uses them.", "layers": [ { "id": "reported-evidence", "name": "Reported evidence", "description": "Findings from the breadth pass, kept separate from the structural claims.", "findings": [ { "id": "evidence-confidence-notes", "name": "Check these first", "description": "Recalled without web access and unsourced; every item is a lead to verify.", "evidence": [ "This describes the hardware class, not a particular product or individual unit; the statements are recalled knowledge rather than researched findings.", "Size and contact-count ranges are illustrative application ranges, not defining limits or verified market statistics.", "Researchers should verify applicable editions and product-specific requirements; power supply, environmental protection, glove support and safety provisions depend on the complete device and its intended use." ], "questions": [ { "id": "evidence-confidence-notes-q01", "text": "Which of these check these first hold for the sense of touchscreen 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": [ "Resistive touchscreen", "Surface-capacitive touchscreen", "Projected-capacitive touchscreen", "Infrared touchscreen", "Surface-acoustic-wave touchscreen", "Optical-imaging touchscreen" ], "questions": [ { "id": "evidence-kinds-q01", "text": "Which of these kinds and varieties hold for the sense of touchscreen 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": [ "ISO 9241-410, issued by ISO, specifies design criteria for physical input devices and is relevant to touchscreen input ergonomics." ], "questions": [ { "id": "evidence-standards-and-regulation-q01", "text": "Which of these standards and regulation hold for the sense of touchscreen 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": [ "Smartphones and tablets", "Self-service kiosks and ticket machines", "Industrial machine control panels", "Vehicle infotainment and control interfaces", "Interactive public displays and classroom boards" ], "questions": [ { "id": "evidence-real-world-use-q01", "text": "Which of these real-world use hold for the sense of touchscreen 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": "Display diagonal in handheld applications", "typical_range": "Approximately 3-15", "unit": "inch" }, { "quantity": "Display diagonal in kiosks and interactive boards", "typical_range": "Approximately 10-86", "unit": "inch" }, { "quantity": "Simultaneously reported touch contacts", "typical_range": "Common implementations support 1-10; some large systems support more", "unit": "contacts" } ], "questions": [ { "id": "evidence-measurements-q01", "text": "Which of these typical measurements hold for the sense of touchscreen 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": [ "Cracking, delamination or damaged sensor conductors can produce dead areas or complete loss of touch input; broken cover glass can cause cuts.", "Water, contamination or electrical interference can cause missed touches or unintended inputs, depending on sensing technology.", "Calibration errors or incorrect coordinate mapping can make a touch activate a different displayed control.", "Gloves and incompatible styluses may prevent reliable operation, particularly on capacitive systems without suitable support.", "Accidental activation and limited tactile feedback can create operating hazards when important controls require visual attention." ], "questions": [ { "id": "evidence-failure-modes-and-hazards-q01", "text": "Which of these failure modes and hazards hold for the sense of touchscreen 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": "Touchpad", "difference": "A touchpad normally controls a pointer or interface on a separate display; a touchscreen senses input at the display surface." }, { "name": "Electronic display", "difference": "A display provides visual output; it becomes a touchscreen assembly only when touch sensing is integrated with or positioned over it." }, { "name": "Touch sensor", "difference": "A touch sensor is a sensing component that need not include a display; a touchscreen combines spatial touch sensing with a display." }, { "name": "Graphical user interface", "difference": "A graphical user interface is the software interaction layer; a touchscreen is hardware through which that interface may be operated." }, { "name": "Pen digitizer", "difference": "A pen digitizer senses a compatible pen and may support hover or pressure; touchscreen capability alone does not imply those functions." } ], "questions": [ { "id": "evidence-neighbours-q01", "text": "Which of these neighbouring kinds and how to tell them apart hold for the sense of touchscreen this model covers, and on what evidence?", "kind": "provenance" } ] } ] } ] } ] }, "openQuestions": [ "Does an existing world model already cover touchscreen, requiring this registry entry to link to that publication instead of creating another?", "Which primary technical sources should establish the sensing-technology categories and their contact-compatibility limits?", "Which measurement methods provide comparable positional accuracy, repeatability and latency results across touchscreen technologies?", "Which standards apply to touchscreen modules themselves, and which apply only to particular hosts, installations or intended uses?", "How should the model represent proximity sensing, hover and active-stylus digitisation when they share the display surface but use capabilities distinct from touch detection?" ], "statistics": { "bundles": 6, "layers": 11, "findings": 17, "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 touchscreen, record what state it is in, and decide what may be done with it.", "whatItIs": "Enable an agent to recognise a touchscreen, assess its display and touch-input condition, and determine which interactions, adjustments and maintenance actions are appropriate.", "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: Force Touch, resistive touchscreen.", "2 finer distinctions are held as aliases rather than separate entries, because telling them apart needs a task that asks for it.", "Described in 82 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 touchscreen, 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": [ "Force Touch", "resistive touchscreen" ] } ], "standing": "Described in 82 Wikipedia languages, which measures how widely it is written about rather than how important or how common it is. 2 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 touchscreen from another, and a touchscreen 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 touchscreen, 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 touchscreen, 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 touchscreen 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 touchscreen, 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 touchscreen, 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 touchscreen 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 touchscreen 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 touchscreen, 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 touchscreen, 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 touchscreen 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 touchscreen from the things most often confused with it.", "questions": [ { "id": "distinguishing-features-q01", "text": "What identifies and describes what distinguishes a touchscreen, 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 touchscreen, 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 touchscreen 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 touchscreen 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 touchscreen, 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 touchscreen, 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 touchscreen 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 touchscreen is built from and which parts are replaceable.", "questions": [ { "id": "parts-and-materials-q01", "text": "What identifies and describes the composition of a touchscreen, 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 touchscreen, 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 touchscreen 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 touchscreen is judged and by whom.", "questions": [ { "id": "condition-assessment-q01", "text": "What identifies and describes the condition of a touchscreen, 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 touchscreen, 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 touchscreen 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 touchscreen 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 touchscreen is, and what that position is measured against.", "questions": [ { "id": "position-and-frame-q01", "text": "What identifies and describes the location of a touchscreen, 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 touchscreen, 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 touchscreen 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 touchscreen 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 touchscreen, 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 touchscreen, 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 touchscreen 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 touchscreen 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 touchscreen between them.", "questions": [ { "id": "stages-and-transitions-q01", "text": "What identifies and describes the lifecycle of a touchscreen, 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 touchscreen, 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 touchscreen 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 touchscreen, how often and by whom.", "findings": [ { "id": "observation-record", "name": "Observation record", "description": "How an observation of a touchscreen 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 touchscreen, 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 touchscreen, 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 touchscreen 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 touchscreen 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 touchscreen 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 touchscreen, 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 touchscreen 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 touchscreen 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 touchscreen 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 touchscreen 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 touchscreen 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 touchscreen, 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 touchscreen 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 touchscreen and how confident it is.", "questions": [ { "id": "claim-provenance-q01", "text": "What identifies and describes a claim about a touchscreen, 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 touchscreen, 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 touchscreen 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 touchscreen is retired without being erased.", "questions": [ { "id": "validity-and-supersession-q01", "text": "What identifies and describes the validity of a claim about a touchscreen, 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 touchscreen, 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 touchscreen 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 } } } }