{ "model": { "rank": 4957, "code": "thing-q150609", "model_id": "vr.tr.mikoyan-gurevich-mig-21", "name": "Mikoyan-Gurevich MiG-21", "purpose": "Enable an AI agent to identify the Mikoyan-Gurevich MiG-21 aircraft family, distinguish its configurations, assess documented condition, and determine which uses require further evidence or authorization.", "family": "Thing Registry", "category": "Physical world and living systems", "status": "research-draft", "kind": "thing", "plane": "PHY", "domain": "PHY.OBJ", "industry": "", "version": "", "url": "/models/thing/q150609/", "tier": 2, "score": 71, "payload": { "layer": "wikidata", "aliases": [ "Ye-50", "The MiG 21 F96, No. 5121", "The MiG-21-F94 No. 4324", "MiG-21MF", "Ye-2", "MiG-21", "MiG-21F", "MiG-21F-13", "MiG-21PF", "MiG-21PFM", "MiG-21R", "Mikojan-Gurevitj MiG-21S", "MiG-21bis", "MiG-21U", "Ye-5", "Chengdu J-7", "S-106", "Ye-2A", "Chengdu J-7-II", "F-7A", "Chengdu JJ-7", "J-7-II", "J-7-III", "J-7B", "Chengdu J-7E", "Chengdu J-7G", "Chengdu F-7" ], "aliasCount": 27, "merged": 27, "knownIn": 71, "facets": null, "markers": [], "lexicalClass": "", "senseRank": null, "alsoRegisteredAs": null, "source": { "dataset": "wikidata", "item": "Q150609", "url": "https://www.wikidata.org/wiki/Q150609", "license": "CC0 1.0" } }, "research": { "vercy": "1.0-draft", "publication": { "status": "research-draft", "adjudicationStatus": "unreviewed", "publishableCanonical": false, "generatedAt": "2026-09-09T21:21:28Z", "providers": [ "Codex" ], "breadth": "recalled by Codex without web access - no source was read", "missingProviders": [], "pass": 2, "cost": { "grok": { "seconds": 25.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: 01a0880b-1947-76a1-9889-9785d795e4be\n--------\nuser\nDescribe what is already known about one registered thing. Answer as JSON only, no prose around it.\n\nThing: Mikoyan-Gurevich MiG-21\nSense to describe: (none recorded)\nDomain code: PHY.OBJ\nAlso known as: (none)\n\n\nContext for this batch of 1001 things:\n# Batch 0", "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: 01a0880b-1952-7e30-8fa5-7375c5f56359\n--------\nuser\nYou are drafting a Vercy meta-model for one registered thing. Answer as JSON only, no prose around it.\n\nThing: Mikoyan-Gurevich MiG-21\nRegistry id: vr.tr.mikoyan-gurevich-mig-21\nPlane / domain: PHY / PHY.OBJ\nRegistry definition: (none recorded)\nNames folded in" } } }, "metaModel": { "id": "THING-Q150609", "registryId": "vr.tr.mikoyan-gurevich-mig-21", "name": "Mikoyan-Gurevich MiG-21", "version": "0.1.0-research.1", "entryKind": "thing", "family": "Thing Registry", "domain": [ "PHY.OBJ" ], "status": "research-draft" }, "canonicalUrl": "https://ver.cy/models/thing/q150609/", "model": { "registry_id": "vr.tr.mikoyan-gurevich-mig-21", "name": "Mikoyan-Gurevich MiG-21", "purpose": "Enable an AI agent to identify the Mikoyan-Gurevich MiG-21 aircraft family, distinguish its configurations, assess documented condition, and determine which uses require further evidence or authorization.", "definition": "The Mikoyan-Gurevich MiG-21 is a Soviet-designed family of single-engine, delta-wing supersonic military jet aircraft developed primarily for fighter and interceptor duties, with reconnaissance and two-seat training variants.", "scope_statement": "This model owns the MiG-21 as a registered aircraft design family within PHY / PHY.OBJ, including distinctions needed to interpret variant and individual-airframe records without treating the family as one fixed configuration.", "in_scope": [ "MiG-21 family identity, variant designations, production provenance, and boundaries with related aircraft", "Characteristic airframe geometry, propulsion architecture, and configuration-dependent limitations", "Single-seat and two-seat configurations, cockpit equipment, avionics, and documented modifications", "Evidence needed to assess airframe completeness, maintenance status, and permitted use", "Variant-specific dimensions, capacities, and performance claims with their measurement conditions" ], "out_of_scope": [ "The general model of fighter aircraft or supersonic flight", "Individual aircraft ownership, flight logs, and maintenance transactions as standalone records", "Detailed models of engines, ejection seats, radar equipment, and weapons fitted to the aircraft", "Combat employment, targeting, and weapon-release procedures", "Histories of operators, military units, campaigns, or the manufacturer", "Related aircraft designs treated automatically as MiG-21 variants without establishing the registry boundary" ], "distinguishing_features": [ "Check the combination of a delta wing, separate horizontal tail, single jet engine, and nose intake with a central cone; this supports identification but cannot alone establish MiG-21 provenance.", "Distinguish the MiG-21's delta wing from the swept-wing layout of earlier MiG fighter families, using drawings or clearly documented photographs.", "Resolve visually similar Chengdu J-7/F-7 aircraft through manufacturer and designation evidence rather than silhouette alone.", "Use canopy arrangement, dorsal spine, intake details, and equipment records together to distinguish variants; no single visible feature should determine the complete configuration.", "Separate an aircraft's original production designation from its later upgrade designation and from names assigned by foreign identification systems." ], "characteristics": [ { "name": "Documented variant designation", "kind": "category", "unit_or_values": "Exact designation, designation system, supporting source, or unresolved", "why_it_matters": "Equipment, dimensions, limitations, and maintenance requirements cannot safely be assigned at family level." }, { "name": "Production and modification lineage", "kind": "relation", "unit_or_values": "Design organization, manufacturer, production record, original variant, and documented upgrade lineage", "why_it_matters": "Distinguishes production identity from later modifications and related designs." }, { "name": "Crew configuration", "kind": "category", "unit_or_values": "Single-seat; tandem two-seat; other documented configuration; unresolved", "why_it_matters": "Changes the interpretation of cockpit layout, training function, and installed equipment." }, { "name": "Airframe geometry", "kind": "measurement", "unit_or_values": "Length and wingspan in m; wing area in m²; measurement convention and variant required", "why_it_matters": "Supports identification and handling planning while preventing incompatible published dimensions from being merged." }, { "name": "Installed propulsion configuration", "kind": "relation", "unit_or_values": "Engine designation, installation applicability, and evidence of replacement or modification", "why_it_matters": "Connects the airframe to the correct performance and maintenance documentation." }, { "name": "Mass and fuel basis", "kind": "measurement", "unit_or_values": "Mass in kg; fuel capacity in L or kg with density basis; internal and external capacity distinguished", "why_it_matters": "Published values depend on variant, loading definition, and external tanks." }, { "name": "Flight-envelope evidence", "kind": "measurement", "unit_or_values": "Mach number, speed with reference convention, altitude in m, and applicable configuration and conditions", "why_it_matters": "Separates demonstrated performance, published maxima, and authorized operating limits." }, { "name": "Avionics and cockpit fit", "kind": "relation", "unit_or_values": "Documented radar or other nose equipment, navigation, communication, instruments, and upgrade package", "why_it_matters": "The MiG-21 designation alone does not establish the aircraft's sensing or cockpit capabilities." }, { "name": "Physical and administrative status", "kind": "state", "unit_or_values": "Physical: unknown, incomplete, preserved, under maintenance, assessed serviceable; administrative: documented permitted uses and restrictions", "why_it_matters": "Physical completeness, technical serviceability, and permission to fly require separate evidence." } ], "affordances": [ "Classify a documented aircraft or exhibit within the MiG-21 family and flag unresolved variant identity.", "Compare claimed configurations against variant references and modification records.", "Retrieve applicable technical references using variant, engine, and equipment identities.", "Identify missing evidence before accepting performance, serviceability, or flight-eligibility claims.", "Support preservation, inspection, and display planning by identifying configuration-dependent hazards and specialist requirements." ] }, "sources": [], "structure": { "bundles": [ { "id": "identity-and-lineage", "name": "Identity and lineage", "description": "Establish what the MiG-21 registry entry includes and how designations connect to production and modification histories.", "rationale": "Similar appearance and overlapping naming systems can cause related designs or upgraded airframes to be assigned the wrong identity.", "layers": [ { "id": "family-boundary", "name": "Family boundary", "description": "Separate the registered family from broader fighter categories and related aircraft.", "findings": [ { "id": "related-design-membership", "name": "Related-design membership requires evidence", "description": "Treat family membership as a documented relationship, particularly for licensed production and derivative designs.", "questions": [ { "text": "What authoritative definition establishes the MiG-21 family's included designations?", "kind": "definition", "id": "related-design-membership-q01" }, { "text": "Where should the boundary with Chengdu J-7/F-7 and other related designs fall under the registry's existing granularity?", "kind": "boundary", "id": "related-design-membership-q02" } ] } ] }, { "id": "designation-and-provenance", "name": "Designation and provenance", "description": "Connect original manufacture, alternate names, and subsequent upgrades.", "findings": [ { "id": "original-and-modified-identity", "name": "Original and modified identity", "description": "Preserve the distinction between a production variant and a later configuration designation.", "questions": [ { "text": "Which manufacturer records or identification documents establish the original variant and production origin?", "kind": "provenance", "id": "original-and-modified-identity-q01" }, { "text": "Which documented upgrades changed the aircraft's designation or equipment while retaining its underlying airframe identity?", "kind": "provenance", "id": "original-and-modified-identity-q02" } ] } ] } ] }, { "id": "airframe-and-flight-envelope", "name": "Airframe and flight envelope", "description": "Describe MiG-21 geometry and interpret performance through the correct variant and configuration.", "rationale": "The recognizable delta-wing form does not justify assigning identical dimensions or flight limits across the family.", "layers": [ { "id": "recognition-geometry", "name": "Recognition geometry", "description": "Use external form to support identification and detect inconsistencies.", "findings": [ { "id": "configuration-sensitive-recognition", "name": "Configuration-sensitive recognition", "description": "Combine wing, tail, intake, canopy, and dorsal-spine observations with documentary evidence.", "questions": [ { "text": "Which visible features distinguish the candidate MiG-21 variant from its closest alternatives?", "kind": "definition", "id": "configuration-sensitive-recognition-q01" }, { "text": "What are its documented dimensions, and does the stated length include projecting probes?", "kind": "measurement", "id": "configuration-sensitive-recognition-q02" } ] } ] }, { "id": "performance-applicability", "name": "Performance applicability", "description": "Attach mass, speed, altitude, and endurance claims to their stated conditions.", "findings": [ { "id": "conditional-performance-values", "name": "Conditional performance values", "description": "Keep reference performance separate from operating limitations and from claims about a particular surviving aircraft.", "questions": [ { "text": "Which variant, engine, loading, altitude, and external configuration underlie each quoted performance value?", "kind": "measurement", "id": "conditional-performance-values-q01" }, { "text": "Which approved reference establishes the applicable operating limits rather than an advertised or demonstrated maximum?", "kind": "provenance", "id": "conditional-performance-values-q02" } ] } ] } ] }, { "id": "propulsion-intake-and-fuel", "name": "Propulsion, intake, and fuel", "description": "Connect the single-engine installation, nose-intake configuration, and fuel system to the appropriate technical evidence.", "rationale": "Engine and fuel differences materially affect how MiG-21 configurations are compared and maintained.", "layers": [ { "id": "engine-and-intake-installation", "name": "Engine and intake installation", "description": "Identify the installed propulsion equipment and its compatible airframe configuration.", "findings": [ { "id": "propulsion-configuration-match", "name": "Propulsion configuration match", "description": "Require installation evidence before applying engine specifications or intake-system descriptions to a variant.", "questions": [ { "text": "Which engine designation and installation standard are documented for this variant or modified configuration?", "kind": "provenance", "id": "propulsion-configuration-match-q01" }, { "text": "Which source describes the applicable nose-intake and central-cone arrangement and its relationship to the engine?", "kind": "definition", "id": "propulsion-configuration-match-q02" } ] } ] }, { "id": "fuel-capacity-and-support", "name": "Fuel capacity and support", "description": "Distinguish internal capacity, external tanks, and approved consumables.", "findings": [ { "id": "fuel-configuration-accounting", "name": "Fuel configuration accounting", "description": "Interpret capacity and endurance only with an explicit fuel and tank configuration.", "questions": [ { "text": "What usable internal fuel capacity is documented, and how are external tanks accounted for separately?", "kind": "measurement", "id": "fuel-configuration-accounting-q01" }, { "text": "Which applicable technical documents identify approved fuels, lubricants, and servicing requirements?", "kind": "provenance", "id": "fuel-configuration-accounting-q02" } ] } ] } ] }, { "id": "crew-and-installed-systems", "name": "Crew and installed systems", "description": "Represent cockpit arrangement, avionics, and equipment changes without assuming a universal MiG-21 fit.", "rationale": "Trainer configurations and modernization programs can substantially change the systems associated with the same family name.", "layers": [ { "id": "cockpit-and-crew-configuration", "name": "Cockpit and crew configuration", "description": "Distinguish seating layout, controls, and crew-safety equipment.", "findings": [ { "id": "crew-layout-applicability", "name": "Crew-layout applicability", "description": "Connect cockpit interpretation to the exact single-seat or two-seat configuration.", "questions": [ { "text": "What seating and control arrangement identifies this configuration, and what role is documented for each crew position?", "kind": "definition", "id": "crew-layout-applicability-q01" }, { "text": "Which canopy and escape-system references apply to its documented production or modification standard?", "kind": "provenance", "id": "crew-layout-applicability-q02" } ] } ] }, { "id": "avionics-and-modifications", "name": "Avionics and modifications", "description": "Identify installed sensing, navigation, communication, and display equipment.", "findings": [ { "id": "equipment-fit-evidence", "name": "Equipment-fit evidence", "description": "Derive capability descriptions from documented installed equipment rather than the family designation.", "questions": [ { "text": "Which radar or alternative nose equipment, navigation systems, radios, and instruments are documented for this configuration?", "kind": "provenance", "id": "equipment-fit-evidence-q01" }, { "text": "Which capability claims belong to an upgrade package rather than to the original MiG-21 variant?", "kind": "boundary", "id": "equipment-fit-evidence-q02" } ] } ] } ] }, { "id": "condition-and-permitted-use", "name": "Condition and permitted use", "description": "Define evidence needed to distinguish a preserved MiG-21 from a complete, serviceable, or flight-authorized aircraft.", "rationale": "A recognizable surviving airframe may have missing systems, exhausted life limits, or unresolved hazardous components.", "layers": [ { "id": "maintenance-and-life-status", "name": "Maintenance and life status", "description": "Relate condition judgments to applicable inspection and component-life records.", "findings": [ { "id": "serviceability-evidence", "name": "Serviceability evidence", "description": "Require documented technical assessment rather than inferring readiness from appearance or restoration claims.", "questions": [ { "text": "Which airframe, engine, and life-limited component records are required by the applicable maintenance regime?", "kind": "provenance", "id": "serviceability-evidence-q01" }, { "text": "Which inspection findings or missing records prevent a supported judgment of serviceability?", "kind": "action", "id": "serviceability-evidence-q02" } ] } ] }, { "id": "display-handling-and-flight-status", "name": "Display, handling, and flight status", "description": "Separate technical condition, residual hazards, and administrative authorization.", "findings": [ { "id": "use-specific-clearance", "name": "Use-specific clearance", "description": "Assess proposed display, access, ground handling, or flight against evidence specific to that activity.", "questions": [ { "text": "What specialist evidence establishes the status of escape-system cartridges, pressure systems, fuel residues, and any retained armament before public access or handling?", "kind": "action", "id": "use-specific-clearance-q01" }, { "text": "Which authority and documents govern the proposed use of this aircraft in its present jurisdiction and configuration?", "kind": "action", "id": "use-specific-clearance-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 knowledge, without consulted sources; verify specifications against documentation for the exact variant.", "Performance depends on altitude, payload, fuel state and configuration; the figures given are approximate family-level indications.", "Variant-specific maintenance requirements, airworthiness rules and current service status require separate verification." ], "questions": [ { "id": "evidence-confidence-notes-q01", "text": "Which of these check these first hold for the sense of Mikoyan-Gurevich MiG-21 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-21F-13 early production fighter", "MiG-21PF radar-equipped interceptor", "MiG-21PFM improved interceptor", "MiG-21MF multirole fighter", "MiG-21bis later production fighter", "MiG-21UM two-seat conversion trainer" ], "questions": [ { "id": "evidence-kinds-q01", "text": "Which of these kinds and varieties hold for the sense of Mikoyan-Gurevich MiG-21 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 aircraft design designation", "value_or_pattern": "MiG-21, followed by a variant suffix", "note": "Identifies an aircraft family and its variants, rather than an individual airframe." }, { "scheme": "NATO reporting name", "value_or_pattern": "Fishbed", "note": "Applied to single-seat MiG-21 variants, with suffix letters distinguishing versions." }, { "scheme": "NATO reporting name", "value_or_pattern": "Mongol", "note": "Applied to two-seat MiG-21 trainers." } ], "questions": [ { "id": "evidence-identifiers-q01", "text": "Which of these identifiers and schemes hold for the sense of Mikoyan-Gurevich MiG-21 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": [ "Air defence interception and combat air patrol.", "Air-to-air combat using variant-dependent cannon and missile armament.", "Ground attack using bombs and unguided rockets.", "Tactical reconnaissance using dedicated variants or equipment.", "Pilot conversion and continuation training using two-seat variants." ], "questions": [ { "id": "evidence-real-world-use-q01", "text": "Which of these real-world use hold for the sense of Mikoyan-Gurevich MiG-21 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": "Wingspan of common production variants", "typical_range": "Approximately 7.15", "unit": "m" }, { "quantity": "Maximum speed at altitude", "typical_range": "Approximately 2,000-2,200, depending on variant and configuration", "unit": "km/h" }, { "quantity": "Service ceiling", "typical_range": "Approximately 17,000-19,000, depending on variant", "unit": "m" }, { "quantity": "Crew", "typical_range": "1 for fighters; 2 for trainers", "unit": "persons" } ], "questions": [ { "id": "evidence-measurements-q01", "text": "Which of these typical measurements hold for the sense of Mikoyan-Gurevich MiG-21 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": [ "Engine failure or flameout removes the aircraft's sole source of propulsive thrust.", "Limited fuel endurance and high afterburner consumption create fuel-exhaustion risks if reserves are mismanaged.", "High approach and landing speeds increase runway-overrun and landing-accident risks.", "High-angle-of-attack manoeuvring can produce rapid energy loss and departure from controlled flight.", "Ageing airframes, corrosion and fatigue can compromise structural integrity without inspection and maintenance." ], "questions": [ { "id": "evidence-failure-modes-and-hazards-q01", "text": "Which of these failure modes and hazards hold for the sense of Mikoyan-Gurevich MiG-21 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 aircraft was manufactured in the Soviet Union and under licence in India and Czechoslovakia.", "Operators introduced differing avionics, weapons and upgrade packages, including India's MiG-21 Bison and Romania's MiG-21 LanceR.", "China developed the related Chengdu J-7 family, exported as the F-7; these should be distinguished from Soviet-built and other licence-built MiG-21 aircraft." ], "questions": [ { "id": "evidence-regional-variation-q01", "text": "Which of these regional variation hold for the sense of Mikoyan-Gurevich MiG-21 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": "Jet fighter", "difference": "The broader aircraft category; MiG-21 denotes a specific design family within it." }, { "name": "MiG-21bis", "difference": "A particular production variant within the MiG-21 family, with its own engine and equipment configuration." }, { "name": "Chengdu J-7", "difference": "A Chinese aircraft family derived from the MiG-21 design, with separate designations and subsequent development." }, { "name": "Mikoyan-Gurevich MiG-23", "difference": "A separate fighter family distinguished by variable-sweep wings rather than the MiG-21's fixed delta wing." }, { "name": "Individual MiG-21 airframe", "difference": "A physical aircraft identified by construction and service records; this entry describes the design family." } ], "questions": [ { "id": "evidence-neighbours-q01", "text": "Which of these neighbouring kinds and how to tell them apart hold for the sense of Mikoyan-Gurevich MiG-21 this model covers, and on what evidence?", "kind": "provenance" } ] } ] } ] } ] }, "openQuestions": [ "Which authoritative variant taxonomy should anchor the model, and how should inconsistent translated or export designations be reconciled?", "Does the existing registry or world-model catalogue place licensed production and J-7/F-7 derivatives inside this entry or in linked entries?", "Which primary technical references establish variant-specific dimensions, usable fuel capacities, engine installations, and operating limitations?", "Which documented MiG-21 failure modes, inspection priorities, and component-life rules can be stated with clear applicability rather than generalized across the family?", "Which jurisdiction-specific military, civil, experimental, or museum requirements govern surviving examples, and what evidence demonstrates compliance for each intended use?" ], "statistics": { "bundles": 6, "layers": 11, "findings": 18, "questions": 28 } }, "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-Gurevich MiG-21, record what state it is in, and decide what may be done with it.", "whatItIs": "Enable an AI agent to identify the Mikoyan-Gurevich MiG-21 aircraft family, distinguish its configurations, assess documented condition, and determine which uses require further evidence or authorization.", "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: Ye-50, The MiG 21 F96, No. 5121, The MiG-21-F94 No. 4324, MiG-21MF, Ye-2, MiG-21, MiG-21F, MiG-21F-13, MiG-21PF, MiG-21PFM, MiG-21R, Mikojan-Gurevitj MiG-21S.", "27 finer distinctions are held as aliases rather than separate entries, because telling them apart needs a task that asks for it.", "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 Mikoyan-Gurevich MiG-21, 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-Gurevich MiG-21 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": [ "Ye-50", "The MiG 21 F96, No. 5121", "The MiG-21-F94 No. 4324", "MiG-21MF", "Ye-2", "MiG-21", "MiG-21F", "MiG-21F-13", "MiG-21PF", "MiG-21PFM", "MiG-21R", "Mikojan-Gurevitj MiG-21S" ] } ], "standing": "Described in 71 Wikipedia languages, which measures how widely it is written about rather than how important or how common it is. 27 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-Gurevich MiG-21 from another, and a Mikoyan-Gurevich MiG-21 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-Gurevich MiG-21, 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-Gurevich MiG-21, 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-Gurevich MiG-21 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-Gurevich MiG-21, 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-Gurevich MiG-21, 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-Gurevich MiG-21 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-Gurevich MiG-21 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-Gurevich MiG-21, 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-Gurevich MiG-21, 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-Gurevich MiG-21 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-Gurevich MiG-21 from the things most often confused with it.", "questions": [ { "id": "distinguishing-features-q01", "text": "What identifies and describes what distinguishes a Mikoyan-Gurevich MiG-21, 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-Gurevich MiG-21, 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-Gurevich MiG-21 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-Gurevich MiG-21 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-Gurevich MiG-21, 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-Gurevich MiG-21, 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-Gurevich MiG-21 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-Gurevich MiG-21 is built from and which parts are replaceable.", "questions": [ { "id": "parts-and-materials-q01", "text": "What identifies and describes the composition of a Mikoyan-Gurevich MiG-21, 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-Gurevich MiG-21, 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-Gurevich MiG-21 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-Gurevich MiG-21 is judged and by whom.", "questions": [ { "id": "condition-assessment-q01", "text": "What identifies and describes the condition of a Mikoyan-Gurevich MiG-21, 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-Gurevich MiG-21, 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-Gurevich MiG-21 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-Gurevich MiG-21 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-Gurevich MiG-21 is, and what that position is measured against.", "questions": [ { "id": "position-and-frame-q01", "text": "What identifies and describes the location of a Mikoyan-Gurevich MiG-21, 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-Gurevich MiG-21, 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-Gurevich MiG-21 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-Gurevich MiG-21 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-Gurevich MiG-21, 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-Gurevich MiG-21, 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-Gurevich MiG-21 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-Gurevich MiG-21 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-Gurevich MiG-21 between them.", "questions": [ { "id": "stages-and-transitions-q01", "text": "What identifies and describes the lifecycle of a Mikoyan-Gurevich MiG-21, 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-Gurevich MiG-21, 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-Gurevich MiG-21 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-Gurevich MiG-21, how often and by whom.", "findings": [ { "id": "observation-record", "name": "Observation record", "description": "How an observation of a Mikoyan-Gurevich MiG-21 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-Gurevich MiG-21, 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-Gurevich MiG-21, 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-Gurevich MiG-21 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-Gurevich MiG-21 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-Gurevich MiG-21 is for, and what it is used for anyway.", "findings": [ { "id": "function-and-purpose", "name": "Function, purpose and misuse", "description": "The function a Mikoyan-Gurevich MiG-21 performs and the uses that fall outside it.", "questions": [ { "id": "function-and-purpose-q01", "text": "What identifies and describes the use of a Mikoyan-Gurevich MiG-21, 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-Gurevich MiG-21, 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-Gurevich MiG-21 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-Gurevich MiG-21.", "findings": [ { "id": "procedures-and-skills", "name": "Procedures, skills and required tools", "description": "What an agent needs before it can act on a Mikoyan-Gurevich MiG-21 at all.", "questions": [ { "id": "procedures-and-skills-q01", "text": "What identifies and describes handling a Mikoyan-Gurevich MiG-21, 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-Gurevich MiG-21, 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-Gurevich MiG-21 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-Gurevich MiG-21 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-Gurevich MiG-21 and how confident it is.", "questions": [ { "id": "claim-provenance-q01", "text": "What identifies and describes a claim about a Mikoyan-Gurevich MiG-21, 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-Gurevich MiG-21, 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-Gurevich MiG-21 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-Gurevich MiG-21 is retired without being erased.", "questions": [ { "id": "validity-and-supersession-q01", "text": "What identifies and describes the validity of a claim about a Mikoyan-Gurevich MiG-21, 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-Gurevich MiG-21, 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-Gurevich MiG-21 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 } } } }