{ "model": { "rank": 6081, "code": "thing-q181787", "model_id": "vr.tr.android", "name": "android", "purpose": "Enable an AI agent to recognise a humanlike physical robot as an android, assess its embodied and interactive state, and determine which uses or interventions are supported and permitted.", "family": "Thing Registry", "category": "Physical world and living systems", "status": "research-draft", "kind": "thing", "plane": "PHY", "domain": "PHY.OBJ", "industry": "", "version": "", "url": "/models/thing/q181787/", "tier": 2, "score": 62, "payload": { "layer": "wikidata", "aliases": [ "sex robot", "Geminoid", "robotic android" ], "aliasCount": 3, "merged": 3, "knownIn": 62, "facets": null, "markers": [], "lexicalClass": "", "senseRank": null, "alsoRegisteredAs": "vr.tr.android", "source": { "dataset": "wikidata", "item": "Q181787", "url": "https://www.wikidata.org/wiki/Q181787", "license": "CC0 1.0" } }, "research": { "vercy": "1.0-draft", "publication": { "status": "research-draft", "adjudicationStatus": "unreviewed", "publishableCanonical": false, "generatedAt": "2026-09-07T11:25:23Z", "providers": [ "Codex", "Grok" ], "missingProviders": [], "pass": 2, "cost": { "grok": { "usd": 0.00526218, "turns": 1, "seconds": 17.9, "error": null }, "codex": { "seconds": 74.9, "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: 01a07b9c-80ea-74d3-9ef3-e340700daab0\n--------\nuser\nYou are drafting a Vercy meta-model for one registered thing. Answer as JSON only, no prose around it.\n\nThing: android\nRegistry id: vr.tr.android\nPlane / domain: PHY / PHY.OBJ\nRegistry definition: (none recorded)\nNames folded into this entry: (none)\n\nA Vercy m" } } }, "metaModel": { "id": "THING-Q181787", "registryId": "vr.tr.android", "name": "android", "version": "0.1.0-research.1", "entryKind": "thing", "family": "Thing Registry", "domain": [ "PHY.OBJ" ], "status": "research-draft" }, "canonicalUrl": "https://ver.cy/models/thing/q181787/", "model": { "registry_id": "vr.tr.android", "name": "android", "purpose": "Enable an AI agent to recognise a humanlike physical robot as an android, assess its embodied and interactive state, and determine which uses or interventions are supported and permitted.", "definition": "A humanoid automaton designed to resemble a human in form and, often, in social behaviour, typically distinguished from other robots by anthropomorphic appearance rather than by a specific control architecture.", "scope_statement": "This draft interprets android in PHY / PHY.OBJ as a physical robot designed to resemble a human; it owns the evidence for that classification, the correspondence between humanlike presentation and actual capability, and the conditions governing its operation and intervention.", "in_scope": [ "Human resemblance in body form, surface appearance, movement and expressive behaviour", "Physical embodiment, actuation and sensing relevant to humanlike activity", "The relationship between apparent agency and actual autonomous, scripted or remotely controlled behaviour", "Human interaction, physical contact and disclosure of robotic identity", "Embodiment integrity, maintenance and conditions for returning to interaction" ], "out_of_scope": [ "Android operating-system platforms and software ecosystems", "Purely virtual human characters and conversational personas", "Biological humans and the classification of people with prostheses or implants", "General robot taxonomies beyond the boundary needed to identify an android", "Complete specifications of installed AI models, batteries, sensors or actuators", "Facility-wide operating rules and organisational workforce governance" ], "distinguishing_features": [ "Verify that the referent is a physically embodied robot, rather than software named Android or a virtual human.", "Look for documented or observable intent to resemble a human; a vaguely human-shaped arrangement alone leaves the boundary with a generic humanoid robot unresolved.", "Separate robotic embodiment from a human wearing a costume, operating a prosthesis or carrying assistive equipment.", "Establish whether apparent human behaviour comes from actuated robotic mechanisms, rather than a static mannequin; the boundary with animated display figures requires an explicit classification rule.", "Record appearance and control mode separately: a humanlike exterior does not demonstrate autonomous behaviour." ], "characteristics": [ { "name": "Evidence of intended human resemblance", "kind": "category", "unit_or_values": "Documented design intent; observed resemblance only; conflicting evidence; unknown", "why_it_matters": "Supports classification without treating every humanoid mechanism as an android." }, { "name": "Humanlike presentation by body region", "kind": "category", "unit_or_values": "For face, head, torso and limbs: lifelike; stylised; visibly mechanical; absent; unassessed", "why_it_matters": "Distinguishes the actual embodiment from an assumption that an android must have a complete lifelike body." }, { "name": "Supported embodiment configuration", "kind": "category", "unit_or_values": "Fixed installation; supported torso; wheeled body; legged body; other documented configuration", "why_it_matters": "Prevents human appearance from being mistaken for walking, balancing or whole-body capability." }, { "name": "Humanlike joint motion envelope", "kind": "measurement", "unit_or_values": "Verified angular range in degrees and speed in degrees per second for each relevant actuated joint", "why_it_matters": "Identifies reachable poses and motion limits that may differ substantially from human anatomy." }, { "name": "Task-specific control authority", "kind": "state", "unit_or_values": "Autonomous; shared control; teleoperated; scripted; inactive; unknown, recorded per task", "why_it_matters": "Determines whether a request can be delegated to the android and who can interrupt its execution." }, { "name": "Operator and controller assignment", "kind": "relation", "unit_or_values": "Links to responsible operator, remote controller and authorised supervisor where applicable", "why_it_matters": "Makes responsibility and remote participation explicit when the humanlike presentation conceals them." }, { "name": "Expressive channel availability", "kind": "state", "unit_or_values": "For gaze, facial expression, gesture and speech: available; degraded; disabled; absent; unverified", "why_it_matters": "Shows which social signals the android can produce and where users might misread its responses." }, { "name": "Physical-contact operating envelope", "kind": "category", "unit_or_values": "Documented permitted contact types, body regions, task conditions and exclusions; otherwise unverified", "why_it_matters": "Humanlike hands or skin do not establish that touch, handshakes or close assistance are supported." }, { "name": "Humanlike covering integrity", "kind": "state", "unit_or_values": "Intact; torn; detached; contaminated; obstructing motion or sensing; absent; unassessed", "why_it_matters": "A damaged covering can change both mechanical operation and how people perceive the android." }, { "name": "Robotic-identity disclosure", "kind": "state", "unit_or_values": "Explicit and accessible; present but ambiguous; absent; unassessed", "why_it_matters": "Determines whether people can distinguish the android's humanlike presentation from a human participant." } ], "affordances": [ "Classify the embodiment provisionally from evidence of robotic construction and intended human resemblance.", "Select supported speech, gaze, expression or gesture channels for an interaction.", "Assign a verified physical task under the recorded control mode and supervision conditions.", "Permit, constrain or decline a proposed contact interaction using the documented operating envelope.", "Pause human-facing activity when expressive behaviour, motion or covering integrity becomes unreliable.", "Inspect and service humanlike coverings and mechanisms, then verify the affected capabilities before reuse." ] }, "sources": [], "structure": { "bundles": [ { "id": "android-identity", "name": "Android identity", "description": "Evidence that this embodiment belongs to the intended android category and the limits of that classification.", "rationale": "The registry has no definition, so an agent must distinguish a working interpretation from a settled category boundary.", "layers": [ { "id": "classification-evidence", "name": "Classification evidence", "description": "Robotic embodiment and intended human resemblance.", "findings": [ { "id": "human-resemblance-intent", "name": "Human resemblance intent", "description": "Record the evidence that the robot was designed to resemble a human and distinguish this from resemblance inferred by an observer.", "questions": [ { "text": "Which documented design intentions or observed features support calling this embodiment an android?", "kind": "definition", "id": "human-resemblance-intent-q01" }, { "text": "Where did that classification originate, and does its source describe this particular embodiment?", "kind": "provenance", "id": "human-resemblance-intent-q02" } ] } ] }, { "id": "neighbouring-category-boundaries", "name": "Neighbouring category boundaries", "description": "Unresolved distinctions from humanoid robots, display figures and partial embodiments.", "findings": [ { "id": "classification-boundary", "name": "Classification boundary", "description": "Record which features establish membership and which leave it provisional.", "questions": [ { "text": "What makes this an android rather than a generic humanoid robot, mannequin or animatronic figure under the adopted definition?", "kind": "boundary", "id": "classification-boundary-q01" }, { "text": "Does a head-only or torso-only version still qualify, and what evidence supports that decision?", "kind": "boundary", "id": "classification-boundary-q02" } ] } ] } ] }, { "id": "humanlike-embodiment", "name": "Humanlike embodiment", "description": "The correspondence between human appearance and the body's actual mechanical capabilities.", "rationale": "People and agents may infer human mobility or dexterity from appearance even when the mechanisms cannot provide it.", "layers": [ { "id": "body-form-and-motion", "name": "Body form and motion", "description": "Humanlike body regions, support arrangements and verified motion.", "findings": [ { "id": "apparent-versus-actual-anatomy", "name": "Apparent versus actual anatomy", "description": "Record how visible anatomy corresponds to actuated joints, support structures and usable movement.", "questions": [ { "text": "Which apparently human body parts can actually move, bear loads or manipulate objects?", "kind": "definition", "id": "apparent-versus-actual-anatomy-q01" }, { "text": "What verified joint ranges, reach limits and support requirements constrain humanlike poses or movement?", "kind": "measurement", "id": "apparent-versus-actual-anatomy-q02" } ] } ] }, { "id": "perception-through-the-body", "name": "Perception through the body", "description": "What the android can sense through or around its humanlike exterior.", "findings": [ { "id": "apparent-versus-actual-senses", "name": "Apparent versus actual senses", "description": "Distinguish visible eyes, ears and skin from active sensing coverage.", "questions": [ { "text": "Which visible humanlike sensory features contain working sensors, and where are the actual sensors located?", "kind": "definition", "id": "apparent-versus-actual-senses-q01" }, { "text": "Under the intended interaction conditions, where are the verified blind spots or failures to detect speech, proximity or touch?", "kind": "measurement", "id": "apparent-versus-actual-senses-q02" } ] } ] } ] }, { "id": "agency-and-expression", "name": "Agency and expression", "description": "How behaviour is controlled and what humanlike signals can reliably communicate.", "rationale": "A convincing face, voice or gesture can obscure remote operation, scripted behaviour or limited task competence.", "layers": [ { "id": "behavioural-control", "name": "Behavioural control", "description": "The source and limits of control for each human-facing activity.", "findings": [ { "id": "task-control-and-intervention", "name": "Task control and intervention", "description": "Record who or what generates behaviour and how authority can be transferred or interrupted.", "questions": [ { "text": "For conversation, facial movement, manipulation and locomotion, which behaviours are autonomous, scripted or remotely controlled?", "kind": "definition", "id": "task-control-and-intervention-q01" }, { "text": "Who may interrupt or take over each behaviour, and what does the body do if the controlling connection fails?", "kind": "action", "id": "task-control-and-intervention-q02" } ] } ] }, { "id": "social-signal-meaning", "name": "Social signal meaning", "description": "The evidential limits of gaze, expression, speech and gesture.", "findings": [ { "id": "expression-state-correspondence", "name": "Expression and state correspondence", "description": "Record whether social signals correspond to sensed events or operational states, without treating simulated expression as evidence of subjective experience.", "questions": [ { "text": "Which expressions or gaze behaviours indicate tracked attention or a recorded system state, and which are decorative or scripted?", "kind": "definition", "id": "expression-state-correspondence-q01" }, { "text": "When speech, gaze and gesture disagree, which signal may an interacting agent rely on before continuing the task?", "kind": "action", "id": "expression-state-correspondence-q02" } ] } ] } ] }, { "id": "human-interaction-conditions", "name": "Human interaction conditions", "description": "Conditions for intelligible, authorised and physically supported interaction with people.", "rationale": "Human resemblance creates specific expectations about identity, responsiveness and acceptable touch that must be checked against actual conditions.", "layers": [ { "id": "identity-and-participation", "name": "Identity and participation", "description": "How robotic identity and any remote participation are made understandable.", "findings": [ { "id": "interaction-disclosure", "name": "Interaction disclosure", "description": "Record how a person can recognise the android as robotic and understand relevant remote control or observation.", "questions": [ { "text": "How is robotic identity communicated when the face, voice or clothing could lead a person to assume a human is present?", "kind": "measurement", "id": "interaction-disclosure-q01" }, { "text": "What disclosure or authorisation is required before enabling remote observation, recording or operator participation in this interaction?", "kind": "action", "id": "interaction-disclosure-q02" } ] } ] }, { "id": "embodied-contact", "name": "Embodied contact", "description": "Supported proximity and contact behaviours for the actual body configuration.", "findings": [ { "id": "contact-permission-and-limits", "name": "Contact permission and limits", "description": "Record task-specific evidence and permission for contact instead of inferring suitability from humanlike surfaces.", "questions": [ { "text": "Which contacts, such as a handshake or assisted handover, have documented operating limits for this configuration?", "kind": "provenance", "id": "contact-permission-and-limits-q01" }, { "text": "What permission, sensing and stop conditions must be satisfied before initiating or continuing each supported contact?", "kind": "action", "id": "contact-permission-and-limits-q02" } ] } ] } ] }, { "id": "embodiment-integrity-and-recovery", "name": "Embodiment integrity and recovery", "description": "Degradation and repair of mechanisms and coverings that support humanlike operation.", "rationale": "Changes to a face, hand or covering can affect sensing, motion and social interpretation together.", "layers": [ { "id": "covering-and-expression-integrity", "name": "Covering and expression integrity", "description": "The condition of humanlike surfaces and their interaction with underlying mechanisms.", "findings": [ { "id": "surface-mechanism-interference", "name": "Surface and mechanism interference", "description": "Record damage or displacement that alters movement, sensor coverage or intended expression.", "questions": [ { "text": "Are coverings, facial elements or artificial fingers damaged, detached or interfering with actuators and sensors?", "kind": "measurement", "id": "surface-mechanism-interference-q01" }, { "text": "Which observed defects require disabling a gesture, contact behaviour or human-facing interaction?", "kind": "action", "id": "surface-mechanism-interference-q02" } ] } ] }, { "id": "post-service-capability", "name": "Post-service capability", "description": "Configuration changes and checks needed to restore affected behaviours.", "findings": [ { "id": "humanlike-behaviour-revalidation", "name": "Humanlike behaviour revalidation", "description": "Record whether maintenance changed the alignment between appearance, sensing, expression and motion.", "questions": [ { "text": "Which replacements or adjustments changed facial calibration, tactile coverage, joint clearance or the visible body configuration?", "kind": "provenance", "id": "humanlike-behaviour-revalidation-q01" }, { "text": "What checks must pass before restoring affected expressions, close interaction or physical-contact tasks?", "kind": "action", "id": "humanlike-behaviour-revalidation-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-kinds", "name": "Kinds and varieties", "description": "Reported by the breadth pass; each item needs checking against its source before it becomes normative.", "evidence": [ "literary and cinematic android", "humanoid social robot", "android replica or doppelgänger", "sex/companion android (fictional and commercial prototypes)", "military or labour android (speculative)" ], "questions": [ { "id": "evidence-kinds-q01", "text": "Which of these kinds and varieties hold for the sense of android this model covers, and on what evidence?", "kind": "provenance" } ] } ] } ] } ] }, "openQuestions": [ "Does the registry intend android to mean any humanlike robot, or require a particular degree of lifelike appearance?", "Does the intended category include partial bodies, teleoperated replicas and animatronic display figures?", "Which existing Vercy world models already own this concept or parts of it, and should this entry link to one rather than become a separate publication?", "Which authoritative sources and embodiment-specific evaluations can establish classification criteria and support motion, contact and maintenance claims?", "Should replicas of identifiable people introduce android-specific requirements, or should likeness authorisation and identity claims be owned entirely by neighbouring models?" ], "statistics": { "bundles": 6, "layers": 11, "findings": 11, "questions": 21 } }, "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 android, record what state it is in, and decide what may be done with it.", "whatItIs": "Enable an AI agent to recognise a humanlike physical robot as an android, assess its embodied and interactive state, and determine which uses or interventions are supported and permitted.", "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: sex robot, Geminoid, robotic android.", "3 finer distinctions are held as aliases rather than separate entries, because telling them apart needs a task that asks for it.", "Described in 62 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 android, 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": [ "sex robot", "Geminoid", "robotic android" ] } ], "standing": "Described in 62 Wikipedia languages, which measures how widely it is written about rather than how important or how common it is. 3 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 android from another, and a android 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 android, 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 android, 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 android 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 android, 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 android, 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 android 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 android 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 android, 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 android, 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 android 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 android from the things most often confused with it.", "questions": [ { "id": "distinguishing-features-q01", "text": "What identifies and describes what distinguishes a android, 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 android, 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 android 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 android 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 android, 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 android, 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 android 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 android is built from and which parts are replaceable.", "questions": [ { "id": "parts-and-materials-q01", "text": "What identifies and describes the composition of a android, 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 android, 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 android 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 android is judged and by whom.", "questions": [ { "id": "condition-assessment-q01", "text": "What identifies and describes the condition of a android, 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 android, 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 android 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 android 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 android is, and what that position is measured against.", "questions": [ { "id": "position-and-frame-q01", "text": "What identifies and describes the location of a android, 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 android, 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 android 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 android 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 android, 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 android, 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 android 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 android 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 android between them.", "questions": [ { "id": "stages-and-transitions-q01", "text": "What identifies and describes the lifecycle of a android, 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 android, 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 android 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 android, how often and by whom.", "findings": [ { "id": "observation-record", "name": "Observation record", "description": "How an observation of a android 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 android, 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 android, 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 android 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 android 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 android 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 android, 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 android 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 android 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 android 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 android 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 android 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 android, 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 android 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 android and how confident it is.", "questions": [ { "id": "claim-provenance-q01", "text": "What identifies and describes a claim about a android, 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 android, 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 android 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 android is retired without being erased.", "questions": [ { "id": "validity-and-supersession-q01", "text": "What identifies and describes the validity of a claim about a android, 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 android, 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 android 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 } } } }