{ "model": { "rank": 6314, "code": "thing-q187377", "model_id": "vr.tr.mikoyan-gurevich-mig-15", "name": "Mikoyan-Gurevich MiG-15", "purpose": "Enable an AI agent to identify a Mikoyan-Gurevich MiG-15, establish an individual airframe's configuration and condition, and determine which inspection, preservation, movement or operational actions its evidence supports.", "family": "Thing Registry", "category": "Physical world and living systems", "status": "research-draft", "kind": "thing", "plane": "PHY", "domain": "PHY.OBJ", "industry": "", "version": "", "url": "/models/thing/q187377/", "tier": 2, "score": 61, "payload": { "layer": "wikidata", "aliases": [ "MiG-15UTI", "MiG-15P", "MiG-15SB", "MiG-15T", "Lim-1", "MiG-15 base", "MiG-15bis", "BA-5", "MiG-15bisR", "MiG-15bisS", "MiG-15bisT", "Lim-2", "J-2", "Avia S-103", "Shenyang F-2" ], "aliasCount": 15, "merged": 15, "knownIn": 61, "facets": null, "markers": [], "lexicalClass": "", "senseRank": null, "alsoRegisteredAs": null, "source": { "dataset": "wikidata", "item": "Q187377", "url": "https://www.wikidata.org/wiki/Q187377", "license": "CC0 1.0" } }, "research": { "vercy": "1.0-draft", "publication": { "status": "research-draft", "adjudicationStatus": "unreviewed", "publishableCanonical": false, "generatedAt": "2026-09-07T13:48:24Z", "providers": [ "Codex", "Grok" ], "missingProviders": [], "pass": 2, "cost": { "grok": { "usd": 0.011373, "turns": 1, "seconds": 132.3, "error": null }, "codex": { "seconds": 108.4, "error": "Reading additional input from stdin...\nOpenAI Codex v0.153.3\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: 01a07c1c-9f4c-7c72-ba6c-455fed54740b\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-15\nRegistry id: vr.tr.mikoyan-gurevich-mig-15\nPlane / domain: PHY / PHY.OBJ\nRegistry definition: (none recorded)\nNames folded in" } } }, "metaModel": { "id": "THING-Q187377", "registryId": "vr.tr.mikoyan-gurevich-mig-15", "name": "Mikoyan-Gurevich MiG-15", "version": "0.1.0-research.1", "entryKind": "thing", "family": "Thing Registry", "domain": [ "PHY.OBJ" ], "status": "research-draft" }, "canonicalUrl": "https://ver.cy/models/thing/q187377/", "model": { "registry_id": "vr.tr.mikoyan-gurevich-mig-15", "name": "Mikoyan-Gurevich MiG-15", "purpose": "Enable an AI agent to identify a Mikoyan-Gurevich MiG-15, establish an individual airframe's configuration and condition, and determine which inspection, preservation, movement or operational actions its evidence supports.", "definition": "The Mikoyan-Gurevich MiG-15 is a Soviet high-subsonic, single-engine, 35-degree swept-wing jet fighter developed by OKB-155, first flown on 30 December 1947 as the I-310 and fielded from 1949 as the USSR's first mass-service transonic interceptor, built around a centrifugal-flow turbojet derived from the Rolls-Royce Nene.", "scope_statement": "This model owns recognition and aircraft-level assessment of the physical aircraft represented by vr.tr.mikoyan-gurevich-mig-15 in PHY / PHY.OBJ, distinguishing type characteristics, variant claims and individual airframe observations without creating separate registry entries.", "in_scope": [ "MiG-15 identification through airframe geometry, manufacturer records and component evidence", "Variant attribution and differences between original, installed and represented configurations", "Airframe, propulsion, flight-control and cockpit condition relevant to intended use", "Installed armament, escape equipment and their documented safe or unknown states", "Evidence supporting conservation, restoration, ground movement and operational eligibility" ], "out_of_scope": [ "MiG-17 and other aircraft types, except as identification comparators", "Standalone engine, cannon, ammunition and ejection-seat design models", "Air combat tactics, targeting and weapon employment", "Korean War campaigns, military organizations and pilot biographies", "Airport operations, pilot licensing and maintenance-provider management", "Scale models, replicas and digital flight simulations as independent objects" ], "distinguishing_features": [ "Compare wing sweep and fence layout against a documented MiG-15 reference: approximately 35-degree sweep and two fences per wing provide a concrete recognition check when resolving MiG-15 versus MiG-17 attribution; require corroborating geometry or identity records. [MAPS Air Museum](https://mapsairmuseum.org/wp-content/uploads/2024/02/MiG-15.pdf)", "Check for the nose intake and its duct routing around the cockpit to the engine; combine this with wing geometry rather than identifying the aircraft from the intake alone. [MAPS Air Museum](https://mapsairmuseum.org/wp-content/uploads/2024/02/MiG-15.pdf)", "When distinguishing an original MiG-15 configuration from a MiG-15bis claim, examine engine identification and aileron-boost equipment: the USAF museum identifies the bis with a more powerful engine and hydraulically boosted ailerons, and lists a VK-1 engine. [USAF museum](https://www.nationalmuseum.af.mil/Visit/Museum-Exhibits/Fact-Sheets/Display/Article/196115/mikoyan-gurevich-mig-15bis/)", "For a claimed MiG-15bis fighter configuration, compare the documented armament arrangement with two 23 mm cannons and one 37 mm cannon; missing or replica guns in a preserved aircraft cannot alone disprove identity. [USAF museum](https://www.nationalmuseum.af.mil/Visit/Museum-Exhibits/Fact-Sheets/Display/Article/196115/mikoyan-gurevich-mig-15bis/)" ], "characteristics": [ { "name": "Supported type and variant attribution", "kind": "category", "unit_or_values": "MiG-15; MiG-15bis; claimed trainer or licensed derivative pending boundary verification; unresolved", "why_it_matters": "Determines which recognition references, equipment expectations and technical documents apply." }, { "name": "Airframe identity evidence", "kind": "relation", "unit_or_values": "Links to manufacturer serial, data plate, production record, service identity and civil registration, with conflicts retained", "why_it_matters": "Separates the physical airframe's identity from painted numbers and exhibit labels." }, { "name": "Wing and fuselage geometry", "kind": "measurement", "unit_or_values": "Span and length in m; sweep in degrees with reference line; fence count per wing", "why_it_matters": "Supports recognition and exposes mismatches with a MiG-17, replica or reconstructed assembly." }, { "name": "Installed engine identity", "kind": "relation", "unit_or_values": "Engine model, serial and installation evidence; absent or unidentified permitted", "why_it_matters": "Prevents a variant label from substituting for evidence about the actual propulsion installation." }, { "name": "Cockpit configuration", "kind": "category", "unit_or_values": "Observed seat count, canopy arrangement, control stations and documented conversion status", "why_it_matters": "Flags trainer attribution, conversions and incompatible assumptions about cockpit equipment." }, { "name": "Configuration authenticity", "kind": "state", "unit_or_values": "Documented original; documented service modification; restoration substitution; replica component; unknown, assessed by assembly", "why_it_matters": "Distinguishes historical representation from the aircraft's installed physical configuration." }, { "name": "Structural and control-system condition", "kind": "state", "unit_or_values": "Serviceable for a stated use; restricted; defective; uninspected, with dated evidence by assembly", "why_it_matters": "Determines whether wings, tail, controls and landing gear support the proposed action." }, { "name": "Airframe and engine usage", "kind": "measurement", "unit_or_values": "Hours and cycles where applicable; time since inspection or overhaul; unknown intervals retained", "why_it_matters": "Exposes missing life-history evidence that a visually complete restoration cannot supply." }, { "name": "Mass and balance configuration", "kind": "measurement", "unit_or_values": "Mass in kg; center of gravity against a documented datum; associated fuel, armament and equipment configuration", "why_it_matters": "Removed guns, substituted equipment and external tanks can invalidate an earlier assessment." }, { "name": "Armament and escape-equipment state", "kind": "state", "unit_or_values": "Absent; replica; documented inert; potentially live; unknown, recorded separately for each installation", "why_it_matters": "Controls whether cockpit access, handling and display preparation require specialist intervention." }, { "name": "Permitted use", "kind": "state", "unit_or_values": "Static display; controlled access; ground movement; maintenance; ground run; flight, each supported, prohibited or unresolved", "why_it_matters": "Keeps permission for one activity from being generalized to another." } ], "affordances": [ "Identify or provisionally classify an airframe by comparing MiG-15 geometry, markings and documentary evidence.", "Select technical references applicable to the supported variant and installed equipment.", "Request targeted inspection of discrepancies affecting structural integrity, propulsion or cockpit access.", "Assess a conservation or restoration proposal against historical configuration and intended use.", "Determine whether evidence supports display, towing, ground running or flight, and refer unresolved decisions to the responsible specialist." ] }, "sources": [ { "id": "wikipedia-mig-15", "title": "Mikoyan-Gurevich MiG-15", "url": "https://en.wikipedia.org/wiki/Mikoyan-Gurevich_MiG-15", "what_it_supports": "Service history, variant list, NATO names, principal dimensions and Korean War context", "url_status": "live" }, { "id": "gordon-mig-15", "title": "Mikoyan-Gurevich MiG-15: The Soviet Union's First Swept-Wing Jet Fighter", "url": "", "what_it_supports": "OKB designations, production batches, RD-45F versus VK-1 airframes, and license manufacture" }, { "id": "icao-doc-8643", "title": "Aircraft Type Designators (Doc 8643)", "url": "", "what_it_supports": "ICAO type designator MG15 for the family" }, { "id": "nmusaf-mig-15bis", "title": "Mikoyan-Gurevich MiG-15bis (NATO reporting name Fagot)", "url": "", "what_it_supports": "Museum-documented bis configuration, armament fit, and typical displayed weights and speeds" } ], "structure": { "bundles": [ { "id": "identity-and-variant", "name": "Identity and variant", "description": "Establish whether the aircraft belongs to this registry entry and which MiG-15 configuration its evidence supports.", "rationale": "MiG-15 family resemblance, variant labels and repainted service markings can each produce a plausible but incorrect identification.", "layers": [ { "id": "airframe-recognition", "name": "Airframe recognition", "description": "Compare observable geometry with documented MiG-15 references.", "findings": [ { "id": "geometry-supported-identification", "name": "Geometry-supported identification", "description": "Record the observed wing, fence, intake, tail and canopy features and any contradictions to the claimed type.", "questions": [ { "text": "Which measured or photographed features support MiG-15 identification over MiG-17 or another early jet?", "kind": "measurement", "id": "geometry-supported-identification-q01" }, { "text": "Which missing, obscured or reconstructed features prevent confident identification?", "kind": "boundary", "id": "geometry-supported-identification-q02" } ] } ] }, { "id": "serial-and-variant-attribution", "name": "Serial and variant attribution", "description": "Reconcile physical identifiers with manufacturer, service and restoration records.", "findings": [ { "id": "supported-production-identity", "name": "Supported production identity", "description": "Keep manufacturer identity, variant attribution, painted identity and registry membership distinguishable.", "questions": [ { "text": "Which data plate and production or service records establish this airframe's serial, manufacturer and variant?", "kind": "provenance", "id": "supported-production-identity-q01" }, { "text": "If the aircraft is described as a trainer or licensed derivative, does the authoritative registry place it here or in a neighbouring entry?", "kind": "boundary", "id": "supported-production-identity-q02" }, { "text": "Do engine and control-system evidence support the claimed MiG-15 or MiG-15bis configuration?", "kind": "definition", "id": "supported-production-identity-q03" } ] } ] } ] }, { "id": "configuration-and-authenticity", "name": "Configuration and authenticity", "description": "Describe what this MiG-15 physically contains and which historical configuration it represents.", "rationale": "A restored MiG-15 can combine an authentic airframe, replacement assemblies and markings representing a different aircraft.", "layers": [ { "id": "installed-assemblies", "name": "Installed assemblies", "description": "Establish the provenance and compatibility of major assemblies.", "findings": [ { "id": "assembly-configuration-baseline", "name": "Assembly configuration baseline", "description": "Record the installed engine, wings, tail, cockpit and control equipment as a dated aircraft configuration.", "questions": [ { "text": "Which installed assemblies are traceable to this airframe, and which were exchanged or reconstructed?", "kind": "provenance", "id": "assembly-configuration-baseline-q01" }, { "text": "Which technical records establish compatibility of substitutions with the claimed MiG-15 configuration?", "kind": "boundary", "id": "assembly-configuration-baseline-q02" } ] } ] }, { "id": "historical-representation", "name": "Historical representation", "description": "Separate the airframe's history from its current appearance.", "findings": [ { "id": "markings-and-restoration-fidelity", "name": "Markings and restoration fidelity", "description": "Explain which period, operator and aircraft identity the paint and equipment represent, with evidence gaps retained.", "questions": [ { "text": "Which dated photographs or records support the displayed markings, cockpit finish and equipment fit?", "kind": "provenance", "id": "markings-and-restoration-fidelity-q01" }, { "text": "Which proposed restoration changes would remove original evidence or create an undocumented historical appearance?", "kind": "action", "id": "markings-and-restoration-fidelity-q02" } ] } ] } ] }, { "id": "airframe-and-flight-systems", "name": "Airframe and flight systems", "description": "Assess the MiG-15's lifting structure, controls, landing gear and installed propulsion as a connected aircraft.", "rationale": "Visual completeness cannot establish structural fitness or the compatibility and condition of variant-dependent flight systems.", "layers": [ { "id": "structure-controls-and-gear", "name": "Structure, controls and gear", "description": "Associate inspection evidence with the assemblies that carry loads and govern movement.", "findings": [ { "id": "structural-and-control-readiness", "name": "Structural and control readiness", "description": "Record damage, corrosion, repairs and inspection status for wings, attachments, tail, flight controls and landing gear.", "questions": [ { "text": "What dated inspections establish the condition of wing and tail attachments, control linkages and landing gear?", "kind": "provenance", "id": "structural-and-control-readiness-q01" }, { "text": "Which defects or undocumented repairs limit display support, towing or flight?", "kind": "action", "id": "structural-and-control-readiness-q02" }, { "text": "What evidence establishes the condition of the aileron-boost installation where applicable?", "kind": "measurement", "id": "structural-and-control-readiness-q03" } ] } ] }, { "id": "propulsion-and-fuel-installation", "name": "Propulsion and fuel installation", "description": "Evaluate the installed engine together with its aircraft interfaces.", "findings": [ { "id": "engine-installation-readiness", "name": "Engine installation readiness", "description": "Relate engine identity and life history to intake, mounting, fuel, exhaust and control-system evidence.", "questions": [ { "text": "Which engine records establish installed model, overhaul history and unknown usage intervals?", "kind": "provenance", "id": "engine-installation-readiness-q01" }, { "text": "What inspection evidence covers the intake duct, engine mounts, fuel installation and exhaust path for the proposed use?", "kind": "measurement", "id": "engine-installation-readiness-q02" }, { "text": "Which unresolved installation discrepancies prevent assessment for a ground run or flight?", "kind": "action", "id": "engine-installation-readiness-q03" } ] } ] } ] }, { "id": "cockpit-and-special-equipment", "name": "Cockpit and special equipment", "description": "Establish the installed state of crew-support, escape and armament equipment.", "rationale": "A museum or restored MiG-15 may retain hazardous equipment even when its engine and flight systems are inactive.", "layers": [ { "id": "crew-support-and-escape", "name": "Crew support and escape", "description": "Assess the actual cockpit, canopy, oxygen, pressurization and escape installations.", "findings": [ { "id": "cockpit-access-and-equipment-state", "name": "Cockpit access and equipment state", "description": "Record equipment identity, completeness, inspection and specialist clearance relevant to access or operation.", "questions": [ { "text": "Which canopy, seat, escape and crew-support equipment is actually installed in each cockpit position?", "kind": "definition", "id": "cockpit-access-and-equipment-state-q01" }, { "text": "What dated specialist evidence establishes whether escape equipment is inert, active or unresolved?", "kind": "provenance", "id": "cockpit-access-and-equipment-state-q02" }, { "text": "Which cockpit-access restrictions follow from the equipment's documented condition?", "kind": "action", "id": "cockpit-access-and-equipment-state-q03" } ] } ] }, { "id": "armament-and-external-stores", "name": "Armament and external stores", "description": "Separate historical armament configuration from the present physical installation.", "findings": [ { "id": "armament-presence-and-clearance", "name": "Armament presence and clearance", "description": "Identify actual, absent and replica cannons or stores and the evidence supporting their handling status.", "questions": [ { "text": "Which cannon installations, ammunition spaces and external-store fittings remain, and which are replicas or empty?", "kind": "definition", "id": "armament-presence-and-clearance-q01" }, { "text": "What specialist records establish clearance or inert status of retained armament and stores?", "kind": "provenance", "id": "armament-presence-and-clearance-q02" }, { "text": "How do removed or substituted guns and external tanks affect the recorded mass and balance configuration?", "kind": "measurement", "id": "armament-presence-and-clearance-q03" } ] } ] } ] }, { "id": "use-limits-and-preservation", "name": "Use limits and preservation", "description": "Connect MiG-15 configuration and condition evidence to a specific proposed activity.", "rationale": "A historical performance figure, a complete restoration and a display approval establish different things and cannot independently authorize operation.", "layers": [ { "id": "operational-evidence", "name": "Operational evidence", "description": "Establish which instructions and limits apply to this airframe in its present configuration.", "findings": [ { "id": "configuration-specific-use-eligibility", "name": "Configuration-specific use eligibility", "description": "Record applicable manual revisions, inspection releases and restrictions for ground running or flight.", "questions": [ { "text": "Which authenticated manuals and supplements match the variant, engine, cockpit and modifications actually installed?", "kind": "provenance", "id": "configuration-specific-use-eligibility-q01" }, { "text": "Which configuration-dependent mass, balance and operating limits are documented, and which remain unknown?", "kind": "measurement", "id": "configuration-specific-use-eligibility-q02" }, { "text": "What current aircraft-specific approvals and inspection releases support the requested activity?", "kind": "action", "id": "configuration-specific-use-eligibility-q03" } ] } ] }, { "id": "conservation-and-ground-handling", "name": "Conservation and ground handling", "description": "Determine how the aircraft can be preserved, accessed and moved in its recorded state.", "findings": [ { "id": "preservation-and-movement-plan", "name": "Preservation and movement plan", "description": "Connect airframe support, gear condition, exposed openings and retained equipment to a reviewed preservation or movement proposal.", "questions": [ { "text": "What evidence supports the proposed use of towing, lifting or support points on this airframe?", "kind": "provenance", "id": "preservation-and-movement-plan-q01" }, { "text": "Which measures are needed to protect the nose intake, exhaust, cockpit and vulnerable structure during storage or display?", "kind": "action", "id": "preservation-and-movement-plan-q02" }, { "text": "Does the proposed action preserve a static artifact or support return to operation, and what different acceptance criteria follow?", "kind": "boundary", "id": "preservation-and-movement-plan-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-kinds", "name": "Kinds and varieties", "description": "Reported by the breadth pass; each item needs checking against its source before it becomes normative.", "evidence": [ "MiG-15 (izdeliye 50): initial production fighter with the RD-45F engine", "MiG-15bis (izdeliye 50bis): VK-1-powered main production fighter, the principal Korean War type", "MiG-15UTI (izdeliye 15; NATO Midget): tandem two-seat conversion trainer", "MiG-15P / MiG-15bisP: limited all-weather interceptors with Izumrud-type radar", "MiG-15SB / MiG-15bisSB and related fighter-bomber fits with underwing stores", "MiG-15R / MiG-15bisR: camera-equipped reconnaissance conversions", "License-built European types: Czechoslovak S-102/S-103/CS-102 and Polish Lim-1/Lim-2", "Chinese-assembled Shenyang J-2 / JJ-2" ], "questions": [ { "id": "evidence-kinds-q01", "text": "Which of these kinds and varieties hold for the sense of Mikoyan-Gurevich MiG-15 this model covers, and on what evidence?", "kind": "provenance" } ] }, { "id": "evidence-identifiers", "name": "Identifiers and schemes", "description": "Reported by the breadth pass; each item needs checking against its source before it becomes normative.", "evidence": [ { "scheme": "Wikidata", "value_or_pattern": "Q182638", "note": "Item for the aircraft type" }, { "scheme": "NATO reporting name", "value_or_pattern": "Fagot (single-seat); Midget (UTI trainer)", "note": "Air Standards Coordinating Committee / NATO ASCC names" }, { "scheme": "ICAO aircraft type designator", "value_or_pattern": "MG15", "note": "Doc 8643 type code used in flight plans and traffic data" }, { "scheme": "Soviet OKB / product designation", "value_or_pattern": "I-310 (prototype); izdeliye 50 / 50bis; izdeliye 15 (UTI)", "note": "Design-bureau and factory article numbers, not the public service name" }, { "scheme": "US Air Technical Intelligence type number", "value_or_pattern": "Type 14", "note": "Early Western intelligence designation before the NATO name stuck" }, { "scheme": "Service designation", "value_or_pattern": "МиГ-15 / MiG-15 plus variant suffix (bis, UTI, P, R, SB)", "note": "VVS and export air-arm usage" } ], "questions": [ { "id": "evidence-identifiers-q01", "text": "Which of these identifiers and schemes hold for the sense of Mikoyan-Gurevich MiG-15 this model covers, and on what evidence?", "kind": "provenance" } ] }, { "id": "evidence-standards-and-regulation", "name": "Standards and regulation", "description": "Reported by the breadth pass; each item needs checking against its source before it becomes normative.", "evidence": [ "ICAO Doc 8643 aircraft type designators (International Civil Aviation Organization): MG15", "NATO reporting-name system (Air Standards Coordinating Committee): Fagot / Midget", "Historical Soviet Air Force tactical-technical requirements (TTZ) that framed the late-1940s jet-fighter competition won by the I-310", "Civil operation of surviving airframes under national experimental, exhibition or limited-category airworthiness rules (e.g. FAA, EASA member states), not under an original Soviet civil type certificate", "Export and remaining-munition controls on complete fighters, engines and guns under national military lists and, for later transfers, Wassenaar-type dual-use/munitions practice" ], "questions": [ { "id": "evidence-standards-and-regulation-q01", "text": "Which of these standards and regulation hold for the sense of Mikoyan-Gurevich MiG-15 this model covers, and on what evidence?", "kind": "provenance" } ] }, { "id": "evidence-real-world-use", "name": "Real-world use", "description": "Reported by the breadth pass; each item needs checking against its source before it becomes normative.", "evidence": [ "Day interceptor and air-superiority fighter for the Soviet Air Force and allied air arms from 1949, including large-scale combat over Korea against F-86 Sabres and other UN types", "Warsaw Pact, Chinese and other client-state homeland air defence through the 1950s and into the 1960s until replaced by MiG-17/19/21 families", "Jet conversion and continuation training in the two-seat UTI, which outlasted the single-seat fighter in many air arms", "Limited fighter-bomber and photo-reconnaissance work with underwing tanks, bombs or cameras", "Today almost entirely museum exhibits, a few airworthy warbirds on the display circuit, and static instructional hulks" ], "questions": [ { "id": "evidence-real-world-use-q01", "text": "Which of these real-world use hold for the sense of Mikoyan-Gurevich MiG-15 this model covers, and on what evidence?", "kind": "provenance" } ] }, { "id": "evidence-measurements", "name": "Typical measurements", "description": "Reported by the breadth pass; each item needs checking against its source before it becomes normative.", "evidence": [ { "quantity": "Wingspan", "typical_range": "10.08", "unit": "m" }, { "quantity": "Length (including pitot, published figures)", "typical_range": "10.10-10.86", "unit": "m" }, { "quantity": "Height", "typical_range": "3.35-3.70", "unit": "m" }, { "quantity": "Wing area", "typical_range": "20.6", "unit": "m²" }, { "quantity": "Empty weight", "typical_range": "3580-3750", "unit": "kg" }, { "quantity": "Maximum take-off weight (with drop tanks)", "typical_range": "5000-6110", "unit": "kg" }, { "quantity": "Maximum speed (MiG-15bis, high subsonic)", "typical_range": "1050-1075", "unit": "km/h" }, { "quantity": "Service ceiling", "typical_range": "15100-15500", "unit": "m" }, { "quantity": "Ferry range with drop tanks", "typical_range": "1860-2000", "unit": "km" }, { "quantity": "Engine static thrust (RD-45F then VK-1)", "typical_range": "22.3-26.5", "unit": "kN" }, { "quantity": "Cannon armament", "typical_range": "1×37 mm N-37 (about 40 rounds) plus 2×23 mm NR-23 (about 80 rounds each)", "unit": "count / rounds" } ], "questions": [ { "id": "evidence-measurements-q01", "text": "Which of these typical measurements hold for the sense of Mikoyan-Gurevich MiG-15 this model covers, and on what evidence?", "kind": "provenance" } ] }, { "id": "evidence-failure-modes-and-hazards", "name": "Failure modes and hazards", "description": "Reported by the breadth pass; each item needs checking against its source before it becomes normative.", "evidence": [ "High-Mach pitch-up, aileron buzz and loss of control approaching about Mach 0.9, a decisive handicap against energy fighters that could stay faster in a dive", "Abrupt stall and a hard-to-recover spin at high angle of attack, with little aerodynamic warning", "Early RD-45F and poorly filtered VK-1 installations prone to compressor stall or flameout from FOD, gun gas or contaminated fuel", "Very limited cannon ammunition and a slow-firing 37 mm gun, so a missed first pass often ended the engagement", "Poor rearward visibility from the faired canopy, inviting bounce attacks", "High approach speed, bounce on landing and nose-over or wing-drop on the ground", "Ejection-seat and canopy-jettison unreliability on early production aircraft", "On surviving airframes: corrosion, undocumented wartime repairs, and expired life-limited engine and structure parts" ], "questions": [ { "id": "evidence-failure-modes-and-hazards-q01", "text": "Which of these failure modes and hazards hold for the sense of Mikoyan-Gurevich MiG-15 this model covers, and on what evidence?", "kind": "provenance" } ] }, { "id": "evidence-regional-variation", "name": "Regional variation", "description": "Reported by the breadth pass; each item needs checking against its source before it becomes normative.", "evidence": [ "NATO/English usage is MiG-15 with reporting names Fagot (fighter) and Midget (trainer); Russian service usage is МиГ-15 with bis/UTI/P/R suffixes and factory izdeliye numbers", "Poland designated license-built fighters Lim-1 (RD-45) and Lim-2 (VK-1), not MiG-15 in local paperwork", "Czechoslovakia used S-102 / S-103 for fighters and CS-102 for the trainer", "China used J-2 for the fighter and JJ-2 for the trainer on Shenyang-assembled aircraft", "Western intelligence first catalogued the type as Type 14 before the NATO name became standard", "North Korean and some other operators kept UTI airframes in training or ceremonial roles long after Soviet front-line withdrawal" ], "questions": [ { "id": "evidence-regional-variation-q01", "text": "Which of these regional variation hold for the sense of Mikoyan-Gurevich MiG-15 this model covers, and on what evidence?", "kind": "provenance" } ] }, { "id": "evidence-neighbours", "name": "Neighbouring kinds and how to tell them apart", "description": "Reported by the breadth pass; each item needs checking against its source before it becomes normative.", "evidence": [ { "name": "Mikoyan-Gurevich MiG-17 (NATO Fresco)", "difference": "Later development: longer rear fuselage, 45° inboard wing sweep, usually three wing fences, and afterburning VK-1F on many versions; the MiG-15 has 35° sweep and two fences" }, { "name": "North American F-86 Sabre", "difference": "Contemporary opponent with a similar nose-intake swept layout; Sabre has a low-set tailplane, leading-edge slats, six 12.7 mm guns and no under-nose cannon troughs, versus the MiG-15's high tail, wing fences and 37/23 mm pack" }, { "name": "Lavochkin La-15 (NATO Fantail)", "difference": "Contemporary Soviet swept-wing jet of similar era but smaller, with a shoulder-mounted wing and different tail; not a Nene-powered mid-wing MiG" }, { "name": "Mikoyan-Gurevich MiG-19 (NATO Farmer)", "difference": "Supersonic twin-engine successor with afterburners and a mid-mounted wing; two nozzles and a sharply different planform, not a single centrifugal turbojet" }, { "name": "Republic F-84 Thunderjet / Thunderstreak", "difference": "Korean War jets sometimes confused in reports; straight-wing F-84E/G and swept F-84F lack the MiG-15's mid-wing fences, high tail and 37 mm nose pack" }, { "name": "Shenyang J-5", "difference": "Chinese MiG-17 derivative, not a MiG-15; treat as Fresco-family unless the airframe is the earlier J-2/JJ-2" } ], "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-15 this model covers, and on what evidence?", "kind": "provenance" } ] } ] } ] } ] }, "openQuestions": [ "Does the authoritative catalogue already contain a world model covering this concept, and how does it allocate MiG-15bis, MiG-15UTI and licensed derivatives?", "Which authenticated manufacturer references establish reliable recognition differences across production batches and between MiG-15 and MiG-17 airframes?", "Which original and translated manuals can be authenticated for each relevant engine, control-system and cockpit configuration?", "What inspection criteria and life-history evidence are available for surviving airframes with undocumented storage, repairs or component exchanges?", "Which aircraft-specific records resolve retained armament and escape-equipment status, historical authenticity and present permission for each intended use?" ], "statistics": { "bundles": 6, "layers": 11, "findings": 18, "questions": 35 } }, "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-15, record what state it is in, and decide what may be done with it.", "whatItIs": "Enable an AI agent to identify a Mikoyan-Gurevich MiG-15, establish an individual airframe's configuration and condition, and determine which inspection, preservation, movement or operational actions its evidence supports.", "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-15UTI, MiG-15P, MiG-15SB, MiG-15T, Lim-1, MiG-15 base, MiG-15bis, BA-5, MiG-15bisR, MiG-15bisS, MiG-15bisT, Lim-2.", "15 finer distinctions are held as aliases rather than separate entries, because telling them apart needs a task that asks for it.", "Described in 61 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-15, 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-15 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-15UTI", "MiG-15P", "MiG-15SB", "MiG-15T", "Lim-1", "MiG-15 base", "MiG-15bis", "BA-5", "MiG-15bisR", "MiG-15bisS", "MiG-15bisT", "Lim-2" ] } ], "standing": "Described in 61 Wikipedia languages, which measures how widely it is written about rather than how important or how common it is. 15 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-15 from another, and a Mikoyan-Gurevich MiG-15 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-15, 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-15, 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-15 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-15, 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-15, 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-15 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-15 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-15, 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-15, 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-15 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-15 from the things most often confused with it.", "questions": [ { "id": "distinguishing-features-q01", "text": "What identifies and describes what distinguishes a Mikoyan-Gurevich MiG-15, 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-15, 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-15 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-15 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-15, 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-15, 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-15 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-15 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-15, 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-15, 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-15 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-15 is judged and by whom.", "questions": [ { "id": "condition-assessment-q01", "text": "What identifies and describes the condition of a Mikoyan-Gurevich MiG-15, 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-15, 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-15 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-15 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-15 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-15, 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-15, 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-15 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-15 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-15, 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-15, 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-15 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-15 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-15 between them.", "questions": [ { "id": "stages-and-transitions-q01", "text": "What identifies and describes the lifecycle of a Mikoyan-Gurevich MiG-15, 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-15, 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-15 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-15, how often and by whom.", "findings": [ { "id": "observation-record", "name": "Observation record", "description": "How an observation of a Mikoyan-Gurevich MiG-15 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-15, 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-15, 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-15 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-15 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-15 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-15 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-15, 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-15, 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-15 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-15.", "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-15 at all.", "questions": [ { "id": "procedures-and-skills-q01", "text": "What identifies and describes handling a Mikoyan-Gurevich MiG-15, 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-15, 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-15 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-15 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-15 and how confident it is.", "questions": [ { "id": "claim-provenance-q01", "text": "What identifies and describes a claim about a Mikoyan-Gurevich MiG-15, 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-15, 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-15 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-15 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-15, 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-15, 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-15 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 } } } }