{ "model": { "rank": 5235, "code": "thing-q173680", "model_id": "vr.tr.sukhoi-su-27", "name": "Sukhoi Su-27", "purpose": "Enable an AI agent to recognise the Sukhoi Su-27 aircraft type, distinguish its variants and derivatives, and assess what configuration, condition and authorisation evidence is needed before proposing an action involving an example.", "family": "Thing Registry", "category": "Physical world and living systems", "status": "research-draft", "kind": "thing", "plane": "PHY", "domain": "PHY.OBJ", "industry": "", "version": "", "url": "/models/thing/q173680/", "tier": 2, "score": 69, "payload": { "layer": "wikidata", "aliases": [ "Sukhoi Su-37", "Sukhoi Su-33", "Sukhoi Su-35BM", "Shenyang J-15", "Sukhoi Su-35", "Sukhoi Su-34", "Shenyang J-15T", "Shenyang J-11", "Su-27SK", "Su-27UBK", "Su-27/30", "Shenyang J-16" ], "aliasCount": 12, "merged": 12, "knownIn": 69, "facets": null, "markers": [], "lexicalClass": "", "senseRank": null, "alsoRegisteredAs": null, "source": { "dataset": "wikidata", "item": "Q173680", "url": "https://www.wikidata.org/wiki/Q173680", "license": "CC0 1.0" } }, "research": { "vercy": "1.0-draft", "publication": { "status": "research-draft", "adjudicationStatus": "unreviewed", "publishableCanonical": false, "generatedAt": "2026-09-09T21:56:49Z", "providers": [ "Codex" ], "breadth": "recalled by Codex without web access - no source was read", "missingProviders": [], "pass": 2, "cost": { "grok": { "seconds": 24.3, "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: 01a0882b-75ee-7d21-b188-40f7de1da172\n--------\nuser\nDescribe what is already known about one registered thing. Answer as JSON only, no prose around it.\n\nThing: Sukhoi Su-27\nSense to describe: (none recorded)\nDomain code: PHY.OBJ\nAlso known as: (none)\n\n\nContext for this batch of 1001 things:\n# Batch 005: 1001 re", "usd": 0, "recall": true }, "codex": { "seconds": 65.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: 01a0882b-75f1-7cc1-a896-b0fb99a25c71\n--------\nuser\nYou are drafting a Vercy meta-model for one registered thing. Answer as JSON only, no prose around it.\n\nThing: Sukhoi Su-27\nRegistry id: vr.tr.sukhoi-su-27\nPlane / domain: PHY / PHY.OBJ\nRegistry definition: (none recorded)\nNames folded into this entry: (none)\n" } } }, "metaModel": { "id": "THING-Q173680", "registryId": "vr.tr.sukhoi-su-27", "name": "Sukhoi Su-27", "version": "0.1.0-research.1", "entryKind": "thing", "family": "Thing Registry", "domain": [ "PHY.OBJ" ], "status": "research-draft" }, "canonicalUrl": "https://ver.cy/models/thing/q173680/", "model": { "registry_id": "vr.tr.sukhoi-su-27", "name": "Sukhoi Su-27", "purpose": "Enable an AI agent to recognise the Sukhoi Su-27 aircraft type, distinguish its variants and derivatives, and assess what configuration, condition and authorisation evidence is needed before proposing an action involving an example.", "definition": "The Sukhoi Su-27 is a Soviet-designed, twin-engine, highly manoeuvrable supersonic fighter aircraft type developed primarily for long-range air superiority, with single-seat and two-seat variants.", "scope_statement": "This model owns the registered Su-27 aircraft type and the distinctions needed to interpret records about its variants and individual airframes; it does not treat the wider Flanker family as interchangeable with the Su-27 or substitute for an aircraft's approved documentation.", "in_scope": [ "Su-27 type identity, designation evidence and boundaries with related Sukhoi aircraft", "Variant-dependent airframe, propulsion, flight-control and avionics configuration", "Performance and operating limitations tied to a documented configuration", "Evidence needed to interpret an individual Su-27's serviceability and maintenance status", "Applicable operating, maintenance, ownership and access authorisations" ], "out_of_scope": [ "Independent models of related aircraft such as the Su-30, Su-33 and Su-35", "The complete design principles shared by all fighter aircraft", "Individual airframe logbooks, inventories and maintenance transactions", "Weapons employment, targeting and combat tactics", "Airbase operations, pilot training programmes and military force organisation" ], "distinguishing_features": [ "Require a documented Su-27 designation and variant suffix; a Flanker reporting name or visual resemblance alone does not establish membership.", "Use the combination of twin engines, twin vertical tails, blended wing-body form and separated engine nacelles as a visual consistency check, then resolve similar Sukhoi types through records.", "Check seating and canopy arrangement against the claimed variant; a two-seat aircraft requires differentiation between Su-27 trainer variants and related two-seat types.", "Check for carrier-related features, canards and other derivative-specific changes; their presence requires resolving the exact designation rather than automatically classifying the aircraft as a baseline Su-27." ], "characteristics": [ { "name": "Documented designation and variant", "kind": "category", "unit_or_values": "Exact designation, suffix and designation authority; unresolved permitted", "why_it_matters": "Determines which specifications and limitations may apply." }, { "name": "Relationship to the Su-27 type", "kind": "relation", "unit_or_values": "Variant of, derivative of, converted from, or visually similar to", "why_it_matters": "Prevents the broader aircraft family from being collapsed into this registry entry." }, { "name": "Crew and seating configuration", "kind": "category", "unit_or_values": "Seat count, arrangement and documented crew roles", "why_it_matters": "Supports variant identification and interpretation of cockpit and escape-system requirements." }, { "name": "Airframe dimensions", "kind": "measurement", "unit_or_values": "Length, wingspan and height in m, with measurement convention and variant", "why_it_matters": "Supports identification, clearance assessment, storage and transport planning." }, { "name": "Mass and fuel basis", "kind": "measurement", "unit_or_values": "Mass in kg; fuel in kg or L with density basis; loading condition and variant required", "why_it_matters": "Published weights and capacities cannot be compared without their configuration and measurement basis." }, { "name": "Propulsion installation", "kind": "relation", "unit_or_values": "Installed engine designation, modification status and applicable technical documentation", "why_it_matters": "Engine substitutions and modifications affect compatibility, maintenance and performance interpretation." }, { "name": "Flight-control configuration", "kind": "category", "unit_or_values": "Documented control-system standard and approved modifications", "why_it_matters": "Connects an airframe to the correct limitations, inspection requirements and fault interpretation." }, { "name": "Avionics and mission-system configuration", "kind": "relation", "unit_or_values": "Documented radar, navigation, communication and identification installations", "why_it_matters": "Avoids assigning one variant's equipment or capabilities to every Su-27." }, { "name": "Documented operating envelope", "kind": "measurement", "unit_or_values": "Speed in Mach and km/h with airspeed basis, altitude in m, load factor in g; conditions and authority required", "why_it_matters": "Separates approved limits from demonstration results and generic published maxima." }, { "name": "Serviceability evidence", "kind": "state", "unit_or_values": "Unknown, under assessment, restricted, released for a specified use, or withdrawn", "why_it_matters": "An aircraft's appearance or historical service record does not establish present fitness for use." }, { "name": "Life consumption", "kind": "measurement", "unit_or_values": "Flight hours, cycles, landings and calendar age as required by the applicable maintenance programme", "why_it_matters": "Connects structural and component eligibility to documented limits." }, { "name": "Authorised use", "kind": "relation", "unit_or_values": "Responsible authority, permitted activity, restrictions and validity period", "why_it_matters": "Technical capability alone does not establish permission to fly, maintain, transfer or display an example." } ], "affordances": [ "Classify a candidate aircraft record as a documented Su-27 variant, a related type or unresolved.", "Compare published Su-27 specifications after aligning variant, configuration, units and test conditions.", "Identify the manuals and configuration records needed to evaluate a particular airframe.", "Flag maintenance, modification or identity evidence that is missing or inconsistent.", "Determine whether a proposed inspection, display, transfer or operation needs specialist assessment or additional authorisation." ] }, "sources": [], "structure": { "bundles": [ { "id": "su-27-identity", "name": "Su-27 identity and family boundaries", "description": "Establishes what the registered Su-27 entry includes and how candidate records demonstrate membership.", "rationale": "Su-27 terminology can refer loosely to a wider family whose members require distinct specifications and authority.", "layers": [ { "id": "designation-evidence", "name": "Designation evidence", "description": "Connects names and variant suffixes to traceable identification records.", "findings": [ { "id": "documented-type-membership", "name": "Documented type membership", "description": "Record the evidence supporting a Su-27 designation without treating an informal family name as decisive.", "questions": [ { "text": "Which manufacturer, service or airframe identification record establishes the exact Su-27 designation?", "kind": "provenance", "id": "documented-type-membership-q01" }, { "text": "Does the source describe the aircraft type, a production variant or one serial-numbered airframe?", "kind": "boundary", "id": "documented-type-membership-q02" } ] } ] }, { "id": "variants-and-derivatives", "name": "Variants and derivatives", "description": "Resolves trainer, export and modified configurations against neighbouring aircraft types.", "findings": [ { "id": "variant-boundary", "name": "Variant boundary", "description": "Represent documented relationships without assuming every Flanker derivative belongs inside this entry.", "questions": [ { "text": "Which Su-27 suffixes are included, and what evidence distinguishes them from separately designated Su-30, Su-33 or Su-35 aircraft?", "kind": "boundary", "id": "variant-boundary-q01" }, { "text": "If an airframe was converted or redesignated, which identity applies to the date being described?", "kind": "provenance", "id": "variant-boundary-q02" } ] } ] } ] }, { "id": "su-27-configuration", "name": "Airframe and installed systems", "description": "Describes the configuration distinctions needed to interpret a Su-27's physical and functional characteristics.", "rationale": "A recognisable Su-27 silhouette does not establish the installed engines, controls or avionics.", "layers": [ { "id": "airframe-and-propulsion", "name": "Airframe and propulsion", "description": "Relates geometry, seating and engine installation to the documented variant.", "findings": [ { "id": "physical-configuration", "name": "Physical configuration", "description": "Keep dimensions, mass conventions and propulsion records attached to their actual configuration.", "questions": [ { "text": "What dimensions, seating arrangement and engine designation are documented for this Su-27 variant?", "kind": "measurement", "id": "physical-configuration-q01" }, { "text": "Which changes from its production configuration are supported by modification records?", "kind": "provenance", "id": "physical-configuration-q02" } ] } ] }, { "id": "controls-and-avionics", "name": "Controls and avionics", "description": "Distinguishes flight-control and mission-system installations across Su-27 configurations.", "findings": [ { "id": "installed-system-standard", "name": "Installed system standard", "description": "Associate system descriptions with verified installations rather than a generic Su-27 capability list.", "questions": [ { "text": "Which flight-control, radar, navigation and communication standards are supported by the configuration evidence?", "kind": "provenance", "id": "installed-system-standard-q01" }, { "text": "What documentation establishes compatibility between installed replacements, upgrades and the claimed variant?", "kind": "boundary", "id": "installed-system-standard-q02" } ] } ] } ] }, { "id": "su-27-operating-limits", "name": "Performance and operating limits", "description": "Makes Su-27 performance claims interpretable through configuration, conditions and documentary authority.", "rationale": "Range, speed and manoeuvring claims are misleading when detached from loading and the applicable flight documentation.", "layers": [ { "id": "performance-basis", "name": "Performance basis", "description": "Captures the conditions behind quoted capacities and performance.", "findings": [ { "id": "conditional-performance", "name": "Conditional performance", "description": "Treat published performance as a conditioned claim rather than an unconditional property.", "questions": [ { "text": "For each quoted speed, range or altitude, what variant, loading, fuel state and flight profile does the source specify?", "kind": "measurement", "id": "conditional-performance-q01" }, { "text": "Is the value an approved limit, a test result, a manufacturer claim or an estimate?", "kind": "provenance", "id": "conditional-performance-q02" } ] } ] }, { "id": "approved-limitations", "name": "Approved limitations", "description": "Connects operating restrictions to the aircraft's current configuration.", "findings": [ { "id": "applicable-flight-documentation", "name": "Applicable flight documentation", "description": "Require the governing documentation before interpreting operational eligibility.", "questions": [ { "text": "Which flight-manual revision and supplements govern this Su-27 configuration?", "kind": "provenance", "id": "applicable-flight-documentation-q01" }, { "text": "Which documented restrictions arising from modifications, loading or system status affect the proposed activity?", "kind": "action", "id": "applicable-flight-documentation-q02" } ] } ] } ] }, { "id": "su-27-maintenance-and-condition", "name": "Maintenance and condition evidence", "description": "Defines the evidence needed to interpret the condition of an individual Su-27 without embedding its logbook in the type model.", "rationale": "Age, service history, component limits and preservation can make superficially similar airframes eligible for very different uses.", "layers": [ { "id": "structural-and-component-life", "name": "Structural and component life", "description": "Connects recorded usage and inspections to applicable life limits.", "findings": [ { "id": "life-limit-evidence", "name": "Life-limit evidence", "description": "Identify required usage measures and supporting records for the airframe and life-limited components.", "questions": [ { "text": "Which approved limits apply to the airframe, installed engines and other life-limited components?", "kind": "provenance", "id": "life-limit-evidence-q01" }, { "text": "Are hours, cycles, calendar life and any authorised extensions traceable through the available records?", "kind": "measurement", "id": "life-limit-evidence-q02" } ] } ] }, { "id": "system-condition-and-preservation", "name": "System condition and preservation", "description": "Distinguishes documented serviceability from storage, display or incomplete restoration.", "findings": [ { "id": "condition-assessment", "name": "Condition assessment", "description": "Require appropriate evidence for propulsion, controls, landing gear and safety-critical equipment.", "questions": [ { "text": "What inspection or test records establish the status of engines, flight controls, hydraulic systems, landing gear and escape equipment?", "kind": "provenance", "id": "condition-assessment-q01" }, { "text": "Which preservation, consumable replacement or specialist inspections are required before the proposed use?", "kind": "action", "id": "condition-assessment-q02" } ] } ] } ] }, { "id": "su-27-authority-and-safe-use", "name": "Authority and safe use", "description": "Connects a proposed activity involving a Su-27 to responsible authorities, qualified personnel and configuration-specific safeguards.", "rationale": "Military service, private operation and museum display require different evidence of permission and safe condition.", "layers": [ { "id": "governing-authority", "name": "Governing authority", "description": "Identifies the regime and documents governing a particular example and activity.", "findings": [ { "id": "activity-authorisation", "name": "Activity authorisation", "description": "Record the actual approval basis rather than assuming a universal Su-27 certification standard.", "questions": [ { "text": "Which military or civil authority governs this airframe, and which approval covers the proposed activity?", "kind": "provenance", "id": "activity-authorisation-q01" }, { "text": "What qualifications, restrictions and validity conditions must be checked before that activity proceeds?", "kind": "action", "id": "activity-authorisation-q02" } ] } ] }, { "id": "ground-and-display-safety", "name": "Ground and display safety", "description": "Accounts for hazards that depend on installed equipment and preservation status.", "findings": [ { "id": "hazard-status-evidence", "name": "Hazard status evidence", "description": "Treat escape-system, fuel, pressure and installed military-equipment status as matters requiring documented specialist assessment.", "questions": [ { "text": "What records establish whether escape-system pyrotechnics, residual fuel, stored pressure and installed military equipment remain hazardous?", "kind": "provenance", "id": "hazard-status-evidence-q01" }, { "text": "Which documented access restrictions and specialist clearances apply before handling, transport or public display?", "kind": "action", "id": "hazard-status-evidence-q02" } ] } ] } ] }, { "id": "evidence-and-external-alignment", "name": "Evidence and external alignment", "description": "What the world already says about this thing, gathered so the model can be checked against it.", "rationale": "A model that cannot be lined up against existing standards, identifiers and practice cannot be adopted by anyone who already uses them.", "layers": [ { "id": "reported-evidence", "name": "Reported evidence", "description": "Findings from the breadth pass, kept separate from the structural claims.", "findings": [ { "id": "evidence-confidence-notes", "name": "Check these first", "description": "Recalled without web access and unsourced; every item is a lead to verify.", "evidence": [ "This describes an aircraft type, not an individual airframe or every aircraft in the wider Flanker family.", "Dimensions, mass limits and performance are recalled approximate baseline values; check the exact variant, load and operating conditions.", "No sources were consulted; applicable military airworthiness rules, life limits and operator-specific configurations need verification." ], "questions": [ { "id": "evidence-confidence-notes-q01", "text": "Which of these check these first hold for the sense of Sukhoi Su-27 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": [ "Su-27S: initial production combat variant", "Su-27P: air-defence interceptor variant", "Su-27UB: two-seat combat trainer", "Su-27SK: export single-seat variant", "Su-27UBK: export two-seat combat trainer", "Su-27SM: modernised multirole variant" ], "questions": [ { "id": "evidence-kinds-q01", "text": "Which of these kinds and varieties hold for the sense of Sukhoi Su-27 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": "Sukhoi aircraft designation", "value_or_pattern": "Su-27", "note": "Identifies the aircraft type; suffixes distinguish variants, while serial numbers identify individual airframes." }, { "scheme": "NATO reporting name", "value_or_pattern": "Flanker", "note": "Reporting-name family covering the Su-27 and related derivatives; suffixes distinguish particular configurations." }, { "scheme": "ICAO aircraft type designator", "value_or_pattern": "SU27", "note": "Operational type designator, distinct from an aircraft registration or military serial." } ], "questions": [ { "id": "evidence-identifiers-q01", "text": "Which of these identifiers and schemes hold for the sense of Sukhoi Su-27 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-superiority patrols and fighter interception", "Escort of other military aircraft", "Pilot conversion and combat training in two-seat variants", "Aerobatic demonstrations", "Air-to-surface missions, with capabilities dependent on variant and modernisation" ], "questions": [ { "id": "evidence-real-world-use-q01", "text": "Which of these real-world use hold for the sense of Sukhoi Su-27 this model covers, and on what evidence?", "kind": "provenance" } ] }, { "id": "evidence-measurements", "name": "Typical measurements", "description": "Recalled without web access and unsourced; every item is a lead to verify.", "evidence": [ { "quantity": "Overall length of a baseline single-seat Su-27", "typical_range": "approximately 21.9", "unit": "m" }, { "quantity": "Wingspan of a baseline Su-27", "typical_range": "approximately 14.7", "unit": "m" }, { "quantity": "Overall height", "typical_range": "approximately 5.9", "unit": "m" }, { "quantity": "Maximum takeoff mass of a baseline Su-27", "typical_range": "approximately 30,000-33,000", "unit": "kg" }, { "quantity": "Maximum speed at altitude", "typical_range": "approximately 2.35", "unit": "Mach" } ], "questions": [ { "id": "evidence-measurements-q01", "text": "Which of these typical measurements hold for the sense of Sukhoi Su-27 this model covers, and on what evidence?", "kind": "provenance" } ] }, { "id": "evidence-failure-modes-and-hazards", "name": "Failure modes and hazards", "description": "Recalled without web access and unsourced; every item is a lead to verify.", "evidence": [ "Engine failure, fire or foreign-object ingestion can reduce thrust or require an emergency landing.", "Flight-control or hydraulic-system faults can degrade controllability.", "High-angle-of-attack manoeuvring can lead to departure from controlled flight outside the applicable flight envelope.", "Structural fatigue and corrosion require inspection, particularly in ageing airframes.", "Ejection seats, carried weapons, engine intakes and jet exhaust present serious ground-handling hazards." ], "questions": [ { "id": "evidence-failure-modes-and-hazards-q01", "text": "Which of these failure modes and hazards hold for the sense of Sukhoi Su-27 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 distinguished tactical aviation and air-defence variants; export customers received configurations such as the Su-27SK and Su-27UBK.", "Operator-specific upgrades can change avionics, communications and weapons compatibility substantially.", "Chinese licensed production contributed to the J-11 lineage, whose later developments require treatment as distinct derivatives." ], "questions": [ { "id": "evidence-regional-variation-q01", "text": "Which of these regional variation hold for the sense of Sukhoi Su-27 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": "Fighter aircraft", "difference": "The broader functional category; Su-27 denotes a particular aircraft design and its variants." }, { "name": "Sukhoi Su-30", "difference": "A related two-seat multirole derivative with a separate type designation; a two-seat Su-27UB is not automatically a Su-30." }, { "name": "Sukhoi Su-33", "difference": "A carrier-capable derivative with naval operating features, including folding wings and an arresting hook." }, { "name": "Sukhoi Su-35", "difference": "A separately designated development of the Flanker lineage with substantial changes; specifications depend on which Su-35 generation is meant." }, { "name": "Shenyang J-11", "difference": "A Chinese production and development lineage originating from the Su-27, with later variants incorporating substantial domestic changes." } ], "questions": [ { "id": "evidence-neighbours-q01", "text": "Which of these neighbouring kinds and how to tell them apart hold for the sense of Sukhoi Su-27 this model covers, and on what evidence?", "kind": "provenance" } ] } ] } ] } ] }, "openQuestions": [ "Which production, trainer, export and modernised Su-27 variants should this registry entry include, and which already have separate registry or world-model coverage?", "Which authoritative sources can establish variant-specific dimensions, masses, engine installations and performance without mixing configurations?", "Which flight and maintenance documentation is available, authentic and applicable to the variants being modelled?", "Which Su-27 failure modes, inspection requirements, consumables and life limits can be substantiated from authoritative maintenance evidence?", "How should this type model represent jurisdiction-dependent military operation, civil operation and demilitarised display status without implying a universal approval regime?" ], "statistics": { "bundles": 6, "layers": 11, "findings": 18, "questions": 28 } }, "draft": { "generator": "vr.draft.v3", "status": "draft-generated", "researched": false, "archetype": "unclassified", "method": "Written from the archetype playbook - what this kind of thing needs beyond identity and provenance - and from the structure that recurred across 6,333 models already researched by two engines. Applied to this entry by rule. No source was read for this thing and no claim here is researched. This entry carries no facets of its own, so they were inferred from its domain - a guess about a whole domain applied to one thing.", "facetsInferred": true, "nextPass": "A researcher replaces this draft with a sourced specification. Treat every sentence below as a proposal to argue with.", "purpose": "Give an agent a durable, checkable way to recognise a Sukhoi Su-27, record what state it is in, and decide what may be done with it.", "whatItIs": "Enable an AI agent to recognise the Sukhoi Su-27 aircraft type, distinguish its variants and derivatives, and assess what configuration, condition and authorisation evidence is needed before proposing an action involving an example.", "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: Sukhoi Su-37, Sukhoi Su-33, Sukhoi Su-35BM, Shenyang J-15, Sukhoi Su-35, Sukhoi Su-34, Shenyang J-15T, Shenyang J-11, Su-27SK, Su-27UBK, Su-27/30, Shenyang J-16.", "12 finer distinctions are held as aliases rather than separate entries, because telling them apart needs a task that asks for it.", "Described in 69 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 Sukhoi Su-27, 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 Sukhoi Su-27 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": [ "Sukhoi Su-37", "Sukhoi Su-33", "Sukhoi Su-35BM", "Shenyang J-15", "Sukhoi Su-35", "Sukhoi Su-34", "Shenyang J-15T", "Shenyang J-11", "Su-27SK", "Su-27UBK", "Su-27/30", "Shenyang J-16" ] } ], "standing": "Described in 69 Wikipedia languages, which measures how widely it is written about rather than how important or how common it is. 12 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 Sukhoi Su-27 from another, and a Sukhoi Su-27 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 Sukhoi Su-27, 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 Sukhoi Su-27, 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 Sukhoi Su-27 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 Sukhoi Su-27, 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 Sukhoi Su-27, 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 Sukhoi Su-27 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 Sukhoi Su-27 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 Sukhoi Su-27, 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 Sukhoi Su-27, 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 Sukhoi Su-27 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 Sukhoi Su-27 from the things most often confused with it.", "questions": [ { "id": "distinguishing-features-q01", "text": "What identifies and describes what distinguishes a Sukhoi Su-27, 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 Sukhoi Su-27, 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 Sukhoi Su-27 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 Sukhoi Su-27 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 Sukhoi Su-27, 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 Sukhoi Su-27, 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 Sukhoi Su-27 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 Sukhoi Su-27 is built from and which parts are replaceable.", "questions": [ { "id": "parts-and-materials-q01", "text": "What identifies and describes the composition of a Sukhoi Su-27, 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 Sukhoi Su-27, 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 Sukhoi Su-27 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 Sukhoi Su-27 is judged and by whom.", "questions": [ { "id": "condition-assessment-q01", "text": "What identifies and describes the condition of a Sukhoi Su-27, 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 Sukhoi Su-27, 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 Sukhoi Su-27 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 Sukhoi Su-27 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 Sukhoi Su-27 is, and what that position is measured against.", "questions": [ { "id": "position-and-frame-q01", "text": "What identifies and describes the location of a Sukhoi Su-27, 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 Sukhoi Su-27, 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 Sukhoi Su-27 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 Sukhoi Su-27 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 Sukhoi Su-27, 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 Sukhoi Su-27, 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 Sukhoi Su-27 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 Sukhoi Su-27 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 Sukhoi Su-27 between them.", "questions": [ { "id": "stages-and-transitions-q01", "text": "What identifies and describes the lifecycle of a Sukhoi Su-27, 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 Sukhoi Su-27, 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 Sukhoi Su-27 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 Sukhoi Su-27, how often and by whom.", "findings": [ { "id": "observation-record", "name": "Observation record", "description": "How an observation of a Sukhoi Su-27 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 Sukhoi Su-27, 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 Sukhoi Su-27, 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 Sukhoi Su-27 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 Sukhoi Su-27 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 Sukhoi Su-27 is for, and what it is used for anyway.", "findings": [ { "id": "function-and-purpose", "name": "Function, purpose and misuse", "description": "The function a Sukhoi Su-27 performs and the uses that fall outside it.", "questions": [ { "id": "function-and-purpose-q01", "text": "What identifies and describes the use of a Sukhoi Su-27, 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 Sukhoi Su-27, 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 Sukhoi Su-27 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 Sukhoi Su-27.", "findings": [ { "id": "procedures-and-skills", "name": "Procedures, skills and required tools", "description": "What an agent needs before it can act on a Sukhoi Su-27 at all.", "questions": [ { "id": "procedures-and-skills-q01", "text": "What identifies and describes handling a Sukhoi Su-27, 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 Sukhoi Su-27, 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 Sukhoi Su-27 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 Sukhoi Su-27 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 Sukhoi Su-27 and how confident it is.", "questions": [ { "id": "claim-provenance-q01", "text": "What identifies and describes a claim about a Sukhoi Su-27, 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 Sukhoi Su-27, 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 Sukhoi Su-27 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 Sukhoi Su-27 is retired without being erased.", "questions": [ { "id": "validity-and-supersession-q01", "text": "What identifies and describes the validity of a claim about a Sukhoi Su-27, 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 Sukhoi Su-27, 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 Sukhoi Su-27 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 } } } }