{ "model": { "rank": 6658, "code": "thing-q150050", "model_id": "vr.tr.mikoyan-mig-31", "name": "Mikoyan MiG-31", "purpose": "Enable an AI agent to identify a Mikoyan MiG-31, distinguish its documented configuration, assess evidence of its condition, and determine which inspection, support or preservation actions are appropriate.", "family": "Thing Registry", "category": "Physical world and living systems", "status": "research-draft", "kind": "thing", "plane": "PHY", "domain": "PHY.OBJ", "industry": "", "version": "", "url": "/models/thing/q150050/", "tier": 2, "score": 59, "payload": { "layer": "wikidata", "aliases": [ "Mikojan-Gurevitj MiG-31BM" ], "aliasCount": 1, "merged": 1, "knownIn": 59, "facets": null, "markers": [], "lexicalClass": "", "senseRank": null, "alsoRegisteredAs": null, "source": { "dataset": "wikidata", "item": "Q150050", "url": "https://www.wikidata.org/wiki/Q150050", "license": "CC0 1.0" } }, "research": { "vercy": "1.0-draft", "publication": { "status": "research-draft", "adjudicationStatus": "unreviewed", "publishableCanonical": false, "generatedAt": "2026-09-09T23:13:29Z", "providers": [ "Codex" ], "breadth": "recalled by Codex without web access - no source was read", "missingProviders": [], "pass": 2, "cost": { "grok": { "seconds": 22.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: 01a08871-a757-7790-a1fe-37d1d4f81963\n--------\nuser\nDescribe what is already known about one registered thing. Answer as JSON only, no prose around it.\n\nThing: Mikoyan MiG-31\nSense to describe: (none recorded)\nDomain code: PHY.OBJ\nAlso known as: (none)\n\n\nContext for this batch of 1001 things:\n# Batch 007: 1001 ", "usd": 0, "recall": true }, "codex": { "seconds": 64.5, "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: 01a08871-a750-7413-ba96-835b328e4301\n--------\nuser\nYou are drafting a Vercy meta-model for one registered thing. Answer as JSON only, no prose around it.\n\nThing: Mikoyan MiG-31\nRegistry id: vr.tr.mikoyan-mig-31\nPlane / domain: PHY / PHY.OBJ\nRegistry definition: (none recorded)\nNames folded into this entry: (no" } } }, "metaModel": { "id": "THING-Q150050", "registryId": "vr.tr.mikoyan-mig-31", "name": "Mikoyan MiG-31", "version": "0.1.0-research.1", "entryKind": "thing", "family": "Thing Registry", "domain": [ "PHY.OBJ" ], "status": "research-draft" }, "canonicalUrl": "https://ver.cy/models/thing/q150050/", "model": { "registry_id": "vr.tr.mikoyan-mig-31", "name": "Mikoyan MiG-31", "purpose": "Enable an AI agent to identify a Mikoyan MiG-31, distinguish its documented configuration, assess evidence of its condition, and determine which inspection, support or preservation actions are appropriate.", "definition": "The Mikoyan MiG-31 is a Soviet-designed, twin-engine, two-seat supersonic interceptor aircraft type developed from the MiG-25 for long-range, all-weather interception using powerful radar and long-range air-to-air missiles.", "scope_statement": "This model owns the MiG-31 aircraft family represented by vr.tr.mikoyan-mig-31 in PHY / PHY.OBJ, including variant-dependent recognition and assessment criteria; individual airframes supply observations without becoming separate aircraft-type models.", "in_scope": [ "MiG-31 identity, development lineage and distinguishing airframe features", "Documented variants, conversions and installed equipment configurations", "Configuration-dependent dimensions, propulsion and flight limitations", "Crew stations, avionics and aircraft-level equipment interfaces", "Airframe condition, maintenance evidence and eligibility for ground handling, flight or preservation" ], "out_of_scope": [ "General aircraft and jet-propulsion principles owned by broader models", "MiG-25 aircraft specifications beyond identification and lineage comparisons", "Independent models of engines, radars, missiles and ground equipment", "Military organizations, procurement programs and fleet inventories", "Combat tactics, targeting decisions and weapon-employment procedures" ], "distinguishing_features": [ "Require documented MiG-31 type identity rather than identifying it solely from resemblance to the MiG-25; EUROCONTROL identifies the MiG-31 as a two-seat interceptor development of that aircraft. [EUROCONTROL aircraft identification](https://contentzone.eurocontrol.int/aircraftperformance/details.aspx?ICAO=MG31)", "Check the combination of tandem crew accommodation, intake and tail arrangement, and landing-gear geometry against an authenticated MiG-31 reference; a twin-fin silhouette alone is insufficient.", "Use documented engine and radar installations as corroborating evidence: D-30F6 engines and the Zaslon phased-array radar are associated with the MiG-31, but equipment applicability must be checked for the particular variant. [Military Technical Courier](https://www.vtg.mod.gov.rs/arhiva/1995/vojnotehnicki-glasnik-1-1995.pdf)", "Distinguish an original production configuration from a later conversion through modification records and installed equipment; paint schemes, captions and external stores do not independently establish variant identity." ], "characteristics": [ { "name": "Type and variant identity", "kind": "category", "unit_or_values": "MiG-31; documented variant or conversion designation; unresolved", "why_it_matters": "Determines which equipment descriptions, limitations and maintenance references apply." }, { "name": "Airframe identity evidence", "kind": "relation", "unit_or_values": "Links to manufacturer serial, identification plate, service records and dated imagery", "why_it_matters": "Separates the aircraft family from a particular aircraft and prevents markings from being treated as permanent identity." }, { "name": "Installed propulsion configuration", "kind": "relation", "unit_or_values": "Engine model, modification standard and installation records for each engine position", "why_it_matters": "Connects the observed aircraft to applicable servicing requirements and propulsion limitations." }, { "name": "Radar and avionics configuration", "kind": "relation", "unit_or_values": "Documented radar designation, avionics modification standard and supporting evidence", "why_it_matters": "Prevents capabilities of one modernization standard from being assigned to all MiG-31 aircraft." }, { "name": "Aircraft dimensions", "kind": "measurement", "unit_or_values": "Length, span and height in m, with variant and measurement convention", "why_it_matters": "Supports recognition, hangar clearance and transport assessment." }, { "name": "Mass and loading condition", "kind": "measurement", "unit_or_values": "kg, distinguishing empty, actual loaded and authorized limiting masses", "why_it_matters": "Prevents incompatible weight definitions from being used in handling or operating assessments." }, { "name": "Published flight envelope", "kind": "measurement", "unit_or_values": "Mach number, speed in km/h, altitude in m and duration in min, each qualified by configuration and conditions", "why_it_matters": "Distinguishes headline performance figures from applicable operating limitations." }, { "name": "Structural and engine life status", "kind": "state", "unit_or_values": "Documented remaining life; inspection due; life limit reached; unknown", "why_it_matters": "Appearance and aircraft age cannot establish remaining service life." }, { "name": "Assessment disposition", "kind": "state", "unit_or_values": "Authorized for specified activity; restricted; awaiting inspection; preserved display; unknown", "why_it_matters": "Records what evidence and authority permit without equating an intact aircraft with an airworthy one." } ], "affordances": [ "Classify a candidate aircraft as a confirmed, probable or unresolved MiG-31 using documentary and visual evidence.", "Compare documented variants and identify which configuration differences affect an assessment.", "Associate measurements and observed condition with the applicable MiG-31 configuration and reference revision.", "Flag missing maintenance, life-limit or modification evidence before an authorized handling or flight decision.", "Prepare a configuration-aware inspection or preservation information request.", "Link installed engines, avionics and external equipment to their separate component models." ] }, "sources": [], "structure": { "bundles": [ { "id": "identity-and-configuration", "name": "Identity and configuration", "description": "Establish what qualifies as a MiG-31 and which configuration an assessment concerns.", "rationale": "The MiG-25 lineage and MiG-31 modifications create opportunities to confuse related aircraft and transfer incompatible specifications.", "layers": [ { "id": "family-recognition", "name": "Family recognition", "description": "Combine type documentation with discriminating physical observations.", "findings": [ { "id": "mig-31-identity-evidence", "name": "MiG-31 identity evidence", "description": "Require a traceable identification argument connecting the candidate aircraft to this registry entry.", "questions": [ { "text": "Which manufacturer, service or museum record explicitly identifies the aircraft as a MiG-31?", "kind": "provenance", "id": "mig-31-identity-evidence-q01" }, { "text": "Which observed crew-station, intake, tail and landing-gear features distinguish it from a MiG-25 or a mislabeled display?", "kind": "boundary", "id": "mig-31-identity-evidence-q02" } ] } ] }, { "id": "variant-and-conversion-record", "name": "Variant and conversion record", "description": "Separate original manufacture, subsequent modification and present equipment.", "findings": [ { "id": "configuration-applicability", "name": "Configuration applicability", "description": "Treat a variant designation as an evidence-backed configuration claim rather than a complete equipment inventory.", "questions": [ { "text": "What designation was assigned at manufacture, and which later conversion records change it?", "kind": "provenance", "id": "configuration-applicability-q01" }, { "text": "Which documented differences in radar, crew stations, refueling provisions or external interfaces require different assessment criteria?", "kind": "boundary", "id": "configuration-applicability-q02" } ] } ] } ] }, { "id": "airframe-propulsion-and-envelope", "name": "Airframe, propulsion and envelope", "description": "Describe the physical aircraft and the conditions governing its published performance and limitations.", "rationale": "MiG-31 recognition and support decisions depend on configuration-specific geometry, propulsion and high-speed operating limits.", "layers": [ { "id": "physical-installation", "name": "Physical installation", "description": "Connect dimensions, mass and installed propulsion to a defined aircraft configuration.", "findings": [ { "id": "geometry-and-propulsion-baseline", "name": "Geometry and propulsion baseline", "description": "Record dimensions and engine identity with conventions that permit valid comparison across MiG-31 references.", "questions": [ { "text": "What are the documented span, height and length, and does the stated length include probes or other projections?", "kind": "measurement", "id": "geometry-and-propulsion-baseline-q01" }, { "text": "Which engine model and modification standard are installed in each position, and what records establish that configuration?", "kind": "provenance", "id": "geometry-and-propulsion-baseline-q02" } ] } ] }, { "id": "qualified-flight-limits", "name": "Qualified flight limits", "description": "Keep operating restrictions distinct from demonstration results and generalized catalogue figures.", "findings": [ { "id": "envelope-with-conditions", "name": "Envelope with conditions", "description": "Attach altitude, loading, temperature, duration and configuration qualifications to every MiG-31 performance claim used in assessment.", "questions": [ { "text": "Which applicable reference defines speed, altitude and mass limits for the configuration being assessed?", "kind": "provenance", "id": "envelope-with-conditions-q01" }, { "text": "What loading, atmospheric conditions and time restrictions accompany each quoted speed or altitude figure?", "kind": "measurement", "id": "envelope-with-conditions-q02" } ] } ] } ] }, { "id": "crew-avionics-and-interfaces", "name": "Crew, avionics and interfaces", "description": "Record crew-station configuration and aircraft-level dependencies on installed electronic and external equipment.", "rationale": "A MiG-31's documented configuration cannot be established from the airframe alone, especially after modernization or conversion.", "layers": [ { "id": "crew-station-configuration", "name": "Crew-station configuration", "description": "Establish the installed controls, displays and crew-support provisions.", "findings": [ { "id": "station-functions-and-serviceability", "name": "Station functions and serviceability", "description": "Record the assigned functions and verified condition of each crew station without assuming that every configuration has identical equipment.", "questions": [ { "text": "Which functions and controls are assigned to each crew station in the applicable MiG-31 documentation?", "kind": "definition", "id": "station-functions-and-serviceability-q01" }, { "text": "What inspection evidence establishes the condition of cockpit displays, communication equipment, oxygen systems and escape-system provisions?", "kind": "provenance", "id": "station-functions-and-serviceability-q02" } ] } ] }, { "id": "electronic-and-external-interfaces", "name": "Electronic and external interfaces", "description": "Identify installed systems and supported interfaces without reproducing their independent models.", "findings": [ { "id": "equipment-compatibility-evidence", "name": "Equipment compatibility evidence", "description": "Separate fitted equipment, documented compatibility and current serviceability when characterizing a MiG-31.", "questions": [ { "text": "Which records establish the installed radar, navigation, identification and data-link equipment and their modification standards?", "kind": "provenance", "id": "equipment-compatibility-evidence-q01" }, { "text": "Which external-equipment interfaces are documented for this configuration, and which details belong in separate component models?", "kind": "boundary", "id": "equipment-compatibility-evidence-q02" } ] } ] } ] }, { "id": "condition-support-and-disposition", "name": "Condition, support and disposition", "description": "Translate aircraft-specific condition and support evidence into a bounded assessment of permissible activities.", "rationale": "An operational aircraft, stored airframe and museum MiG-31 may look similar while requiring different handling and authorization.", "layers": [ { "id": "life-and-maintenance-evidence", "name": "Life and maintenance evidence", "description": "Assess structural, propulsion and system condition against applicable maintenance requirements.", "findings": [ { "id": "remaining-life-and-support-status", "name": "Remaining life and support status", "description": "Require records for life consumption, inspections, repairs and support materials instead of inferring readiness from completeness.", "questions": [ { "text": "What flight-hour, cycle, engine-life and inspection records support the stated remaining life of this MiG-31?", "kind": "measurement", "id": "remaining-life-and-support-status-q01" }, { "text": "Which applicable maintenance documents identify inspection concerns, approved consumables and servicing equipment for its configuration?", "kind": "provenance", "id": "remaining-life-and-support-status-q02" } ] } ] }, { "id": "activity-eligibility", "name": "Activity eligibility", "description": "Distinguish evidence sufficient for display or movement from evidence required for powered operation or flight.", "findings": [ { "id": "authorized-condition-dependent-actions", "name": "Authorized condition-dependent actions", "description": "Tie each proposed action to verified aircraft condition, relevant technical instructions and the responsible authority.", "questions": [ { "text": "What evidence confirms the status of fuel, pressure systems, escape-system energetic components and any retained armament before handling or public display?", "kind": "provenance", "id": "authorized-condition-dependent-actions-q01" }, { "text": "Which authority and applicable technical document permit the proposed inspection, towing, servicing, powered operation or flight?", "kind": "action", "id": "authorized-condition-dependent-actions-q02" } ] } ] } ] }, { "id": "evidence-and-external-alignment", "name": "Evidence and external alignment", "description": "What the world already says about this thing, gathered so the model can be checked against it.", "rationale": "A model that cannot be lined up against existing standards, identifiers and practice cannot be adopted by anyone who already uses them.", "layers": [ { "id": "reported-evidence", "name": "Reported evidence", "description": "Findings from the breadth pass, kept separate from the structural claims.", "findings": [ { "id": "evidence-confidence-notes", "name": "Check these first", "description": "Recalled without web access and unsourced; every item is a lead to verify.", "evidence": [ "This is recalled information without source verification; dimensions and performance figures are approximate and principally describe interceptor configurations.", "Variant suffixes, equipment fits and retained interception capabilities should be checked against variant-specific documentation.", "Current fleet numbers, readiness, operator status and applicable military airworthiness requirements are not asserted." ], "questions": [ { "id": "evidence-confidence-notes-q01", "text": "Which of these check these first hold for the sense of Mikoyan MiG-31 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": [ "MiG-31: initial production interceptor", "MiG-31B: improved production interceptor", "MiG-31BS: earlier aircraft upgraded toward MiG-31B standard", "MiG-31BM: modernized interceptor with upgraded avionics and weapons integration", "MiG-31M: extensively revised development variant that did not enter series production", "MiG-31K: modified carrier aircraft for the Kinzhal air-launched ballistic missile" ], "questions": [ { "id": "evidence-kinds-q01", "text": "Which of these kinds and varieties hold for the sense of Mikoyan MiG-31 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": "Soviet/Russian aircraft designation", "value_or_pattern": "MiG-31 / МиГ-31, with variant suffixes", "note": "Identifies the aircraft type or variant, not an individual airframe." }, { "scheme": "NATO reporting name", "value_or_pattern": "Foxhound", "note": "Western reporting name for the MiG-31 aircraft family." } ], "questions": [ { "id": "evidence-identifiers-q01", "text": "Which of these identifiers and schemes hold for the sense of Mikoyan MiG-31 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": [ "Long-range interception of hostile aircraft and cruise missiles.", "Air defence over extensive territories, including northern approaches with sparse ground infrastructure.", "Coordinated interception using radar tracks and data links shared with other aircraft and ground control.", "Carriage and launch of Kinzhal missiles by specially modified variants." ], "questions": [ { "id": "evidence-real-world-use-q01", "text": "Which of these real-world use hold for the sense of Mikoyan MiG-31 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": "Approximately 22.7", "unit": "m" }, { "quantity": "Wingspan", "typical_range": "Approximately 13.5", "unit": "m" }, { "quantity": "Maximum takeoff mass", "typical_range": "Approximately 46,000-47,000, depending on variant", "unit": "kg" }, { "quantity": "Maximum speed at high altitude", "typical_range": "Approximately 2.8", "unit": "Mach" }, { "quantity": "Service ceiling", "typical_range": "Approximately 20,000-21,000", "unit": "m" }, { "quantity": "Crew complement", "typical_range": "2", "unit": "persons" } ], "questions": [ { "id": "evidence-measurements-q01", "text": "Which of these typical measurements hold for the sense of Mikoyan MiG-31 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": [ "Sustained high-speed flight produces substantial aerodynamic heating and imposes thermal limits on the airframe and systems.", "Engine malfunction, inlet-flow disruption or fire can cause loss of thrust and require an emergency response.", "High fuel consumption during afterburner use constrains endurance and diversion margins.", "Loss or degradation of radar, navigation or data-link functions reduces interception effectiveness.", "Aging airframes require inspection for fatigue, corrosion and deterioration of components." ], "questions": [ { "id": "evidence-failure-modes-and-hazards-q01", "text": "Which of these failure modes and hazards hold for the sense of Mikoyan MiG-31 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 type originated in the Soviet Union and subsequently served with Russian and Kazakh forces.", "Equipment, modernization level and mission configuration differ across operators and variants." ], "questions": [ { "id": "evidence-regional-variation-q01", "text": "Which of these regional variation hold for the sense of Mikoyan MiG-31 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": "Mikoyan-Gurevich MiG-25", "difference": "The MiG-25 is the predecessor design; the MiG-31 introduced a two-person operational crew, different engines and a substantially more capable interception radar and weapons system." }, { "name": "Interceptor aircraft", "difference": "An interceptor is a functional aircraft category; the MiG-31 is one particular aircraft type within it." }, { "name": "Individual MiG-31 airframe", "difference": "An individual airframe has its own serial number, maintenance history and configuration; this entry describes the aircraft family." }, { "name": "Kh-47M2 Kinzhal", "difference": "Kinzhal is a missile carried by specially modified MiG-31 aircraft, not the aircraft itself." } ], "questions": [ { "id": "evidence-neighbours-q01", "text": "Which of these neighbouring kinds and how to tell them apart hold for the sense of Mikoyan MiG-31 this model covers, and on what evidence?", "kind": "provenance" } ] } ] } ] } ] }, "openQuestions": [ "Which authoritative sources establish the production-variant and conversion taxonomy, including how prototypes and specialized conversions should be represented within this single registry entry?", "Which accessible flight and maintenance manuals provide revision-controlled dimensions, mass definitions, operating limits and consumable specifications for each included configuration?", "What reliable evidence distinguishes installed radar and avionics standards when published variant descriptions conflict or omit later modifications?", "Which documented structural, engine and system failure modes, life limits and storage effects should become MiG-31-specific condition checks?", "Which military airworthiness, maintenance-release and demilitarization requirements apply in each relevant jurisdiction, and what evidence permits assessment of an individual airframe?" ], "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 Mikoyan MiG-31, record what state it is in, and decide what may be done with it.", "whatItIs": "Enable an AI agent to identify a Mikoyan MiG-31, distinguish its documented configuration, assess evidence of its condition, and determine which inspection, support or preservation actions are appropriate.", "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: Mikojan-Gurevitj MiG-31BM.", "1 finer distinctions are held as aliases rather than separate entries, because telling them apart needs a task that asks for it.", "Described in 59 Wikipedia languages, which is a measure of how widely the thing is known, not of how important it is." ], "openQuestionsForResearch": [ "Which of the bundles below does a real task actually need, and which are ceremony?", "What does this thing have that the facets do not capture at all?", "Which neighbouring kind is most often confused with a Mikoyan MiG-31, 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 Mikoyan MiG-31 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": [ "Mikojan-Gurevitj MiG-31BM" ] } ], "standing": "Described in 59 Wikipedia languages, which measures how widely it is written about rather than how important or how common it is. 1 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 Mikoyan MiG-31 from another, and a Mikoyan MiG-31 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 Mikoyan MiG-31, 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 Mikoyan MiG-31, 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 Mikoyan MiG-31 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 Mikoyan MiG-31, 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 Mikoyan MiG-31, 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 Mikoyan MiG-31 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 Mikoyan MiG-31 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 Mikoyan MiG-31, 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 Mikoyan MiG-31, 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 Mikoyan MiG-31 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 Mikoyan MiG-31 from the things most often confused with it.", "questions": [ { "id": "distinguishing-features-q01", "text": "What identifies and describes what distinguishes a Mikoyan MiG-31, 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 Mikoyan MiG-31, 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 Mikoyan MiG-31 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 Mikoyan MiG-31 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 Mikoyan MiG-31, 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 Mikoyan MiG-31, 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 Mikoyan MiG-31 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 Mikoyan MiG-31 is built from and which parts are replaceable.", "questions": [ { "id": "parts-and-materials-q01", "text": "What identifies and describes the composition of a Mikoyan MiG-31, 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 Mikoyan MiG-31, 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 Mikoyan MiG-31 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 Mikoyan MiG-31 is judged and by whom.", "questions": [ { "id": "condition-assessment-q01", "text": "What identifies and describes the condition of a Mikoyan MiG-31, 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 Mikoyan MiG-31, 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 Mikoyan MiG-31 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 Mikoyan MiG-31 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 Mikoyan MiG-31 is, and what that position is measured against.", "questions": [ { "id": "position-and-frame-q01", "text": "What identifies and describes the location of a Mikoyan MiG-31, 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 Mikoyan MiG-31, 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 Mikoyan MiG-31 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 Mikoyan MiG-31 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 Mikoyan MiG-31, 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 Mikoyan MiG-31, 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 Mikoyan MiG-31 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 Mikoyan MiG-31 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 Mikoyan MiG-31 between them.", "questions": [ { "id": "stages-and-transitions-q01", "text": "What identifies and describes the lifecycle of a Mikoyan MiG-31, 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 Mikoyan MiG-31, 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 Mikoyan MiG-31 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 Mikoyan MiG-31, how often and by whom.", "findings": [ { "id": "observation-record", "name": "Observation record", "description": "How an observation of a Mikoyan MiG-31 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 Mikoyan MiG-31, 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 Mikoyan MiG-31, 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 Mikoyan MiG-31 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 Mikoyan MiG-31 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 Mikoyan MiG-31 is for, and what it is used for anyway.", "findings": [ { "id": "function-and-purpose", "name": "Function, purpose and misuse", "description": "The function a Mikoyan MiG-31 performs and the uses that fall outside it.", "questions": [ { "id": "function-and-purpose-q01", "text": "What identifies and describes the use of a Mikoyan MiG-31, 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 Mikoyan MiG-31, 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 Mikoyan MiG-31 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 Mikoyan MiG-31.", "findings": [ { "id": "procedures-and-skills", "name": "Procedures, skills and required tools", "description": "What an agent needs before it can act on a Mikoyan MiG-31 at all.", "questions": [ { "id": "procedures-and-skills-q01", "text": "What identifies and describes handling a Mikoyan MiG-31, 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 Mikoyan MiG-31, 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 Mikoyan MiG-31 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 Mikoyan MiG-31 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 Mikoyan MiG-31 and how confident it is.", "questions": [ { "id": "claim-provenance-q01", "text": "What identifies and describes a claim about a Mikoyan MiG-31, 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 Mikoyan MiG-31, 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 Mikoyan MiG-31 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 Mikoyan MiG-31 is retired without being erased.", "questions": [ { "id": "validity-and-supersession-q01", "text": "What identifies and describes the validity of a claim about a Mikoyan MiG-31, 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 Mikoyan MiG-31, 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 Mikoyan MiG-31 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 } } } }