{ "model": { "rank": 5739, "code": "thing-q155651", "model_id": "vr.tr.mil-mi-24", "name": "Mil Mi-24", "purpose": "Enable an AI agent to recognise a Mil Mi-24, assess an individual aircraft's configuration and condition, and identify evidence and authorization needed for inspection, maintenance, transport, preservation or flight.", "family": "Thing Registry", "category": "Physical world and living systems", "status": "research-draft", "kind": "thing", "plane": "PHY", "domain": "PHY.OBJ", "industry": "", "version": "", "url": "/models/thing/q155651/", "tier": 2, "score": 65, "payload": { "layer": "wikidata", "aliases": [ "Mi-24U", "Mi-24RKhR", "Mi-24K", "Mil Mi-24RA", "Mil Mi-24D", "Mil Mi-24P", "Iraqi Mil Mi-24 capured by Iran", "Mil Mi-24M", "ATE Mi-24 Super Hind", "Mi-24A", "Mi-24BMT", "Mil Mi-24V", "Mi-24PS", "Mi-25/35", "Mi-24PM", "Mi-35P", "Mi-24VP", "Mi-24VN" ], "aliasCount": 18, "merged": 19, "knownIn": 65, "facets": null, "markers": [], "lexicalClass": "", "senseRank": null, "alsoRegisteredAs": null, "source": { "dataset": "wikidata", "item": "Q155651", "url": "https://www.wikidata.org/wiki/Q155651", "license": "CC0 1.0" } }, "research": { "vercy": "1.0-draft", "publication": { "status": "research-draft", "adjudicationStatus": "unreviewed", "publishableCanonical": false, "generatedAt": "2026-09-07T09:10:43Z", "providers": [ "Codex" ], "missingProviders": [ "Grok" ], "pass": 2, "cost": { "grok": { "usd": null, "turns": null, "seconds": 9.3, "error": "Error: Internal error: {\n \"message\": \"API error (status 402 Payment Required): Grok Build usage balance exhausted\",\n \"http_status\": 402\n}", "retried": true }, "codex": { "seconds": 116.7, "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: 01a07b20-93cf-7831-b018-62e14ac0d58f\n--------\nuser\nYou are drafting a Vercy meta-model for one registered thing. Answer as JSON only, no prose around it.\n\nThing: Mil Mi-24\nRegistry id: vr.tr.mil-mi-24\nPlane / domain: PHY / PHY.OBJ\nRegistry definition: (none recorded)\nNames folded into this entry: (none)\n\nA Ver" } } }, "metaModel": { "id": "THING-Q155651", "registryId": "vr.tr.mil-mi-24", "name": "Mil Mi-24", "version": "0.1.0-research.1", "entryKind": "thing", "family": "Thing Registry", "domain": [ "PHY.OBJ" ], "status": "research-draft" }, "canonicalUrl": "https://ver.cy/models/thing/q155651/", "model": { "registry_id": "vr.tr.mil-mi-24", "name": "Mil Mi-24", "purpose": "Enable an AI agent to recognise a Mil Mi-24, assess an individual aircraft's configuration and condition, and identify evidence and authorization needed for inspection, maintenance, transport, preservation or flight.", "definition": "", "scope_statement": "This model owns the identification, installed configuration, physical condition and activity-specific constraints of aircraft assigned to vr.tr.mil-mi-24 within PHY / PHY.OBJ, distinguishing family-level expectations from evidence about an individual airframe.", "in_scope": [ "Mi-24 identity, variant attribution, serial identity and documented modifications", "Rotorcraft structure, propulsion, transmission, controls and landing gear as installed", "Crew stations, internal cabin and documented passenger or cargo configurations", "Installed avionics, protective equipment and armament interfaces at configuration and safety-status level", "Maintenance evidence, operating limitations and readiness for a specified activity", "Storage, demilitarization, restoration and display condition" ], "out_of_scope": [ "Combat tactics, targeting, weapon employment and mission execution", "Internal design and independent lifecycle of engines, weapons, ammunition and other separately modelled components", "Operator organizations, personnel qualifications and ownership law beyond links to applicable records", "Airfields, maintenance facilities, routes and airspace management", "Mi-28, Mi-8/Mi-17 and other helicopter types", "Automatic inclusion of aircraft designated Mi-25 or Mi-35 without resolving their registry relationship" ], "distinguishing_features": [ "Check the combined silhouette of a five-blade main rotor, short mid-fuselage wings and a substantial oval fuselage; no single feature establishes identity. [FM 44-80, Mi-24 recognition entry](https://www.marines.mil/Portals/1/Publications/FM%2044-80.pdf)", "Check for two engines above the fuselage, paired round intakes above the cockpit and lateral exhausts as part of the recognition signature. [FM 44-80](https://www.marines.mil/Portals/1/Publications/FM%2044-80.pdf)", "Distinguish the early Hind-A glassed-in cockpit from the Hind-D tandem bubble canopies; requiring the latter would wrongly exclude early aircraft. [FM 44-80](https://www.marines.mil/Portals/1/Publications/FM%2044-80.pdf)", "Against an armed Mi-8/Mi-17, compare the cockpit, fuselage profile and wing arrangement together: the recognition guide describes the Mi-8 as bus-like with low external fuel pods. [FM 44-80](https://www.marines.mil/Portals/1/Publications/FM%2044-80.pdf)", "Require serial-linked manufacturing or modification records to resolve a Mi-24 versus a related export designation, converted aircraft or visual replica; appearance and painted markings alone are insufficient." ], "characteristics": [ { "name": "Documented designation and variant", "kind": "category", "unit_or_values": "Recorded designation and variant; disputed; unknown", "why_it_matters": "Determines which recognition expectations, manuals and limitations apply." }, { "name": "Airframe identity", "kind": "relation", "unit_or_values": "Manufacturer serial linked to identity plate, airframe records and dated operator markings", "why_it_matters": "Separates the physical aircraft from changing registrations, markings or museum labels." }, { "name": "Cockpit and cabin configuration", "kind": "category", "unit_or_values": "Observed canopy arrangement, crew stations, cabin fittings and documented conversion", "why_it_matters": "Supports variant recognition and determines which occupancy assumptions are justified." }, { "name": "Installed propulsion and rotor configuration", "kind": "relation", "unit_or_values": "Engine, gearbox, main-rotor and tail-rotor assembly identities linked to modification records", "why_it_matters": "A family designation does not establish the equipment currently fitted." }, { "name": "Aircraft mass and balance", "kind": "measurement", "unit_or_values": "kg and centre-of-gravity position in the applicable manual's datum convention, with loading configuration", "why_it_matters": "Cabin loads, fuel and external equipment must be assessed together against aircraft-specific limits." }, { "name": "Life consumption", "kind": "measurement", "unit_or_values": "Flight hours, cycles and calendar age for the airframe and applicable life-limited assemblies", "why_it_matters": "Remaining life cannot be inferred from appearance or airframe hours alone." }, { "name": "Installed equipment serviceability", "kind": "state", "unit_or_values": "Serviceable; restricted; unserviceable; removed; unverified, per identified system", "why_it_matters": "Separates installed capability from equipment that is usable now." }, { "name": "Armament and energetic equipment status", "kind": "state", "unit_or_values": "Absent; inert with evidence; isolated with evidence; live declared; unknown", "why_it_matters": "Constrains access, maintenance, movement and public display without implying permission to employ weapons." }, { "name": "Aircraft lifecycle condition", "kind": "state", "unit_or_values": "Operating; grounded; stored; under restoration; static display; incomplete; wreck", "why_it_matters": "Distinguishes preservation or assembly completeness from readiness to fly." }, { "name": "Activity authorization", "kind": "relation", "unit_or_values": "Dated release or restriction linked to aircraft, configuration, activity and responsible authority", "why_it_matters": "Authorization for towing, maintenance or display does not establish authorization for flight." } ], "affordances": [ "Identify and catalogue an aircraft using visual evidence and serial-linked documentation.", "Compare its installed configuration with the applicable Mi-24 variant and modification records.", "Assess whether documented condition supports inspection, maintenance, towing, shipment or preservation.", "Identify missing evidence or restrictions that prevent an activity-specific readiness decision.", "Record cabin configuration and evaluate documented loading compatibility.", "Track restoration or demilitarization changes while preserving identity and configuration history." ] }, "sources": [], "structure": { "bundles": [ { "id": "mi-24-identity-and-boundaries", "name": "Mi-24 identity and boundaries", "description": "Establish what aircraft is represented and which Mi-24 knowledge applies to it.", "rationale": "Family resemblance, variant changes and related export designations can produce incorrect identification and duplicate models.", "layers": [ { "id": "designation-and-registry-membership", "name": "Designation and registry membership", "description": "Resolve the aircraft's designation without expanding the registry entry by assumption.", "findings": [ { "id": "documented-mi-24-membership", "name": "Documented Mi-24 membership", "description": "Record the evidence linking the airframe to this entry and separate variant labels from neighbouring designations.", "questions": [ { "text": "Which manufacturing or service document identifies this aircraft as a Mi-24 and specifies its variant?", "kind": "provenance", "id": "documented-mi-24-membership-q01" }, { "text": "Does an existing registry or world model own any related Mi-25 or Mi-35 designation appearing in its records?", "kind": "boundary", "id": "documented-mi-24-membership-q02" } ] } ] }, { "id": "airframe-and-visual-identity", "name": "Airframe and visual identity", "description": "Reconcile serial identity with the observed cockpit, fuselage, wings and rotor configuration.", "findings": [ { "id": "identity-evidence-agreement", "name": "Identity evidence agreement", "description": "Distinguish an identified Mi-24 from an uncertain sighting, altered display aircraft or replica.", "questions": [ { "text": "Do the serial plate, airframe records and dated photographs refer to the same physical aircraft?", "kind": "provenance", "id": "identity-evidence-agreement-q01" }, { "text": "Which observed cockpit, wing and rotor features agree with the claimed variant, and which need explanation?", "kind": "definition", "id": "identity-evidence-agreement-q02" } ] } ] } ] }, { "id": "mi-24-airframe-and-flight-systems", "name": "Mi-24 airframe and flight systems", "description": "Represent the installed mechanical configuration and condition of the helicopter.", "rationale": "Mi-24 identity alone cannot establish compatibility or serviceability of its engines, rotor assemblies, transmission and landing gear.", "layers": [ { "id": "propulsion-and-rotor-train", "name": "Propulsion and rotor train", "description": "Link the engines and power-transmission assemblies to their installed configuration and condition evidence.", "findings": [ { "id": "installed-dynamic-assemblies", "name": "Installed dynamic assemblies", "description": "Record assembly identities, compatibility evidence and restrictions without treating nominal variant equipment as observed fact.", "questions": [ { "text": "Which engines, gearboxes and main- and tail-rotor assemblies are actually installed?", "kind": "definition", "id": "installed-dynamic-assemblies-q01" }, { "text": "Which configuration records establish that these assemblies are approved together on this airframe?", "kind": "provenance", "id": "installed-dynamic-assemblies-q02" }, { "text": "What recorded defects or restrictions affect these assemblies?", "kind": "measurement", "id": "installed-dynamic-assemblies-q03" } ] } ] }, { "id": "structure-controls-and-ground-support", "name": "Structure, controls and ground support", "description": "Assess the fuselage, wing attachments, flight-control systems and installed landing gear.", "findings": [ { "id": "structural-and-control-condition", "name": "Structural and control condition", "description": "Associate damage, repairs and configuration changes with the affected Mi-24 structural or control assembly.", "questions": [ { "text": "What inspections establish the condition of the fuselage, tail boom, wing attachments and control systems?", "kind": "provenance", "id": "structural-and-control-condition-q01" }, { "text": "What landing-gear configuration is fitted, and what documented defects limit ground handling or flight?", "kind": "action", "id": "structural-and-control-condition-q02" } ] } ] } ] }, { "id": "mi-24-cockpit-cabin-and-loading", "name": "Mi-24 cockpit, cabin and loading", "description": "Represent crew accommodation and the internal cabin as parts of one loading configuration.", "rationale": "The model must account for the Mi-24's cockpit and cabin together rather than assuming the accommodation of a cockpit-only attack helicopter.", "layers": [ { "id": "crew-and-cabin-accommodation", "name": "Crew and cabin accommodation", "description": "Identify actual stations, seating, restraints, access and conversions.", "findings": [ { "id": "documented-occupancy-configuration", "name": "Documented occupancy configuration", "description": "Determine the occupancy supported by installed fittings and applicable documentation.", "questions": [ { "text": "Which crew stations and passenger, cargo or medical fittings are installed in this aircraft?", "kind": "definition", "id": "documented-occupancy-configuration-q01" }, { "text": "Which applicable document establishes permitted occupancy and access or egress requirements for that configuration?", "kind": "provenance", "id": "documented-occupancy-configuration-q02" } ] } ] }, { "id": "combined-loading-state", "name": "Combined loading state", "description": "Evaluate cabin contents, fuel and external equipment against a common mass-and-balance basis.", "findings": [ { "id": "configuration-specific-loading-envelope", "name": "Configuration-specific loading envelope", "description": "Keep measured loading separate from catalogue payload figures and unverified capacity claims.", "questions": [ { "text": "What current empty-mass and balance record includes the aircraft's installed modifications?", "kind": "measurement", "id": "configuration-specific-loading-envelope-q01" }, { "text": "Do the recorded occupants, cargo, fuel and external equipment remain within the applicable loading limits?", "kind": "boundary", "id": "configuration-specific-loading-envelope-q02" }, { "text": "Which missing load or configuration measurements prevent a loading decision?", "kind": "action", "id": "configuration-specific-loading-envelope-q03" } ] } ] } ] }, { "id": "mi-24-avionics-and-external-equipment", "name": "Mi-24 avionics and external equipment", "description": "Describe variant-sensitive equipment and its installed, serviceable and hazardous states.", "rationale": "Mi-24 upgrades and equipment changes make designation-based capability assumptions unreliable.", "layers": [ { "id": "avionics-and-protective-fit", "name": "Avionics and protective fit", "description": "Identify navigation, communication, sensor and protective installations without inferring capability from appearance.", "findings": [ { "id": "verified-equipment-capability", "name": "Verified equipment capability", "description": "Associate claimed functions with identifiable equipment, integration records and serviceability evidence.", "questions": [ { "text": "Which avionics, sensors and protective systems are fitted, removed or replaced by an upgrade?", "kind": "definition", "id": "verified-equipment-capability-q01" }, { "text": "What integration and serviceability evidence supports each claimed function on this aircraft?", "kind": "provenance", "id": "verified-equipment-capability-q02" } ] } ] }, { "id": "armament-fit-and-safe-access", "name": "Armament fit and safe access", "description": "Record gun installations, external stations and energetic equipment only as configuration and handling constraints.", "findings": [ { "id": "installed-armament-and-isolation-status", "name": "Installed armament and isolation status", "description": "Distinguish empty mounts, display substitutes, installed weapons and unresolved energetic hazards.", "questions": [ { "text": "Which gun installation, external stores and energetic devices are present, and which are documented as inert or absent?", "kind": "definition", "id": "installed-armament-and-isolation-status-q01" }, { "text": "Who verified the recorded safety status, when, and for which access or maintenance activity?", "kind": "provenance", "id": "installed-armament-and-isolation-status-q02" }, { "text": "Which unresolved equipment states require specialist clearance before the proposed activity?", "kind": "action", "id": "installed-armament-and-isolation-status-q03" } ] } ] } ] }, { "id": "mi-24-life-history-and-activity-readiness", "name": "Mi-24 life history and activity readiness", "description": "Combine maintenance history, lifecycle condition and applicable releases into a bounded decision.", "rationale": "A complete-looking Mi-24 may be grounded, time-expired or preserved for display, and each intended activity requires different evidence.", "layers": [ { "id": "life-limits-and-maintenance-continuity", "name": "Life limits and maintenance continuity", "description": "Establish traceable life consumption and maintenance status for the airframe and installed assemblies.", "findings": [ { "id": "traceable-maintenance-basis", "name": "Traceable maintenance basis", "description": "Identify applicable maintenance requirements, remaining life and gaps in records.", "questions": [ { "text": "What hours, cycles and calendar limits apply to this airframe and its installed life-limited assemblies?", "kind": "measurement", "id": "traceable-maintenance-basis-q01" }, { "text": "Which records substantiate inspections, overhauls, replacements and any authorized life extensions?", "kind": "provenance", "id": "traceable-maintenance-basis-q02" }, { "text": "Which missing records or overdue tasks prevent a serviceability determination?", "kind": "boundary", "id": "traceable-maintenance-basis-q03" } ] } ] }, { "id": "operating-storage-and-display-state", "name": "Operating, storage and display state", "description": "Distinguish flight readiness from suitability for ground movement, restoration or public display.", "findings": [ { "id": "activity-specific-release", "name": "Activity-specific release", "description": "Record a decision for a named activity, configuration and date, including unresolved restrictions.", "questions": [ { "text": "Which storage, cannibalization, demilitarization or restoration changes affect the aircraft's present condition?", "kind": "provenance", "id": "activity-specific-release-q01" }, { "text": "What current release and applicable limitations support the proposed flight, towing, shipment, maintenance or display activity?", "kind": "action", "id": "activity-specific-release-q02" }, { "text": "What condition or configuration change would invalidate that decision?", "kind": "boundary", "id": "activity-specific-release-q03" } ] } ] } ] } ] }, "openQuestions": [ "Does an existing Vercy world model already own the Mi-24 concept, and how does the registry delimit Mi-24, Mi-25 and Mi-35 designations?", "Which authoritative variant and modification references establish recognition features without treating one Mi-24 configuration as universal?", "Which applicable flight and maintenance manuals establish occupancy, loading limits and installed-system compatibility for the variants represented?", "How should incomplete serial, component-life and overhaul records constrain confidence in identity and activity readiness?", "What evidence distinguishes a reversible equipment removal from permanent demilitarization or a restoration that changes the aircraft's applicable approvals?" ], "statistics": { "bundles": 5, "layers": 10, "findings": 10, "questions": 25 } }, "draft": { "generator": "vr.draft.v3", "status": "draft-generated", "researched": false, "archetype": "unclassified", "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 Mil Mi-24, record what state it is in, and decide what may be done with it.", "whatItIs": "Enable an AI agent to recognise a Mil Mi-24, assess an individual aircraft's configuration and condition, and identify evidence and authorization needed for inspection, maintenance, transport, preservation or flight.", "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: Mi-24U, Mi-24RKhR, Mi-24K, Mil Mi-24RA, Mil Mi-24D, Mil Mi-24P, Iraqi Mil Mi-24 capured by Iran, Mil Mi-24M, ATE Mi-24 Super Hind, Mi-24A, Mi-24BMT, Mil Mi-24V.", "19 finer distinctions are held as aliases rather than separate entries, because telling them apart needs a task that asks for it.", "Described in 65 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 Mil Mi-24, 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 and material. The registry holds no appearance data, so what a Mil Mi-24 looks like has to come from research." ], "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": [ "Mi-24U", "Mi-24RKhR", "Mi-24K", "Mil Mi-24RA", "Mil Mi-24D", "Mil Mi-24P", "Iraqi Mil Mi-24 capured by Iran", "Mil Mi-24M", "ATE Mi-24 Super Hind", "Mi-24A", "Mi-24BMT", "Mil Mi-24V" ] } ], "standing": "Described in 65 Wikipedia languages, which measures how widely it is written about rather than how important or how common it is. 19 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 Mil Mi-24 from another, and a Mil Mi-24 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 Mil Mi-24, 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 Mil Mi-24, 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 Mil Mi-24 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 Mil Mi-24, 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 Mil Mi-24, 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 Mil Mi-24 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 Mil Mi-24 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 Mil Mi-24, 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 Mil Mi-24, 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 Mil Mi-24 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 Mil Mi-24 from the things most often confused with it.", "questions": [ { "id": "distinguishing-features-q01", "text": "What identifies and describes what distinguishes a Mil Mi-24, 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 Mil Mi-24, 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 Mil Mi-24 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 Mil Mi-24 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 Mil Mi-24, 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 Mil Mi-24, 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 Mil Mi-24 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 Mil Mi-24 is built from and which parts are replaceable.", "questions": [ { "id": "parts-and-materials-q01", "text": "What identifies and describes the composition of a Mil Mi-24, 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 Mil Mi-24, 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 Mil Mi-24 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 Mil Mi-24 is judged and by whom.", "questions": [ { "id": "condition-assessment-q01", "text": "What identifies and describes the condition of a Mil Mi-24, 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 Mil Mi-24, 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 Mil Mi-24 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 Mil Mi-24 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 Mil Mi-24 is, and what that position is measured against.", "questions": [ { "id": "position-and-frame-q01", "text": "What identifies and describes the location of a Mil Mi-24, 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 Mil Mi-24, 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 Mil Mi-24 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 Mil Mi-24 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 Mil Mi-24, 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 Mil Mi-24, 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 Mil Mi-24 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 Mil Mi-24 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 Mil Mi-24 between them.", "questions": [ { "id": "stages-and-transitions-q01", "text": "What identifies and describes the lifecycle of a Mil Mi-24, 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 Mil Mi-24, 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 Mil Mi-24 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 Mil Mi-24, how often and by whom.", "findings": [ { "id": "observation-record", "name": "Observation record", "description": "How an observation of a Mil Mi-24 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 Mil Mi-24, 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 Mil Mi-24, 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 Mil Mi-24 is known, and what must it refuse?", "kind": "action", "answer_data": [ "permitted actions", "preconditions", "refusals", "escalation" ] } ] } ] } ] }, { "id": "use-and-operation", "name": "Use and operation", "description": "What can be done with a Mil Mi-24 and what it takes to do it.", "rationale": "An agent that can recognise a thing but not act on it has only half a model.", "layers": [ { "id": "intended-use", "name": "Intended use and function", "description": "What a Mil Mi-24 is for, and what it is used for anyway.", "findings": [ { "id": "function-and-purpose", "name": "Function, purpose and misuse", "description": "The function a Mil Mi-24 performs and the uses that fall outside it.", "questions": [ { "id": "function-and-purpose-q01", "text": "What identifies and describes the use of a Mil Mi-24, and in what units or vocabulary?", "kind": "definition", "answer_data": [ "identifiers", "types and classes", "values with units", "explicit unknowns" ] }, { "id": "function-and-purpose-q02", "text": "Who or what asserted this about the use of a Mil Mi-24, by which method, and when was it true?", "kind": "provenance", "answer_data": [ "authority", "method", "evidence", "event time", "knowledge time" ] }, { "id": "function-and-purpose-q03", "text": "What may an agent decide or do once the use of a Mil Mi-24 is known, and what must it refuse?", "kind": "action", "answer_data": [ "permitted actions", "preconditions", "refusals", "escalation" ] } ] } ] }, { "id": "handling-and-procedure", "name": "Handling and procedure", "description": "The steps, skills and tools involved in using a Mil Mi-24.", "findings": [ { "id": "procedures-and-skills", "name": "Procedures, skills and required tools", "description": "What an agent needs before it can act on a Mil Mi-24 at all.", "questions": [ { "id": "procedures-and-skills-q01", "text": "What identifies and describes handling a Mil Mi-24, and in what units or vocabulary?", "kind": "definition", "answer_data": [ "identifiers", "types and classes", "values with units", "explicit unknowns" ] }, { "id": "procedures-and-skills-q02", "text": "Who or what asserted this about handling a Mil Mi-24, by which method, and when was it true?", "kind": "provenance", "answer_data": [ "authority", "method", "evidence", "event time", "knowledge time" ] }, { "id": "procedures-and-skills-q03", "text": "What may an agent decide or do once handling a Mil Mi-24 is known, and what must it refuse?", "kind": "action", "answer_data": [ "permitted actions", "preconditions", "refusals", "escalation" ] } ] } ] } ] }, { "id": "provenance-and-evidence", "name": "Provenance, evidence and time", "description": "Where every claim about a Mil Mi-24 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 Mil Mi-24 and how confident it is.", "questions": [ { "id": "claim-provenance-q01", "text": "What identifies and describes a claim about a Mil Mi-24, 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 Mil Mi-24, 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 Mil Mi-24 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 Mil Mi-24 is retired without being erased.", "questions": [ { "id": "validity-and-supersession-q01", "text": "What identifies and describes the validity of a claim about a Mil Mi-24, 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 Mil Mi-24, 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 Mil Mi-24 is known, and what must it refuse?", "kind": "action", "answer_data": [ "permitted actions", "preconditions", "refusals", "escalation" ] } ] } ] } ] } ] }, "statistics": { "bundles": 6, "layers": 13, "findings": 15, "questions": 45 } } } }