{ "model": { "rank": 1670, "code": "thing-q22645", "model_id": "vr.tr.smartphone", "name": "smartphone", "purpose": "Let an agent recognise a smartphone, know whose it is and what it can currently do, and decide what may be asked of it - including what must not be, because it is the most personal object most people own.", "family": "Thing Registry", "category": "Physical world and living systems", "status": "research-draft", "kind": "thing", "plane": "PHY", "domain": "PHY.OBJ", "industry": "", "version": "", "url": "/models/thing/q22645/", "tier": 2, "score": 133, "payload": { "layer": "wikidata", "aliases": [ "slate smartphone", "LG Optimus", "phablet", "Honor X series", "foldable smartphone", "Huawei Y9a", "Sony Xperia 5 II", "OnePlus 8T", "realme 7 Pro", "Huawei P40", "Huawei Mate 40 Pro+", "Honor 6C", "Huawei P Smart 2020", "Huawei Mate Xs", "Samsung Galaxy A42 5G", "Realme 7", "Realme 6i", "Wiko Lenny 4", "HTC First", "Samsung GT-i6220", "Realme C12", "Oppo F17 Pro", "Xiaomi Mi 11", "Samsung Galaxy S21 series", "Moto G9", "Samsung Galaxy A12", "Huawei Y360", "Huawei Y3 2018", "Meizu PRO 7", "Moto E7", "Nokia 2.4", "Nokia 3.4", "Moto E", "Samsung Galaxy F41", "Samsung Wave 525", "OnePlus Nord N100", "Redmi 8A", "Huawei Y5p", "Huawei Y5 2019", "Honor 9A" ], "aliasCount": 1827, "merged": 1837, "knownIn": 133, "facets": null, "markers": [], "lexicalClass": "", "senseRank": null, "alsoRegisteredAs": null, "source": { "dataset": "wikidata", "item": "Q22645", "url": "https://www.wikidata.org/wiki/Q22645", "license": "CC0 1.0" } }, "research": { "vercy": "1.0-draft", "publication": { "status": "research-draft", "adjudicationStatus": "unreviewed", "publishableCanonical": false, "generatedAt": "2026-09-10T20:10:00Z", "providers": [ "Claude" ], "breadth": "written by Claude from model knowledge without web access - no source was read, every claim is a lead to verify", "pass": 2, "wave": 1, "engine": "claude" }, "metaModel": { "id": "THING-Q22645", "registryId": "vr.tr.smartphone", "name": "smartphone", "version": "0.2.0-wave.1", "entryKind": "thing", "family": "Thing Registry", "domain": [ "PHY.OBJ" ], "status": "research-draft" }, "canonicalUrl": "https://ver.cy/models/thing/q22645/", "model": { "registry_id": "vr.tr.smartphone", "name": "smartphone", "purpose": "Let an agent recognise a smartphone, know whose it is and what it can currently do, and decide what may be asked of it - including what must not be, because it is the most personal object most people own.", "definition": "A pocket-sized computer with a cellular radio, a touchscreen as its principal interface, and an operating system that runs third-party applications, carried by one person and normally tied to that person's accounts.", "what_it_is_for": "Carrying a person's communications, identity, payments, navigation and sensing in one hand-held device that is with them almost all the time.", "affordances": [ "communicate through it, over cellular and local radios", "run applications that were not written by whoever made it", "sense - camera, microphone, position, motion - which is also what makes it a surveillance risk", "authenticate its holder to other systems, and so act as a key", "charge it, and lose all of the above when it is flat", "lose it or have it stolen, which is an identity incident rather than a property loss" ], "distinguishing_features": [ "Runs third-party applications on a general-purpose operating system, which separates it from a feature phone that also makes calls", "Carries a cellular radio and a subscriber identity, which separates it from a small tablet or media player with the same shape", "Sized to be carried in one hand and a pocket, which is the working boundary with tablets rather than any technical property", "Bound to accounts and credentials, which is why an identical device with a different owner is a different problem entirely" ], "appearance": "A flat slab, typically 140 to 170 mm tall and 65 to 80 mm wide, under 10 mm thick, almost entirely screen on one face, with one or more camera lenses on the other and a single charging port on an edge.", "visual_identification": [ "Screen occupying nearly the whole front face, which separates it from feature phones and small tablets by proportion rather than by size alone", "Camera array on the back, whose arrangement is the most reliable visual clue to model and generation", "Model and regulatory markings, usually printed under the SIM tray or shown in a settings screen rather than on the case", "IMEI, which identifies the individual device and is the only thing here that is not cosmetic" ], "physical_properties": [ { "quantity": "mass", "typical_range": "150-250", "unit": "g", "note": "" }, { "quantity": "screen diagonal", "typical_range": "5.4-6.9", "unit": "in", "note": "the boundary with tablets is conventional, not technical" }, { "quantity": "battery capacity", "typical_range": "3000-5500", "unit": "mAh", "note": "usable life depends far more on age and workload than on this number" }, { "quantity": "ingress protection", "typical_range": "IP53-IP68", "unit": "IP code", "note": "the rating is tested new; it degrades with every repair and drop" } ], "families_and_kinds": [ "by platform: iOS, Android, and the small remainder of others", "by tier: flagship, mid-range, entry - a market split that maps onto support lifetime more than onto capability", "by intent: consumer, rugged, enterprise-managed, single-purpose kiosk", "by subscriber identity: physical SIM, eSIM, dual-SIM" ], "related_models": [ { "relation": "is a kind of", "target": "mobile computer", "why": "it inherits everything true of portable computers, including update and end-of-life questions" }, { "relation": "is confused with", "target": "tablet", "why": "same platform and often the same software; the difference is carriability and a cellular subscription" }, { "relation": "needs", "target": "battery charger", "why": "the device is inert without it, and charging behaviour is a real constraint on any plan" }, { "relation": "needs", "target": "cellular network", "why": "most of what it does depends on a network it does not control" }, { "relation": "contains", "target": "battery", "why": "the battery ages faster than the device and decides when it is finished" }, { "relation": "is confused with", "target": "the person's accounts", "why": "the device is not the identity it carries, and resetting one does not reset the other" } ], "identifiers": [ { "scheme": "IMEI", "value_or_pattern": "15 digits", "note": "identifies the individual device; a dual-SIM device has two" }, { "scheme": "model number", "value_or_pattern": "vendor-specific", "note": "regional variants of one model differ in radio bands" }, { "scheme": "ICCID / IMSI", "value_or_pattern": "on the SIM", "note": "identifies the subscription, not the device, and moves between devices" } ], "standards_and_regulation": [ "3GPP releases, which define the cellular radio generations a device supports", "Regional radio equipment approvals, which decide whether a given model may lawfully be used in a country", "Common charger requirements in some jurisdictions, which is why the port has converged", "Data protection regimes, which apply to what the device holds rather than to the device" ], "failure_modes_and_hazards": [ "Battery degradation and swelling, which ends the device's usable life and is a fire risk when damaged", "Screen and water damage, the two most common physical failures", "Loss of vendor software support, which makes a working device unsafe to use rather than unusable", "Theft, which is an account compromise before it is a property loss", "Surveillance by whatever runs on it, since the sensors serve any application that is permitted them" ], "in_scope": [], "out_of_scope": [], "characteristics": [] }, "sources": [], "structure": { "bundles": [ { "id": "device-identity-and-holder", "name": "Device identity and holder", "description": "Which device this is, who holds it, and what that entitles them to.", "rationale": "A smartphone is only meaningful in relation to a person and their accounts; the same hardware in different hands is a different thing to reason about.", "layers": [ { "id": "hardware-identity", "name": "Hardware identity", "description": "What names this handset as opposed to another of the same model.", "findings": [ { "id": "identifiers-and-scope", "name": "Identifiers and what each identifies", "description": "IMEI names the device, the SIM names the subscription, the account names the person, and they move independently.", "questions": [ { "text": "What IMEI, model and regional variant does this device carry, and which of those changes when the SIM changes?", "kind": "definition" }, { "text": "What evidence establishes that this device is the one a record refers to?", "kind": "provenance" } ] } ] }, { "id": "holder-and-accounts", "name": "Holder, accounts and enrolment", "description": "Who carries it, whose accounts it is signed into, and who manages it.", "findings": [ { "id": "who-controls-it", "name": "Who controls it, and at which layer", "description": "Possession, account ownership and device management are three different powers over one object.", "questions": [ { "text": "Who holds this device, whose accounts are signed in on it, and who can administer it remotely?", "kind": "definition" }, { "text": "What must an agent refuse to do with a device whose holder is not its account owner?", "kind": "action" } ] } ] } ] }, { "id": "capability-and-state", "name": "Capability and current state", "description": "What this handset can do right now, as opposed to what the model can do.", "rationale": "Charge, storage, connectivity and permissions change hour by hour, and every plan that uses the device depends on them.", "layers": [ { "id": "power-and-endurance", "name": "Power and endurance", "description": "Charge, battery health and what running out means.", "findings": [ { "id": "endurance", "name": "Endurance under a stated workload", "description": "How long it will last doing a particular thing, not in the abstract.", "questions": [ { "text": "What charge and battery health does this device have, and how long does that give it under the intended workload?", "kind": "measurement" }, { "text": "What should an agent do differently when the device may go flat mid-task?", "kind": "action" } ] } ] }, { "id": "connectivity-and-permissions", "name": "Connectivity and permissions", "description": "Which radios are available and what software is allowed to use which sensor.", "findings": [ { "id": "what-is-permitted", "name": "What is permitted, to whom", "description": "Permissions are per-application and revocable, and they bound everything an agent can ask of the device.", "questions": [ { "text": "Which networks is this device attached to, and which sensors and data are permitted to the software that would act?", "kind": "definition" }, { "text": "What must be asked of the holder rather than assumed from a permission already granted?", "kind": "action" } ] } ] } ] }, { "id": "software-and-support", "name": "Software, updates and support life", "description": "What it runs, and how long that stays safe to run.", "rationale": "A smartphone stops being usable long before it stops working, because support ends while the hardware is fine - and that date is a property of the model, not of the handset.", "layers": [ { "id": "platform-state", "name": "Platform and version", "description": "Operating system, version, and the software that is actually installed.", "findings": [ { "id": "version-and-consequence", "name": "Version and what depends on it", "description": "What the current version permits, and what a required update would change.", "questions": [ { "text": "What platform and version is this device on, and what capability does that version gate?", "kind": "definition" }, { "text": "What breaks for the holder if it is updated, and what is at risk if it is not?", "kind": "action" } ] } ] }, { "id": "support-window", "name": "Support window", "description": "How long the vendor will issue security updates, and what follows after.", "findings": [ { "id": "end-of-support", "name": "End of support and its consequence", "description": "The date, its source, and what an agent should stop doing with the device after it.", "questions": [ { "text": "Until when does this model receive security updates, and who states that?", "kind": "provenance" }, { "text": "What may an unsupported device no longer be trusted to do - payments, authentication, sensitive data?", "kind": "boundary" } ] } ] } ] }, { "id": "data-and-exposure", "name": "Data held and exposure", "description": "What is on it, who can reach that, and what a loss means.", "rationale": "The hardware is replaceable and the contents are not; almost every real consequence of a smartphone incident is about the data and the credentials.", "layers": [ { "id": "contents", "name": "Contents and their sensitivity", "description": "Categories of data present and which of them are sensitive by law.", "findings": [ { "id": "what-is-held", "name": "What is held, and under whose control", "description": "Local data, synchronised data, and credentials that unlock other systems.", "questions": [ { "text": "What categories of data does this device hold or unlock, and which are on it rather than merely visible through it?", "kind": "definition" }, { "text": "Whose consent governs each category, and what may an agent not read even with the device in hand?", "kind": "action" } ] } ] }, { "id": "loss-and-compromise", "name": "Loss, theft and compromise", "description": "What happens when it goes, and what the response is.", "findings": [ { "id": "incident-response", "name": "Response to loss or compromise", "description": "The sequence that limits harm, and who is able to perform each step.", "questions": [ { "text": "What happens to the data and the credentials when this device is lost or stolen?", "kind": "boundary" }, { "text": "What must be done first, by whom, and what evidence should be preserved?", "kind": "action" } ] } ] } ] }, { "id": "lifecycle-and-disposal", "name": "Lifecycle, repair and disposal", "description": "How it enters service, what may be repaired, and how it ends.", "rationale": "Repairability and disposal are governed by rules the holder rarely knows, and the battery makes disposal a hazardous-waste question rather than a rubbish one.", "layers": [ { "id": "repair", "name": "Repair and refurbishment", "description": "What can be repaired, by whom, and what a repair does to warranties and ratings.", "findings": [ { "id": "repair-consequences", "name": "Repair and its consequences", "description": "Parts, pairing, and what a repair invalidates.", "questions": [ { "text": "Which components of this device are replaceable, by whom, and what does replacement invalidate?", "kind": "definition" }, { "text": "How should an agent record that a device has been repaired, given that it changes ingress protection and sometimes function?", "kind": "provenance" } ] } ] }, { "id": "disposal", "name": "Erasure and disposal", "description": "Wiping, recycling routes and the battery.", "findings": [ { "id": "end-of-life-handling", "name": "End-of-life handling", "description": "What must be erased, what must be separated, and who must be told.", "questions": [ { "text": "What must be erased or unlinked before this device leaves its holder, and how is that verified?", "kind": "action" }, { "text": "Which disposal routes are lawful for a device with a lithium battery in the relevant jurisdiction?", "kind": "definition" } ] } ] } ] } ] }, "openQuestions": [ "Where should the model draw the line between the device and the person's digital identity, given that most consequences follow the identity rather than the hardware?", "How should support-window facts be attached - to the model, the regional variant, or the individual handset - when vendors state them inconsistently?", "Should an enterprise-managed handset be one thing with a management relation, or a different kind of thing from a personal one?", "What minimum evidence should an agent require before acting on a claim that a device belongs to a particular person?" ], "statistics": { "bundles": 5, "layers": 10, "findings": 10, "questions": 20 } }, "draft": { "generator": "vr.draft.v3", "status": "draft-generated", "researched": false, "archetype": "device, machine or tool", "method": "Written from the archetype playbook - what this kind of thing needs beyond identity and provenance - and from the structure that recurred across 6,333 models already researched by two engines. Applied to this entry by rule. No source was read for this thing and no claim here is researched. This entry carries no facets of its own, so they were inferred from its domain - a guess about a whole domain applied to one thing.", "facetsInferred": true, "nextPass": "A researcher replaces this draft with a sourced specification. Treat every sentence below as a proposal to argue with.", "purpose": "Give an agent a durable, checkable way to recognise a smartphone, record what state it is in, and decide what may be done with it.", "whatItIs": "Let an agent recognise a smartphone, know whose it is and what it can currently do, and decide what may be asked of it - including what must not be, because it is the most personal object most people own.", "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: slate smartphone, LG Optimus, phablet, Honor X series, foldable smartphone, Huawei Y9a, Sony Xperia 5 II, OnePlus 8T, realme 7 Pro, Huawei P40, Huawei Mate 40 Pro+, Honor 6C.", "1837 finer distinctions are held as aliases rather than separate entries, because telling them apart needs a task that asks for it.", "Described in 133 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 smartphone, 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": [ "slate smartphone", "LG Optimus", "phablet", "Honor X series", "foldable smartphone", "Huawei Y9a", "Sony Xperia 5 II", "OnePlus 8T", "realme 7 Pro", "Huawei P40", "Huawei Mate 40 Pro+", "Honor 6C" ] } ], "standing": "Described in 133 Wikipedia languages, which measures how widely it is written about rather than how important or how common it is. 1837 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 smartphone from another, and a smartphone 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 smartphone, 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 smartphone, 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 smartphone 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 smartphone, 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 smartphone, 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 smartphone 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 smartphone 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 smartphone, 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 smartphone, 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 smartphone 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 smartphone from the things most often confused with it.", "questions": [ { "id": "distinguishing-features-q01", "text": "What identifies and describes what distinguishes a smartphone, 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 smartphone, 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 smartphone 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 smartphone 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 smartphone, 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 smartphone, 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 smartphone 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 smartphone is built from and which parts are replaceable.", "questions": [ { "id": "parts-and-materials-q01", "text": "What identifies and describes the composition of a smartphone, 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 smartphone, 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 smartphone 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 smartphone is judged and by whom.", "questions": [ { "id": "condition-assessment-q01", "text": "What identifies and describes the condition of a smartphone, 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 smartphone, 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 smartphone 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 smartphone 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 smartphone is, and what that position is measured against.", "questions": [ { "id": "position-and-frame-q01", "text": "What identifies and describes the location of a smartphone, 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 smartphone, 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 smartphone 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 smartphone 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 smartphone, 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 smartphone, 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 smartphone 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 smartphone 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 smartphone between them.", "questions": [ { "id": "stages-and-transitions-q01", "text": "What identifies and describes the lifecycle of a smartphone, 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 smartphone, 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 smartphone 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 smartphone, how often and by whom.", "findings": [ { "id": "observation-record", "name": "Observation record", "description": "How an observation of a smartphone 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 smartphone, 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 smartphone, 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 smartphone 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 smartphone 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 smartphone 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 smartphone, 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 smartphone 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 smartphone 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 smartphone 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 smartphone 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 smartphone 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 smartphone, 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 smartphone 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 smartphone and how confident it is.", "questions": [ { "id": "claim-provenance-q01", "text": "What identifies and describes a claim about a smartphone, 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 smartphone, 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 smartphone 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 smartphone is retired without being erased.", "questions": [ { "id": "validity-and-supersession-q01", "text": "What identifies and describes the validity of a claim about a smartphone, 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 smartphone, 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 smartphone 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 } } } }