{ "model": { "rank": 6582, "code": "thing-q741490", "model_id": "vr.tr.autonomous-car", "name": "autonomous car", "purpose": "Enable an AI agent to recognise an autonomous car, assess whether its automated driving capability is usable in the current situation, and determine what operation or intervention is 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/q741490/", "tier": 2, "score": 59, "payload": { "layer": "wikidata", "aliases": [ "Hyundai Ioniq 5 Robotaxi", "Self-driving taxis", "Blees BB-1", "Stanley", "H1ghlander", "Sedric", "kar-go", "robotaxi", "Renault EZ-GO", "Renault EZ-Ultimo", "Navya Autonom Cab", "Apolong", "Kat-5", "Yandex self-driving car", "Sandstorm" ], "aliasCount": 15, "merged": 15, "knownIn": 59, "facets": null, "markers": [], "lexicalClass": "", "senseRank": null, "alsoRegisteredAs": null, "source": { "dataset": "wikidata", "item": "Q741490", "url": "https://www.wikidata.org/wiki/Q741490", "license": "CC0 1.0" } }, "research": { "vercy": "1.0-draft", "publication": { "status": "research-draft", "adjudicationStatus": "unreviewed", "publishableCanonical": false, "generatedAt": "2026-09-09T23:04:03Z", "providers": [ "Codex" ], "breadth": "recalled by Codex without web access - no source was read", "missingProviders": [], "pass": 2, "cost": { "grok": { "seconds": 24.7, "error": "Reading additional input from stdin...\nOpenAI Codex v0.153.4\n--------\nworkdir: R:\\02_PROJECTS\\02_Meta_Models_Platforms\\Ver.cy\\current\\thing-registry-backlog\nmodel: gpt-6-astra\nprovider: openai\napproval: never\nsandbox: read-only\nreasoning effort: none\nreasoning summaries: none\nsession id: 01a08869-1d6d-7660-9074-55c567e41193\n--------\nuser\nDescribe what is already known about one registered thing. Answer as JSON only, no prose around it.\n\nThing: autonomous car\nSense to describe: (none recorded)\nDomain code: PHY.OBJ\nAlso known as: (none)\n\n\nContext for this batch of 1001 things:\n# Batch 007: 1001 ", "usd": 0, "recall": true }, "codex": { "seconds": 58.2, "error": "Reading additional input from stdin...\nOpenAI Codex v0.153.4\n--------\nworkdir: R:\\02_PROJECTS\\02_Meta_Models_Platforms\\Ver.cy\\current\\thing-registry-backlog\nmodel: gpt-6-astra\nprovider: openai\napproval: never\nsandbox: read-only\nreasoning effort: none\nreasoning summaries: none\nsession id: 01a08869-1d7d-7440-96f3-f789938624d3\n--------\nuser\nYou are drafting a Vercy meta-model for one registered thing. Answer as JSON only, no prose around it.\n\nThing: autonomous car\nRegistry id: vr.tr.autonomous-car\nPlane / domain: PHY / PHY.OBJ\nRegistry definition: (none recorded)\nNames folded into this entry: (no" } } }, "metaModel": { "id": "THING-Q741490", "registryId": "vr.tr.autonomous-car", "name": "autonomous car", "version": "0.1.0-research.1", "entryKind": "thing", "family": "Thing Registry", "domain": [ "PHY.OBJ" ], "status": "research-draft" }, "canonicalUrl": "https://ver.cy/models/thing/q741490/", "model": { "registry_id": "vr.tr.autonomous-car", "name": "autonomous car", "purpose": "Enable an AI agent to recognise an autonomous car, assess whether its automated driving capability is usable in the current situation, and determine what operation or intervention is permitted.", "definition": "An autonomous car is a passenger road vehicle equipped with an automated driving system capable of performing the entire dynamic driving task within specified operating conditions, with human fallback requirements depending on its automation level.", "scope_statement": "This model owns the autonomous car as a kind of physical road vehicle, concentrating on the capabilities, operating boundaries, driving states and evidence that distinguish it from an ordinary car; product models and individual vehicles supply values for these characteristics.", "in_scope": [ "Automated execution of the driving task and its dependence on human supervision", "Operational design domain and present eligibility for automated driving", "Onboard sensing, localisation, planning and vehicle control", "Failure response, fallback, passenger interaction and remote assistance", "Configuration, maintenance and validation evidence affecting autonomous operation" ], "out_of_scope": [ "General car construction and propulsion except where they constrain automated driving", "Fleet dispatch, pricing and transport service management", "Road infrastructure and traffic regulation as independent systems", "Development of general artificial intelligence or robotics algorithms", "Manufacturer organisations, product catalogues and individual vehicle identity records" ], "distinguishing_features": [ "Determine whether an enabled driving feature performs the complete driving task within stated conditions, rather than only assisting steering or speed control.", "Identify who must monitor the driving environment and respond when the feature cannot continue; automation claims alone do not establish driverless capability.", "Establish whether driving decisions are executed onboard or require continuous control by a remote human driver.", "Verify that the thing is a car intended for road travel, rather than a delivery robot, industrial mobile robot or simulated vehicle.", "Distinguish an installed and operational automated driving capability from hardware marketed as capable of supporting a future capability." ], "characteristics": [ { "name": "Driving automation responsibility", "kind": "category", "unit_or_values": "Per feature: driving-task performer, environment-monitoring responsibility and fallback responsibility", "why_it_matters": "Separates autonomous operation from assistance and identifies required human participation." }, { "name": "Operational design domain", "kind": "category", "unit_or_values": "Permitted road types, geographic area, speed range, weather, lighting and infrastructure conditions", "why_it_matters": "Defines the conditions under which the capability is intended to operate." }, { "name": "Current domain eligibility", "kind": "state", "unit_or_values": "Inside domain, approaching boundary, outside domain or undetermined; with evidence timestamp", "why_it_matters": "Supports decisions about activation, continuation and exit." }, { "name": "Driving control mode", "kind": "state", "unit_or_values": "Unavailable, available, engaged, transition requested, fallback active or stopped; mapped to implementation-specific states", "why_it_matters": "Identifies who or what currently controls the car and which transitions are possible." }, { "name": "Perception and localisation health", "kind": "state", "unit_or_values": "Subsystem-specific health, uncertainty, degraded functions and timestamps", "why_it_matters": "Connects sensor and positioning limitations to remaining driving capability." }, { "name": "Automated operating speed envelope", "kind": "measurement", "unit_or_values": "Minimum and maximum speed in km/h for specified conditions", "why_it_matters": "Constrains activation, route suitability and manoeuvre planning." }, { "name": "Fallback capability", "kind": "category", "unit_or_values": "Supported fallback behaviours, triggering conditions and intended stopping or other risk-reducing outcomes", "why_it_matters": "Makes loss of normal autonomous operation assessable." }, { "name": "Remote support dependency", "kind": "relation", "unit_or_values": "Required external service, advisory or control authority, connectivity conditions and loss-of-link behaviour", "why_it_matters": "Distinguishes assistance from remote driving and exposes operational dependencies." }, { "name": "Validated configuration", "kind": "relation", "unit_or_values": "Linked hardware, software, calibration and map versions with applicable validation evidence", "why_it_matters": "Prevents capability evidence for one configuration being assumed valid for another." }, { "name": "Operational permission", "kind": "relation", "unit_or_values": "Applicable jurisdiction, operating authorisation, conditions, validity period and supporting record", "why_it_matters": "Separates technical capability from permission to operate." } ], "affordances": [ "Check whether a proposed route and current conditions fit the car's supported operating domain.", "Assess readiness and recommend enabling, restricting or withholding automated driving.", "Identify the responsible human or system during a control transition.", "Request a supported stop or fallback action through an authorised interface.", "Assess whether a fault, repair or software change requires inspection or renewed validation.", "Explain an operational decision using configuration, state and event evidence." ] }, "sources": [], "structure": { "bundles": [ { "id": "automation-boundary", "name": "Automation boundary", "description": "The driving capability being claimed and the division of responsibility between vehicle and humans.", "rationale": "The term autonomous car does not by itself establish which driving tasks the car can perform or whether a human must remain ready.", "layers": [ { "id": "driving-task-coverage", "name": "Driving task coverage", "description": "The automated feature's coverage of vehicle motion and response to the road environment.", "findings": [ { "id": "complete-driving-capability", "name": "Complete driving capability", "description": "Record the supported driving tasks and the evidence separating automated driving from partial assistance.", "questions": [ { "text": "Which feature performs steering, speed control and response to objects and events during its intended operation?", "kind": "definition", "id": "complete-driving-capability-q01" }, { "text": "Which driving responsibilities remain with an occupant, and under what conditions?", "kind": "boundary", "id": "complete-driving-capability-q02" } ] } ] }, { "id": "human-and-remote-roles", "name": "Human and remote roles", "description": "Required human availability and the authority of remote participants.", "findings": [ { "id": "supervision-and-intervention", "name": "Supervision and intervention", "description": "Record occupant and remote roles without treating supervision, advice and direct driving as interchangeable.", "questions": [ { "text": "Must a person monitor the road, remain available for a takeover request or perform fallback?", "kind": "boundary", "id": "supervision-and-intervention-q01" }, { "text": "Can remote personnel advise the car, authorise a manoeuvre or directly control its motion?", "kind": "action", "id": "supervision-and-intervention-q02" } ] } ] } ] }, { "id": "operating-domain", "name": "Operating domain", "description": "The conditions that bound automated operation and their evaluation during a journey.", "rationale": "A car may support autonomous driving only on certain roads or under particular environmental conditions.", "layers": [ { "id": "domain-definition", "name": "Domain definition", "description": "Explicit road, geographic and environmental limits of each automated driving feature.", "findings": [ { "id": "permitted-driving-conditions", "name": "Permitted driving conditions", "description": "Record a feature-specific operating envelope, including combinations of conditions that exclude use.", "questions": [ { "text": "Which roads, locations, speeds, weather and lighting conditions are included or excluded?", "kind": "boundary", "id": "permitted-driving-conditions-q01" }, { "text": "Which versioned capability description or validation record establishes these limits?", "kind": "provenance", "id": "permitted-driving-conditions-q02" } ] } ] }, { "id": "domain-monitoring", "name": "Domain monitoring", "description": "Assessment of current conditions and foreseeable exits from the supported envelope.", "findings": [ { "id": "journey-eligibility", "name": "Journey eligibility", "description": "Record whether a route remains eligible and how uncertainty or a domain boundary affects operation.", "questions": [ { "text": "What observations establish that the current road segment and conditions are inside the domain?", "kind": "measurement", "id": "journey-eligibility-q01" }, { "text": "What must happen before a planned or unexpected exit from the domain?", "kind": "action", "id": "journey-eligibility-q02" } ] } ] } ] }, { "id": "driving-system", "name": "Driving system", "description": "The chain from observing the road to executing a manoeuvre.", "rationale": "Autonomous capability depends on how sensing, interpretation, planning and physical control function together.", "layers": [ { "id": "perception-and-positioning", "name": "Perception and positioning", "description": "Observation of relevant road actors and estimation of the car's location.", "findings": [ { "id": "environment-estimate", "name": "Environment estimate", "description": "Record installed sensing and positioning dependencies, their limitations and their current health.", "questions": [ { "text": "Which sensors, positioning services and maps are required, and what happens when one is obscured, unavailable or stale?", "kind": "boundary", "id": "environment-estimate-q01" }, { "text": "How are object-detection limitations and localisation uncertainty measured and exposed to the driving system?", "kind": "measurement", "id": "environment-estimate-q02" } ] } ] }, { "id": "planning-and-actuation", "name": "Planning and actuation", "description": "Selection and physical execution of driving actions within the available control envelope.", "findings": [ { "id": "manoeuvre-feasibility", "name": "Manoeuvre feasibility", "description": "Record supported manoeuvres and how vehicle condition constrains their execution.", "questions": [ { "text": "Which manoeuvres can the system execute, and which require assistance or are excluded?", "kind": "boundary", "id": "manoeuvre-feasibility-q01" }, { "text": "How do braking, steering, tyre condition, load and available power constrain the actions the planner may request?", "kind": "action", "id": "manoeuvre-feasibility-q02" } ] } ] } ] }, { "id": "fallback-and-interaction", "name": "Fallback and interaction", "description": "Control transitions, degraded operation and communication during abnormal situations.", "rationale": "Assessing an autonomous car requires knowing how it behaves when normal driving cannot continue and how people can intervene.", "layers": [ { "id": "degradation-and-fallback", "name": "Degradation and fallback", "description": "Responses to faults, lost dependencies and conditions exceeding the driving capability.", "findings": [ { "id": "risk-reducing-response", "name": "Risk-reducing response", "description": "Record fault-specific fallback actions and the evidence supporting their intended outcomes.", "questions": [ { "text": "Which failures or domain violations trigger restricted driving, a takeover request or an automated fallback manoeuvre?", "kind": "action", "id": "risk-reducing-response-q01" }, { "text": "What stopping or other risk-reducing outcome is intended, and what conditions could prevent it?", "kind": "boundary", "id": "risk-reducing-response-q02" } ] } ] }, { "id": "occupant-and-responder-interface", "name": "Occupant and responder interface", "description": "How people understand the current mode and request supported interventions.", "findings": [ { "id": "control-transition-interface", "name": "Control transition interface", "description": "Record mode indications, takeover communication and intervention access for occupants and responders.", "questions": [ { "text": "How does the car communicate who controls driving and whether a takeover request has been acknowledged?", "kind": "definition", "id": "control-transition-interface-q01" }, { "text": "How can an occupant or emergency responder request a stop, inhibit further movement or obtain assistance?", "kind": "action", "id": "control-transition-interface-q02" } ] } ] } ] }, { "id": "assurance-and-service", "name": "Assurance and service", "description": "Evidence, authorisation and upkeep needed to sustain an assessed automated driving capability.", "rationale": "A capability assessment can become invalid when the configuration, condition or operating permission changes.", "layers": [ { "id": "capability-evidence-and-permission", "name": "Capability evidence and permission", "description": "Traceable support for capability claims and their applicability to a particular deployment.", "findings": [ { "id": "applicable-assurance", "name": "Applicable assurance", "description": "Record validation scope, unresolved limitations and applicable operating permissions separately.", "questions": [ { "text": "Which test reports or assessments support the claimed capability for this configuration and operating domain?", "kind": "provenance", "id": "applicable-assurance-q01" }, { "text": "Which issuing bodies, standards and operating authorisations apply, and what restrictions do their records impose?", "kind": "boundary", "id": "applicable-assurance-q02" } ] } ] }, { "id": "configuration-and-maintenance", "name": "Configuration and maintenance", "description": "Changes and service conditions that affect readiness for automated driving.", "findings": [ { "id": "continued-driving-readiness", "name": "Continued driving readiness", "description": "Record software, map, calibration and hardware changes together with required checks and diagnostic evidence.", "questions": [ { "text": "Which updates, sensor replacements, repairs or calibration changes require checks before automated operation resumes?", "kind": "action", "id": "continued-driving-readiness-q01" }, { "text": "Which configuration records and time-aligned event logs establish the car's state when an operational decision or incident occurred?", "kind": "provenance", "id": "continued-driving-readiness-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": [ "Autonomous car is an informal term with inconsistent boundaries; confirm whether this registry includes conditional automation or reserves the term for driverless operation.", "Standards are recalled by identifier and scope; applicable editions, legal adoption, and approval requirements require verification.", "No universal dimensions, power source, speed range, or safety certification mark distinguishes autonomous cars; quantitative claims require a specified vehicle and operational design domain." ], "questions": [ { "id": "evidence-confidence-notes-q01", "text": "Which of these check these first hold for the sense of autonomous car 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": [ "Conditionally automated cars requiring a fallback-ready user (SAE Level 3)", "Highly automated cars requiring no human driving fallback within their operational design domain (SAE Level 4)", "Fully automated cars intended to operate under all driver-manageable on-road conditions (SAE Level 5)" ], "questions": [ { "id": "evidence-kinds-q01", "text": "Which of these kinds and varieties hold for the sense of autonomous car this model covers, and on what evidence?", "kind": "provenance" } ] }, { "id": "evidence-identifiers", "name": "Identifiers and schemes", "description": "Recalled without web access and unsourced; every item is a lead to verify.", "evidence": [ { "scheme": "Vehicle identification number (VIN)", "value_or_pattern": "17-character identifier under widely used VIN systems", "note": "Identifies an individual vehicle, not its automation level, software version, or permitted operating conditions." }, { "scheme": "SAE J3016 driving automation classification", "value_or_pattern": "Level 0 through Level 5", "note": "Classifies driving automation features rather than uniquely identifying vehicles; Levels 3-5 involve automated driving systems." } ], "questions": [ { "id": "evidence-identifiers-q01", "text": "Which of these identifiers and schemes hold for the sense of autonomous car 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": [ "SAE International J3016: terminology and taxonomy for driving automation systems for on-road motor vehicles.", "ISO 26262, issued by the International Organization for Standardization: functional safety of road-vehicle electrical and electronic systems.", "ISO 21448, issued by the International Organization for Standardization: safety of the intended functionality.", "ISO/SAE 21434, jointly issued by ISO and SAE International: road-vehicle cybersecurity engineering.", "UN Regulation No. 157, developed through UNECE WP.29: approval requirements for Automated Lane Keeping Systems within its defined scope." ], "questions": [ { "id": "evidence-standards-and-regulation-q01", "text": "Which of these standards and regulation hold for the sense of autonomous car 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": [ "Driverless passenger transport within geographically and operationally restricted service areas.", "Conditional automation of driving on suitable roads under specified conditions.", "Automated valet parking within supported facilities.", "Research and validation of automated driving through instrumented road testing." ], "questions": [ { "id": "evidence-real-world-use-q01", "text": "Which of these real-world use hold for the sense of autonomous car 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": [ "Missed or incorrect detection of road users, obstacles, signals, or markings because of occlusion, adverse weather, contamination, or perception limitations.", "Localization errors or outdated map information causing incorrect positioning or route interpretation.", "Prediction and planning errors around unusual situations or other road users' unexpected behavior.", "Sensor, computing, power, steering, or braking failures that prevent continued safe operation or a safe fallback.", "Unsafe transitions of control, including delayed human takeover in conditional automation and use outside the supported operational design domain." ], "questions": [ { "id": "evidence-failure-modes-and-hazards-q01", "text": "Which of these failure modes and hazards hold for the sense of autonomous car this model covers, and on what evidence?", "kind": "provenance" } ] }, { "id": "evidence-regional-variation", "name": "Regional variation", "description": "Recalled without web access and unsourced; every item is a lead to verify.", "evidence": [ "Testing permissions, deployment authorization, and requirements for a safety driver differ between jurisdictions.", "Road markings, traffic conventions, signage, and driving behavior require locally appropriate validation." ], "questions": [ { "id": "evidence-regional-variation-q01", "text": "Which of these regional variation hold for the sense of autonomous car 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": "car", "difference": "The broader vehicle kind does not require an automated driving system; autonomous cars add automated performance of the driving task." }, { "name": "advanced driver-assistance system", "difference": "Assistance features at SAE Levels 1-2 require the driver to supervise the driving environment and remain responsible for completing the driving task." }, { "name": "automated driving system", "difference": "The system is the hardware and software that performs the driving task; the autonomous car is the vehicle incorporating it." }, { "name": "connected car", "difference": "External data connectivity does not establish the ability to perform the driving task autonomously." }, { "name": "remotely driven car", "difference": "A remote human performs the driving task; remote assistance alone does not necessarily make an autonomous car remotely driven." } ], "questions": [ { "id": "evidence-neighbours-q01", "text": "Which of these neighbouring kinds and how to tell them apart hold for the sense of autonomous car this model covers, and on what evidence?", "kind": "provenance" } ] } ] } ] } ] }, "openQuestions": [ "What definition and automation taxonomy should anchor this registry entry, particularly for features that require a human to perform fallback?", "Does an existing Vercy car or world model already own any of this scope, and which capabilities should be represented through links?", "Which operating-domain descriptions and validation sources provide enough detail to assess combined environmental limits?", "Which jurisdiction-specific standards, approvals and remote-operation rules apply to the deployments the catalogue intends to represent?", "What evidence is sufficient to judge fallback effectiveness and continued readiness after software changes, repairs or sensor degradation?" ], "statistics": { "bundles": 6, "layers": 11, "findings": 18, "questions": 28 } }, "draft": { "generator": "vr.draft.v3", "status": "draft-generated", "researched": false, "archetype": "device, machine or tool", "method": "Written from the archetype playbook - what this kind of thing needs beyond identity and provenance - and from the structure that recurred across 6,333 models already researched by two engines. Applied to this entry by rule. No source was read for this thing and no claim here is researched. This entry carries no facets of its own, so they were inferred from its domain - a guess about a whole domain applied to one thing.", "facetsInferred": true, "nextPass": "A researcher replaces this draft with a sourced specification. Treat every sentence below as a proposal to argue with.", "purpose": "Give an agent a durable, checkable way to recognise a autonomous car, record what state it is in, and decide what may be done with it.", "whatItIs": "Enable an AI agent to recognise an autonomous car, assess whether its automated driving capability is usable in the current situation, and determine what operation or intervention is 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: Hyundai Ioniq 5 Robotaxi, Self-driving taxis, Blees BB-1, Stanley, H1ghlander, Sedric, kar-go, robotaxi, Renault EZ-GO, Renault EZ-Ultimo, Navya Autonom Cab, Apolong.", "15 finer distinctions are held as aliases rather than separate entries, because telling them apart needs a task that asks for it.", "Described in 59 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 autonomous car, 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": [ "Hyundai Ioniq 5 Robotaxi", "Self-driving taxis", "Blees BB-1", "Stanley", "H1ghlander", "Sedric", "kar-go", "robotaxi", "Renault EZ-GO", "Renault EZ-Ultimo", "Navya Autonom Cab", "Apolong" ] } ], "standing": "Described in 59 Wikipedia languages, which measures how widely it is written about rather than how important or how common it is. 15 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 autonomous car from another, and a autonomous car 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 autonomous car, 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 autonomous car, 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 autonomous car 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 autonomous car, 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 autonomous car, 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 autonomous car 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 autonomous car 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 autonomous car, 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 autonomous car, 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 autonomous car 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 autonomous car from the things most often confused with it.", "questions": [ { "id": "distinguishing-features-q01", "text": "What identifies and describes what distinguishes a autonomous car, 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 autonomous car, 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 autonomous car 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 autonomous car 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 autonomous car, 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 autonomous car, 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 autonomous car 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 autonomous car is built from and which parts are replaceable.", "questions": [ { "id": "parts-and-materials-q01", "text": "What identifies and describes the composition of a autonomous car, 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 autonomous car, 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 autonomous car 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 autonomous car is judged and by whom.", "questions": [ { "id": "condition-assessment-q01", "text": "What identifies and describes the condition of a autonomous car, 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 autonomous car, 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 autonomous car 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 autonomous car 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 autonomous car is, and what that position is measured against.", "questions": [ { "id": "position-and-frame-q01", "text": "What identifies and describes the location of a autonomous car, 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 autonomous car, 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 autonomous car 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 autonomous car 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 autonomous car, 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 autonomous car, 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 autonomous car 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 autonomous car 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 autonomous car between them.", "questions": [ { "id": "stages-and-transitions-q01", "text": "What identifies and describes the lifecycle of a autonomous car, 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 autonomous car, 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 autonomous car 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 autonomous car, how often and by whom.", "findings": [ { "id": "observation-record", "name": "Observation record", "description": "How an observation of a autonomous car 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 autonomous car, 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 autonomous car, 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 autonomous car 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 autonomous car 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 autonomous car 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 autonomous car, 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 autonomous car 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 autonomous car 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 autonomous car 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 autonomous car 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 autonomous car 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 autonomous car, 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 autonomous car 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 autonomous car and how confident it is.", "questions": [ { "id": "claim-provenance-q01", "text": "What identifies and describes a claim about a autonomous car, 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 autonomous car, 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 autonomous car 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 autonomous car is retired without being erased.", "questions": [ { "id": "validity-and-supersession-q01", "text": "What identifies and describes the validity of a claim about a autonomous car, 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 autonomous car, 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 autonomous car 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 } } } }