{ "model": { "rank": 6743, "code": "thing-q191111", "model_id": "vr.tr.tupolev-tu-160", "name": "Tupolev Tu-160", "purpose": "Enable an AI agent to recognize the Tupolev Tu-160 aircraft family, distinguish its documented configurations, and assess what evidence is required before making claims about an individual aircraft's condition or permitted 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/q191111/", "tier": 2, "score": 59, "payload": { "layer": "wikidata", "aliases": [], "aliasCount": 0, "merged": 0, "knownIn": 59, "facets": null, "markers": [], "lexicalClass": "", "senseRank": null, "alsoRegisteredAs": null, "source": { "dataset": "wikidata", "item": "Q191111", "url": "https://www.wikidata.org/wiki/Q191111", "license": "CC0 1.0" } }, "research": { "vercy": "1.0-draft", "publication": { "status": "research-draft", "adjudicationStatus": "unreviewed", "publishableCanonical": false, "generatedAt": "2026-09-09T23:25:01Z", "providers": [ "Codex" ], "breadth": "recalled by Codex without web access - no source was read", "missingProviders": [], "pass": 2, "cost": { "grok": { "seconds": 20.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: 01a0887c-27b8-7cc3-9438-efd2c9b54de5\n--------\nuser\nDescribe what is already known about one registered thing. Answer as JSON only, no prose around it.\n\nThing: Tupolev Tu-160\nSense to describe: (none recorded)\nDomain code: PHY.OBJ\nAlso known as: (none)\n\n\nContext for this batch of 1001 things:\n# Batch 007: 1001 ", "usd": 0, "recall": true }, "codex": { "seconds": 69, "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: 01a0887c-27c9-7ea3-b27e-f0c6fee729d9\n--------\nuser\nYou are drafting a Vercy meta-model for one registered thing. Answer as JSON only, no prose around it.\n\nThing: Tupolev Tu-160\nRegistry id: vr.tr.tupolev-tu-160\nPlane / domain: PHY / PHY.OBJ\nRegistry definition: (none recorded)\nNames folded into this entry: (no" } } }, "metaModel": { "id": "THING-Q191111", "registryId": "vr.tr.tupolev-tu-160", "name": "Tupolev Tu-160", "version": "0.1.0-research.1", "entryKind": "thing", "family": "Thing Registry", "domain": [ "PHY.OBJ" ], "status": "research-draft" }, "canonicalUrl": "https://ver.cy/models/thing/q191111/", "model": { "registry_id": "vr.tr.tupolev-tu-160", "name": "Tupolev Tu-160", "purpose": "Enable an AI agent to recognize the Tupolev Tu-160 aircraft family, distinguish its documented configurations, and assess what evidence is required before making claims about an individual aircraft's condition or permitted use.", "definition": "The Tupolev Tu-160 is a Soviet-designed family of four-engine, variable-sweep-wing supersonic strategic bombers intended principally to carry and launch long-range cruise missiles.", "scope_statement": "This model owns the type-level identity and configuration-dependent assessment requirements for vr.tr.tupolev-tu-160 in PHY / PHY.OBJ: a Tupolev supersonic strategic missile-carrier aircraft with variable wing geometry, as described by [United Aircraft Corporation](https://uacrussia.ru/ru/aircraft/lineup/special/Tu-160/). Individual airframes instantiate this model; their records remain separate.", "in_scope": [ "Tu-160 family identity, documented variants, and relationships between original, modernized, and newly manufactured configurations", "Distinctive airframe geometry, propulsion configuration, and configuration-dependent dimensions", "Publicly documented performance claims with their measurement conditions and applicability", "Evidence needed to assess airframe condition, maintenance status, and authorized ground handling", "Aircraft-level interfaces to crew, support equipment, and separately modeled payload systems" ], "out_of_scope": [ "Generic aircraft and jet-aircraft principles inherited from broader models", "Individual airframe histories, ownership records, and maintenance logs as independent records", "Detailed engine, missile, warhead, or avionics component models", "Combat mission planning, targeting, weapon employment, and operational tactics", "Airbase infrastructure, military organizations, and fleet deployment models" ], "distinguishing_features": [ "Require a manufacturer designation or traceable airframe record identifying Tu-160 membership; a similar swept-wing silhouette alone cannot distinguish it reliably from a B-1.", "Check the combination of variable wing geometry and documented supersonic strategic missile-carrier identity, rather than treating any Tupolev bomber as a Tu-160. These attributes are documented by [United Aircraft Corporation](https://uacrussia.ru/ru/aircraft/lineup/special/Tu-160/).", "Use sourced dimensions and detailed airframe configuration to resolve confusion with other variable-sweep aircraft; do not infer identity from white paint or a nickname.", "Distinguish family identity from production provenance: a Tu-160M designation does not by itself establish whether an aircraft was modernized or newly manufactured. [Rostec documents newly manufactured Tu-160M aircraft](https://www.rostec.ru/media/news/vnov-izgotovlennyy-tu-160m-sovershil-pervyy-polet/)." ], "characteristics": [ { "name": "Designation and configuration baseline", "kind": "category", "unit_or_values": "Verbatim documented designation, modification standard, effective date, or unresolved", "why_it_matters": "Prevents specifications associated with one Tu-160 configuration from being applied to the whole family." }, { "name": "Production and modernization provenance", "kind": "relation", "unit_or_values": "Links to manufacturer records, original build identity, and documented modification events", "why_it_matters": "Separates modernization of an existing airframe from manufacture of a new aircraft." }, { "name": "Wing geometry", "kind": "measurement", "unit_or_values": "Sweep angle in degrees and corresponding span in metres, with configuration and source", "why_it_matters": "A single unqualified wingspan is inadequate for a variable-geometry aircraft." }, { "name": "Propulsion installation", "kind": "relation", "unit_or_values": "Engine model, series, installed quantity, and supporting configuration record", "why_it_matters": "Engine applicability and support requirements must follow the documented installation." }, { "name": "Mass and loading basis", "kind": "measurement", "unit_or_values": "kg, distinguishing empty, operating, takeoff, landing, fuel, and payload quantities", "why_it_matters": "Published weights describe different conditions and cannot be compared interchangeably." }, { "name": "Published performance", "kind": "measurement", "unit_or_values": "Speed in Mach or km/h; altitude in m; distance in km; each with configuration and test or calculation conditions", "why_it_matters": "Maximum speed, range, and altitude need not be simultaneously achievable." }, { "name": "Airframe disposition", "kind": "state", "unit_or_values": "Under manufacture, under test, in service, under maintenance, stored, preserved, retired, or unknown; dated and sourced", "why_it_matters": "Historical type capability does not establish the present condition of a particular aircraft." }, { "name": "Maintenance and release evidence", "kind": "relation", "unit_or_values": "Applicable technical-publication revision, inspection record, life-limit record, and release authority", "why_it_matters": "An agent needs authoritative records before representing an aircraft as serviceable or cleared for an activity." } ], "affordances": [ "Classify a candidate aircraft as Tu-160, another aircraft type, or unresolved using provenance and configuration evidence.", "Compare documented Tu-160 configurations while marking unsupported equivalence claims.", "Normalize public dimensions and performance figures by units, wing geometry, loading, and source date.", "Identify missing records that prevent an assessment of an individual aircraft's condition or maintenance status.", "Route a proposed inspection, preservation, or ground-handling activity to the applicable documentation and responsible authority." ] }, "sources": [], "structure": { "bundles": [ { "id": "family-identity-and-lineage", "name": "Family identity and lineage", "description": "Establish Tu-160 membership and distinguish aircraft-family identity from variant labels and individual airframes.", "rationale": "The registry names a specific aircraft family, so generic bomber classification and individual aircraft identity are insufficient.", "layers": [ { "id": "designation-and-recognition", "name": "Designation and recognition", "description": "Connect names and observable features to an authoritative type identity.", "findings": [ { "id": "evidence-for-tu-160-membership", "name": "Evidence for Tu-160 membership", "description": "Assess recognition through traceable designation evidence supported by airframe features.", "questions": [ { "text": "Which manufacturer or authoritative aircraft record identifies the candidate as belonging to the Tu-160 family?", "kind": "provenance", "id": "evidence-for-tu-160-membership-q01" }, { "text": "Which documented geometric features resolve resemblance to a B-1 or another variable-sweep bomber?", "kind": "boundary", "id": "evidence-for-tu-160-membership-q02" } ] } ] }, { "id": "variant-and-build-provenance", "name": "Variant and build provenance", "description": "Separate configuration labels from the history of manufacture and modification.", "findings": [ { "id": "configuration-label-applicability", "name": "Configuration label applicability", "description": "Treat each variant label as a sourced assertion with a defined scope, rather than an automatic statement of installed equipment.", "questions": [ { "text": "How does the cited source define the Tu-160 variant label, and which modifications does it explicitly include?", "kind": "definition", "id": "configuration-label-applicability-q01" }, { "text": "What record establishes whether the aircraft is an original build, a modernized airframe, or a newly manufactured example?", "kind": "provenance", "id": "configuration-label-applicability-q02" } ] } ] } ] }, { "id": "variable-geometry-airframe", "name": "Variable-geometry airframe", "description": "Describe the airframe through geometry-dependent measurements and the evidence needed to assess its moving structure.", "rationale": "Wing sweep changes the meaning of dimensional claims and introduces configuration-specific assessment requirements.", "layers": [ { "id": "geometry-and-dimensional-basis", "name": "Geometry and dimensional basis", "description": "Attach aircraft dimensions to the wing and ground configuration in which they apply.", "findings": [ { "id": "sweep-dependent-dimensions", "name": "Sweep-dependent dimensions", "description": "Record wingspan and clearance claims with the associated wing position and measurement basis.", "questions": [ { "text": "At which documented wing-sweep angle was each quoted wingspan measured?", "kind": "measurement", "id": "sweep-dependent-dimensions-q01" }, { "text": "Which configuration and dimensional reference must be used to assess whether this Tu-160 fits a proposed storage or maintenance space?", "kind": "action", "id": "sweep-dependent-dimensions-q02" } ] } ] }, { "id": "moving-structure-condition", "name": "Moving-structure condition", "description": "Identify documentation needed to assess wing-position mechanisms and associated structure.", "findings": [ { "id": "wing-geometry-condition-evidence", "name": "Wing-geometry condition evidence", "description": "Separate visible wing position from verified mechanical condition and movement authorization.", "questions": [ { "text": "Which applicable inspection records address the variable-geometry mechanism and its supporting structure?", "kind": "provenance", "id": "wing-geometry-condition-evidence-q01" }, { "text": "Which approved procedure and recorded isolation or interlock status govern a proposed wing movement during ground work?", "kind": "action", "id": "wing-geometry-condition-evidence-q02" } ] } ] } ] }, { "id": "propulsion-and-performance-basis", "name": "Propulsion and performance basis", "description": "Connect installed propulsion and loading assumptions to public aircraft-performance claims.", "rationale": "Tu-160 family descriptions can conflate engine configurations and quote maxima without their operating conditions.", "layers": [ { "id": "installed-propulsion-configuration", "name": "Installed propulsion configuration", "description": "Establish the engine installation applicable to a particular configuration.", "findings": [ { "id": "engine-series-and-support-applicability", "name": "Engine series and support applicability", "description": "Require configuration evidence before assigning engine specifications or support requirements.", "questions": [ { "text": "Which engine model, series, and quantity are documented for the Tu-160 configuration being described?", "kind": "provenance", "id": "engine-series-and-support-applicability-q01" }, { "text": "Which fuel, lubricant, and servicing specifications are applicable to that installation according to its approved documentation?", "kind": "definition", "id": "engine-series-and-support-applicability-q02" } ] } ] }, { "id": "conditional-performance", "name": "Conditional performance", "description": "Distinguish published capability figures from comparable measurements and approved limits.", "findings": [ { "id": "performance-claim-conditions", "name": "Performance claim conditions", "description": "Keep speed, range, altitude, and mass claims tied to their stated conditions and evidential status.", "questions": [ { "text": "What loading, altitude, wing geometry, propulsion mode, and refuelling assumptions accompany each quoted performance figure?", "kind": "measurement", "id": "performance-claim-conditions-q01" }, { "text": "Is the figure a design target, demonstrated result, publicity statement, or approved limit for the identified configuration?", "kind": "boundary", "id": "performance-claim-conditions-q02" } ] } ] } ] }, { "id": "aircraft-system-boundaries", "name": "Aircraft system boundaries", "description": "Describe aircraft-level crew, avionics, and payload interfaces without absorbing their separate component or operational models.", "rationale": "Tu-160 identity includes its strategic missile-carrier role, but the airframe model must distinguish installed systems from compatible or proposed equipment.", "layers": [ { "id": "crew-and-avionics-baseline", "name": "Crew and avionics baseline", "description": "Identify the documented human and electronic system configuration relevant to aircraft assessment.", "findings": [ { "id": "documented-system-installation", "name": "Documented system installation", "description": "Record evidence for crew provisions and avionics changes at the applicable configuration level.", "questions": [ { "text": "Which crew stations, escape provisions, and avionics baseline are documented for this Tu-160 configuration?", "kind": "definition", "id": "documented-system-installation-q01" }, { "text": "Which source distinguishes systems installed on the aircraft from announced modernization intentions?", "kind": "provenance", "id": "documented-system-installation-q02" } ] } ] }, { "id": "payload-interface-boundary", "name": "Payload interface boundary", "description": "Represent payload compatibility as a relation to separately modeled equipment.", "findings": [ { "id": "compatibility-versus-carriage", "name": "Compatibility versus carriage", "description": "Separate a documented aircraft capability from evidence of equipment actually installed or carried.", "questions": [ { "text": "Which public authoritative source establishes payload-system compatibility for the specified Tu-160 configuration?", "kind": "provenance", "id": "compatibility-versus-carriage-q01" }, { "text": "Does the evidence establish compatibility, a test installation, or actual carriage, and which details belong to the separate payload model?", "kind": "boundary", "id": "compatibility-versus-carriage-q02" } ] } ] } ] }, { "id": "service-life-and-authorized-handling", "name": "Service life and authorized handling", "description": "Establish what records are needed to assess an individual Tu-160's disposition, condition, and permitted support activities.", "rationale": "A Tu-160 may appear externally complete while its life limits, maintenance status, or preservation state remain unknown.", "layers": [ { "id": "condition-and-life-records", "name": "Condition and life records", "description": "Connect condition assessments to dated inspection and service-life evidence.", "findings": [ { "id": "airframe-specific-serviceability", "name": "Airframe-specific serviceability", "description": "Require airframe and component records before drawing conclusions about remaining life or serviceability.", "questions": [ { "text": "Which dated records establish accumulated airframe hours, cycles, applicable life limits, and formally approved extensions?", "kind": "measurement", "id": "airframe-specific-serviceability-q01" }, { "text": "Which unresolved defects or missing inspection records prevent a supported condition assessment?", "kind": "provenance", "id": "airframe-specific-serviceability-q02" } ] } ] }, { "id": "activity-specific-authorization", "name": "Activity-specific authorization", "description": "Identify governing documents and approval evidence for maintenance, movement, and preservation activities.", "findings": [ { "id": "support-activity-release", "name": "Support activity release", "description": "Keep authorization specific to the aircraft configuration and proposed activity.", "questions": [ { "text": "Which issuing authority, technical-publication revision, and release record govern the proposed Tu-160 maintenance, towing, or preservation activity?", "kind": "action", "id": "support-activity-release-q01" }, { "text": "What configuration-specific support equipment and documented aircraft state must be verified before that activity can be represented as permitted?", "kind": "action", "id": "support-activity-release-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 is recalled knowledge, with no sources consulted.", "Researchers should verify Tu-160M and Tu-160M2 nomenclature, particularly distinctions between upgraded existing airframes and newly manufactured aircraft.", "Dimensions and mass are approximate baseline figures; hazards listed are engineering concerns, not claims of documented Tu-160-specific accident causes." ], "questions": [ { "id": "evidence-confidence-notes-q01", "text": "Which of these check these first hold for the sense of Tupolev Tu-160 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": [ "Tu-160 baseline production aircraft", "Tu-160M modernized aircraft" ], "questions": [ { "id": "evidence-kinds-q01", "text": "Which of these kinds and varieties hold for the sense of Tupolev Tu-160 this model covers, and on what evidence?", "kind": "provenance" } ] }, { "id": "evidence-identifiers", "name": "Identifiers and schemes", "description": "Recalled without web access and unsourced; every item is a lead to verify.", "evidence": [ { "scheme": "Soviet/Russian aircraft design designation", "value_or_pattern": "Tu-160", "note": "Identifies the aircraft design family, not an individual airframe." }, { "scheme": "NATO reporting name", "value_or_pattern": "Blackjack", "note": "Reporting name for the Tu-160." } ], "questions": [ { "id": "evidence-identifiers-q01", "text": "Which of these identifiers and schemes hold for the sense of Tupolev Tu-160 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": [ "Long-range strategic deterrence missions with nuclear-capable cruise missiles.", "Conventional cruise-missile strikes.", "Long-range patrols and military exercises." ], "questions": [ { "id": "evidence-real-world-use-q01", "text": "Which of these real-world use hold for the sense of Tupolev Tu-160 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", "typical_range": "Approximately 54.1", "unit": "m" }, { "quantity": "Wingspan across wing-sweep positions", "typical_range": "Approximately 35.6-55.7", "unit": "m" }, { "quantity": "Maximum takeoff mass", "typical_range": "Approximately 275000", "unit": "kg" }, { "quantity": "Crew complement", "typical_range": "4", "unit": "people" } ], "questions": [ { "id": "evidence-measurements-q01", "text": "Which of these typical measurements hold for the sense of Tupolev Tu-160 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": [ "Fuel leaks or engine malfunction can cause fire and loss of propulsion.", "Wing-sweep mechanism or flight-control failures can compromise controllability.", "Structural fatigue and corrosion require inspection over an airframe's service life.", "High-speed flight imposes substantial aerodynamic, thermal and structural loads.", "Ejection and emergency escape carry risks that depend on flight conditions." ], "questions": [ { "id": "evidence-failure-modes-and-hazards-q01", "text": "Which of these failure modes and hazards hold for the sense of Tupolev Tu-160 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": [ "The aircraft originated in the Soviet Union and subsequently served in Russian military aviation.", "Ukraine inherited Tu-160 aircraft after the Soviet Union dissolved; some were transferred to Russia and others dismantled." ], "questions": [ { "id": "evidence-regional-variation-q01", "text": "Which of these regional variation hold for the sense of Tupolev Tu-160 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": "Strategic bomber", "difference": "The broader aircraft category; Tu-160 denotes a particular design family within it." }, { "name": "Tupolev Tu-95", "difference": "The Tu-95 is a turboprop strategic bomber with fixed swept wings; the Tu-160 uses afterburning turbofans and variable-sweep wings." }, { "name": "Tupolev Tu-22M", "difference": "The Tu-22M is a separate, smaller twin-engine bomber family; the Tu-160 has four engines and a larger strategic mission platform." }, { "name": "Rockwell B-1B Lancer", "difference": "A distinct American variable-sweep-wing bomber design with different airframe, propulsion and weapons integration." }, { "name": "Individual Tu-160 airframe", "difference": "An individual aircraft has its own serial number, service history and configuration; this entry describes the design family." } ], "questions": [ { "id": "evidence-neighbours-q01", "text": "Which of these neighbouring kinds and how to tell them apart hold for the sense of Tupolev Tu-160 this model covers, and on what evidence?", "kind": "provenance" } ] } ] } ] } ] }, "openQuestions": [ "Does an existing Vercy world model already cover the Tu-160 family, requiring this registry entry to link to that publication?", "How do authoritative sources distinguish Tu-160, Tu-160M, and any use of Tu-160M2, especially across modernization and new manufacture?", "Which configuration-specific manufacturer data can settle conflicting public dimensions, mass definitions, and performance claims?", "Which military airworthiness authorities, technical publications, inspection requirements, and life-extension rules can be verified from accessible sources?", "Which Tu-160-specific failure modes and ground-handling interlocks are publicly documented well enough to model without inference?" ], "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 Tupolev Tu-160, record what state it is in, and decide what may be done with it.", "whatItIs": "Enable an AI agent to recognize the Tupolev Tu-160 aircraft family, distinguish its documented configurations, and assess what evidence is required before making claims about an individual aircraft's condition or permitted use.", "characteristics": { "substance": "material", "origin": "manufactured", "agency": "inert", "mobility": "varies" }, "whatYouCanDoWithIt": [ "observed and measured" ], "distinguishingFeatures": [ "Described in 59 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 Tupolev Tu-160, 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 Tupolev Tu-160 looks like has to come from research." ], "relatedModels": [], "standing": "Described in 59 Wikipedia languages, which measures how widely it is written about rather than how important or how common it is.", "structure": { "bundles": [ { "id": "identity-and-classification", "name": "Identity, naming and classification", "description": "How an agent tells one Tupolev Tu-160 from another, and a Tupolev Tu-160 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 Tupolev Tu-160, 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 Tupolev Tu-160, 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 Tupolev Tu-160 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 Tupolev Tu-160, 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 Tupolev Tu-160, 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 Tupolev Tu-160 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 Tupolev Tu-160 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 Tupolev Tu-160, 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 Tupolev Tu-160, 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 Tupolev Tu-160 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 Tupolev Tu-160 from the things most often confused with it.", "questions": [ { "id": "distinguishing-features-q01", "text": "What identifies and describes what distinguishes a Tupolev Tu-160, 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 Tupolev Tu-160, 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 Tupolev Tu-160 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 Tupolev Tu-160 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 Tupolev Tu-160, 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 Tupolev Tu-160, 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 Tupolev Tu-160 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 Tupolev Tu-160 is built from and which parts are replaceable.", "questions": [ { "id": "parts-and-materials-q01", "text": "What identifies and describes the composition of a Tupolev Tu-160, 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 Tupolev Tu-160, 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 Tupolev Tu-160 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 Tupolev Tu-160 is judged and by whom.", "questions": [ { "id": "condition-assessment-q01", "text": "What identifies and describes the condition of a Tupolev Tu-160, 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 Tupolev Tu-160, 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 Tupolev Tu-160 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 Tupolev Tu-160 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 Tupolev Tu-160 is, and what that position is measured against.", "questions": [ { "id": "position-and-frame-q01", "text": "What identifies and describes the location of a Tupolev Tu-160, 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 Tupolev Tu-160, 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 Tupolev Tu-160 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 Tupolev Tu-160 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 Tupolev Tu-160, 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 Tupolev Tu-160, 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 Tupolev Tu-160 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 Tupolev Tu-160 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 Tupolev Tu-160 between them.", "questions": [ { "id": "stages-and-transitions-q01", "text": "What identifies and describes the lifecycle of a Tupolev Tu-160, 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 Tupolev Tu-160, 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 Tupolev Tu-160 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 Tupolev Tu-160, how often and by whom.", "findings": [ { "id": "observation-record", "name": "Observation record", "description": "How an observation of a Tupolev Tu-160 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 Tupolev Tu-160, 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 Tupolev Tu-160, 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 Tupolev Tu-160 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 Tupolev Tu-160 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 Tupolev Tu-160 is for, and what it is used for anyway.", "findings": [ { "id": "function-and-purpose", "name": "Function, purpose and misuse", "description": "The function a Tupolev Tu-160 performs and the uses that fall outside it.", "questions": [ { "id": "function-and-purpose-q01", "text": "What identifies and describes the use of a Tupolev Tu-160, 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 Tupolev Tu-160, 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 Tupolev Tu-160 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 Tupolev Tu-160.", "findings": [ { "id": "procedures-and-skills", "name": "Procedures, skills and required tools", "description": "What an agent needs before it can act on a Tupolev Tu-160 at all.", "questions": [ { "id": "procedures-and-skills-q01", "text": "What identifies and describes handling a Tupolev Tu-160, 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 Tupolev Tu-160, 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 Tupolev Tu-160 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 Tupolev Tu-160 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 Tupolev Tu-160 and how confident it is.", "questions": [ { "id": "claim-provenance-q01", "text": "What identifies and describes a claim about a Tupolev Tu-160, 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 Tupolev Tu-160, 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 Tupolev Tu-160 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 Tupolev Tu-160 is retired without being erased.", "questions": [ { "id": "validity-and-supersession-q01", "text": "What identifies and describes the validity of a claim about a Tupolev Tu-160, 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 Tupolev Tu-160, 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 Tupolev Tu-160 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 } } } }