{ "model": { "rank": 6864, "code": "thing-q155679", "model_id": "vr.tr.mikoyan-gurevich-mig-23", "name": "Mikoyan-Gurevich MiG-23", "purpose": "Enable an agent to identify the registered MiG-23 aircraft family, resolve variant-dependent characteristics, and determine what evidence is needed to assess an associated airframe and proposed action.", "family": "Thing Registry", "category": "Physical world and living systems", "status": "research-draft", "kind": "thing", "plane": "PHY", "domain": "PHY.OBJ", "industry": "", "version": "", "url": "/models/thing/q155679/", "tier": 2, "score": 58, "payload": { "layer": "wikidata", "aliases": [ "Mikoyan-Gurevich MiG-23 in service", "MiG-23 trainer series", "MiG-23 attack", "MiG-23 fighter" ], "aliasCount": 4, "merged": 4, "knownIn": 58, "facets": null, "markers": [], "lexicalClass": "", "senseRank": null, "alsoRegisteredAs": null, "source": { "dataset": "wikidata", "item": "Q155679", "url": "https://www.wikidata.org/wiki/Q155679", "license": "CC0 1.0" } }, "research": { "vercy": "1.0-draft", "publication": { "status": "research-draft", "adjudicationStatus": "unreviewed", "publishableCanonical": false, "generatedAt": "2026-09-09T23:40:15Z", "providers": [ "Codex" ], "breadth": "recalled by Codex without web access - no source was read", "missingProviders": [], "pass": 2, "cost": { "grok": { "seconds": 24.8, "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: 01a0888a-00b2-76f1-ac3e-e35aa685e501\n--------\nuser\nDescribe what is already known about one registered thing. Answer as JSON only, no prose around it.\n\nThing: Mikoyan-Gurevich MiG-23\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": 75.1, "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: 01a0888a-00ac-73d0-a1a9-192d97e1b296\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-23\nRegistry id: vr.tr.mikoyan-gurevich-mig-23\nPlane / domain: PHY / PHY.OBJ\nRegistry definition: (none recorded)\nNames folded in" } } }, "metaModel": { "id": "THING-Q155679", "registryId": "vr.tr.mikoyan-gurevich-mig-23", "name": "Mikoyan-Gurevich MiG-23", "version": "0.1.0-research.1", "entryKind": "thing", "family": "Thing Registry", "domain": [ "PHY.OBJ" ], "status": "research-draft" }, "canonicalUrl": "https://ver.cy/models/thing/q155679/", "model": { "registry_id": "vr.tr.mikoyan-gurevich-mig-23", "name": "Mikoyan-Gurevich MiG-23", "purpose": "Enable an agent to identify the registered MiG-23 aircraft family, resolve variant-dependent characteristics, and determine what evidence is needed to assess an associated airframe and proposed action.", "definition": "The Mikoyan-Gurevich MiG-23 is a Soviet-designed family of single-engine, supersonic military jet aircraft with variable-sweep wings, developed principally for interception and fighter duties and including strike and two-seat training variants.", "scope_statement": "This model owns the type-level identity and assessment requirements of Mikoyan-Gurevich MiG-23, registry id vr.tr.mikoyan-gurevich-mig-23, in PHY / PHY.OBJ; variants remain within this entry, while individual aircraft are linked instances.", "in_scope": [ "MiG-23 family identity, variant designations, export configurations and documented modifications", "Variable-sweep airframe geometry and configuration-dependent dimensions", "Variant-specific propulsion, cockpit, avionics and installed-equipment interfaces", "Requirements for recording condition, service life and maintenance applicability", "Evidence needed to distinguish display, ground-operable and flight-authorized examples" ], "out_of_scope": [ "General aircraft and jet-propulsion principles owned by broader aircraft models", "MiG-27 as a separate aircraft type, with its relationship recorded here", "Individual airframe ownership histories and maintenance logs, except as linked evidence", "Engines, radar sets, missiles and other equipment as independently modeled things", "Combat tactics, targeting procedures and weapon-employment instructions", "Military organizations, campaigns and manufacturing enterprises" ], "distinguishing_features": [ "Use the combination of variable-sweep wings and lateral intakes to distinguish the conventional MiG-23 configuration from the MiG-21; corroborate visual identification with designation evidence. [USAF museum description and photographs](https://www.nationalmuseum.af.mil/Visit/Museum-Exhibits/Fact-Sheets/Display/Article/1162493/mikoyan-gurevich-mig-23ms-flogger-e/)", "Require a documented subtype and configuration match when separating MiG-23 from MiG-27; a Flogger label or swing-wing silhouette alone is insufficient.", "Test cockpit arrangement and designation together when separating trainer and single-seat configurations; seat count must not become a family-wide requirement.", "Distinguish MiG-23MS from other configurations using designation records and its documented export radar and smaller radome, rather than attributing every MiG-23 capability to it. [USAF museum fact sheet](https://www.nationalmuseum.af.mil/Visit/Museum-Exhibits/Fact-Sheets/Display/Article/1162493/mikoyan-gurevich-mig-23ms-flogger-e/)" ], "characteristics": [ { "name": "Variant and modification identity", "kind": "category", "unit_or_values": "Documented MiG-23 suffix, production configuration, export configuration and modification standard; unresolved permitted", "why_it_matters": "Determines which descriptions, equipment lists and limitations apply." }, { "name": "Designation evidence", "kind": "relation", "unit_or_values": "Links to manufacturer identifiers, airframe records, manuals and corroborating photographs", "why_it_matters": "Separates demonstrated identity from museum labels, repainting and visual guesses." }, { "name": "Wing geometry", "kind": "measurement", "unit_or_values": "Sweep in degrees and corresponding span in m, with angle convention and variant", "why_it_matters": "Dimensions and configuration assessments require a stated sweep position." }, { "name": "Dimensional envelope", "kind": "measurement", "unit_or_values": "Length, height and span in m; specify probes, stores, landing gear and wing position", "why_it_matters": "Supports reliable comparison and evaluation of storage or display space." }, { "name": "Mass and fuel basis", "kind": "measurement", "unit_or_values": "Mass in kg; fuel in kg or L with density basis; identify empty, loaded or limiting condition", "why_it_matters": "Prevents mixing incompatible weights and internal versus external fuel capacities." }, { "name": "Propulsion configuration", "kind": "relation", "unit_or_values": "Installed engine designation and applicable documentation; thrust in kN by rating and conditions", "why_it_matters": "Engine identity governs support requirements and the applicability of performance claims." }, { "name": "Crew and avionics configuration", "kind": "category", "unit_or_values": "Seat count, cockpit arrangement, radar or sight designation and navigation fit; absent or unknown permitted", "why_it_matters": "Distinguishes role and equipment differences within the family." }, { "name": "Mechanical configuration", "kind": "state", "unit_or_values": "Recorded wing, landing-gear, ventral-fin and control-surface positions; secured, functional, unverified or defective", "why_it_matters": "An observed position does not establish that the corresponding mechanism works." }, { "name": "Life and preservation status", "kind": "state", "unit_or_values": "Hours, cycles and calendar limits with source; storage, restoration, display or operational status dated", "why_it_matters": "Distinguishes physical completeness from supported remaining service life." }, { "name": "Action authorization", "kind": "relation", "unit_or_values": "Applicable authority, document identifier, revision, permitted activity and validity period", "why_it_matters": "A type identification or historical capability does not authorize activity involving a particular aircraft." } ], "affordances": [ "Classify a candidate aircraft within the MiG-23 family and expose conflicting identification evidence.", "Compare variants using explicitly matched engine, avionics and airframe configurations.", "Attach dimensions and performance claims to their variant and measurement conditions.", "Identify missing records before evaluating inspection, movement, restoration or display proposals.", "Route maintenance and condition questions to documentation applicable to the installed configuration.", "Link an individual example to this family without creating a duplicate type model." ] }, "sources": [], "structure": { "bundles": [ { "id": "family-and-variant-identity", "name": "Family and variant identity", "description": "Establish what counts as MiG-23 and how a claimed subtype is supported.", "rationale": "Family names, export suffixes and visually similar derivatives can otherwise collapse into one misleading configuration.", "layers": [ { "id": "designation-boundaries", "name": "Designation boundaries", "description": "Separate registry identity from naming conventions and neighboring types.", "findings": [ { "id": "mig-23-membership", "name": "MiG-23 membership", "description": "Require evidence for family membership and retain uncertain prototype or derivative assignments as unresolved.", "questions": [ { "text": "Which manufacturer designations and documented variants belong under this MiG-23 registry entry?", "kind": "definition", "id": "mig-23-membership-q01" }, { "text": "Where do authoritative designation records place the boundary with MiG-27 and experimental predecessors?", "kind": "boundary", "id": "mig-23-membership-q02" } ] } ] }, { "id": "configuration-attribution", "name": "Configuration attribution", "description": "Connect subtype claims to identifying evidence and modification history.", "findings": [ { "id": "documented-versus-observed-variant", "name": "Documented versus observed variant", "description": "Record original designation, subsequent modifications and visible features separately, including mixed-component restorations.", "questions": [ { "text": "Which data plates, production records or manuals substantiate the claimed suffix and production configuration?", "kind": "provenance", "id": "documented-versus-observed-variant-q01" }, { "text": "Do the cockpit, nose, wing-glove and tail features agree with that configuration, or suggest replacement parts?", "kind": "boundary", "id": "documented-versus-observed-variant-q02" } ] } ] } ] }, { "id": "variable-sweep-airframe", "name": "Variable-sweep airframe", "description": "Represent the geometry and mechanical states that make MiG-23 measurements configuration-dependent.", "rationale": "A fixed silhouette or single span cannot adequately characterize a variable-sweep aircraft.", "layers": [ { "id": "sweep-and-envelope", "name": "Sweep and envelope", "description": "Bind dimensions to wing position and measurement conventions.", "findings": [ { "id": "sweep-dependent-dimensions", "name": "Sweep-dependent dimensions", "description": "Record supported sweep positions and corresponding dimensions by variant; the museum lists 16, 45 and 72 degrees for MiG-23MS. [USAF museum technical notes](https://www.nationalmuseum.af.mil/Visit/Museum-Exhibits/Fact-Sheets/Display/Article/1162493/mikoyan-gurevich-mig-23ms-flogger-e/)", "questions": [ { "text": "Which sweep settings and angle-reference convention are documented for the selected variant?", "kind": "measurement", "id": "sweep-dependent-dimensions-q01" }, { "text": "What span, length and height apply with the recorded sweep, probes, landing gear and external equipment?", "kind": "measurement", "id": "sweep-dependent-dimensions-q02" } ] } ] }, { "id": "geometry-mechanism-state", "name": "Geometry mechanism state", "description": "Distinguish observed configuration from mechanism serviceability.", "findings": [ { "id": "sweep-gear-and-fin-evidence", "name": "Sweep, gear and fin evidence", "description": "Require applicable documentation for wing-sweep mechanisms, landing gear, ventral-fin movement and associated locks or interlocks.", "questions": [ { "text": "Which mechanisms, position indications and interlocks are fitted to this MiG-23 configuration?", "kind": "definition", "id": "sweep-gear-and-fin-evidence-q01" }, { "text": "What inspection evidence establishes their condition before a proposed movement or configuration change?", "kind": "action", "id": "sweep-gear-and-fin-evidence-q02" } ] } ] } ] }, { "id": "propulsion-and-aircraft-systems", "name": "Propulsion and aircraft systems", "description": "Resolve installed propulsion and the support systems needed to interpret aircraft condition.", "rationale": "A MiG-23 family label does not determine engine compatibility, consumables or subsystem serviceability.", "layers": [ { "id": "engine-and-fuel-fit", "name": "Engine and fuel fit", "description": "Associate propulsion claims with installed equipment and documented conditions.", "findings": [ { "id": "engine-rating-and-consumables", "name": "Engine rating and consumables", "description": "Record engine identity, rating basis, fuel capacity and approved consumable references without transferring values across variants.", "questions": [ { "text": "Which engine designation and modification state are documented for the airframe configuration?", "kind": "provenance", "id": "engine-rating-and-consumables-q01" }, { "text": "Which thrust ratings, fuel quantities and consumable specifications apply, with what units and conditions?", "kind": "measurement", "id": "engine-rating-and-consumables-q02" } ] } ] }, { "id": "power-and-control-dependencies", "name": "Power and control dependencies", "description": "Map the installed systems supporting sweep, flight controls and cockpit functions.", "findings": [ { "id": "system-availability", "name": "System availability", "description": "Record the documented hydraulic, electrical, pneumatic and cockpit-support configuration, including isolation and missing equipment.", "questions": [ { "text": "Which installed systems supply the wing-sweep mechanism, flight controls and cockpit equipment?", "kind": "definition", "id": "system-availability-q01" }, { "text": "Which defects, disconnected services or undocumented substitutions prevent assessment of the proposed activity?", "kind": "action", "id": "system-availability-q02" } ] } ] } ] }, { "id": "role-and-equipment-configuration", "name": "Role and equipment configuration", "description": "Represent cockpit, sensor and external-equipment differences without assuming uniform family capabilities.", "rationale": "Variant and export configurations change what equipment and role descriptions apply.", "layers": [ { "id": "crew-and-sensor-fit", "name": "Crew and sensor fit", "description": "Identify cockpit arrangement and actual avionics installation.", "findings": [ { "id": "variant-specific-role-evidence", "name": "Variant-specific role evidence", "description": "Bind fighter, trainer or attack-role descriptions to the documented subtype and installed cockpit and sensor configuration.", "questions": [ { "text": "Which role and crew arrangement are supported by documentation for this exact variant?", "kind": "definition", "id": "variant-specific-role-evidence-q01" }, { "text": "Which radar, sight and navigation systems were specified, and which are actually present?", "kind": "provenance", "id": "variant-specific-role-evidence-q02" } ] } ] }, { "id": "external-equipment-interfaces", "name": "External equipment interfaces", "description": "Separate physical attachment features from documented equipment compatibility.", "findings": [ { "id": "configuration-compatibility", "name": "Configuration compatibility", "description": "Record approved external-tank, pylon and other equipment relationships at identification level, including inert display substitutes.", "questions": [ { "text": "Which authoritative configuration records establish compatibility for the fitted external equipment?", "kind": "provenance", "id": "configuration-compatibility-q01" }, { "text": "Which attachments are original equipment, later adaptations, inert replicas or unidentified items?", "kind": "boundary", "id": "configuration-compatibility-q02" } ] } ] } ] }, { "id": "condition-and-permitted-activity", "name": "Condition and permitted activity", "description": "Connect MiG-23 maintenance evidence, preservation state and applicable authority to proposed activities.", "rationale": "A complete-looking preserved aircraft may lack service-life evidence, functional mechanisms or authorization for operation.", "layers": [ { "id": "airframe-life-and-support", "name": "Airframe life and support", "description": "Assess the evidence needed for aging structure, installed components and maintenance support.", "findings": [ { "id": "life-limit-and-inspection-applicability", "name": "Life-limit and inspection applicability", "description": "Identify applicable inspection and life-limit requirements, with particular attention to sweep pivots, actuators and their supporting structure.", "questions": [ { "text": "Which maintenance publications establish inspection intervals and life limits for this variant and its installed components?", "kind": "provenance", "id": "life-limit-and-inspection-applicability-q01" }, { "text": "What recorded hours, cycles, calendar exposure and inspection findings support the remaining-life assessment?", "kind": "measurement", "id": "life-limit-and-inspection-applicability-q02" } ] } ] }, { "id": "preservation-and-authorization", "name": "Preservation and authorization", "description": "Distinguish display condition, residual hazards and documented permission for activity.", "findings": [ { "id": "activity-evidence-gates", "name": "Activity evidence gates", "description": "Require activity-specific evidence for ejection-seat and other pyrotechnic status, stored pressure, fuel condition, mechanical security and applicable authorization.", "questions": [ { "text": "What records establish the state of the ejection system, other pyrotechnic equipment, stored-energy systems and secured movable structures?", "kind": "provenance", "id": "activity-evidence-gates-q01" }, { "text": "Which issuing authority and document revision govern the proposed display, towing, ground-running or flight activity?", "kind": "action", "id": "activity-evidence-gates-q02" }, { "text": "Which unresolved configuration or condition issues require specialist assessment before that activity?", "kind": "action", "id": "activity-evidence-gates-q03" } ] } ] } ] }, { "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 variant-specific performance and equipment before reuse.", "Measurements are approximate and should not be applied uniformly to all variants, loads or operating conditions.", "The variant list is selective; no specific military airworthiness standard or current operator status is asserted." ], "questions": [ { "id": "evidence-confidence-notes-q01", "text": "Which of these check these first hold for the sense of Mikoyan-Gurevich MiG-23 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-23S: early production fighter", "MiG-23M: developed production fighter", "MiG-23MF: export fighter variant", "MiG-23ML: lighter, revised fighter variant", "MiG-23MLD: fighter upgrade with aerodynamic and equipment improvements", "MiG-23UB: two-seat conversion trainer" ], "questions": [ { "id": "evidence-kinds-q01", "text": "Which of these kinds and varieties hold for the sense of Mikoyan-Gurevich MiG-23 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-23 followed by a variant suffix", "note": "Identifies the aircraft family and variant; individual airframes have separate construction numbers and military markings." }, { "scheme": "NATO reporting name", "value_or_pattern": "Flogger", "note": "Reporting-name suffixes distinguish versions; the Flogger name also covers the related MiG-27." } ], "questions": [ { "id": "evidence-identifiers-q01", "text": "Which of these identifiers and schemes hold for the sense of Mikoyan-Gurevich MiG-23 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 territorial air defence", "Air-superiority fighter operations", "Ground attack by suitably equipped variants", "Pilot conversion and proficiency training using two-seat variants", "Foreign-aircraft evaluation and threat familiarisation" ], "questions": [ { "id": "evidence-real-world-use-q01", "text": "Which of these real-world use hold for the sense of Mikoyan-Gurevich MiG-23 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 across sweep positions", "typical_range": "Approximately 7.8-14.0", "unit": "m" }, { "quantity": "Principal selectable wing-sweep angles", "typical_range": "Approximately 16, 45 and 72", "unit": "degree" }, { "quantity": "Maximum speed at altitude for principal fighter variants", "typical_range": "Approximately 2.3", "unit": "Mach" } ], "questions": [ { "id": "evidence-measurements-q01", "text": "Which of these typical measurements hold for the sense of Mikoyan-Gurevich MiG-23 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": [ "Stall, departure from controlled flight and spin hazards depend on angle of attack, configuration and variant.", "Wing-sweep mechanism or indication faults can compromise configuration control and handling.", "Failure of the single engine removes the aircraft's sole source of powered thrust.", "Ageing structures, corrosion and fatigue can reduce airworthiness without inspection and maintenance.", "Fuel, live ordnance and pyrotechnic ejection-seat components present fire, explosion and 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-Gurevich MiG-23 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": [ "Soviet-service and export variants differed in radar, avionics and permitted weapons.", "Operator-specific modifications and maintenance histories produce differences between aircraft bearing the same basic variant designation.", "Military markings and individual aircraft identification practices differ by operator." ], "questions": [ { "id": "evidence-regional-variation-q01", "text": "Which of these regional variation hold for the sense of Mikoyan-Gurevich MiG-23 this model covers, and on what evidence?", "kind": "provenance" } ] }, { "id": "evidence-neighbours", "name": "Neighbouring kinds and how to tell them apart", "description": "Recalled without web access and unsourced; every item is a lead to verify.", "evidence": [ { "name": "Mikoyan-Gurevich MiG-21", "difference": "The MiG-21 has a fixed delta wing and nose intake; the MiG-23 has variable-sweep wings and side intakes." }, { "name": "Mikoyan MiG-27", "difference": "The MiG-27 is a separately designated ground-attack derivative with a redesigned nose and intake arrangement; it is not simply another MiG-23 fighter variant." }, { "name": "MiG-23BN", "difference": "The MiG-23BN is a ground-attack variant within the MiG-23 family, distinguished from interceptor variants by its specialised nose and mission equipment." }, { "name": "Individual MiG-23 airframe", "difference": "An airframe is one manufactured aircraft with its own identity and service history; 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-23 this model covers, and on what evidence?", "kind": "provenance" } ] } ] } ] } ] }, "openQuestions": [ "Which authoritative designation history settles inclusion of early prototypes, MiG-23 attack variants and trainer variants while preserving the boundary with MiG-27?", "Which primary manuals establish a reliable variant matrix for engine, radar, cockpit, wing and landing-gear changes, including export and retrofit configurations?", "What variant-specific dimensions, capacities and performance values can be supported with explicit sweep, mass, altitude and equipment conditions?", "Which documented failure modes, life limits and inspection criteria apply specifically to MiG-23 sweep mechanisms and aging airframe structure?", "Which operator or civil authority documents govern surviving examples, and what evidence distinguishes preservation, ground operation and flight authorization?" ], "statistics": { "bundles": 6, "layers": 11, "findings": 18, "questions": 29 } }, "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-23, record what state it is in, and decide what may be done with it.", "whatItIs": "Enable an agent to identify the registered MiG-23 aircraft family, resolve variant-dependent characteristics, and determine what evidence is needed to assess an associated airframe and proposed action.", "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: Mikoyan-Gurevich MiG-23 in service, MiG-23 trainer series, MiG-23 attack, MiG-23 fighter.", "4 finer distinctions are held as aliases rather than separate entries, because telling them apart needs a task that asks for it.", "Described in 58 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-23, 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-23 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": [ "Mikoyan-Gurevich MiG-23 in service", "MiG-23 trainer series", "MiG-23 attack", "MiG-23 fighter" ] } ], "standing": "Described in 58 Wikipedia languages, which measures how widely it is written about rather than how important or how common it is. 4 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-23 from another, and a Mikoyan-Gurevich MiG-23 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-23, 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-23, 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-23 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-23, 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-23, 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-23 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-23 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-23, 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-23, 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-23 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-23 from the things most often confused with it.", "questions": [ { "id": "distinguishing-features-q01", "text": "What identifies and describes what distinguishes a Mikoyan-Gurevich MiG-23, 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-23, 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-23 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-23 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-23, 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-23, 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-23 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-23 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-23, 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-23, 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-23 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-23 is judged and by whom.", "questions": [ { "id": "condition-assessment-q01", "text": "What identifies and describes the condition of a Mikoyan-Gurevich MiG-23, 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-23, 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-23 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-23 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-23 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-23, 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-23, 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-23 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-23 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-23, 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-23, 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-23 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-23 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-23 between them.", "questions": [ { "id": "stages-and-transitions-q01", "text": "What identifies and describes the lifecycle of a Mikoyan-Gurevich MiG-23, 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-23, 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-23 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-23, how often and by whom.", "findings": [ { "id": "observation-record", "name": "Observation record", "description": "How an observation of a Mikoyan-Gurevich MiG-23 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-23, 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-23, 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-23 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-23 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-23 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-23 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-23, 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-23, 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-23 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-23.", "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-23 at all.", "questions": [ { "id": "procedures-and-skills-q01", "text": "What identifies and describes handling a Mikoyan-Gurevich MiG-23, 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-23, 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-23 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-23 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-23 and how confident it is.", "questions": [ { "id": "claim-provenance-q01", "text": "What identifies and describes a claim about a Mikoyan-Gurevich MiG-23, 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-23, 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-23 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-23 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-23, 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-23, 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-23 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 } } } }