{ "model": { "rank": 3707, "code": "thing-q180481", "model_id": "vr.tr.ambulance", "name": "ambulance", "purpose": "Enable an agent to recognise an ambulance, assess its readiness for a specified patient transport mission, and identify the conditions governing its safe use.", "family": "Thing Registry", "category": "Physical world and living systems", "status": "research-draft", "kind": "thing", "plane": "PHY", "domain": "PHY.OBJ", "industry": "", "version": "", "url": "/models/thing/q180481/", "tier": 2, "score": 82, "payload": { "layer": "wikidata", "aliases": [ "mobile intensive care unit", "animal ambulance", "medical helicopter", "Ambulances in Japan", "Animal Ambulance Foundation Zwolle", "Krankentransportwagen in Germany", "military ambulance", "mobile hospital unit", "water ambulance", "air ambulance", "Mobile Intensive Care Ambulance", "ISUZU SUPERMEDIC", "SEC", "Baby-Notarztwagen in Germany" ], "aliasCount": 14, "merged": 14, "knownIn": 82, "facets": null, "markers": [], "lexicalClass": "", "senseRank": null, "alsoRegisteredAs": null, "source": { "dataset": "wikidata", "item": "Q180481", "url": "https://www.wikidata.org/wiki/Q180481", "license": "CC0 1.0" } }, "research": { "vercy": "1.0-draft", "publication": { "status": "research-draft", "adjudicationStatus": "unreviewed", "publishableCanonical": false, "generatedAt": "2026-09-07T14:56:53Z", "providers": [ "Codex" ], "breadth": "recalled by Codex without web access - no source was read", "missingProviders": [], "pass": 2, "cost": { "grok": { "seconds": 31.8, "error": "Reading additional input from stdin...\nOpenAI Codex v0.153.3\n--------\nworkdir: R:\\02_PROJECTS\\02_Meta_Models_Platforms\\Ver.cy\\current\\thing-registry-backlog\nmodel: gpt-6-astra\nprovider: openai\napproval: never\nsandbox: read-only\nreasoning effort: none\nreasoning summaries: none\nsession id: 01a07c5e-09eb-7592-83db-1efb4fe1e5c3\n--------\nuser\nDescribe what is already known about one registered thing. Answer as JSON only, no prose around it.\n\nThing: ambulance\nSense to describe: (none recorded)\nDomain code: PHY.OBJ\nAlso known as: (none)\n\n\nContext for this batch of 801 things:\n# Batch 004: 1001 regist", "usd": 0, "recall": true }, "codex": { "seconds": 82.2, "error": "Reading additional input from stdin...\nOpenAI Codex v0.153.3\n--------\nworkdir: R:\\02_PROJECTS\\02_Meta_Models_Platforms\\Ver.cy\\current\\thing-registry-backlog\nmodel: gpt-6-astra\nprovider: openai\napproval: never\nsandbox: read-only\nreasoning effort: none\nreasoning summaries: none\nsession id: 01a07c5e-0bdb-78f0-9993-d9555e4ca850\n--------\nuser\nYou are drafting a Vercy meta-model for one registered thing. Answer as JSON only, no prose around it.\n\nThing: ambulance\nRegistry id: vr.tr.ambulance\nPlane / domain: PHY / PHY.OBJ\nRegistry definition: (none recorded)\nNames folded into this entry: (none)\n\n\nCont" } } }, "metaModel": { "id": "THING-Q180481", "registryId": "vr.tr.ambulance", "name": "ambulance", "version": "0.1.0-research.1", "entryKind": "thing", "family": "Thing Registry", "domain": [ "PHY.OBJ" ], "status": "research-draft" }, "canonicalUrl": "https://ver.cy/models/thing/q180481/", "model": { "registry_id": "vr.tr.ambulance", "name": "ambulance", "purpose": "Enable an agent to recognise an ambulance, assess its readiness for a specified patient transport mission, and identify the conditions governing its safe use.", "definition": "An ambulance is a vehicle designed or adapted to transport sick or injured people and equipped to support care appropriate to its intended patient transport or emergency medical role.", "scope_statement": "This model owns the registered physical kind ambulance (vr.tr.ambulance, PHY / PHY.OBJ): a vehicle configured for transporting patients with provision for care during transit, including its transport platform, patient accommodation, installed systems, and mission readiness; product models and individual vehicles are instances or specialisations of this kind.", "in_scope": [ "Ambulance identity, transport medium, intended mission classes, and care capability", "Patient accommodation, loading arrangements, restraints, and attendant access", "Installed clinical equipment, consumables, and supporting vehicle systems", "Vehicle and patient-compartment condition, maintenance, and decontamination status", "Interfaces with dispatch, crews, receiving facilities, and applicable operating authorisations" ], "out_of_scope": [ "Ambulance service organisations, staffing policy, and fleet-wide deployment strategy", "Clinician qualifications and professional scopes of practice", "Patient diagnoses, treatment protocols, and individual clinical records", "Dispatch incidents, route plans, and completed transport episodes", "Hospital facilities, helipads, and other receiving infrastructure", "Manufacture and servicing of generic vehicle components except their ambulance-specific integration" ], "distinguishing_features": [ "Determine whether the vehicle is configured to carry patients during transit, rather than only carrying responders or equipment to a scene.", "Inspect whether patient accommodation and attendant access support the declared transport and care role, distinguishing an ambulance from ordinary passenger transport.", "Distinguish a patient-carrying vehicle from a stationary treatment facility or a treatment trailer whose occupancy during movement is not authorised.", "Verify ambulance designation and declared capability from configuration and applicable records; emergency markings or warning devices alone do not establish the kind.", "Separate the ambulance vehicle from the organisation operating it and from the particular emergency or transfer mission using it." ], "characteristics": [ { "name": "Transport medium", "kind": "category", "unit_or_values": "road | air | water | other | unresolved", "why_it_matters": "Determines which platform constraints, access interfaces, and operating rules require specialisation." }, { "name": "Declared transport role", "kind": "category", "unit_or_values": "Locally defined emergency, non-emergency, interfacility, specialist, or mixed roles, with supporting evidence", "why_it_matters": "Prevents the ambulance label from implying suitability for every patient transport mission." }, { "name": "Care capability designation", "kind": "category", "unit_or_values": "Designation with issuing authority, jurisdiction, definition, and validity period; unknown where unverified", "why_it_matters": "Capability labels must be interpreted in their local system and checked against actual configuration." }, { "name": "Patient carrying capacity", "kind": "measurement", "unit_or_values": "Number of stretcher, seated, wheelchair, and other patient positions by permitted configuration", "why_it_matters": "Capacity depends on the installed layout and permitted occupancy combination." }, { "name": "Patient handling load limits", "kind": "measurement", "unit_or_values": "kg, separately for stretcher, lift or ramp, anchorage, and other relevant components", "why_it_matters": "The patient handling chain is constrained by each component's applicable rated limit." }, { "name": "Patient access envelope", "kind": "measurement", "unit_or_values": "mm for usable openings, loading clearances, and patient-position dimensions", "why_it_matters": "Determines compatibility with the patient, transport device, and loading location." }, { "name": "Available supporting resources", "kind": "measurement", "unit_or_values": "Fuel or traction energy in L or kWh; auxiliary energy in Wh; usable medical gas quantity with units and reference conditions", "why_it_matters": "Mission duration must account for both propulsion and patient-care resource demands." }, { "name": "Clinical equipment configuration", "kind": "relation", "unit_or_values": "Linked installed and carried equipment, mounting arrangements, service status, and mission requirements", "why_it_matters": "Equipment presence alone does not establish that the required care capability is available." }, { "name": "Mission readiness", "kind": "state", "unit_or_values": "ready | ready with restrictions | not ready | unknown, for a named mission profile and assessment time", "why_it_matters": "Readiness is conditional on the patient, journey, crew, configuration, and current defects." }, { "name": "Decontamination release status", "kind": "state", "unit_or_values": "released | cleaning required | undergoing cleaning | restricted | unknown, with evidence and timestamp", "why_it_matters": "A mechanically serviceable ambulance may remain unavailable for patient occupancy." }, { "name": "Applicable authorisations", "kind": "relation", "unit_or_values": "Linked vehicle approvals, ambulance designations, inspections, operating restrictions, and issuing bodies", "why_it_matters": "Physical capability and permission to operate must both be established." } ], "affordances": [ "Assess suitability for a specified patient, care requirement, transport device, and journey.", "Check loading, restraint, equipment mounting, and receiving-facility compatibility before assignment.", "Estimate mission endurance from available propulsion, electrical, and clinical resources under stated assumptions.", "Identify defects, depleted supplies, contamination, or authorisation gaps that restrict deployment.", "Determine required configuration changes, replenishment, servicing, or inspection before release.", "Record readiness evidence and escalate unresolved clinical or operational suitability decisions to the responsible personnel." ] }, "sources": [], "structure": { "bundles": [ { "id": "ambulance-identity-and-role", "name": "Ambulance identity and role", "description": "Establishes what qualifies as an ambulance and which transport and care roles its configuration supports.", "rationale": "Ambulance appearance and terminology can obscure differences between patient transport vehicles, responder vehicles, and locally defined capability classes.", "layers": [ { "id": "patient-transport-boundary", "name": "Patient transport boundary", "description": "Locates the ambulance kind among vehicles and mobile care facilities.", "findings": [ { "id": "patient-carriage-and-care", "name": "Patient carriage and care", "description": "Record evidence that the vehicle supports patient carriage and its declared provision for care during movement.", "questions": [ { "text": "What patient accommodation and care provisions establish that this vehicle belongs to the ambulance kind?", "kind": "definition", "id": "patient-carriage-and-care-q01" }, { "text": "What excludes responder-only vehicles, ordinary assisted transport, and stationary mobile clinics from this scope?", "kind": "boundary", "id": "patient-carriage-and-care-q02" } ] } ] }, { "id": "mission-and-capability-classes", "name": "Mission and capability classes", "description": "Connects transport medium and intended missions to evidenced capability designations.", "findings": [ { "id": "declared-role-and-local-classification", "name": "Declared role and local classification", "description": "Represent capability labels with their authority and meaning rather than treating them as universal classifications.", "questions": [ { "text": "Which authority defines this ambulance's transport and care capability class, and what evidence supports the designation?", "kind": "provenance", "id": "declared-role-and-local-classification-q01" }, { "text": "Which emergency, transfer, or specialist missions fall outside its declared capability?", "kind": "boundary", "id": "declared-role-and-local-classification-q02" } ] } ] } ] }, { "id": "patient-loading-and-accommodation", "name": "Patient loading and accommodation", "description": "Models the physical path from patient pickup through secured carriage to unloading.", "rationale": "An ambulance must accommodate the particular patient and transport device while maintaining secure carriage and access for care.", "layers": [ { "id": "loading-path-and-limits", "name": "Loading path and limits", "description": "Captures openings, handling equipment, working space, and load constraints along the loading path.", "findings": [ { "id": "patient-and-device-fit", "name": "Patient and device fit", "description": "Assess the combined patient and transport-device envelope against the complete loading arrangement.", "questions": [ { "text": "What usable clearances and component load limits constrain loading this patient with the proposed stretcher, wheelchair, or other device?", "kind": "measurement", "id": "patient-and-device-fit-q01" }, { "text": "What handling equipment, personnel, and site conditions are required to load and unload safely?", "kind": "action", "id": "patient-and-device-fit-q02" } ] } ] }, { "id": "secured-carriage-and-care-access", "name": "Secured carriage and care access", "description": "Describes permitted patient positions, restraints, attendant positions, and access during transport.", "findings": [ { "id": "occupied-layout-compatibility", "name": "Occupied layout compatibility", "description": "Evaluate the occupied configuration, including patient restraints, device anchorage, equipment security, and attendant access.", "questions": [ { "text": "Which combinations of patient positions, transport devices, restraints, and anchorages are approved for this configuration?", "kind": "provenance", "id": "occupied-layout-compatibility-q01" }, { "text": "Can the required patient observations and equipment access occur from the permitted attendant positions during transit?", "kind": "action", "id": "occupied-layout-compatibility-q02" } ] } ] } ] }, { "id": "onboard-care-and-support-systems", "name": "Onboard care and support systems", "description": "Connects the ambulance's declared care role to installed equipment, supplies, utilities, and patient-compartment conditions.", "rationale": "Patient-care capability depends on functioning integrated systems and sufficient resources throughout the journey.", "layers": [ { "id": "clinical-equipment-and-consumables", "name": "Clinical equipment and consumables", "description": "Records mission-relevant equipment availability, compatibility, servicing, and consumable stock.", "findings": [ { "id": "mission-specific-care-equipment", "name": "Mission-specific care equipment", "description": "Compare evidenced equipment requirements with the actual carried and installed configuration.", "questions": [ { "text": "Which equipment and consumables does the responsible clinical service require for the proposed mission and patient group?", "kind": "provenance", "id": "mission-specific-care-equipment-q01" }, { "text": "Which required items are absent, expired, unserviceable, incompatible, or unsecured, and what must happen before deployment?", "kind": "action", "id": "mission-specific-care-equipment-q02" } ] } ] }, { "id": "utilities-and-compartment-environment", "name": "Utilities and compartment environment", "description": "Captures power, medical gas where fitted, lighting, ventilation, and temperature control as support for occupied transport.", "findings": [ { "id": "care-system-endurance-and-continuity", "name": "Care system endurance and continuity", "description": "Assess resource sufficiency and continuity across loading, transit, stops, and handover.", "questions": [ { "text": "What operating duration do available electrical and medical gas resources support under the declared loads, reserve assumptions, and delay allowance?", "kind": "measurement", "id": "care-system-endurance-and-continuity-q01" }, { "text": "Which failures or operating transitions interrupt required power, ventilation, lighting, or temperature control, and what permitted response follows?", "kind": "action", "id": "care-system-endurance-and-continuity-q02" } ] } ] } ] }, { "id": "vehicle-readiness-and-turnaround", "name": "Vehicle readiness and turnaround", "description": "Determines whether platform condition, conversion systems, cleanliness, and replenishment permit patient service.", "rationale": "Ambulance availability requires both transport serviceability and a patient compartment ready for the next mission.", "layers": [ { "id": "platform-and-conversion-serviceability", "name": "Platform and conversion serviceability", "description": "Combines transport-platform checks with checks of ambulance-specific installations and controls.", "findings": [ { "id": "defects-and-release-restrictions", "name": "Defects and release restrictions", "description": "Relate observed faults and overdue work to deployment restrictions for the ambulance's intended role.", "questions": [ { "text": "Which inspections cover the platform, patient-compartment conversion, loading mechanisms, restraints, and warning systems where fitted?", "kind": "provenance", "id": "defects-and-release-restrictions-q01" }, { "text": "Which observed defects require withdrawal, restricted use, or corrective work, and who has authority to release the vehicle?", "kind": "action", "id": "defects-and-release-restrictions-q02" } ] } ] }, { "id": "decontamination-and-replenishment", "name": "Decontamination and replenishment", "description": "Tracks the work required to restore the ambulance after patient contact or resource use.", "findings": [ { "id": "patient-compartment-release", "name": "Patient compartment release", "description": "Record cleaning, waste removal, equipment replacement, and replenishment evidence before renewed patient occupancy.", "questions": [ { "text": "Which approved cleaning procedure applies to the recorded exposure and the installed surfaces and equipment?", "kind": "provenance", "id": "patient-compartment-release-q01" }, { "text": "What unresolved contamination, waste, missing supplies, or incomplete checks prevent release for the next patient?", "kind": "action", "id": "patient-compartment-release-q02" } ] } ] } ] }, { "id": "mission-interfaces-and-operating-permission", "name": "Mission interfaces and operating permission", "description": "Connects the physical ambulance to dispatch, the assigned crew, receiving locations, and jurisdictional permissions.", "rationale": "A serviceable ambulance can still be unsuitable for a mission because of crew, communication, access, or authorisation constraints.", "layers": [ { "id": "dispatch-and-transfer-compatibility", "name": "Dispatch and transfer compatibility", "description": "Represents external dependencies needed to assign, track, receive, and unload the ambulance.", "findings": [ { "id": "crew-and-destination-fit", "name": "Crew and destination fit", "description": "Reference crew readiness and destination interfaces without duplicating personnel or facility models.", "questions": [ { "text": "Which crew-role confirmations and communication interfaces are required to operate this configuration for the proposed mission?", "kind": "action", "id": "crew-and-destination-fit-q01" }, { "text": "What vehicle dimensions, access conditions, and patient-transfer interfaces must the pickup and receiving locations accommodate?", "kind": "measurement", "id": "crew-and-destination-fit-q02" } ] } ] }, { "id": "approvals-and-operating-modes", "name": "Approvals and operating modes", "description": "Separates technical conformity, ambulance designation, and permission for particular operating modes.", "findings": [ { "id": "evidenced-permission-to-operate", "name": "Evidenced permission to operate", "description": "Link applicable approvals and restrictions to the vehicle's jurisdiction, transport medium, configuration, and intended use.", "questions": [ { "text": "Which standards, inspections, and authorisations apply, who issues them, and what evidence establishes their applicability and current validity?", "kind": "provenance", "id": "evidenced-permission-to-operate-q01" }, { "text": "Under what documented conditions may emergency warning equipment or other special operating modes be used, and who may authorise their use?", "kind": "action", "id": "evidenced-permission-to-operate-q02" } ] } ] } ] }, { "id": "evidence-and-external-alignment", "name": "Evidence and external alignment", "description": "What the world already says about this thing, gathered so the model can be checked against it.", "rationale": "A model that cannot be lined up against existing standards, identifiers and practice cannot be adopted by anyone who already uses them.", "layers": [ { "id": "reported-evidence", "name": "Reported evidence", "description": "Findings from the breadth pass, kept separate from the structural claims.", "findings": [ { "id": "evidence-confidence-notes", "name": "Check these first", "description": "Recalled without web access and unsourced; every item is a lead to verify.", "evidence": [ "This describes the vehicle kind, including road, air and water forms; legal definitions may use narrower boundaries.", "Standards are recalled without source consultation; applicable editions, legal adoption and local requirements require verification.", "Patient capacity is indicative for conventional road ambulances; equipment, staffing, dimensions and power systems depend on configuration and clinical role." ], "questions": [ { "id": "evidence-confidence-notes-q01", "text": "Which of these check these first hold for the sense of ambulance 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": [ "Emergency road ambulance", "Non-emergency patient transport ambulance", "Intensive care transport ambulance", "Fixed-wing air ambulance", "Helicopter air ambulance", "Water ambulance" ], "questions": [ { "id": "evidence-kinds-q01", "text": "Which of these kinds and varieties hold for the sense of ambulance 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": "Typically 17 characters for modern road vehicles", "note": "Identifies an individual road vehicle, not the ambulance concept, service provider or clinical capability." }, { "scheme": "Aircraft registration", "value_or_pattern": "National registration mark", "note": "Identifies an individual air ambulance aircraft; the mark does not itself establish medical capability." } ], "questions": [ { "id": "evidence-identifiers-q01", "text": "Which of these identifiers and schemes hold for the sense of ambulance 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": [ "EN 1789, issued by the European Committee for Standardization (CEN), addresses medical vehicles and their equipment for road ambulances.", "The EN 1865 series, issued by CEN, addresses patient handling equipment used in road ambulances.", "CAAS Ground Vehicle Standard, issued by the Commission on Accreditation of Ambulance Services, addresses ground ambulance vehicles in the United States." ], "questions": [ { "id": "evidence-standards-and-regulation-q01", "text": "Which of these standards and regulation hold for the sense of ambulance 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": [ "Transporting patients from emergency scenes to healthcare facilities while providing assessment and care.", "Transferring patients between healthcare facilities.", "Providing scheduled transport for patients requiring ambulance equipment or assistance.", "Moving critically ill patients with specialist staff and intensive care equipment.", "Supporting medical coverage at major incidents and public events." ], "questions": [ { "id": "evidence-real-world-use-q01", "text": "Which of these real-world use hold for the sense of ambulance this model covers, and on what evidence?", "kind": "provenance" } ] }, { "id": "evidence-measurements", "name": "Typical measurements", "description": "Recalled without web access and unsourced; every item is a lead to verify.", "evidence": [ { "quantity": "Stretcher patient capacity in conventional road ambulances", "typical_range": "1-2, depending on vehicle configuration", "unit": "patients" } ], "questions": [ { "id": "evidence-measurements-q01", "text": "Which of these typical measurements hold for the sense of ambulance 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": [ "Collisions during transport, with increased exposure when occupants must provide care while the vehicle is moving.", "Failure of stretcher mounts, equipment restraints or occupant restraints during sudden braking or a collision.", "Loss of electrical power, depleted batteries or exhausted medical oxygen supplies compromising onboard equipment.", "Infection transmission through contaminated surfaces, equipment or inadequate cleaning.", "Patient or crew injury during lifting, loading and unloading." ], "questions": [ { "id": "evidence-failure-modes-and-hazards-q01", "text": "Which of these failure modes and hazards hold for the sense of ambulance 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": [ "European road ambulance classifications distinguish patient transport, emergency and mobile intensive care roles.", "United States Type I, Type II and Type III designations distinguish chassis and body configurations rather than directly specifying clinical capability.", "Staffing, permitted clinical interventions, vehicle markings and emergency traffic privileges vary by jurisdiction." ], "questions": [ { "id": "evidence-regional-variation-q01", "text": "Which of these regional variation hold for the sense of ambulance 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": "Emergency medical services", "difference": "The service system includes personnel, dispatch and clinical operations; an ambulance is a vehicle used within or alongside that system." }, { "name": "Rapid response vehicle", "difference": "Carries responders and equipment but may lack the accommodation and equipment required to transport a patient." }, { "name": "Wheelchair-accessible transport vehicle", "difference": "Provides accessible transport but is not necessarily equipped or operated to provide ambulance-level patient care." }, { "name": "Ambulance model", "difference": "A manufacturer's product design is a particular implementation of the vehicle kind described here." } ], "questions": [ { "id": "evidence-neighbours-q01", "text": "Which of these neighbouring kinds and how to tell them apart hold for the sense of ambulance this model covers, and on what evidence?", "kind": "provenance" } ] } ] } ] } ] }, "openQuestions": [ "Does the registry intend ambulance to include air and water ambulances, or should those be linked specialisations of a road-ambulance scope?", "What minimum patient-care provision distinguishes an ambulance from non-emergency assisted transport across the jurisdictions the catalogue must serve?", "Which governing standards and issuing bodies apply to each transport medium and capability class, and which editions and conformity records should be referenced?", "What sourced capacity, dimension, load-limit, and endurance ranges are useful for each ambulance configuration without implying universal values?", "Which documented failure modes and release criteria should govern readiness decisions, and how should responsibility be divided among vehicle, equipment, clinical-service, and crew models?" ], "statistics": { "bundles": 6, "layers": 11, "findings": 19, "questions": 29 } }, "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 ambulance, record what state it is in, and decide what may be done with it.", "whatItIs": "Enable an agent to recognise an ambulance, assess its readiness for a specified patient transport mission, and identify the conditions governing its safe use.", "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: mobile intensive care unit, animal ambulance, medical helicopter, Ambulances in Japan, Animal Ambulance Foundation Zwolle, Krankentransportwagen in Germany, military ambulance, mobile hospital unit, water ambulance, air ambulance, Mobile Intensive Care Ambulance, ISUZU SUPERMEDIC.", "14 finer distinctions are held as aliases rather than separate entries, because telling them apart needs a task that asks for it.", "Described in 82 Wikipedia languages, which is a measure of how widely the thing is known, not of how important it is." ], "openQuestionsForResearch": [ "Which of the bundles below does a real task actually need, and which are ceremony?", "What does this thing have that the facets do not capture at all?", "Which neighbouring kind is most often confused with a ambulance, 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": [ "mobile intensive care unit", "animal ambulance", "medical helicopter", "Ambulances in Japan", "Animal Ambulance Foundation Zwolle", "Krankentransportwagen in Germany", "military ambulance", "mobile hospital unit", "water ambulance", "air ambulance", "Mobile Intensive Care Ambulance", "ISUZU SUPERMEDIC" ] } ], "standing": "Described in 82 Wikipedia languages, which measures how widely it is written about rather than how important or how common it is. 14 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 ambulance from another, and a ambulance 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 ambulance, 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 ambulance, 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 ambulance 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 ambulance, 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 ambulance, 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 ambulance 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 ambulance 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 ambulance, 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 ambulance, 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 ambulance 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 ambulance from the things most often confused with it.", "questions": [ { "id": "distinguishing-features-q01", "text": "What identifies and describes what distinguishes a ambulance, 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 ambulance, 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 ambulance 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 ambulance 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 ambulance, 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 ambulance, 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 ambulance 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 ambulance is built from and which parts are replaceable.", "questions": [ { "id": "parts-and-materials-q01", "text": "What identifies and describes the composition of a ambulance, 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 ambulance, 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 ambulance 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 ambulance is judged and by whom.", "questions": [ { "id": "condition-assessment-q01", "text": "What identifies and describes the condition of a ambulance, 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 ambulance, 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 ambulance 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 ambulance 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 ambulance is, and what that position is measured against.", "questions": [ { "id": "position-and-frame-q01", "text": "What identifies and describes the location of a ambulance, 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 ambulance, 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 ambulance 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 ambulance 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 ambulance, 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 ambulance, 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 ambulance 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 ambulance 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 ambulance between them.", "questions": [ { "id": "stages-and-transitions-q01", "text": "What identifies and describes the lifecycle of a ambulance, 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 ambulance, 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 ambulance 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 ambulance, how often and by whom.", "findings": [ { "id": "observation-record", "name": "Observation record", "description": "How an observation of a ambulance 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 ambulance, 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 ambulance, 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 ambulance 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 ambulance 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 ambulance 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 ambulance, 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 ambulance 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 ambulance 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 ambulance 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 ambulance 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 ambulance 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 ambulance, 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 ambulance 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 ambulance and how confident it is.", "questions": [ { "id": "claim-provenance-q01", "text": "What identifies and describes a claim about a ambulance, 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 ambulance, 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 ambulance 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 ambulance is retired without being erased.", "questions": [ { "id": "validity-and-supersession-q01", "text": "What identifies and describes the validity of a claim about a ambulance, 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 ambulance, 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 ambulance 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 } } } }