{ "model": { "rank": 5630, "code": "thing-q204331", "model_id": "vr.tr.sukhoi-su-30", "name": "Sukhoi Su-30", "purpose": "Enable an AI agent to recognise a Sukhoi Su-30 family member, assess evidence about its configuration and condition, and identify the approvals needed for a proposed use.", "family": "Thing Registry", "category": "Physical world and living systems", "status": "research-draft", "kind": "thing", "plane": "PHY", "domain": "PHY.OBJ", "industry": "", "version": "", "url": "/models/thing/q204331/", "tier": 2, "score": 66, "payload": { "layer": "wikidata", "aliases": [ "Sukhoi Su-30MKA", "Su-30MKM", "Su-30MKK", "Su-30MKI" ], "aliasCount": 4, "merged": 4, "knownIn": 66, "facets": null, "markers": [], "lexicalClass": "", "senseRank": null, "alsoRegisteredAs": null, "source": { "dataset": "wikidata", "item": "Q204331", "url": "https://www.wikidata.org/wiki/Q204331", "license": "CC0 1.0" } }, "research": { "vercy": "1.0-draft", "publication": { "status": "research-draft", "adjudicationStatus": "unreviewed", "publishableCanonical": false, "generatedAt": "2026-09-09T22:48:23Z", "providers": [ "Codex" ], "breadth": "recalled by Codex without web access - no source was read", "missingProviders": [], "pass": 2, "cost": { "grok": { "seconds": 23.4, "error": "Reading additional input from stdin...\nOpenAI Codex v0.153.4\n--------\nworkdir: R:\\02_PROJECTS\\02_Meta_Models_Platforms\\Ver.cy\\current\\thing-registry-backlog\nmodel: gpt-6-astra\nprovider: openai\napproval: never\nsandbox: read-only\nreasoning effort: none\nreasoning summaries: none\nsession id: 01a0885a-94ba-7211-92e0-1487652e49c7\n--------\nuser\nDescribe what is already known about one registered thing. Answer as JSON only, no prose around it.\n\nThing: Sukhoi Su-30\nSense to describe: (none recorded)\nDomain code: PHY.OBJ\nAlso known as: (none)\n\n\nContext for this batch of 188 things:\n# Batch 006: 1001 reg", "usd": 0, "recall": true }, "codex": { "seconds": 71.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: 01a0885a-94b6-7363-848c-429d38e3d529\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-30\nRegistry id: vr.tr.sukhoi-su-30\nPlane / domain: PHY / PHY.OBJ\nRegistry definition: (none recorded)\nNames folded into this entry: (none)\n" } } }, "metaModel": { "id": "THING-Q204331", "registryId": "vr.tr.sukhoi-su-30", "name": "Sukhoi Su-30", "version": "0.1.0-research.1", "entryKind": "thing", "family": "Thing Registry", "domain": [ "PHY.OBJ" ], "status": "research-draft" }, "canonicalUrl": "https://ver.cy/models/thing/q204331/", "model": { "registry_id": "vr.tr.sukhoi-su-30", "name": "Sukhoi Su-30", "purpose": "Enable an AI agent to recognise a Sukhoi Su-30 family member, assess evidence about its configuration and condition, and identify the approvals needed for a proposed use.", "definition": "The Sukhoi Su-30 is a family of Russian-designed, twin-engine, two-seat, multirole combat aircraft developed from the Su-27 lineage for air-to-air and air-to-surface missions.", "scope_statement": "This model owns the Su-30 aircraft family represented by vr.tr.sukhoi-su-30 in PHY / PHY.OBJ, including variant distinctions and the evidence required to assess an associated aircraft; individual airframes remain instances, and variant-specific properties must not become universal family claims.", "in_scope": [ "Su-30 family identity, variant designation and configuration provenance", "Variant-dependent airframe, propulsion, flight-control and cockpit arrangements", "Installed avionics, equipment interfaces and documented role eligibility", "Configuration-qualified dimensions, masses and performance limits", "Airframe condition, maintenance applicability and operating authorization" ], "out_of_scope": [ "The general aircraft or military fighter category", "Separate models for neighbouring Sukhoi aircraft families", "Individual airframe identity, ownership and service history as standalone records", "Independent models of engines, weapons, sensors and ground equipment", "Combat tactics, targeting decisions and weapon employment procedures", "Operator organisations, procurement programmes and geopolitical assessments" ], "distinguishing_features": [ "Require a documented Su-30 designation and traceable variant identity; resemblance to another Sukhoi aircraft is insufficient.", "Use the two-seat arrangement as a consistency check: manufacturer descriptions identify both Su-30MKI and Su-30SME as two-seat aircraft, but seating alone does not establish family membership. [HAL Su-30MKI](https://hal-india.co.in/product/su-30-mki), [UAC Su-30SME](https://uacrussia.ru/en/aircraft/lineup/military/su-30sme/)", "Compare the exact suffix and modification baseline before transferring an engine, radar, flight-control or performance claim between Su-30 records.", "Check observed canards, exhaust-nozzle configuration and cockpit layout against documentation for the identified variant; do not treat an unverified visual feature as a family-wide requirement.", "Distinguish the family designation from a serial number or operator marking: the former identifies the registered thing, while the latter identifies an associated aircraft." ], "characteristics": [ { "name": "Documented variant and baseline", "kind": "category", "unit_or_values": "Exact source designation, production baseline and incorporated modification identifiers; unresolved permitted", "why_it_matters": "Determines which Su-30 technical claims and instructions apply." }, { "name": "Identity evidence", "kind": "relation", "unit_or_values": "Links to manufacturer documentation, airframe identification and configuration records", "why_it_matters": "Prevents classification from relying solely on appearance or informal labels." }, { "name": "Crew-station configuration", "kind": "category", "unit_or_values": "Seat arrangement, documented station functions and installed controls", "why_it_matters": "Separates physical seating from approved crew roles and training use." }, { "name": "Airframe and control configuration", "kind": "category", "unit_or_values": "Documented aerodynamic surfaces, control-system baseline and nozzle-control configuration", "why_it_matters": "Supports variant recognition and prevents inappropriate handling assumptions." }, { "name": "Installed propulsion", "kind": "relation", "unit_or_values": "Engine model and modification standard linked to installation approval", "why_it_matters": "Connects propulsion characteristics and maintenance requirements to the actual configuration." }, { "name": "Dimensions and clearance envelope", "kind": "measurement", "unit_or_values": "Length, span, height and required clearances in m, with configuration and source", "why_it_matters": "Supports hangar, transport and ground-support compatibility checks." }, { "name": "Mass and fuel limits", "kind": "measurement", "unit_or_values": "kg, separating empty-mass definition, fuel capacity and approved operating mass limits", "why_it_matters": "Avoids comparing incompatible mass definitions or applying another variant's limits." }, { "name": "Published performance conditions", "kind": "measurement", "unit_or_values": "Speed in Mach or km/h, altitude in m, distance in km and endurance in h, each with stated conditions", "why_it_matters": "Keeps maximum speed, range, radius and endurance from becoming unconditional capabilities." }, { "name": "Avionics and interface baseline", "kind": "relation", "unit_or_values": "Installed sensor, navigation, communication and software identifiers linked to compatibility evidence", "why_it_matters": "A shared Su-30 name does not establish equipment equivalence." }, { "name": "Life consumption", "kind": "measurement", "unit_or_values": "Flight hours, cycles and calendar age against applicable component and airframe limits", "why_it_matters": "Supports assessment of remaining authorized service life." }, { "name": "Technical serviceability", "kind": "state", "unit_or_values": "Unknown, under maintenance, unserviceable, serviceable with restrictions, serviceable; dated and attributed", "why_it_matters": "Describes condition without implying permission to operate." }, { "name": "Operating authorization", "kind": "relation", "unit_or_values": "Applicable military airworthiness authority, release record, permitted activity and restrictions", "why_it_matters": "Establishes who may authorize a proposed activity for the identified configuration." } ], "affordances": [ "Classify an aircraft as a documented Su-30 variant and flag conflicting identity evidence.", "Compare variant configurations while preserving the applicability of each technical claim.", "Check published dimensions and equipment interfaces against proposed storage or support arrangements.", "Identify missing inspection, life-limit and configuration evidence before a serviceability assessment.", "Determine which authority, approved documents and personnel qualifications govern a proposed maintenance or operating activity.", "Link associated airframe records to this family model without creating duplicate registry concepts." ] }, "sources": [], "structure": { "bundles": [ { "id": "family-and-variant-identity", "name": "Family and variant identity", "description": "Establish what qualifies as Su-30 and which configuration is being described.", "rationale": "Su-30 family membership must remain distinct from variant identity and individual aircraft identity.", "layers": [ { "id": "designation-boundary", "name": "Designation boundary", "description": "Resolve official designations and neighbouring aircraft boundaries.", "findings": [ { "id": "documented-family-membership", "name": "Documented family membership", "description": "Classification requires evidence connecting the designation to the registered Su-30 family.", "questions": [ { "text": "Which manufacturer or authority document establishes this designation as a Su-30 family member?", "kind": "provenance", "id": "documented-family-membership-q01" }, { "text": "What documentary evidence separates it from a similarly configured neighbouring Sukhoi aircraft?", "kind": "boundary", "id": "documented-family-membership-q02" } ] } ] }, { "id": "configuration-provenance", "name": "Configuration provenance", "description": "Connect the variant designation to production and modification evidence.", "findings": [ { "id": "variant-baseline-traceability", "name": "Variant baseline traceability", "description": "A suffix establishes a starting point; incorporated changes determine the applicable configuration.", "questions": [ { "text": "What exact variant, production baseline and modification status does the supporting record identify?", "kind": "definition", "id": "variant-baseline-traceability-q01" }, { "text": "Which records substantiate departures from the published baseline for this Su-30 variant?", "kind": "provenance", "id": "variant-baseline-traceability-q02" } ] } ] } ] }, { "id": "airframe-propulsion-and-controls", "name": "Airframe, propulsion and controls", "description": "Describe the physical and control-system configuration relevant to recognising and supporting a Su-30 variant.", "rationale": "Aerodynamic and propulsion features cannot be transferred between variants without checking applicability.", "layers": [ { "id": "airframe-configuration", "name": "Airframe configuration", "description": "Record observable geometry and documented control arrangements.", "findings": [ { "id": "geometry-and-control-evidence", "name": "Geometry and control evidence", "description": "Observed surfaces and dimensions are checked against a named Su-30 configuration.", "questions": [ { "text": "What aerodynamic surfaces and flight-control baseline are documented for this variant?", "kind": "definition", "id": "geometry-and-control-evidence-q01" }, { "text": "What sourced length, span and height apply, and in what equipment configuration?", "kind": "measurement", "id": "geometry-and-control-evidence-q02" } ] } ] }, { "id": "propulsion-installation", "name": "Propulsion installation", "description": "Resolve engine and exhaust-control applicability.", "findings": [ { "id": "engine-installation-identity", "name": "Engine installation identity", "description": "Propulsion assessment follows the installed engine standard and its approved integration.", "questions": [ { "text": "Which engine model and modification standard are approved and recorded as installed?", "kind": "provenance", "id": "engine-installation-identity-q01" }, { "text": "Does this configuration include controlled thrust-vectoring nozzles, and what evidence establishes their installation and status?", "kind": "definition", "id": "engine-installation-identity-q02" } ] } ] } ] }, { "id": "crew-avionics-and-role-configuration", "name": "Crew, avionics and role configuration", "description": "Connect crew stations and installed systems to documented aircraft roles.", "rationale": "Two seats and a multirole designation do not establish identical crew functions or equipment across the family.", "layers": [ { "id": "crew-stations", "name": "Crew stations", "description": "Distinguish seating from installed controls and authorized crew functions.", "findings": [ { "id": "station-role-applicability", "name": "Station role applicability", "description": "Crew-station functions require variant-specific documentation rather than assumptions about the second seat.", "questions": [ { "text": "Which flight, instruction and system-management functions are available at each station in this configuration?", "kind": "definition", "id": "station-role-applicability-q01" }, { "text": "Which approved document establishes the crew composition and qualifications for the proposed activity?", "kind": "action", "id": "station-role-applicability-q02" } ] } ] }, { "id": "installed-systems", "name": "Installed systems", "description": "Identify avionics and equipment eligibility without inferring operational effectiveness.", "findings": [ { "id": "avionics-and-interface-applicability", "name": "Avionics and interface applicability", "description": "Role and compatibility claims must identify installed hardware, software and approval scope.", "questions": [ { "text": "Which radar, navigation, communication and mission-system baselines are documented for this Su-30 configuration?", "kind": "provenance", "id": "avionics-and-interface-applicability-q01" }, { "text": "Which equipment compatibility claims have configuration-specific approval rather than family-level marketing support?", "kind": "boundary", "id": "avionics-and-interface-applicability-q02" } ] } ] } ] }, { "id": "qualified-limits-and-support-fit", "name": "Qualified limits and support fit", "description": "Make Su-30 specification comparisons and support decisions conditional on configuration and source definitions.", "rationale": "Published headline values cannot independently establish the limits or support needs of a particular variant.", "layers": [ { "id": "mass-fuel-and-performance", "name": "Mass, fuel and performance", "description": "Preserve definitions and conditions attached to numerical specifications.", "findings": [ { "id": "conditional-specification-values", "name": "Conditional specification values", "description": "Every mass, fuel and performance value carries variant, configuration and measurement context.", "questions": [ { "text": "Which empty-mass definition, fuel capacity and operating mass limits apply to the identified variant?", "kind": "measurement", "id": "conditional-specification-values-q01" }, { "text": "Do reported distance values describe ferry range, another range definition or mission radius, and what conditions accompany them?", "kind": "measurement", "id": "conditional-specification-values-q02" } ] } ] }, { "id": "ground-support-compatibility", "name": "Ground support compatibility", "description": "Determine whether facilities and support equipment match the documented aircraft configuration.", "findings": [ { "id": "facility-and-equipment-fit", "name": "Facility and equipment fit", "description": "Storage and servicing eligibility depend on clearances and approved support interfaces.", "questions": [ { "text": "What documented clearances and ground-loading constraints govern storage or movement of this Su-30 configuration?", "kind": "measurement", "id": "facility-and-equipment-fit-q01" }, { "text": "Which ground-power, towing and servicing equipment references are approved for this variant?", "kind": "action", "id": "facility-and-equipment-fit-q02" } ] } ] } ] }, { "id": "sustainment-and-authorized-state", "name": "Sustainment and authorized state", "description": "Assess condition and permitted activity using applicable maintenance and military airworthiness evidence.", "rationale": "A recognisable Su-30 with an apparently complete configuration may still lack serviceability evidence or operating authorization.", "layers": [ { "id": "maintenance-and-life", "name": "Maintenance and life", "description": "Connect accumulated use, defects and maintenance requirements to the correct variant baseline.", "findings": [ { "id": "remaining-life-and-defect-evidence", "name": "Remaining life and defect evidence", "description": "Life consumption and unresolved defects are assessed against applicable approved records.", "questions": [ { "text": "What flight hours, cycles and calendar limits apply to the airframe and installed life-limited components?", "kind": "measurement", "id": "remaining-life-and-defect-evidence-q01" }, { "text": "Which applicable Su-30 maintenance instructions, inspections or service bulletins remain outstanding?", "kind": "provenance", "id": "remaining-life-and-defect-evidence-q02" }, { "text": "Which recorded defects require restriction or withdrawal under the applicable approved documentation?", "kind": "action", "id": "remaining-life-and-defect-evidence-q03" } ] } ] }, { "id": "release-and-ground-safety", "name": "Release and ground safety", "description": "Separate technical condition from permission to maintain, move or operate the aircraft.", "findings": [ { "id": "activity-specific-authorization", "name": "Activity-specific authorization", "description": "Permitted activity depends on a valid release, configuration restrictions and documented safety status.", "questions": [ { "text": "Which military airworthiness authority and current release govern the proposed activity for this Su-30?", "kind": "provenance", "id": "activity-specific-authorization-q01" }, { "text": "What documented status of escape systems, onboard stores and maintenance isolations is required before the proposed ground activity?", "kind": "action", "id": "activity-specific-authorization-q02" }, { "text": "Does the available evidence authorize flight, restricted ground activity, storage or display only?", "kind": "boundary", "id": "activity-specific-authorization-q03" } ] } ] } ] }, { "id": "evidence-and-external-alignment", "name": "Evidence and external alignment", "description": "What the world already says about this thing, gathered so the model can be checked against it.", "rationale": "A model that cannot be lined up against existing standards, identifiers and practice cannot be adopted by anyone who already uses them.", "layers": [ { "id": "reported-evidence", "name": "Reported evidence", "description": "Findings from the breadth pass, kept separate from the structural claims.", "findings": [ { "id": "evidence-confidence-notes", "name": "Check these first", "description": "Recalled without web access and unsourced; every item is a lead to verify.", "evidence": [ "This is recall-based information; no sources were consulted.", "Dimensions are approximate family-level figures; performance, mass limits, engines, sensors and weapon compatibility require variant-specific verification.", "The hazards listed are general combat-aircraft hazards, not claims about documented Su-30 defect rates; applicable military airworthiness requirements depend on operator and variant." ], "questions": [ { "id": "evidence-confidence-notes-q01", "text": "Which of these check these first hold for the sense of Sukhoi Su-30 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-30MKI", "Su-30MKM", "Su-30MKK", "Su-30MK2", "Su-30SM" ], "questions": [ { "id": "evidence-kinds-q01", "text": "Which of these kinds and varieties hold for the sense of Sukhoi Su-30 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-30, with variant suffixes such as MKI, MKM, MKK, MK2 and SM", "note": "Identifies the aircraft family or variant, not an individual airframe." } ], "questions": [ { "id": "evidence-identifiers-q01", "text": "Which of these identifiers and schemes hold for the sense of Sukhoi Su-30 this model covers, and on what evidence?", "kind": "provenance" } ] }, { "id": "evidence-real-world-use", "name": "Real-world use", "description": "Recalled without web access and unsourced; every item is a lead to verify.", "evidence": [ "Air defence and interception.", "Air-superiority patrols and escort missions.", "Attacks on ground targets using weapons supported by the particular variant.", "Maritime strike by appropriately equipped variants.", "Long-range patrols supported by aerial refuelling." ], "questions": [ { "id": "evidence-real-world-use-q01", "text": "Which of these real-world use hold for the sense of Sukhoi Su-30 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": "Crew", "typical_range": "2", "unit": "people" }, { "quantity": "Length", "typical_range": "approximately 21.9", "unit": "m" }, { "quantity": "Wingspan", "typical_range": "approximately 14.7", "unit": "m" }, { "quantity": "Engine count", "typical_range": "2", "unit": "afterburning turbofan engines" } ], "questions": [ { "id": "evidence-measurements-q01", "text": "Which of these typical measurements hold for the sense of Sukhoi Su-30 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, foreign-object ingestion or bird strikes can reduce thrust and damage aircraft systems.", "Fuel leaks and onboard fires can threaten the aircraft and crew.", "Flight-control or hydraulic-system failures can impair controllability.", "High-angle-of-attack flight can present departure and loss-of-control hazards.", "Ejection seats, carried weapons, engine intakes and exhaust create hazards during ground handling and maintenance." ], "questions": [ { "id": "evidence-failure-modes-and-hazards-q01", "text": "Which of these failure modes and hazards hold for the sense of Sukhoi Su-30 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": [ "India operates the Su-30MKI, with licensed production by Hindustan Aeronautics Limited; this variant incorporates canards and thrust-vectoring engines.", "Malaysia's Su-30MKM has an avionics configuration distinct from the Indian Su-30MKI.", "China's Su-30MKK and Russia's Su-30SM represent different development branches; the Su-30MKK lacks the canards characteristic of the Su-30SM." ], "questions": [ { "id": "evidence-regional-variation-q01", "text": "Which of these regional variation hold for the sense of Sukhoi Su-30 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": "Sukhoi Su-27", "difference": "The parent aircraft family; an aircraft's designation and configuration distinguish a Su-27 from a Su-30, since seating alone does not distinguish them." }, { "name": "Sukhoi Su-30MKI", "difference": "An India-specific variant within the Su-30 family, rather than the whole family." }, { "name": "Sukhoi Su-34", "difference": "A distinct strike aircraft derived from the Su-27 lineage, with side-by-side crew seating instead of the Su-30's tandem seating." }, { "name": "Sukhoi Su-35", "difference": "A distinct fighter designation whose contemporary production configuration is single-seat." }, { "name": "Individual Su-30 airframe", "difference": "A physical aircraft identified by its serial number and service markings; this entry describes the family." } ], "questions": [ { "id": "evidence-neighbours-q01", "text": "Which of these neighbouring kinds and how to tell them apart hold for the sense of Sukhoi Su-30 this model covers, and on what evidence?", "kind": "provenance" } ] } ] } ] } ] }, "openQuestions": [ "Which authoritative designation history establishes the complete Su-30 family boundary, including early designations and upgrade suffixes?", "Which aerodynamic, engine, nozzle-control and cockpit properties are shared across the family, and which must remain variant-specific?", "Which accessible approved documents establish comparable dimensions, mass definitions and performance conditions for each variant?", "Which operator-specific military airworthiness requirements, maintenance limits and documented recurring defects can be supported by available evidence?", "Does the existing Vercy world-model catalogue already cover this concept, requiring vr.tr.sukhoi-su-30 to link to that publication instead of receiving a duplicate model?" ], "statistics": { "bundles": 6, "layers": 11, "findings": 18, "questions": 30 } }, "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-30, record what state it is in, and decide what may be done with it.", "whatItIs": "Enable an AI agent to recognise a Sukhoi Su-30 family member, assess evidence about its configuration and condition, and identify the approvals needed for a proposed use.", "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-30MKA, Su-30MKM, Su-30MKK, Su-30MKI.", "4 finer distinctions are held as aliases rather than separate entries, because telling them apart needs a task that asks for it.", "Described in 66 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-30, 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-30 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-30MKA", "Su-30MKM", "Su-30MKK", "Su-30MKI" ] } ], "standing": "Described in 66 Wikipedia languages, which measures how widely it is written about rather than how important or how common it is. 4 finer distinctions are held inside this entry as names rather than as separate models.", "structure": { "bundles": [ { "id": "identity-and-classification", "name": "Identity, naming and classification", "description": "How an agent tells one Sukhoi Su-30 from another, and a Sukhoi Su-30 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-30, 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-30, 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-30 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-30, 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-30, 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-30 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-30 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-30, 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-30, 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-30 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-30 from the things most often confused with it.", "questions": [ { "id": "distinguishing-features-q01", "text": "What identifies and describes what distinguishes a Sukhoi Su-30, 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-30, 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-30 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-30 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-30, 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-30, 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-30 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-30 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-30, 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-30, 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-30 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-30 is judged and by whom.", "questions": [ { "id": "condition-assessment-q01", "text": "What identifies and describes the condition of a Sukhoi Su-30, 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-30, 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-30 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-30 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-30 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-30, 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-30, 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-30 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-30 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-30, 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-30, 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-30 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-30 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-30 between them.", "questions": [ { "id": "stages-and-transitions-q01", "text": "What identifies and describes the lifecycle of a Sukhoi Su-30, 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-30, 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-30 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-30, how often and by whom.", "findings": [ { "id": "observation-record", "name": "Observation record", "description": "How an observation of a Sukhoi Su-30 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-30, 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-30, 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-30 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-30 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-30 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-30 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-30, 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-30, 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-30 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-30.", "findings": [ { "id": "procedures-and-skills", "name": "Procedures, skills and required tools", "description": "What an agent needs before it can act on a Sukhoi Su-30 at all.", "questions": [ { "id": "procedures-and-skills-q01", "text": "What identifies and describes handling a Sukhoi Su-30, 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-30, 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-30 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-30 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-30 and how confident it is.", "questions": [ { "id": "claim-provenance-q01", "text": "What identifies and describes a claim about a Sukhoi Su-30, 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-30, 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-30 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-30 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-30, 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-30, 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-30 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 } } } }