{ "model": { "rank": 4884, "code": "thing-q178351", "model_id": "vr.tr.antonov-an-225-mriya", "name": "Antonov An-225 Mriya", "purpose": "Enable an agent to identify the Antonov An-225 Mriya design, distinguish its capabilities from an individual airframe's condition, and determine what evidence is needed before proposing transport, maintenance or recovery actions.", "family": "Thing Registry", "category": "Physical world and living systems", "status": "research-draft", "kind": "thing", "plane": "PHY", "domain": "PHY.OBJ", "industry": "", "version": "", "url": "/models/thing/q178351/", "tier": 2, "score": 71, "payload": { "layer": "wikidata", "aliases": [], "aliasCount": 0, "merged": 0, "knownIn": 71, "facets": null, "markers": [], "lexicalClass": "", "senseRank": null, "alsoRegisteredAs": null, "source": { "dataset": "wikidata", "item": "Q178351", "url": "https://www.wikidata.org/wiki/Q178351", "license": "CC0 1.0" } }, "research": { "vercy": "1.0-draft", "publication": { "status": "research-draft", "adjudicationStatus": "unreviewed", "publishableCanonical": false, "generatedAt": "2026-09-09T21:12:12Z", "providers": [ "Codex" ], "breadth": "recalled by Codex without web access - no source was read", "missingProviders": [], "pass": 2, "cost": { "grok": { "seconds": 23.2, "error": "Reading additional input from stdin...\nOpenAI Codex v0.153.4\n--------\nworkdir: R:\\02_PROJECTS\\02_Meta_Models_Platforms\\Ver.cy\\current\\thing-registry-backlog\nmodel: gpt-6-astra\nprovider: openai\napproval: never\nsandbox: read-only\nreasoning effort: none\nreasoning summaries: none\nsession id: 01a08802-8cc4-7cd0-b9e5-be393eeaa9f4\n--------\nuser\nDescribe what is already known about one registered thing. Answer as JSON only, no prose around it.\n\nThing: Antonov An-225 Mriya\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": 69.4, "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: 01a08802-8cd4-7193-b2dc-a99a374da486\n--------\nuser\nYou are drafting a Vercy meta-model for one registered thing. Answer as JSON only, no prose around it.\n\nThing: Antonov An-225 Mriya\nRegistry id: vr.tr.antonov-an-225-mriya\nPlane / domain: PHY / PHY.OBJ\nRegistry definition: (none recorded)\nNames folded into thi" } } }, "metaModel": { "id": "THING-Q178351", "registryId": "vr.tr.antonov-an-225-mriya", "name": "Antonov An-225 Mriya", "version": "0.1.0-research.1", "entryKind": "thing", "family": "Thing Registry", "domain": [ "PHY.OBJ" ], "status": "research-draft" }, "canonicalUrl": "https://ver.cy/models/thing/q178351/", "model": { "registry_id": "vr.tr.antonov-an-225-mriya", "name": "Antonov An-225 Mriya", "purpose": "Enable an agent to identify the Antonov An-225 Mriya design, distinguish its capabilities from an individual airframe's condition, and determine what evidence is needed before proposing transport, maintenance or recovery actions.", "definition": "The Antonov An-225 Mriya is a Soviet-designed, six-engine strategic transport aircraft type developed to carry exceptionally heavy and outsized loads, including the Buran spacecraft, of which only one aircraft was completed.", "scope_statement": "This model owns registry entry vr.tr.antonov-an-225-mriya in PHY / PHY.OBJ, interpreted as the An-225 aircraft design and its configuration-dependent capabilities; individual airframes, historical missions and reconstruction projects are linked instances rather than interchangeable meanings of the entry.", "in_scope": [ "An-225 identification and differences from the related An-124 design", "Internal and external cargo configurations and their separate operating envelopes", "Propulsion, flight controls, loading systems and ground support dependencies", "Payload, structural loading, range and airport compatibility constraints", "Evidence connecting design capabilities to dated airframe condition and operating authority" ], "out_of_scope": [ "Generic fixed-wing aircraft principles already owned by an aircraft model", "The An-124 design except where comparison establishes An-225 differences", "Antonov's corporate organisation and airline business", "Buran, launch vehicles and other transported objects as independently modelled things", "Individual flight histories, accident events and reconstruction projects beyond their effects on configuration or availability" ], "distinguishing_features": [ "Check the manufacturer designation and configuration records for An-225; an Antonov identity or heavy-cargo role alone is insufficient.", "Check the six-engine arrangement against the related An-124 configuration. [Antonov brochure](https://www.antonov.com/en/file/V5hQc2hGrJGRs?inline=1)", "Check the paired vertical fins and external-load arrangement against authenticated An-225 drawings rather than identifying it from size alone.", "Separate the An-225 design designation from the registration, serial number and dated condition of a particular airframe.", "Treat Antonov's historical 250-tonne payload statement as an identification and capability reference, not approval for a proposed load. [Antonov operational report](https://www.antonov.com/en/article/an-225-mriya-uspishno-dostaviv-110-tonn-komplektiv-dlya-testuvannya-na-covid-19-do-avstriji-v-umovah-globalnogo-deficitu-transportnih-potuzhnostey)" ], "characteristics": [ { "name": "Design and airframe identity", "kind": "relation", "unit_or_values": "Registry entry → manufacturer designation → configuration revision → serial number and dated registration", "why_it_matters": "Prevents a design capability, an unfinished airframe and a historically operated aircraft from being treated as the same operational asset." }, { "name": "Cargo configuration", "kind": "category", "unit_or_values": "Internal cargo; external load; other documented configuration", "why_it_matters": "Each configuration requires its own structural, aerodynamic and approval evidence." }, { "name": "Payload and aircraft mass limits", "kind": "measurement", "unit_or_values": "kg or tonnes, separately for payload, ramp, takeoff and landing mass", "why_it_matters": "A headline payload value does not establish permissible aircraft mass for a particular flight." }, { "name": "Cargo clearance envelope", "kind": "measurement", "unit_or_values": "m, including usable hold dimensions, entrance clearance and loading-path clearance", "why_it_matters": "A load may fit inside the hold but fail to pass through the entrance or loading trajectory." }, { "name": "Load distribution and balance", "kind": "measurement", "unit_or_values": "Centre of gravity in m from datum or percent mean aerodynamic chord; floor loading in kN/m²; concentrated loads in kN", "why_it_matters": "Oversized cargo can exceed local structural or balance limits while remaining below total payload limits." }, { "name": "Propulsion configuration", "kind": "relation", "unit_or_values": "Six engine positions linked to installed engine variant, service status and supporting records", "why_it_matters": "Installation identity and serviceability are necessary to assess the applicable performance envelope." }, { "name": "Mission performance envelope", "kind": "measurement", "unit_or_values": "Range in km; fuel mass in kg; runway distances in m, with mass, weather, elevation and configuration conditions", "why_it_matters": "Range and runway suitability cannot be inferred independently of payload and operating conditions." }, { "name": "Airframe physical condition", "kind": "state", "unit_or_values": "Incomplete; intact; damaged; destroyed; under restoration; unknown, each dated and sourced", "why_it_matters": "Historical performance must not be interpreted as evidence of present availability." }, { "name": "Operating authority", "kind": "state", "unit_or_values": "Documented permission with scope and validity dates; restricted; expired; absent; unknown", "why_it_matters": "Physical condition and legal permission to operate are separate determinations." } ], "affordances": [ "Identify a documented aircraft or component collection as related to the An-225 design and flag conflicting identifiers.", "Screen an oversized cargo proposal against documented geometry, loading and balance constraints.", "Identify missing runway, pavement, parking, handling and fuel evidence for a proposed airport.", "Compare a dated airframe configuration with the manuals and approvals that apply to it.", "Prepare evidence requirements for specialist maintenance, recovery or reconstruction review.", "Prevent historical specifications from being presented as evidence of current flight capability." ] }, "sources": [], "structure": { "bundles": [ { "id": "an-225-identity-and-lineage", "name": "An-225 identity and lineage", "description": "Establish the design boundary and connect it to identifiable airframes and configurations.", "rationale": "The name Mriya can refer to a design, a particular aircraft or a reconstruction ambition, with different implications for an agent.", "layers": [ { "id": "design-recognition", "name": "Design recognition", "description": "Recognise the An-225 through designation and distinguishing configuration evidence.", "findings": [ { "id": "an-124-derived-but-distinct", "name": "An-124-derived but distinct", "description": "Record the An-124 relationship while requiring An-225-specific configuration evidence before transferring capabilities or procedures.", "questions": [ { "text": "Which manufacturer records establish the An-225 designation and its differences from the An-124?", "kind": "provenance", "id": "an-124-derived-but-distinct-q01" }, { "text": "Which propulsion, empennage, fuselage and landing-gear features distinguish an An-225 in the available evidence?", "kind": "definition", "id": "an-124-derived-but-distinct-q02" } ] } ] }, { "id": "airframe-identity-continuity", "name": "Airframe identity continuity", "description": "Connect physical examples and component assemblies without conflating their identities.", "findings": [ { "id": "design-versus-physical-example", "name": "Design versus physical example", "description": "Maintain separate identities for the design, completed or incomplete airframes, recovered components and any proposed reconstruction.", "questions": [ { "text": "Which serial numbers and dated registrations identify each physical An-225 airframe?", "kind": "provenance", "id": "design-versus-physical-example-q01" }, { "text": "What documented decision would establish whether a reconstructed aircraft continues an existing airframe identity or creates a new one?", "kind": "boundary", "id": "design-versus-physical-example-q02" } ] } ] } ] }, { "id": "outsized-cargo-integration", "name": "Outsized cargo integration", "description": "Represent the distinct constraints of transporting cargo inside the aircraft or mounted externally.", "rationale": "An-225 suitability depends on cargo interfaces and load distribution as much as total payload mass.", "layers": [ { "id": "internal-cargo-loading", "name": "Internal cargo loading", "description": "Assess the complete loading path and structural support of cargo carried inside the aircraft.", "findings": [ { "id": "cargo-fit-and-floor-load", "name": "Cargo fit and floor load", "description": "Require a loading arrangement that satisfies entrance clearance, support reactions, restraint and balance throughout loading and flight.", "questions": [ { "text": "What are the documented entrance, hold and loading-path dimensions for the applicable configuration?", "kind": "measurement", "id": "cargo-fit-and-floor-load-q01" }, { "text": "Does the proposed cargo and support-frame arrangement satisfy floor, ramp, restraint and centre-of-gravity limits at every loading stage?", "kind": "action", "id": "cargo-fit-and-floor-load-q02" } ] } ] }, { "id": "external-load-integration", "name": "External load integration", "description": "Treat externally carried objects as configuration-specific structural and aerodynamic integrations.", "findings": [ { "id": "external-carriage-approval-boundary", "name": "External carriage approval boundary", "description": "Historical carriage of one external object is insufficient evidence that another object can use the same attachment or flight envelope.", "questions": [ { "text": "Which external-load configurations have documented attachment geometry, structural limits and flight-test evidence?", "kind": "provenance", "id": "external-carriage-approval-boundary-q01" }, { "text": "What additional analysis, testing and approval would a different external load require?", "kind": "action", "id": "external-carriage-approval-boundary-q02" } ] } ] } ] }, { "id": "flight-and-ground-operating-envelope", "name": "Flight and ground operating envelope", "description": "Connect propulsion, configuration and mass to flight performance and airport requirements.", "rationale": "The An-225's exceptional size and loading demands make generic airport compatibility and maximum-capacity figures inadequate.", "layers": [ { "id": "propulsion-controls-and-performance", "name": "Propulsion, controls and performance", "description": "Determine which documented aircraft systems and operating conditions support a performance assessment.", "findings": [ { "id": "configuration-dependent-flight-capability", "name": "Configuration-dependent flight capability", "description": "Record engine installation, fuel requirements, control-system status and applicable limitations before evaluating a mission.", "questions": [ { "text": "Which approved documents define engine variants, fuel specifications, control-system dependencies and degraded-system restrictions for this An-225 configuration?", "kind": "provenance", "id": "configuration-dependent-flight-capability-q01" }, { "text": "What payload, fuel, range and takeoff or landing performance follows from the proposed mass, cargo configuration and atmospheric conditions?", "kind": "measurement", "id": "configuration-dependent-flight-capability-q02" } ] } ] }, { "id": "airport-and-loading-support", "name": "Airport and loading support", "description": "Assess movement, parking and cargo handling against the aircraft's actual geometry and loads.", "findings": [ { "id": "airport-compatibility-beyond-runway-length", "name": "Airport compatibility beyond runway length", "description": "Require evidence for pavement loading, clearances, turning geometry and loading equipment as well as runway performance.", "questions": [ { "text": "What wingspan, height, turning envelope, wheel loads and clearance margins must the proposed route through the airport accommodate?", "kind": "measurement", "id": "airport-compatibility-beyond-runway-length-q01" }, { "text": "Can the airport provide documented pavement capacity, towing equipment, loading-system safeguards, fuel supply and emergency support for the planned operation?", "kind": "action", "id": "airport-compatibility-beyond-runway-length-q02" } ] } ] } ] }, { "id": "airworthiness-damage-and-recovery", "name": "Airworthiness, damage and recovery", "description": "Separate historical capability from dated condition, maintainability and permission to operate.", "rationale": "An agent must not infer an available aircraft from the continuing existence of the An-225 design or its published specifications.", "layers": [ { "id": "condition-and-maintenance-evidence", "name": "Condition and maintenance evidence", "description": "Determine what inspection and service records establish about an airframe or recovered component.", "findings": [ { "id": "serviceability-requires-traceable-evidence", "name": "Serviceability requires traceable evidence", "description": "Record damage, storage exposure, fatigue history, life limits and parts provenance without equating physical survival with serviceability.", "questions": [ { "text": "Which dated inspections establish the condition of the structure, engines, landing gear and flight-control systems?", "kind": "provenance", "id": "serviceability-requires-traceable-evidence-q01" }, { "text": "Which An-225 maintenance instructions govern structural fatigue, corrosion, engine life limits, tyres, brakes, fluids and replacement-part eligibility?", "kind": "action", "id": "serviceability-requires-traceable-evidence-q02" } ] } ] }, { "id": "approval-and-reconstruction-boundaries", "name": "Approval and reconstruction boundaries", "description": "Connect an intended action to applicable technical authority and a documented aircraft configuration.", "findings": [ { "id": "historical-approval-does-not-establish-current-authority", "name": "Historical approval does not establish current authority", "description": "Require identifiable issuing bodies, document revisions, configuration applicability and validity dates for operating or return-to-service claims.", "questions": [ { "text": "Which issuing authority, certification basis, airworthiness documents and operating limitations apply to the identified airframe and proposed date?", "kind": "provenance", "id": "historical-approval-does-not-establish-current-authority-q01" }, { "text": "What engineering substantiation and authority decisions would be required before a repaired, completed or reconstructed An-225 could return to flight?", "kind": "action", "id": "historical-approval-does-not-establish-current-authority-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 describes the aircraft type. The sole completed aircraft was destroyed at Hostomel in February 2022; any reconstruction status requires verification.", "Dimensions and capacities are recalled nominal figures, not flight-planning data; approved limits depend on configuration and operating conditions.", "The ICAO annexes are general regulatory frameworks, not evidence of the An-225's specific certification basis, which should be checked separately." ], "questions": [ { "id": "evidence-confidence-notes-q01", "text": "Which of these check these first hold for the sense of Antonov An-225 Mriya 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": "Antonov aircraft designation", "value_or_pattern": "An-225", "note": "Identifies the aircraft type; Mriya is its name." }, { "scheme": "ICAO aircraft type designator", "value_or_pattern": "A225", "note": "Used in flight planning and air traffic services." }, { "scheme": "Aircraft nationality and registration marks", "value_or_pattern": "UR-82060", "note": "Ukrainian registration of the sole completed aircraft, not an identifier for the type." } ], "questions": [ { "id": "evidence-identifiers-q01", "text": "Which of these identifiers and schemes hold for the sense of Antonov An-225 Mriya 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": [ "ICAO Annex 8 - Airworthiness of Aircraft: international framework implemented through national airworthiness authorities.", "ICAO Annex 6, Part I - International Commercial Air Transport - Aeroplanes: operational framework relevant to commercial cargo service." ], "questions": [ { "id": "evidence-standards-and-regulation-q01", "text": "Which of these standards and regulation hold for the sense of Antonov An-225 Mriya 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 the Buran spacecraft externally above the fuselage.", "Carrying exceptionally heavy industrial equipment and oversized freight.", "Delivering humanitarian and emergency relief cargo.", "Loading large cargo through an upward-opening nose using a kneeling landing gear arrangement and onboard handling equipment." ], "questions": [ { "id": "evidence-real-world-use-q01", "text": "Which of these real-world use hold for the sense of Antonov An-225 Mriya 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": "Overall length", "typical_range": "84", "unit": "m" }, { "quantity": "Wingspan", "typical_range": "88.4", "unit": "m" }, { "quantity": "Overall height", "typical_range": "18.1", "unit": "m" }, { "quantity": "Maximum takeoff mass in its later operating configuration", "typical_range": "640000", "unit": "kg" }, { "quantity": "Maximum internal payload, subject to operating constraints", "typical_range": "250000", "unit": "kg" } ], "questions": [ { "id": "evidence-measurements-q01", "text": "Which of these typical measurements hold for the sense of Antonov An-225 Mriya 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": [ "Incorrect cargo restraint or load distribution can exceed structural limits or move the centre of gravity outside its permitted envelope.", "Its mass and dimensions impose demanding runway, pavement strength, taxiway clearance and parking requirements.", "Heavy loading increases sensitivity to takeoff performance limits, weather and available runway length.", "Large wake vortices and jet blast pose hazards to nearby aircraft, personnel and equipment.", "Complex landing gear, hydraulic systems and six turbofan engines require extensive inspection and maintenance." ], "questions": [ { "id": "evidence-failure-modes-and-hazards-q01", "text": "Which of these failure modes and hazards hold for the sense of Antonov An-225 Mriya 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": [ "Developed within the Soviet Union; the completed aircraft subsequently operated under Ukrainian registration.", "International operations required airport-specific infrastructure assessments and applicable national operating permissions." ], "questions": [ { "id": "evidence-regional-variation-q01", "text": "Which of these regional variation hold for the sense of Antonov An-225 Mriya 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": "Antonov An-124 Ruslan", "difference": "The related four-engine heavy transport from which the An-225 was developed; the An-225 has six engines, a larger airframe and twin vertical tails." }, { "name": "UR-82060", "difference": "The individual completed aircraft, whereas An-225 denotes the aircraft type." }, { "name": "Buran", "difference": "A spacecraft carried as an external payload, rather than the aircraft transporting it." } ], "questions": [ { "id": "evidence-neighbours-q01", "text": "Which of these neighbouring kinds and how to tell them apart hold for the sense of Antonov An-225 Mriya this model covers, and on what evidence?", "kind": "provenance" } ] } ] } ] } ] }, "openQuestions": [ "Does registry provenance intend the An-225 design or specifically the aircraft historically known as Mriya, and does an existing world model already own that concept?", "What authoritative, dated evidence establishes the present condition and disposition of the flown airframe, the unfinished airframe and any reconstruction work?", "Which primary manuals establish configuration-specific dimensions, mass limits, cargo-floor loads, external-load limits and performance envelopes?", "What certification basis, issuing authorities and operating permissions applied historically, and what would govern a future completed or reconstructed aircraft?", "Which An-225-specific maintenance programmes, failure records, loading interlocks and component-life records are available beyond public promotional material?" ], "statistics": { "bundles": 5, "layers": 9, "findings": 16, "questions": 24 } }, "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 Antonov An-225 Mriya, record what state it is in, and decide what may be done with it.", "whatItIs": "Enable an agent to identify the Antonov An-225 Mriya design, distinguish its capabilities from an individual airframe's condition, and determine what evidence is needed before proposing transport, maintenance or recovery actions.", "characteristics": { "substance": "material", "origin": "manufactured", "agency": "inert", "mobility": "varies" }, "whatYouCanDoWithIt": [ "observed and measured" ], "distinguishingFeatures": [ "Described in 71 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 Antonov An-225 Mriya, 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 Antonov An-225 Mriya looks like has to come from research." ], "relatedModels": [], "standing": "Described in 71 Wikipedia languages, which measures how widely it is written about rather than how important or how common it is.", "structure": { "bundles": [ { "id": "identity-and-classification", "name": "Identity, naming and classification", "description": "How an agent tells one Antonov An-225 Mriya from another, and a Antonov An-225 Mriya 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 Antonov An-225 Mriya, 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 Antonov An-225 Mriya, 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 Antonov An-225 Mriya 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 Antonov An-225 Mriya, 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 Antonov An-225 Mriya, 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 Antonov An-225 Mriya 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 Antonov An-225 Mriya 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 Antonov An-225 Mriya, 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 Antonov An-225 Mriya, 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 Antonov An-225 Mriya 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 Antonov An-225 Mriya from the things most often confused with it.", "questions": [ { "id": "distinguishing-features-q01", "text": "What identifies and describes what distinguishes a Antonov An-225 Mriya, 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 Antonov An-225 Mriya, 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 Antonov An-225 Mriya 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 Antonov An-225 Mriya 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 Antonov An-225 Mriya, 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 Antonov An-225 Mriya, 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 Antonov An-225 Mriya 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 Antonov An-225 Mriya is built from and which parts are replaceable.", "questions": [ { "id": "parts-and-materials-q01", "text": "What identifies and describes the composition of a Antonov An-225 Mriya, 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 Antonov An-225 Mriya, 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 Antonov An-225 Mriya 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 Antonov An-225 Mriya is judged and by whom.", "questions": [ { "id": "condition-assessment-q01", "text": "What identifies and describes the condition of a Antonov An-225 Mriya, 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 Antonov An-225 Mriya, 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 Antonov An-225 Mriya 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 Antonov An-225 Mriya 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 Antonov An-225 Mriya is, and what that position is measured against.", "questions": [ { "id": "position-and-frame-q01", "text": "What identifies and describes the location of a Antonov An-225 Mriya, 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 Antonov An-225 Mriya, 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 Antonov An-225 Mriya 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 Antonov An-225 Mriya 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 Antonov An-225 Mriya, 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 Antonov An-225 Mriya, 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 Antonov An-225 Mriya 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 Antonov An-225 Mriya 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 Antonov An-225 Mriya between them.", "questions": [ { "id": "stages-and-transitions-q01", "text": "What identifies and describes the lifecycle of a Antonov An-225 Mriya, 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 Antonov An-225 Mriya, 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 Antonov An-225 Mriya 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 Antonov An-225 Mriya, how often and by whom.", "findings": [ { "id": "observation-record", "name": "Observation record", "description": "How an observation of a Antonov An-225 Mriya 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 Antonov An-225 Mriya, 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 Antonov An-225 Mriya, 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 Antonov An-225 Mriya 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 Antonov An-225 Mriya 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 Antonov An-225 Mriya is for, and what it is used for anyway.", "findings": [ { "id": "function-and-purpose", "name": "Function, purpose and misuse", "description": "The function a Antonov An-225 Mriya performs and the uses that fall outside it.", "questions": [ { "id": "function-and-purpose-q01", "text": "What identifies and describes the use of a Antonov An-225 Mriya, 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 Antonov An-225 Mriya, 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 Antonov An-225 Mriya 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 Antonov An-225 Mriya.", "findings": [ { "id": "procedures-and-skills", "name": "Procedures, skills and required tools", "description": "What an agent needs before it can act on a Antonov An-225 Mriya at all.", "questions": [ { "id": "procedures-and-skills-q01", "text": "What identifies and describes handling a Antonov An-225 Mriya, 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 Antonov An-225 Mriya, 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 Antonov An-225 Mriya 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 Antonov An-225 Mriya 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 Antonov An-225 Mriya and how confident it is.", "questions": [ { "id": "claim-provenance-q01", "text": "What identifies and describes a claim about a Antonov An-225 Mriya, 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 Antonov An-225 Mriya, 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 Antonov An-225 Mriya 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 Antonov An-225 Mriya is retired without being erased.", "questions": [ { "id": "validity-and-supersession-q01", "text": "What identifies and describes the validity of a claim about a Antonov An-225 Mriya, 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 Antonov An-225 Mriya, 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 Antonov An-225 Mriya 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 } } } }