{ "model": { "rank": 4704, "code": "thing-q130681", "model_id": "vr.tr.mikoyan-mig-29", "name": "Mikoyan MiG-29", "purpose": "Enable an AI agent to identify a Mikoyan MiG-29 configuration, assess the evidence for an aircraft's condition, and determine which uses require further technical or operating 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/q130681/", "tier": 2, "score": 73, "payload": { "layer": "wikidata", "aliases": [ "MiG-29UB", "MiG-29K", "Mikojan-Gurevitj MiG-29SMT", "MiG-29A", "MiG-29B", "MiG-29S", "MiG-29SE", "MiG-29N", "Mikoyan MiG-35", "MiG-29MU1", "Mikoyan MiG-29M", "MiG-29BM", "MiG-29OVT" ], "aliasCount": 13, "merged": 14, "knownIn": 73, "facets": null, "markers": [], "lexicalClass": "", "senseRank": null, "alsoRegisteredAs": null, "source": { "dataset": "wikidata", "item": "Q130681", "url": "https://www.wikidata.org/wiki/Q130681", "license": "CC0 1.0" } }, "research": { "vercy": "1.0-draft", "publication": { "status": "research-draft", "adjudicationStatus": "unreviewed", "publishableCanonical": false, "generatedAt": "2026-09-09T20:49:23Z", "providers": [ "Codex" ], "breadth": "recalled by Codex without web access - no source was read", "missingProviders": [], "pass": 2, "cost": { "grok": { "seconds": 24.6, "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: 01a087ed-afb7-7ad3-927a-c1c736a39197\n--------\nuser\nDescribe what is already known about one registered thing. Answer as JSON only, no prose around it.\n\nThing: Mikoyan MiG-29\nSense to describe: (none recorded)\nDomain code: PHY.OBJ\nAlso known as: (none)\n\n\nContext for this batch of 1001 things:\n# Batch 005: 1001 ", "usd": 0, "recall": true }, "codex": { "seconds": 67.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: 01a087ed-afb2-76c0-acd6-9d9471b98d1e\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-29\nRegistry id: vr.tr.mikoyan-mig-29\nPlane / domain: PHY / PHY.OBJ\nRegistry definition: (none recorded)\nNames folded into this entry: (no" } } }, "metaModel": { "id": "THING-Q130681", "registryId": "vr.tr.mikoyan-mig-29", "name": "Mikoyan MiG-29", "version": "0.1.0-research.1", "entryKind": "thing", "family": "Thing Registry", "domain": [ "PHY.OBJ" ], "status": "research-draft" }, "canonicalUrl": "https://ver.cy/models/thing/q130681/", "model": { "registry_id": "vr.tr.mikoyan-mig-29", "name": "Mikoyan MiG-29", "purpose": "Enable an AI agent to identify a Mikoyan MiG-29 configuration, assess the evidence for an aircraft's condition, and determine which uses require further technical or operating authorization.", "definition": "The Mikoyan MiG-29 is a Soviet-designed family of twin-engine supersonic tactical fighter aircraft, originally developed primarily for air-to-air combat and subsequently adapted for multirole and carrier-based operations.", "scope_statement": "This model owns the configuration-aware description of the Mikoyan MiG-29 aircraft family within registry entry vr.tr.mikoyan-mig-29, distinguishing family identity, documented variants and individual airframes without creating separate registry entries.", "in_scope": [ "MiG-29 family identity, variant designations and configuration lineage", "Airframe, propulsion, fuel and flight-control characteristics tied to an identified configuration", "Installed avionics, mission equipment and documented role limitations", "Airframe condition, maintenance evidence and remaining service-life constraints", "Configuration-specific operating authority and suitability for flight, training, storage or display" ], "out_of_scope": [ "Fighter aircraft as a general category", "Mikoyan as an aircraft-design organization", "Standalone models of engines, radars, weapons and support equipment", "Pilot qualifications and military-unit organization", "Combat tactics, targeting and weapon-employment procedures", "Individual airframes as separate catalogue concepts" ], "distinguishing_features": [ "Require documentary identification as a MiG-29 configuration; twin engines and twin vertical tails alone do not distinguish it from other fighters.", "Use the combined arrangement of widely spaced engines, under-fuselage intakes, twin vertical tails and wing-root extensions as a visual consistency check against the documented identity.", "Distinguish single-seat and tandem-seat configurations through cockpit arrangement and the corresponding variant documentation; do not assume identical mission equipment.", "Distinguish original, substantially redesigned and upgraded configurations through manufacturer designation and modification records, rather than treating the MiG-29 name as a uniform technical specification.", "Resolve aircraft marketed or designated under related names through documented lineage and registry boundaries, rather than visual resemblance alone." ], "characteristics": [ { "name": "Documented variant and modification baseline", "kind": "category", "unit_or_values": "Manufacturer designation, operator designation and dated modification standard; unknown where unverified", "why_it_matters": "Determines which technical descriptions and limitations apply." }, { "name": "Airframe identity", "kind": "relation", "unit_or_values": "Links to manufacturer serial number, operator identifiers and supporting records", "why_it_matters": "Separates evidence about one aircraft from claims about the entire family." }, { "name": "Cockpit configuration", "kind": "category", "unit_or_values": "Single-seat or tandem two-seat, with documented variant", "why_it_matters": "Helps distinguish configurations and assess supported crew and training roles." }, { "name": "Engine installation", "kind": "relation", "unit_or_values": "Two installed engines, each linked to its documented type, modification standard and service record", "why_it_matters": "Family-level engine assumptions cannot establish an individual aircraft's propulsion configuration or condition." }, { "name": "Dimensions and mass limits", "kind": "measurement", "unit_or_values": "Length, span and height in m; defined empty mass and authorized mass limits in kg", "why_it_matters": "Supports identification and infrastructure compatibility only when the variant and measurement definitions are known." }, { "name": "Fuel configuration", "kind": "category", "unit_or_values": "Documented internal storage, approved external tanks and refuelling provisions", "why_it_matters": "Fuel arrangements and supported missions must not be generalized across configurations." }, { "name": "Sensor and avionics baseline", "kind": "relation", "unit_or_values": "Links to installed radar, electro-optical equipment, navigation, communications and identification systems", "why_it_matters": "External appearance and aircraft designation do not establish installed capability." }, { "name": "Recorded life consumption", "kind": "measurement", "unit_or_values": "Flight hours, cycles and calendar age, each associated with the applicable component and approved limit", "why_it_matters": "Different life measures constrain different structures and components." }, { "name": "Technical condition", "kind": "state", "unit_or_values": "Serviceable, restricted, under maintenance, stored, display-only or unknown, with evidence date", "why_it_matters": "Prevents an intact-looking aircraft from being assumed fit for flight." }, { "name": "Operating authorization", "kind": "relation", "unit_or_values": "Responsible authority, governing document, permitted use, restrictions and validity period", "why_it_matters": "Technical capability alone does not authorize operation." } ], "affordances": [ "Match a claimed MiG-29 identity to documentary and visual evidence while flagging inconsistent identifiers.", "Compare documented configurations and isolate which capabilities belong to each variant or upgrade.", "Identify missing records that prevent a defensible assessment of serviceability or remaining life.", "Assess compatibility with storage, display and ground-support arrangements using verified dimensions and requirements.", "Route proposed flight, maintenance or restoration work to the applicable documentation and responsible authority." ] }, "sources": [], "structure": { "bundles": [ { "id": "identity-and-configuration", "name": "Identity and configuration", "description": "Establish what the MiG-29 name denotes in each record and which technical baseline applies.", "rationale": "The registry covers a named aircraft family whose variants, upgrades and individual examples must remain distinguishable.", "layers": [ { "id": "family-boundary", "name": "Family boundary", "description": "Define the relationship between the registered MiG-29 concept and related aircraft designations.", "findings": [ { "id": "designation-evidence", "name": "Designation evidence", "description": "Require evidence for family membership without treating every related designation as a synonym.", "questions": [ { "text": "Which manufacturer and operator designations are explicitly documented as MiG-29 variants?", "kind": "definition", "id": "designation-evidence-q01" }, { "text": "Where does the registry place related names such as MiG-35, and which relationships should be represented without merging their identities?", "kind": "boundary", "id": "designation-evidence-q02" } ] } ] }, { "id": "airframe-baseline", "name": "Airframe baseline", "description": "Connect an aircraft's identity to its original configuration and subsequent modifications.", "findings": [ { "id": "configuration-traceability", "name": "Configuration traceability", "description": "Separate manufacturer identity, changing operator markings and the currently evidenced equipment standard.", "questions": [ { "text": "Which serial-number records establish this airframe's original MiG-29 configuration?", "kind": "provenance", "id": "configuration-traceability-q01" }, { "text": "Which accepted modification records establish its present baseline, and do they resolve discrepancies with visible features?", "kind": "provenance", "id": "configuration-traceability-q02" } ] } ] } ] }, { "id": "airframe-propulsion-and-flight", "name": "Airframe, propulsion and flight", "description": "Describe the physical and functional systems that determine configuration-specific aircraft limits.", "rationale": "MiG-29 geometry, propulsion installations and fuel arrangements must be represented at the correct variant level.", "layers": [ { "id": "geometry-and-loads", "name": "Geometry and loads", "description": "Associate aircraft dimensions, structural configuration and mass definitions with a documented baseline.", "findings": [ { "id": "variant-specific-physical-envelope", "name": "Variant-specific physical envelope", "description": "Prevent dimensions and mass limits from one MiG-29 configuration being silently applied to another.", "questions": [ { "text": "What are the documented span, length, height and mass limits for the identified variant, and what equipment state does each value assume?", "kind": "measurement", "id": "variant-specific-physical-envelope-q01" }, { "text": "Which structural features distinguish this configuration, including any documented carrier-operation adaptations?", "kind": "boundary", "id": "variant-specific-physical-envelope-q02" } ] } ] }, { "id": "propulsion-fuel-and-controls", "name": "Propulsion, fuel and controls", "description": "Record the installed engine, intake, fuel and flight-control arrangements rather than assuming family-wide uniformity.", "findings": [ { "id": "installed-system-baseline", "name": "Installed system baseline", "description": "Connect operating principles and limitations to the actual installed systems.", "questions": [ { "text": "Which engine versions, intake arrangements and flight-control architecture are documented for this MiG-29 baseline?", "kind": "definition", "id": "installed-system-baseline-q01" }, { "text": "What usable fuel quantities and external-tank or refuelling provisions are documented, with units and configuration conditions?", "kind": "measurement", "id": "installed-system-baseline-q02" } ] } ] } ] }, { "id": "crew-avionics-and-role", "name": "Crew, avionics and role", "description": "Establish the aircraft's crew arrangement and evidenced mission-system configuration.", "rationale": "A MiG-29 designation does not by itself establish cockpit equipment, sensor capability or authorized roles.", "layers": [ { "id": "cockpit-and-training", "name": "Cockpit and training", "description": "Distinguish crew stations, control provision and training roles across configurations.", "findings": [ { "id": "crew-station-capability", "name": "Crew-station capability", "description": "Represent single-seat and tandem-seat aircraft without assuming that the latter duplicates all equipment of the former.", "questions": [ { "text": "What crew stations, flight controls and displays are installed in this configuration?", "kind": "definition", "id": "crew-station-capability-q01" }, { "text": "Which documented training and operational roles apply to this variant, and what equipment differences constrain them?", "kind": "boundary", "id": "crew-station-capability-q02" } ] } ] }, { "id": "mission-system-fit", "name": "Mission-system fit", "description": "Track installed sensors, communications and approved equipment interfaces.", "findings": [ { "id": "capability-evidence", "name": "Capability evidence", "description": "Distinguish installed and accepted capabilities from advertised upgrade options.", "questions": [ { "text": "Which records verify the installed radar, electro-optical, navigation, communications and identification equipment?", "kind": "provenance", "id": "capability-evidence-q01" }, { "text": "Which role and external-equipment compatibility claims are approved for this exact baseline rather than merely advertised for the family?", "kind": "boundary", "id": "capability-evidence-q02" } ] } ] } ] }, { "id": "condition-and-sustainment", "name": "Condition and sustainment", "description": "Connect technical condition to life records, inspections, repairs and available support.", "rationale": "An individual MiG-29's usability depends on its service history and support baseline, not simply its type designation.", "layers": [ { "id": "life-and-defect-status", "name": "Life and defect status", "description": "Record the evidence needed to assess structural and component eligibility for continued use.", "findings": [ { "id": "remaining-life-evidence", "name": "Remaining-life evidence", "description": "Keep recorded usage, approved limits, inspection results and unresolved defects distinct.", "questions": [ { "text": "What flight-hour, cycle and calendar limits apply to this airframe and its installed engines, and which records establish consumed life?", "kind": "measurement", "id": "remaining-life-evidence-q01" }, { "text": "Which applicable inspection directives, repair records or unresolved defects restrict this MiG-29's current status?", "kind": "provenance", "id": "remaining-life-evidence-q02" } ] } ] }, { "id": "maintenance-support", "name": "Maintenance support", "description": "Identify the documentation, approved materials and qualified support required for the configuration.", "findings": [ { "id": "support-baseline", "name": "Support baseline", "description": "Treat support compatibility as a documented relationship to the particular aircraft and installed equipment.", "questions": [ { "text": "Which maintenance publications and revisions cover this variant, its engines and its accepted modifications?", "kind": "provenance", "id": "support-baseline-q01" }, { "text": "Are approved consumables, life-controlled replacement parts and compatible ground-support equipment available for the proposed maintenance activity?", "kind": "action", "id": "support-baseline-q02" } ] } ] } ] }, { "id": "authorized-use-and-ground-safety", "name": "Authorized use and ground safety", "description": "Determine the permitted operating state and the evidence needed before flight, ground activity or display.", "rationale": "Military service, civil operation, storage and museum display impose different requirements on the same MiG-29 airframe.", "layers": [ { "id": "operating-authority", "name": "Operating authority", "description": "Associate each proposed use with its responsible authority and applicable limitations.", "findings": [ { "id": "permission-and-limitations", "name": "Permission and limitations", "description": "Record the actual authority governing the aircraft rather than assuming a universal certification regime.", "questions": [ { "text": "Which military or civil authority governs this aircraft, and which current documents authorize its intended use?", "kind": "provenance", "id": "permission-and-limitations-q01" }, { "text": "Do the documented configuration, technical release and operating restrictions permit the proposed flight or ground activity?", "kind": "action", "id": "permission-and-limitations-q02" } ] } ] }, { "id": "stored-and-display-states", "name": "Stored and display states", "description": "Distinguish preserved aircraft from flight-ready aircraft and track residual hazardous systems.", "findings": [ { "id": "non-flying-state-evidence", "name": "Non-flying state evidence", "description": "Require explicit status evidence for fuel, pressure systems, ejection-seat equipment and any retained armament-related equipment.", "questions": [ { "text": "Which records establish the current preservation, isolation or removal status of hazardous systems on this airframe?", "kind": "provenance", "id": "non-flying-state-evidence-q01" }, { "text": "What qualified assessment and authority are required before moving, opening to visitors or considering return to service for this MiG-29?", "kind": "action", "id": "non-flying-state-evidence-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": [ "Dimensions and speed refer approximately to original land-based variants and must not be generalized to the entire family.", "Variant suffixes can conceal substantial differences; verify production version, export configuration and upgrade history before assigning capabilities.", "No sources were consulted; precise performance limits, maintenance requirements and applicable national military airworthiness rules require verification." ], "questions": [ { "id": "evidence-confidence-notes-q01", "text": "Which of these check these first hold for the sense of Mikoyan MiG-29 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-29: original single-seat land-based fighter", "MiG-29UB: two-seat combat trainer", "MiG-29S: improved fighter variant", "MiG-29SMT: upgraded multirole variant", "MiG-29M/M2: substantially redesigned single-seat and two-seat multirole variants", "MiG-29K/KUB: carrier-based single-seat and two-seat variants" ], "questions": [ { "id": "evidence-kinds-q01", "text": "Which of these kinds and varieties hold for the sense of Mikoyan MiG-29 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-29; МиГ-29", "note": "Identifies the aircraft family; suffixes distinguish variants, while serial numbers identify individual airframes." }, { "scheme": "NATO reporting name", "value_or_pattern": "Fulcrum", "note": "Reporting name for the family; lettered extensions distinguish particular versions." } ], "questions": [ { "id": "evidence-identifiers-q01", "text": "Which of these identifiers and schemes hold for the sense of Mikoyan MiG-29 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 interception and air-defence duties.", "Air-superiority missions using radar, infrared sensing, air-to-air missiles and an internal cannon.", "Aircrew conversion and proficiency training in two-seat variants.", "Ground attack, with weapon capabilities depending on variant and upgrades.", "Aircraft-carrier operations using MiG-29K/KUB variants equipped for arrested landings." ], "questions": [ { "id": "evidence-real-world-use-q01", "text": "Which of these real-world use hold for the sense of Mikoyan MiG-29 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": "Length of original land-based single-seat variants", "typical_range": "approximately 17.3", "unit": "m" }, { "quantity": "Wingspan of original land-based variants", "typical_range": "approximately 11.4", "unit": "m" }, { "quantity": "Maximum speed at high altitude for original fighter variants", "typical_range": "approximately 2.25", "unit": "Mach" }, { "quantity": "Installed engines", "typical_range": "2", "unit": "afterburning turbofan engines" } ], "questions": [ { "id": "evidence-measurements-q01", "text": "Which of these typical measurements hold for the sense of Mikoyan MiG-29 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 foreign-object ingestion, compressor malfunction or fire can reduce or eliminate thrust.", "Structural fatigue and corrosion require inspection and life management, particularly on ageing airframes.", "Fuel exhaustion or fuel-system faults can cause engine shutdown; usable endurance depends strongly on flight profile and afterburner use.", "Hydraulic or flight-control failures can impair controllability.", "Ejection-seat pyrotechnics, live weapons, engine intakes and jet exhaust create substantial ground-handling hazards." ], "questions": [ { "id": "evidence-failure-modes-and-hazards-q01", "text": "Which of these failure modes and hazards hold for the sense of Mikoyan MiG-29 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": [ "Export configurations and national upgrades differ in avionics, identification systems, communications and compatible weapons.", "Aircraft adapted to NATO operating environments may carry different navigation and communications equipment from original Soviet configurations.", "Carrier-based MiG-29K/KUB aircraft differ structurally and operationally from legacy land-based MiG-29 aircraft." ], "questions": [ { "id": "evidence-regional-variation-q01", "text": "Which of these regional variation hold for the sense of Mikoyan MiG-29 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 MiG-35", "difference": "A separately designated development of the later MiG-29 design lineage, rather than a name for every upgraded MiG-29." }, { "name": "Sukhoi Su-27", "difference": "A separate, larger fighter family developed by Sukhoi, with a different airframe and propulsion installation." }, { "name": "Mikoyan MiG-23", "difference": "An earlier single-engine fighter with variable-sweep wings; the MiG-29 has two engines and fixed-sweep wings." }, { "name": "An individual MiG-29 airframe", "difference": "A serial-numbered physical aircraft with its own configuration and maintenance history; this entry describes the family." } ], "questions": [ { "id": "evidence-neighbours-q01", "text": "Which of these neighbouring kinds and how to tell them apart hold for the sense of Mikoyan MiG-29 this model covers, and on what evidence?", "kind": "provenance" } ] } ] } ] } ] }, "openQuestions": [ "Does an existing Vercy world model already cover the MiG-29 concept, requiring this registry entry to link to it?", "Which variants and related designations fall within this registry entry, especially where later designs or marketing names complicate family boundaries?", "Which primary technical sources can establish variant-specific dimensions, mass limits, engine installations and fuel arrangements without mixing configurations?", "Which authoritative records establish service-life limits, recurring inspection requirements and accepted life-extension programs for each relevant baseline?", "Which operator-specific upgrades and operating-authority requirements can be verified, and which capabilities must remain explicitly unknown?" ], "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 MiG-29, record what state it is in, and decide what may be done with it.", "whatItIs": "Enable an AI agent to identify a Mikoyan MiG-29 configuration, assess the evidence for an aircraft's condition, and determine which uses require further technical or operating 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: MiG-29UB, MiG-29K, Mikojan-Gurevitj MiG-29SMT, MiG-29A, MiG-29B, MiG-29S, MiG-29SE, MiG-29N, Mikoyan MiG-35, MiG-29MU1, Mikoyan MiG-29M, MiG-29BM.", "14 finer distinctions are held as aliases rather than separate entries, because telling them apart needs a task that asks for it.", "Described in 73 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-29, 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-29 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": [ "MiG-29UB", "MiG-29K", "Mikojan-Gurevitj MiG-29SMT", "MiG-29A", "MiG-29B", "MiG-29S", "MiG-29SE", "MiG-29N", "Mikoyan MiG-35", "MiG-29MU1", "Mikoyan MiG-29M", "MiG-29BM" ] } ], "standing": "Described in 73 Wikipedia languages, which measures how widely it is written about rather than how important or how common it is. 14 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-29 from another, and a Mikoyan MiG-29 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-29, 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-29, 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-29 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-29, 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-29, 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-29 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-29 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-29, 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-29, 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-29 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-29 from the things most often confused with it.", "questions": [ { "id": "distinguishing-features-q01", "text": "What identifies and describes what distinguishes a Mikoyan MiG-29, 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-29, 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-29 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-29 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-29, 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-29, 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-29 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-29 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-29, 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-29, 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-29 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-29 is judged and by whom.", "questions": [ { "id": "condition-assessment-q01", "text": "What identifies and describes the condition of a Mikoyan MiG-29, 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-29, 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-29 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-29 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-29 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-29, 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-29, 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-29 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-29 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-29, 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-29, 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-29 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-29 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-29 between them.", "questions": [ { "id": "stages-and-transitions-q01", "text": "What identifies and describes the lifecycle of a Mikoyan MiG-29, 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-29, 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-29 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-29, how often and by whom.", "findings": [ { "id": "observation-record", "name": "Observation record", "description": "How an observation of a Mikoyan MiG-29 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-29, 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-29, 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-29 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-29 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-29 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-29 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-29, 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-29, 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-29 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-29.", "findings": [ { "id": "procedures-and-skills", "name": "Procedures, skills and required tools", "description": "What an agent needs before it can act on a Mikoyan MiG-29 at all.", "questions": [ { "id": "procedures-and-skills-q01", "text": "What identifies and describes handling a Mikoyan MiG-29, 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-29, 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-29 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-29 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-29 and how confident it is.", "questions": [ { "id": "claim-provenance-q01", "text": "What identifies and describes a claim about a Mikoyan MiG-29, 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-29, 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-29 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-29 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-29, 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-29, 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-29 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 } } } }