{ "model": { "rank": 5185, "code": "thing-q171468", "model_id": "vr.tr.hughes-ah-64-apache", "name": "Hughes AH-64 Apache", "purpose": "Enable an AI agent to recognise the AH-64 Apache aircraft family registered under the Hughes name, assess evidence about a particular configuration or airframe, and identify permitted inspection, maintenance and operation.", "family": "Thing Registry", "category": "Physical world and living systems", "status": "research-draft", "kind": "thing", "plane": "PHY", "domain": "PHY.OBJ", "industry": "", "version": "", "url": "/models/thing/q171468/", "tier": 2, "score": 69, "payload": { "layer": "wikidata", "aliases": [ "AH-64E", "Apache AH1" ], "aliasCount": 2, "merged": 2, "knownIn": 69, "facets": null, "markers": [], "lexicalClass": "", "senseRank": null, "alsoRegisteredAs": null, "source": { "dataset": "wikidata", "item": "Q171468", "url": "https://www.wikidata.org/wiki/Q171468", "license": "CC0 1.0" } }, "research": { "vercy": "1.0-draft", "publication": { "status": "research-draft", "adjudicationStatus": "unreviewed", "publishableCanonical": false, "generatedAt": "2026-09-09T21:51:08Z", "providers": [ "Codex" ], "breadth": "recalled by Codex without web access - no source was read", "missingProviders": [], "pass": 2, "cost": { "grok": { "seconds": 21.3, "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: 01a08826-4653-7181-b7d8-6958b3ca8306\n--------\nuser\nDescribe what is already known about one registered thing. Answer as JSON only, no prose around it.\n\nThing: Hughes AH-64 Apache\nSense to describe: (none recorded)\nDomain code: PHY.OBJ\nAlso known as: (none)\n\n\nContext for this batch of 1001 things:\n# Batch 005: ", "usd": 0, "recall": true }, "codex": { "seconds": 63.9, "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: 01a08826-4649-79d2-8787-c23c24121c0e\n--------\nuser\nYou are drafting a Vercy meta-model for one registered thing. Answer as JSON only, no prose around it.\n\nThing: Hughes AH-64 Apache\nRegistry id: vr.tr.hughes-ah-64-apache\nPlane / domain: PHY / PHY.OBJ\nRegistry definition: (none recorded)\nNames folded into this " } } }, "metaModel": { "id": "THING-Q171468", "registryId": "vr.tr.hughes-ah-64-apache", "name": "Hughes AH-64 Apache", "version": "0.1.0-research.1", "entryKind": "thing", "family": "Thing Registry", "domain": [ "PHY.OBJ" ], "status": "research-draft" }, "canonicalUrl": "https://ver.cy/models/thing/q171468/", "model": { "registry_id": "vr.tr.hughes-ah-64-apache", "name": "Hughes AH-64 Apache", "purpose": "Enable an AI agent to recognise the AH-64 Apache aircraft family registered under the Hughes name, assess evidence about a particular configuration or airframe, and identify permitted inspection, maintenance and operation.", "definition": "The Hughes AH-64 Apache is a US-developed family of twin-turboshaft, tandem-seat attack helicopters, originally developed by Hughes Helicopters and subsequently produced by McDonnell Douglas and Boeing, designed for armed reconnaissance and attacks on ground targets.", "scope_statement": "This model owns the identifying features and assessment requirements of the AH-64 Apache family, distinguishing its historical Hughes designation, subsequent manufacturer lineage, variants and individual aircraft without treating them as interchangeable.", "in_scope": [ "Apache family identity, manufacturer lineage and variant boundaries", "Characteristic airframe, propulsion, rotor and tandem-crew configuration", "Variant-dependent flight controls, sensors, avionics and installed equipment", "Evidence needed to assess aircraft condition, maintenance status and operating restrictions", "Relationships between approved configurations, applicable technical publications and operating authority" ], "out_of_scope": [ "Attack helicopters as a general aircraft category", "Hughes, McDonnell Douglas and Boeing as corporate organisations", "Detailed models of engines, weapons, ammunition and sensors as separately registered things", "Combat tactics, target selection and weapon-employment procedures", "Individual airframe histories as independent catalogue definitions", "Military units, procurement programmes and historical campaigns" ], "distinguishing_features": [ "Identification evidence places the aircraft within the AH-64 Apache lineage; an attack-helicopter role or visual resemblance alone is insufficient.", "The characteristic arrangement combines tandem crew stations, twin engines, a four-bladed main rotor, a tail rotor and short equipment-carrying wings.", "The nose-mounted sensor installation and under-fuselage gun installation help distinguish the Apache from helicopters with broadly similar tandem seating.", "A mast-mounted radar installation is configuration-dependent and must not be required to identify every Apache.", "Manufacturer name alone does not separate Hughes-origin Apaches from later aircraft in the same lineage; variant and production evidence must establish the relationship." ], "characteristics": [ { "name": "Family and variant designation", "kind": "category", "unit_or_values": "AH-64 designation, variant, modification standard and evidence source", "why_it_matters": "Determines which capabilities, limits and technical publications may apply." }, { "name": "Manufacturer lineage", "kind": "relation", "unit_or_values": "Original manufacturer, subsequent programme holder and supporting record", "why_it_matters": "Resolves the historical Hughes name without creating duplicate family models." }, { "name": "Airframe identity", "kind": "relation", "unit_or_values": "Manufacturer serial number, operator identifier and configuration record", "why_it_matters": "Connects family-level expectations to evidence about a particular aircraft." }, { "name": "Crew arrangement", "kind": "category", "unit_or_values": "Tandem crew stations; documented station roles and installed controls", "why_it_matters": "Supports recognition and determines which crew responsibilities require verification." }, { "name": "Dimensions", "kind": "measurement", "unit_or_values": "m; fuselage length, overall length, rotor diameter and height with measurement configuration", "why_it_matters": "Supports clearance and handling decisions without confusing rotor-inclusive and fuselage dimensions." }, { "name": "Mass and balance", "kind": "measurement", "unit_or_values": "kg and approved centre-of-gravity units; loading condition and configuration required", "why_it_matters": "An aircraft's allowable use depends on its actual loading and approved envelope." }, { "name": "Powerplant configuration", "kind": "relation", "unit_or_values": "Installed engine models, ratings with conditions, and drivetrain compatibility", "why_it_matters": "Prevents transferring performance assumptions across different Apache configurations." }, { "name": "Sensor and avionics configuration", "kind": "category", "unit_or_values": "Installed equipment identities, software standard and modification status", "why_it_matters": "Radar, sighting, navigation and communication capabilities cannot be inferred from the family name." }, { "name": "Technical condition", "kind": "state", "unit_or_values": "Serviceable, restricted, unserviceable or undetermined, with date and evidence", "why_it_matters": "Separates observed condition from an unsupported claim of readiness." }, { "name": "Life-limited component usage", "kind": "measurement", "unit_or_values": "Flight hours, cycles, calendar age or component-specific usage metric", "why_it_matters": "Remaining permitted life depends on the component and its applicable maintenance rules." }, { "name": "Operating authority", "kind": "relation", "unit_or_values": "Operator, responsible airworthiness authority, applicable approval and restrictions", "why_it_matters": "Technical capability alone does not establish permission to fly or maintain the aircraft." } ], "affordances": [ "Classify an evidenced aircraft or reference as belonging to the Apache family and identify unresolved variant ambiguity.", "Compare documented installed equipment with the approved configuration for that airframe.", "Identify applicable technical publications and route maintenance questions to authorised personnel.", "Assess whether condition records support serviceability, restricted use or a need for further inspection.", "Check documented dimensions and loading limits for proposed storage, transport or ground handling.", "Explain which claimed capabilities remain unsupported because configuration or approval evidence is missing." ] }, "sources": [], "structure": { "bundles": [ { "id": "apache-identity-and-lineage", "name": "Apache identity and lineage", "description": "Establishes what the Hughes AH-64 registry name denotes and how variants and airframes relate to it.", "rationale": "Historical manufacturer names and later Apache designations can otherwise produce duplicate models or incorrect capability inheritance.", "layers": [ { "id": "registry-boundary", "name": "Registry boundary", "description": "Defines the aircraft family represented by this entry.", "findings": [ { "id": "hughes-name-and-family-continuity", "name": "Hughes name and family continuity", "description": "Record whether Hughes is a historical naming anchor for the family or an explicitly restricted production scope.", "questions": [ { "text": "Does the registry intend the complete AH-64 Apache family or only aircraft produced under Hughes?", "kind": "boundary", "id": "hughes-name-and-family-continuity-q01" }, { "text": "Which authoritative designation or programme records establish continuity across manufacturer changes?", "kind": "provenance", "id": "hughes-name-and-family-continuity-q02" } ] } ] }, { "id": "variant-and-airframe-resolution", "name": "Variant and airframe resolution", "description": "Separates family identity from production and modification configurations.", "findings": [ { "id": "configuration-evidence", "name": "Configuration evidence", "description": "Identify variants through records and installed configuration rather than appearance or operator labels alone.", "questions": [ { "text": "Which designation, serial record and modification history establish this aircraft's Apache variant?", "kind": "provenance", "id": "configuration-evidence-q01" }, { "text": "Which attributes belong to the family, and which require a variant or individual-airframe qualification?", "kind": "boundary", "id": "configuration-evidence-q02" } ] } ] } ] }, { "id": "rotorcraft-and-flight-envelope", "name": "Rotorcraft and flight envelope", "description": "Covers the Apache's airframe arrangement, propulsion dependencies and configuration-specific operating limits.", "rationale": "Recognition and physical-use decisions require more than the generic label of attack helicopter.", "layers": [ { "id": "airframe-and-propulsion", "name": "Airframe and propulsion", "description": "Connects the characteristic aircraft layout to its installed engines and dynamic components.", "findings": [ { "id": "apache-physical-configuration", "name": "Apache physical configuration", "description": "Record tandem cockpit, rotor arrangement, twin-engine installation and equipment-carrying wings alongside variant-specific dimensions.", "questions": [ { "text": "Which documented physical features distinguish this Apache configuration from another tandem-seat attack helicopter?", "kind": "definition", "id": "apache-physical-configuration-q01" }, { "text": "What are its rotor diameter, overall length and height, and under which rotor and equipment configuration were they measured?", "kind": "measurement", "id": "apache-physical-configuration-q02" } ] } ] }, { "id": "loading-and-performance-limits", "name": "Loading and performance limits", "description": "Treats performance as conditional on aircraft configuration, loading and environment.", "findings": [ { "id": "applicable-flight-envelope", "name": "Applicable flight envelope", "description": "Associate mass, balance and performance limits with the approved Apache variant documentation.", "questions": [ { "text": "Which approved limits apply to this engine, rotor, equipment and loading configuration?", "kind": "provenance", "id": "applicable-flight-envelope-q01" }, { "text": "What mass, centre of gravity and environmental conditions qualify a quoted performance value?", "kind": "measurement", "id": "applicable-flight-envelope-q02" } ] } ] } ] }, { "id": "crew-and-mission-equipment", "name": "Crew and mission equipment", "description": "Describes how Apache crew stations and installed avionics affect available functions and restrictions.", "rationale": "Apache variants can look similar while differing materially in sensors, interfaces and system integration.", "layers": [ { "id": "crew-stations-and-controls", "name": "Crew stations and controls", "description": "Identifies station roles, interfaces and configuration-dependent control availability.", "findings": [ { "id": "station-function-allocation", "name": "Station function allocation", "description": "Record documented responsibilities and controls for the tandem crew stations without assuming identical interfaces across variants.", "questions": [ { "text": "Which flight and mission-system functions are available at each station in this configuration?", "kind": "definition", "id": "station-function-allocation-q01" }, { "text": "Which crew qualification and equipment-status requirements constrain authorised operation?", "kind": "action", "id": "station-function-allocation-q02" } ] } ] }, { "id": "installed-sensors-and-avionics", "name": "Installed sensors and avionics", "description": "Distinguishes fitted equipment from capabilities merely associated with the Apache family.", "findings": [ { "id": "sensor-fit-and-integration", "name": "Sensor fit and integration", "description": "Record nose sensors, any mast-mounted radar, navigation and communications equipment, and their integration status.", "questions": [ { "text": "Which sensor and avionics systems are actually installed, including the presence or absence of mast-mounted radar?", "kind": "provenance", "id": "sensor-fit-and-integration-q01" }, { "text": "Which configuration and software records substantiate the claimed system functions?", "kind": "provenance", "id": "sensor-fit-and-integration-q02" }, { "text": "Which equipment details belong in linked subsystem models rather than this aircraft-family model?", "kind": "boundary", "id": "sensor-fit-and-integration-q03" } ] } ] } ] }, { "id": "apache-condition-and-sustainment", "name": "Apache condition and sustainment", "description": "Connects airframe condition, component usage and maintenance evidence to serviceability.", "rationale": "An identifiable Apache may still have unresolved rotor, drivetrain, structural or equipment conditions that restrict its use.", "layers": [ { "id": "dynamic-components-and-structure", "name": "Dynamic components and structure", "description": "Tracks evidence affecting rotor systems, drivetrain, engines and structural condition.", "findings": [ { "id": "usage-and-inspection-status", "name": "Usage and inspection status", "description": "Associate component identities and usage histories with applicable inspections and life limits.", "questions": [ { "text": "Which installed Apache components have mandatory life limits or usage-dependent inspection requirements?", "kind": "provenance", "id": "usage-and-inspection-status-q01" }, { "text": "What verified usage and inspection records establish their remaining permitted service?", "kind": "measurement", "id": "usage-and-inspection-status-q02" } ] } ] }, { "id": "maintenance-and-restoration", "name": "Maintenance and restoration", "description": "Determines whether discrepancies have been resolved under applicable maintenance instructions.", "findings": [ { "id": "documented-serviceability", "name": "Documented serviceability", "description": "Separate reported symptoms, inspection findings, corrective work and authorised release.", "questions": [ { "text": "Which unresolved discrepancies affect this Apache's flight systems or installed mission equipment?", "kind": "provenance", "id": "documented-serviceability-q01" }, { "text": "Which current technical instructions govern required servicing, consumables and corrective work for this configuration?", "kind": "provenance", "id": "documented-serviceability-q02" }, { "text": "What authorised inspection or release is needed before the proposed use can proceed?", "kind": "action", "id": "documented-serviceability-q03" } ] } ] } ] }, { "id": "authority-and-safe-handling", "name": "Authority and safe handling", "description": "Records the approvals and aircraft-specific conditions governing operation and ground activity.", "rationale": "Military aircraft approval and safe handling depend on operator authority, configuration and equipment state.", "layers": [ { "id": "applicable-airworthiness-basis", "name": "Applicable airworthiness basis", "description": "Identifies the authority and controlled documents applicable to an Apache airframe.", "findings": [ { "id": "approval-and-document-applicability", "name": "Approval and document applicability", "description": "Record the relevant military or other operating approval without presuming a universal civil certification basis.", "questions": [ { "text": "Which authority approves this Apache's operation, and which airworthiness requirements does it apply?", "kind": "provenance", "id": "approval-and-document-applicability-q01" }, { "text": "How are technical-publication revisions and modification applicability verified for this airframe?", "kind": "action", "id": "approval-and-document-applicability-q02" } ] } ] }, { "id": "ground-and-equipment-state", "name": "Ground and equipment state", "description": "Captures conditions needed to assess access, storage, transport and maintenance readiness.", "findings": [ { "id": "handling-readiness", "name": "Handling readiness", "description": "Record rotor and engine state, electrical and hydraulic energy status, and authorised confirmation of hazardous-equipment safety.", "questions": [ { "text": "Which documented Apache-specific clearances, support equipment and configuration conditions apply to the proposed ground activity?", "kind": "action", "id": "handling-readiness-q01" }, { "text": "What authorised evidence establishes that installed weapons and other hazardous equipment are safe for that activity?", "kind": "provenance", "id": "handling-readiness-q02" } ] } ] } ] }, { "id": "evidence-and-external-alignment", "name": "Evidence and external alignment", "description": "What the world already says about this thing, gathered so the model can be checked against it.", "rationale": "A model that cannot be lined up against existing standards, identifiers and practice cannot be adopted by anyone who already uses them.", "layers": [ { "id": "reported-evidence", "name": "Reported evidence", "description": "Findings from the breadth pass, kept separate from the structural claims.", "findings": [ { "id": "evidence-confidence-notes", "name": "Check these first", "description": "Recalled without web access and unsourced; every item is a lead to verify.", "evidence": [ "This entry interprets the historical Hughes name as referring to the AH-64 family, rather than only aircraft manufactured while Hughes owned the programme.", "Recalled information only; no sources were consulted. Performance, dimensions and equipment should be checked against a specified variant and configuration.", "Applicable military airworthiness requirements depend on the operating authority and modification state; no universal certification standard is asserted." ], "questions": [ { "id": "evidence-confidence-notes-q01", "text": "Which of these check these first hold for the sense of Hughes AH-64 Apache 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": [ "AH-64A Apache", "AH-64D Apache Longbow", "AH-64E Apache Guardian", "Apache AH Mk 1, a UK derivative of the AH-64D" ], "questions": [ { "id": "evidence-kinds-q01", "text": "Which of these kinds and varieties hold for the sense of Hughes AH-64 Apache 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": "US military Mission Design Series designation", "value_or_pattern": "AH-64A; AH-64D; AH-64E", "note": "These identify aircraft variants, not individual airframes; AH denotes an attack helicopter." } ], "questions": [ { "id": "evidence-identifiers-q01", "text": "Which of these identifiers and schemes hold for the sense of Hughes AH-64 Apache 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": [ "Attacking armoured vehicles and other ground targets", "Armed reconnaissance", "Providing close combat support to ground forces", "Escorting helicopters and ground movements" ], "questions": [ { "id": "evidence-real-world-use-q01", "text": "Which of these real-world use hold for the sense of Hughes AH-64 Apache 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": "Crew complement", "typical_range": "2", "unit": "people" }, { "quantity": "Main rotor diameter", "typical_range": "approximately 14.6", "unit": "m" }, { "quantity": "Number of turboshaft engines", "typical_range": "2", "unit": "engines" }, { "quantity": "Installed M230 chain gun calibre", "typical_range": "30", "unit": "mm" } ], "questions": [ { "id": "evidence-measurements-q01", "text": "Which of these typical measurements hold for the sense of Hughes AH-64 Apache 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": [ "Rotor or transmission damage can compromise lift and aircraft control.", "Engine failure or loss of available power can prevent maintaining flight under demanding weight and environmental conditions.", "Dust-induced brownout can obscure external visual references during landing and takeoff.", "Low-altitude operations expose the aircraft to terrain, wires and other obstacles.", "Fuel and carried ammunition create fire and explosion hazards following damage or mishandling." ], "questions": [ { "id": "evidence-failure-modes-and-hazards-q01", "text": "Which of these failure modes and hazards hold for the sense of Hughes AH-64 Apache 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": [ "The UK Apache AH Mk 1 incorporated national equipment and a different engine installation from US AH-64D aircraft.", "Export configurations vary in communications, identification equipment, defensive systems and approved weapons." ], "questions": [ { "id": "evidence-regional-variation-q01", "text": "Which of these regional variation hold for the sense of Hughes AH-64 Apache 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": "Attack helicopter", "difference": "The broader aircraft category; the Apache is a particular aircraft family within it." }, { "name": "Bell AH-1 Cobra", "difference": "A separate attack-helicopter design lineage, rather than an Apache variant." }, { "name": "An individual AH-64 airframe", "difference": "A physical aircraft identified by a serial number; this entry describes the aircraft family." }, { "name": "AN/APG-78 Longbow radar", "difference": "A radar subsystem fitted to some Apache configurations, rather than the helicopter itself." } ], "questions": [ { "id": "evidence-neighbours-q01", "text": "Which of these neighbouring kinds and how to tell them apart hold for the sense of Hughes AH-64 Apache this model covers, and on what evidence?", "kind": "provenance" } ] } ] } ] } ] }, "openQuestions": [ "Does this registry entry intentionally cover the whole Apache family, or does Hughes restrict its scope to a historical production subset?", "Does an existing Vercy world model already cover the Apache family and require this entry to link to it?", "Which authoritative, accessible references establish variant boundaries, equipment options and measurement conditions?", "Which operator-specific airworthiness requirements and technical-publication systems should the model recognise?", "Which documented Apache failure modes and maintenance indicators can support condition assessment without implying unsupported diagnostic certainty?" ], "statistics": { "bundles": 6, "layers": 11, "findings": 18, "questions": 30 } }, "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 Hughes AH-64 Apache, record what state it is in, and decide what may be done with it.", "whatItIs": "Enable an AI agent to recognise the AH-64 Apache aircraft family registered under the Hughes name, assess evidence about a particular configuration or airframe, and identify permitted inspection, maintenance and operation.", "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: AH-64E, Apache AH1.", "2 finer distinctions are held as aliases rather than separate entries, because telling them apart needs a task that asks for it.", "Described in 69 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 Hughes AH-64 Apache, 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 Hughes AH-64 Apache 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": [ "AH-64E", "Apache AH1" ] } ], "standing": "Described in 69 Wikipedia languages, which measures how widely it is written about rather than how important or how common it is. 2 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 Hughes AH-64 Apache from another, and a Hughes AH-64 Apache 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 Hughes AH-64 Apache, 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 Hughes AH-64 Apache, 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 Hughes AH-64 Apache 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 Hughes AH-64 Apache, 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 Hughes AH-64 Apache, 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 Hughes AH-64 Apache 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 Hughes AH-64 Apache 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 Hughes AH-64 Apache, 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 Hughes AH-64 Apache, 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 Hughes AH-64 Apache 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 Hughes AH-64 Apache from the things most often confused with it.", "questions": [ { "id": "distinguishing-features-q01", "text": "What identifies and describes what distinguishes a Hughes AH-64 Apache, 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 Hughes AH-64 Apache, 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 Hughes AH-64 Apache 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 Hughes AH-64 Apache 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 Hughes AH-64 Apache, 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 Hughes AH-64 Apache, 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 Hughes AH-64 Apache 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 Hughes AH-64 Apache is built from and which parts are replaceable.", "questions": [ { "id": "parts-and-materials-q01", "text": "What identifies and describes the composition of a Hughes AH-64 Apache, 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 Hughes AH-64 Apache, 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 Hughes AH-64 Apache 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 Hughes AH-64 Apache is judged and by whom.", "questions": [ { "id": "condition-assessment-q01", "text": "What identifies and describes the condition of a Hughes AH-64 Apache, 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 Hughes AH-64 Apache, 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 Hughes AH-64 Apache 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 Hughes AH-64 Apache 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 Hughes AH-64 Apache is, and what that position is measured against.", "questions": [ { "id": "position-and-frame-q01", "text": "What identifies and describes the location of a Hughes AH-64 Apache, 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 Hughes AH-64 Apache, 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 Hughes AH-64 Apache 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 Hughes AH-64 Apache 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 Hughes AH-64 Apache, 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 Hughes AH-64 Apache, 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 Hughes AH-64 Apache 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 Hughes AH-64 Apache 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 Hughes AH-64 Apache between them.", "questions": [ { "id": "stages-and-transitions-q01", "text": "What identifies and describes the lifecycle of a Hughes AH-64 Apache, 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 Hughes AH-64 Apache, 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 Hughes AH-64 Apache 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 Hughes AH-64 Apache, how often and by whom.", "findings": [ { "id": "observation-record", "name": "Observation record", "description": "How an observation of a Hughes AH-64 Apache 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 Hughes AH-64 Apache, 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 Hughes AH-64 Apache, 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 Hughes AH-64 Apache 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 Hughes AH-64 Apache 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 Hughes AH-64 Apache is for, and what it is used for anyway.", "findings": [ { "id": "function-and-purpose", "name": "Function, purpose and misuse", "description": "The function a Hughes AH-64 Apache performs and the uses that fall outside it.", "questions": [ { "id": "function-and-purpose-q01", "text": "What identifies and describes the use of a Hughes AH-64 Apache, 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 Hughes AH-64 Apache, 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 Hughes AH-64 Apache 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 Hughes AH-64 Apache.", "findings": [ { "id": "procedures-and-skills", "name": "Procedures, skills and required tools", "description": "What an agent needs before it can act on a Hughes AH-64 Apache at all.", "questions": [ { "id": "procedures-and-skills-q01", "text": "What identifies and describes handling a Hughes AH-64 Apache, 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 Hughes AH-64 Apache, 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 Hughes AH-64 Apache 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 Hughes AH-64 Apache 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 Hughes AH-64 Apache and how confident it is.", "questions": [ { "id": "claim-provenance-q01", "text": "What identifies and describes a claim about a Hughes AH-64 Apache, 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 Hughes AH-64 Apache, 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 Hughes AH-64 Apache 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 Hughes AH-64 Apache is retired without being erased.", "questions": [ { "id": "validity-and-supersession-q01", "text": "What identifies and describes the validity of a claim about a Hughes AH-64 Apache, 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 Hughes AH-64 Apache, 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 Hughes AH-64 Apache 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 } } } }