{ "model": { "rank": 6618, "code": "thing-q208281", "model_id": "vr.tr.fire-engine", "name": "fire engine", "purpose": "Enable an agent to recognise a fire engine, assess its readiness for a specified firefighting task, and identify actions permitted by its equipment, condition and operating limits.", "family": "Thing Registry", "category": "Physical world and living systems", "status": "research-draft", "kind": "thing", "plane": "PHY", "domain": "PHY.OBJ", "industry": "", "version": "", "url": "/models/thing/q208281/", "tier": 2, "score": 59, "payload": { "layer": "wikidata", "aliases": [ "hand-drawn fire pumper", "turntable ladder", "LUF 30", "LUF 60", "Dennis Rapier", "Jupiter", "Platform truck", "Helitack", "fire engines in Austria", "water tender", "airport crash tender", "fire engines of the German Democratic Republic", "Airport crash tenders of the Netherlands", "Hose tenders", "rescue pumper", "Hilfeleistungslöschfahrzeug 24/14-S", "Tragkraftspritzenfahrzeug", "Löschgruppenfahrzeug", "AC-40", "fire engines in Japan", "Aerial rescue vehicles", "Fast Response Car", "Electric fire engine", "heavy rescue vehicle", "Firefighting turbine vehicles", "Alvis Salamander", "Quint", "hook and ladder truck", "steam-powered fire engine", "DOK-ING MVF-5", "large tank fire-fighting vehicle", "Ziegler Z series", "Rosenbauer Simba", "Rosenbauer Panther", "Oshkosh Striker" ], "aliasCount": 35, "merged": 36, "knownIn": 59, "facets": null, "markers": [], "lexicalClass": "", "senseRank": null, "alsoRegisteredAs": null, "source": { "dataset": "wikidata", "item": "Q208281", "url": "https://www.wikidata.org/wiki/Q208281", "license": "CC0 1.0" } }, "research": { "vercy": "1.0-draft", "publication": { "status": "research-draft", "adjudicationStatus": "unreviewed", "publishableCanonical": false, "generatedAt": "2026-09-09T23:08:56Z", "providers": [ "Codex" ], "breadth": "recalled by Codex without web access - no source was read", "missingProviders": [], "pass": 2, "cost": { "grok": { "seconds": 26.6, "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: 01a0886d-7c6b-7da0-b420-40636bdb93fa\n--------\nuser\nDescribe what is already known about one registered thing. Answer as JSON only, no prose around it.\n\nThing: fire engine\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 reg", "usd": 0, "recall": true }, "codex": { "seconds": 64.6, "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: 01a0886d-7c93-7c11-8d9c-f16c7e27925c\n--------\nuser\nYou are drafting a Vercy meta-model for one registered thing. Answer as JSON only, no prose around it.\n\nThing: fire engine\nRegistry id: vr.tr.fire-engine\nPlane / domain: PHY / PHY.OBJ\nRegistry definition: (none recorded)\nNames folded into this entry: (none)\n\n\n" } } }, "metaModel": { "id": "THING-Q208281", "registryId": "vr.tr.fire-engine", "name": "fire engine", "version": "0.1.0-research.1", "entryKind": "thing", "family": "Thing Registry", "domain": [ "PHY.OBJ" ], "status": "research-draft" }, "canonicalUrl": "https://ver.cy/models/thing/q208281/", "model": { "registry_id": "vr.tr.fire-engine", "name": "fire engine", "purpose": "Enable an agent to recognise a fire engine, assess its readiness for a specified firefighting task, and identify actions permitted by its equipment, condition and operating limits.", "definition": "A fire engine is a road vehicle equipped to carry firefighters and firefighting equipment to incidents and, in its narrower operational sense, to pump water or other extinguishing agents through hose lines.", "scope_statement": "This model owns the fire-engine kind as a mobile firefighting apparatus, including how to describe configurations and assess individual units; it provisionally treats pumping and hose-based suppression as central while leaving regional terminology and specialist variants open for research.", "in_scope": [ "Firefighting role, apparatus configuration and boundaries between engine variants", "Water supply, pump, hose and extinguishing-agent delivery capabilities", "Vehicle mobility, equipment loading and access constraints", "Pump controls, operating states and dependencies between propulsion and firefighting systems", "Inspection, replenishment, faults and task-specific readiness", "Equipment protections, operating limits and applicable conformity evidence" ], "out_of_scope": [ "Incident command, dispatch policy and firefighting tactics", "Firefighter qualifications, staffing arrangements and occupational roles", "Hydrant networks and other external water-supply infrastructure", "Detailed combustion behaviour and extinguishing-agent chemistry", "Standalone models of aerial appliances, ambulances and rescue tools", "Manufacturer product catalogues and the identity histories of individual vehicles" ], "distinguishing_features": [ "Check for an integrated firefighting water-delivery system, including pumping equipment and hose connections, rather than identifying the vehicle from colour or warning lights.", "Distinguish an engine from a water tender by its intended suppression and hose-supply role; carrying a large water tank alone does not establish engine identity.", "Distinguish an engine from a dedicated aerial appliance by its principal operational role, while recording combination apparatus explicitly.", "Distinguish an engine from a rescue or command vehicle by installed suppression capability rather than shared crew space or emergency markings.", "Separate the apparatus kind from a manufacturer's model designation and from an individual vehicle identified by a fleet number or chassis identifier." ], "characteristics": [ { "name": "Apparatus role and configuration", "kind": "category", "unit_or_values": "Locally recognised apparatus class, primary role and secondary capabilities", "why_it_matters": "Determines whether the vehicle belongs to this kind and which operational capabilities require assessment." }, { "name": "Pump performance envelope", "kind": "measurement", "unit_or_values": "Flow in L/min at specified discharge pressure in kPa, with suction conditions and test basis", "why_it_matters": "A flow figure without pressure and supply conditions cannot establish hose-supply capability." }, { "name": "Usable onboard water", "kind": "measurement", "unit_or_values": "L; distinguish usable capacity from current available quantity", "why_it_matters": "Supports estimates of initial operating duration before replenishment." }, { "name": "Water-source compatibility", "kind": "category", "unit_or_values": "Onboard tank, pressurised external supply or drafting, with supported connection specifications", "why_it_matters": "Establishes whether an available source can actually feed the apparatus." }, { "name": "Hose and outlet configuration", "kind": "measurement", "unit_or_values": "Outlet count; hose length in m; hose bore in mm; coupling designation", "why_it_matters": "Constrains compatible connections, deployment reach and delivery losses." }, { "name": "Extinguishing-agent system", "kind": "category", "unit_or_values": "Water-only or documented additional agent systems, compatible agents and proportioning range", "why_it_matters": "Prevents assuming that every engine can produce or deliver every extinguishing medium." }, { "name": "Pump power arrangement", "kind": "category", "unit_or_values": "Documented drive source and supported stationary or moving pumping modes", "why_it_matters": "Identifies propulsion dependencies and restrictions on simultaneous movement and pumping." }, { "name": "Loaded vehicle envelope", "kind": "measurement", "unit_or_values": "Length, width, height and ground clearance in m; actual and permitted mass in kg", "why_it_matters": "Supports access and load checks in the operational configuration." }, { "name": "Crew accommodation", "kind": "measurement", "unit_or_values": "Number of approved seated and restrained occupants", "why_it_matters": "Distinguishes available crew transport capacity from the staffing an incident requires." }, { "name": "Suppression readiness", "kind": "state", "unit_or_values": "Ready, restricted, unavailable or unknown, for a named task and assessment time", "why_it_matters": "Roadworthiness alone does not demonstrate firefighting readiness." }, { "name": "Applicable requirements and evidence", "kind": "relation", "unit_or_values": "Issuing body, document identifier, edition, jurisdiction, applicability and linked inspection or conformity record", "why_it_matters": "Connects a claimed operating limit or compliance status to evidence appropriate to that apparatus." } ], "affordances": [ "Check whether a configured engine can reach an incident location and use the available water source.", "Compare documented pump capability with a specified flow and pressure requirement.", "Estimate onboard-water endurance under explicit discharge and replenishment assumptions.", "Identify compatible hose, inlet and agent connections from verified specifications.", "Determine whether recorded faults or missing equipment restrict a proposed firefighting task.", "Identify required inspection, replenishment or qualified maintenance before returning the engine to service." ] }, "sources": [], "structure": { "bundles": [ { "id": "apparatus-identity", "name": "Apparatus identity and role", "description": "Establishes what counts as a fire engine and how mixed-role configurations are represented.", "rationale": "Emergency appearance and local naming conventions are insufficient to establish suppression capability.", "layers": [ { "id": "engine-boundary", "name": "Engine boundary", "description": "Tests membership using intended role and installed equipment.", "findings": [ { "id": "suppression-role", "name": "Suppression role", "description": "Record the evidence connecting the apparatus to mobile pumping and hose-based firefighting.", "questions": [ { "text": "Which installed systems and documented duties establish this apparatus as a fire engine?", "kind": "definition", "id": "suppression-role-q01" }, { "text": "Under the applicable terminology, what separates it from a water tender, rescue vehicle or aerial appliance?", "kind": "boundary", "id": "suppression-role-q02" } ] } ] }, { "id": "configuration-variants", "name": "Configuration variants", "description": "Captures specialist and combination capabilities without conflating kind, product and unit.", "findings": [ { "id": "variant-inheritance", "name": "Variant inheritance", "description": "Describe additional capabilities as configuration-specific extensions to the engine role.", "questions": [ { "text": "Which capabilities are common to the engine kind, and which depend on a specialist configuration?", "kind": "boundary", "id": "variant-inheritance-q01" }, { "text": "Which manufacturer or operator records substantiate the configuration being assessed?", "kind": "provenance", "id": "variant-inheritance-q02" } ] } ] } ] }, { "id": "water-and-agent-delivery", "name": "Water and agent delivery", "description": "Describes the supply-to-discharge chain that makes the apparatus useful for suppression.", "rationale": "Effective delivery depends jointly on water availability, pump performance, connections and fitted agent equipment.", "layers": [ { "id": "supply-and-storage", "name": "Supply and storage", "description": "Captures onboard reserves and external supply compatibility.", "findings": [ { "id": "available-water-path", "name": "Available water path", "description": "Record usable water and the conditions required to feed the pump from each supported source.", "questions": [ { "text": "How much usable water is onboard now, and how was that quantity established?", "kind": "measurement", "id": "available-water-path-q01" }, { "text": "Which inlet fittings, source conditions and auxiliary equipment are required for each supported supply mode?", "kind": "action", "id": "available-water-path-q02" } ] } ] }, { "id": "pump-and-discharge", "name": "Pump and discharge", "description": "Relates tested pump performance to the installed delivery equipment.", "findings": [ { "id": "delivery-envelope", "name": "Delivery envelope", "description": "Represent delivery as a conditional performance envelope rather than a single maximum flow.", "questions": [ { "text": "What flow and pressure combinations are documented, under which inlet and pump-speed conditions?", "kind": "measurement", "id": "delivery-envelope-q01" }, { "text": "How do the proposed hose arrangement and simultaneous outlets constrain the required delivery?", "kind": "measurement", "id": "delivery-envelope-q02" } ] }, { "id": "agent-compatibility", "name": "Agent compatibility", "description": "Record additional extinguishing-agent capability only where supported by the fitted equipment.", "questions": [ { "text": "Which agents and proportioning ranges are approved for this installed system?", "kind": "provenance", "id": "agent-compatibility-q01" }, { "text": "What documented replenishment, flushing or isolation actions apply after agent use?", "kind": "action", "id": "agent-compatibility-q02" } ] } ] } ] }, { "id": "mobility-and-deployment", "name": "Mobility and deployment", "description": "Connects vehicle access, carried load and equipment deployment to the firefighting role.", "rationale": "An engine must reach a usable position with its crew and equipment before its pump capability becomes available.", "layers": [ { "id": "loaded-access", "name": "Loaded access", "description": "Assesses the apparatus in its operational load state.", "findings": [ { "id": "route-fit", "name": "Route fit", "description": "Record physical and mobility limits relevant to the proposed approach and operating location.", "questions": [ { "text": "What are the dimensions, axle loads and total mass with the intended water, equipment and crew load?", "kind": "measurement", "id": "route-fit-q01" }, { "text": "Which documented turning, gradient, clearance and surface limits constrain access to the proposed position?", "kind": "boundary", "id": "route-fit-q02" } ] } ] }, { "id": "crew-and-equipment-deployment", "name": "Crew and equipment deployment", "description": "Captures transport capacity and practical access to firefighting equipment.", "findings": [ { "id": "deployable-load", "name": "Deployable load", "description": "Distinguish equipment carried from equipment that is secured, accessible and usable for the task.", "questions": [ { "text": "Which hose, portable ladders and other task-required equipment are present and serviceable?", "kind": "measurement", "id": "deployable-load-q01" }, { "text": "Can the crew safely access the pump panel and required equipment in the proposed parked configuration?", "kind": "action", "id": "deployable-load-q02" } ] } ] } ] }, { "id": "operating-modes-and-protections", "name": "Operating modes and protections", "description": "Describes power dependencies, controls and protections during pumping and vehicle movement.", "rationale": "Incorrect assumptions about drive engagement or permitted movement can make an otherwise capable engine unsuitable for a task.", "layers": [ { "id": "power-and-mode-transitions", "name": "Power and mode transitions", "description": "Records supported operating states and their documented prerequisites.", "findings": [ { "id": "pump-drive-dependencies", "name": "Pump drive dependencies", "description": "Connect the pump's power source to permitted propulsion and pumping combinations.", "questions": [ { "text": "What powers the pump, and which stationary or moving pumping modes are explicitly supported?", "kind": "definition", "id": "pump-drive-dependencies-q01" }, { "text": "What prerequisites and operator indications confirm a permitted transition into or out of pumping mode?", "kind": "action", "id": "pump-drive-dependencies-q02" } ] } ] }, { "id": "protective-functions", "name": "Protective functions", "description": "Captures fitted safeguards and responses to abnormal operating conditions.", "findings": [ { "id": "pressure-and-drive-protection", "name": "Pressure and drive protection", "description": "Record actual protective devices, alarms and interlocks without assuming universal fitment.", "questions": [ { "text": "Which pressure-control, temperature-monitoring and drive-interlock functions are fitted and verified operational?", "kind": "provenance", "id": "pressure-and-drive-protection-q01" }, { "text": "Which documented conditions require reduced operation, pump shutdown or withdrawal from service?", "kind": "action", "id": "pressure-and-drive-protection-q02" } ] } ] } ] }, { "id": "readiness-and-service-evidence", "name": "Readiness and service evidence", "description": "Combines condition, consumables and inspection evidence into a task-specific readiness assessment.", "rationale": "A vehicle may remain mobile while its pump, hose or supply systems are unavailable or restricted.", "layers": [ { "id": "suppression-condition", "name": "Suppression condition", "description": "Assesses faults and depleted resources across the firefighting delivery chain.", "findings": [ { "id": "capability-restrictions", "name": "Capability restrictions", "description": "Link observed defects and resource shortages to the particular capabilities they affect.", "questions": [ { "text": "What evidence shows the current condition of the pump, valves, tank, hoses and fitted agent system?", "kind": "provenance", "id": "capability-restrictions-q01" }, { "text": "Which proposed tasks remain permitted given recorded leaks, priming problems, damaged hose or depleted supplies?", "kind": "action", "id": "capability-restrictions-q02" } ] } ] }, { "id": "inspection-and-conformity", "name": "Inspection and conformity", "description": "Establishes the applicable requirements and evidence needed to support readiness.", "findings": [ { "id": "service-release-basis", "name": "Service release basis", "description": "Separate applicable design requirements, recurring inspections and current evidence of serviceability.", "questions": [ { "text": "Which issuing bodies, document editions and local requirements govern this apparatus and its intended use?", "kind": "provenance", "id": "service-release-basis-q01" }, { "text": "Which inspections, performance tests, replenishment actions or qualified repairs remain necessary before service release?", "kind": "action", "id": "service-release-basis-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 is recall, without source consultation; the unqualified name can denote either firefighting vehicles broadly or pumping apparatus specifically.", "The measurement ranges are illustrative of conventional structural pumpers, not universal limits or compliance requirements.", "Check applicable standard editions, local adoption and apparatus classification before making regulatory claims." ], "questions": [ { "id": "evidence-confidence-notes-q01", "text": "Which of these check these first hold for the sense of fire engine 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": [ "Structural firefighting pumper", "Wildland fire engine", "Airport rescue and firefighting vehicle", "Mini-pumper", "Rescue-pumper", "Combined pumping and aerial appliance" ], "questions": [ { "id": "evidence-kinds-q01", "text": "Which of these kinds and varieties hold for the sense of fire engine 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 alphanumeric identifier on many modern road vehicles", "note": "Identifies an individual chassis or vehicle, not the fire-engine category; applicability depends on jurisdiction and vehicle age." }, { "scheme": "Fire-service fleet or apparatus number", "value_or_pattern": "Locally assigned letters and numbers", "note": "Identifies an apparatus within a service; an operational designation such as Engine 1 may be reassigned to a replacement vehicle." } ], "questions": [ { "id": "evidence-identifiers-q01", "text": "Which of these identifiers and schemes hold for the sense of fire engine 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 1846 series, issued by CEN: firefighting and rescue service vehicles, including nomenclature, safety and performance requirements.", "NFPA 1901, issued by the National Fire Protection Association: a longstanding standard for automotive fire apparatus; researchers should check its consolidation into NFPA 1900 before treating it as the applicable edition." ], "questions": [ { "id": "evidence-standards-and-regulation-q01", "text": "Which of these standards and regulation hold for the sense of fire engine 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 firefighters, hose, breathing apparatus and tools to emergencies.", "Supplying pressurized water to attack hose lines from an onboard tank, hydrant or suitable open-water source.", "Supporting rural water supply through relay pumping and tanker operations.", "Applying foam solutions when equipped with compatible proportioning and delivery systems.", "Supporting rescue and other emergency operations according to installed equipment and crew training." ], "questions": [ { "id": "evidence-real-world-use-q01", "text": "Which of these real-world use hold for the sense of fire engine 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": "Rated pump flow for a conventional structural pumper", "typical_range": "Approximately 1000-2000", "unit": "US gal/min" }, { "quantity": "Onboard water capacity for a conventional structural pumper", "typical_range": "Approximately 1500-4000", "unit": "L" } ], "questions": [ { "id": "evidence-measurements-q01", "text": "Which of these typical measurements hold for the sense of fire engine 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": [ "Loss of water supply, failed priming or pump cavitation can interrupt delivery and damage the pump.", "Hose rupture, coupling separation and uncontrolled nozzle reaction can injure crews.", "High vehicle mass and elevated centre of gravity contribute to braking, collision and rollover hazards.", "Exhaust, heat, moving machinery and pressurized systems expose operators to injury.", "Freezing, corrosion, contaminated fluids and neglected maintenance can impair pumps, valves and delivery systems." ], "questions": [ { "id": "evidence-failure-modes-and-hazards-q01", "text": "Which of these failure modes and hazards hold for the sense of fire engine 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": [ "In North American operational terminology, an engine usually emphasizes pumping, while a truck often emphasizes aerial access and support equipment; everyday usage is broader.", "British services commonly use appliance and distinguish pumping appliances from aerial appliances.", "Water availability, terrain and local practice influence tank size, hose connections, vehicle dimensions and off-road capability." ], "questions": [ { "id": "evidence-regional-variation-q01", "text": "Which of these regional variation hold for the sense of fire engine 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": "Aerial ladder truck", "difference": "Its defining equipment is an elevated ladder or platform; some vehicles combine this with an engine's pumping functions." }, { "name": "Water tender", "difference": "Its principal role is transporting bulk water rather than serving as the primary attack pumper, although capabilities can overlap." }, { "name": "Rescue vehicle", "difference": "Its defining role is carrying rescue personnel and equipment; a firefighting pump and water tank are not required." }, { "name": "Fire pump", "difference": "A pump is the fluid-moving machine and may be portable or fixed; a fire engine is the equipped vehicle." } ], "questions": [ { "id": "evidence-neighbours-q01", "text": "Which of these neighbouring kinds and how to tell them apart hold for the sense of fire engine this model covers, and on what evidence?", "kind": "provenance" } ] } ] } ] } ] }, "openQuestions": [ "Does the registry intend fire engine to mean a pumping apparatus specifically or the broader regional category of firefighting vehicles?", "Does an existing Vercy world model already cover this concept and therefore provide the authoritative publication?", "Which specialist configurations, including wildland, airport and combination aerial apparatus, belong within this entry rather than neighbouring models?", "Which standards, issuing bodies, editions and conformity practices apply in the jurisdictions this model must support?", "What sourced capacity ranges, dimensions, failure patterns and inspection criteria are representative of each included configuration?" ], "statistics": { "bundles": 6, "layers": 11, "findings": 20, "questions": 31 } }, "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 fire engine, record what state it is in, and decide what may be done with it.", "whatItIs": "Enable an agent to recognise a fire engine, assess its readiness for a specified firefighting task, and identify actions permitted by its equipment, condition and operating limits.", "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: hand-drawn fire pumper, turntable ladder, LUF 30, LUF 60, Dennis Rapier, Jupiter, Platform truck, Helitack, fire engines in Austria, water tender, airport crash tender, fire engines of the German Democratic Republic.", "36 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 fire engine, 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": [ "hand-drawn fire pumper", "turntable ladder", "LUF 30", "LUF 60", "Dennis Rapier", "Jupiter", "Platform truck", "Helitack", "fire engines in Austria", "water tender", "airport crash tender", "fire engines of the German Democratic Republic" ] } ], "standing": "Described in 59 Wikipedia languages, which measures how widely it is written about rather than how important or how common it is. 36 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 fire engine from another, and a fire engine 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 fire engine, 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 fire engine, 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 fire engine 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 fire engine, 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 fire engine, 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 fire engine 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 fire engine 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 fire engine, 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 fire engine, 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 fire engine 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 fire engine from the things most often confused with it.", "questions": [ { "id": "distinguishing-features-q01", "text": "What identifies and describes what distinguishes a fire engine, 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 fire engine, 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 fire engine 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 fire engine 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 fire engine, 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 fire engine, 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 fire engine 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 fire engine is built from and which parts are replaceable.", "questions": [ { "id": "parts-and-materials-q01", "text": "What identifies and describes the composition of a fire engine, 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 fire engine, 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 fire engine 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 fire engine is judged and by whom.", "questions": [ { "id": "condition-assessment-q01", "text": "What identifies and describes the condition of a fire engine, 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 fire engine, 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 fire engine 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 fire engine 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 fire engine is, and what that position is measured against.", "questions": [ { "id": "position-and-frame-q01", "text": "What identifies and describes the location of a fire engine, 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 fire engine, 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 fire engine 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 fire engine 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 fire engine, 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 fire engine, 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 fire engine 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 fire engine 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 fire engine between them.", "questions": [ { "id": "stages-and-transitions-q01", "text": "What identifies and describes the lifecycle of a fire engine, 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 fire engine, 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 fire engine 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 fire engine, how often and by whom.", "findings": [ { "id": "observation-record", "name": "Observation record", "description": "How an observation of a fire engine 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 fire engine, 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 fire engine, 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 fire engine 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 fire engine 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 fire engine 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 fire engine, 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 fire engine 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 fire engine 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 fire engine 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 fire engine 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 fire engine 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 fire engine, 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 fire engine 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 fire engine and how confident it is.", "questions": [ { "id": "claim-provenance-q01", "text": "What identifies and describes a claim about a fire engine, 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 fire engine, 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 fire engine 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 fire engine is retired without being erased.", "questions": [ { "id": "validity-and-supersession-q01", "text": "What identifies and describes the validity of a claim about a fire engine, 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 fire engine, 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 fire engine 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 } } } }