{ "model": { "rank": 6213, "code": "thing-q181815", "model_id": "vr.tr.tupolev-tu-95", "name": "Tupolev Tu-95", "purpose": "Enable an AI agent to recognize the Tupolev Tu-95 aircraft family, distinguish its variants, and assess documented configuration, condition, and authorized handling.", "family": "Thing Registry", "category": "Physical world and living systems", "status": "research-draft", "kind": "thing", "plane": "PHY", "domain": "PHY.MAT", "industry": "", "version": "", "url": "/models/thing/q181815/", "tier": 2, "score": 62, "payload": { "layer": "wikidata", "aliases": [], "aliasCount": 0, "merged": 0, "knownIn": 62, "facets": null, "markers": [], "lexicalClass": "", "senseRank": null, "alsoRegisteredAs": null, "source": { "dataset": "wikidata", "item": "Q181815", "url": "https://www.wikidata.org/wiki/Q181815", "license": "CC0 1.0" } }, "research": { "vercy": "1.0-draft", "publication": { "status": "research-draft", "adjudicationStatus": "unreviewed", "publishableCanonical": false, "generatedAt": "2026-09-09T22:55:13Z", "providers": [ "Codex" ], "breadth": "recalled by Codex without web access - no source was read", "missingProviders": [], "pass": 2, "cost": { "grok": { "seconds": 21.5, "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: 01a08860-d4e6-7133-9e18-07633fb80d98\n--------\nuser\nDescribe what is already known about one registered thing. Answer as JSON only, no prose around it.\n\nThing: Tupolev Tu-95\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 re", "usd": 0, "recall": true }, "codex": { "seconds": 70.9, "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: 01a08860-d4f7-7e51-8679-21a0bb82973e\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-95\nRegistry id: vr.tr.tupolev-tu-95\nPlane / domain: PHY / PHY.OBJ\nRegistry definition: (none recorded)\nNames folded into this entry: (none" } } }, "metaModel": { "id": "THING-Q181815", "registryId": "vr.tr.tupolev-tu-95", "name": "Tupolev Tu-95", "version": "0.1.0-research.1", "entryKind": "thing", "family": "Thing Registry", "domain": [ "PHY.OBJ" ], "status": "research-draft" }, "canonicalUrl": "https://ver.cy/models/thing/q181815/", "model": { "registry_id": "vr.tr.tupolev-tu-95", "name": "Tupolev Tu-95", "purpose": "Enable an AI agent to recognize the Tupolev Tu-95 aircraft family, distinguish its variants, and assess documented configuration, condition, and authorized handling.", "definition": "The Tupolev Tu-95 is a Soviet-designed family of long-range, swept-wing military aircraft powered by four turboprop engines driving contra-rotating propellers, developed primarily for strategic bombing and subsequently adapted for cruise-missile carriage and maritime reconnaissance.", "scope_statement": "This model owns registry entry vr.tr.tupolev-tu-95 in PHY / PHY.OBJ as an aircraft design family, including variant-specific recognition and assessment requirements; individual airframes instantiate it, while separately designated related aircraft remain linked neighbours.", "in_scope": [ "Tu-95 family identity, designation aliases, and variant boundaries", "Variant-specific airframe, propulsion, and equipment configurations", "Dimensions, mass, endurance, and performance with configuration and measurement conditions", "Evidence needed to assess individual airframes against their documented configuration", "Maintenance status, preservation state, and authorized ground handling" ], "out_of_scope": [ "Separately designated related types such as Tu-142, Tu-114, and Tu-126", "Individual airframes as independent registry concepts", "Detailed internal models of engines, propellers, missiles, and avionics", "Combat targeting, weapon employment procedures, and mission optimization", "Operator organizations, airbases, and campaign histories" ], "distinguishing_features": [ "Check for the combination of a swept wing, four turboprop nacelles, and paired contra-rotating propellers; this is a recognition cue requiring designation evidence, especially when distinguishing related aircraft.", "Require a documented Tu-95 designation or a supported alias mapping; the reporting name Bear alone does not establish the exact type or variant.", "Distinguish Tu-95 variants using documented nose, radome, antenna, refuelling, and payload-installation features rather than general silhouette alone.", "Treat Tu-95MS and its modernization states as specific configurations, not specifications applicable to every Tu-95; manufacturer reporting distinguishes modernization work on Tu-95MS. [Rostec modernization announcement](https://rostec.ru/media/news/tupolev-zavershil-raboty-po-maloy-modernizatsii-pervoy-partii-tu-95ms/)", "Check the formal type designation before admitting related aircraft: manufacturer history identifies Tu-142 and Tu-126 as separately named developments. [Rostec Tu-95MS history](https://www.rostec.ru/media/news/tu-95ms-krylatyy-medved/)" ], "characteristics": [ { "name": "Variant designation", "kind": "category", "unit_or_values": "Original-script designation, normalized designation, reporting-name mapping, or unresolved", "why_it_matters": "Controls which recognition features and technical documentation apply." }, { "name": "Configuration baseline", "kind": "relation", "unit_or_values": "Links to production standard, modification records, and dated configuration evidence", "why_it_matters": "Prevents modernized equipment from being attributed to an earlier configuration." }, { "name": "Airframe identity", "kind": "relation", "unit_or_values": "Manufacturer serial identity with dated registration and marking associations", "why_it_matters": "Separates persistent airframe identity from changeable paint schemes and numbers." }, { "name": "Propulsion installation", "kind": "category", "unit_or_values": "Engine, gearbox, and propeller designations by installation position; unknown permitted", "why_it_matters": "Family-level engine names do not establish installed component compatibility." }, { "name": "External geometry", "kind": "measurement", "unit_or_values": "Length, wingspan, and height in m, with variant and measurement convention", "why_it_matters": "Supports identification and ground-space assessment without inventing a family-wide dimension." }, { "name": "Mass and loading basis", "kind": "measurement", "unit_or_values": "kg, identifying empty, operating, actual, or maximum permitted mass and configuration", "why_it_matters": "Prevents comparison of unlike mass definitions." }, { "name": "Published flight performance", "kind": "measurement", "unit_or_values": "Speed in km/h, altitude and range in km, endurance in h; each with loading and refuelling assumptions", "why_it_matters": "Separates conditional published figures from verified capability of an individual aircraft." }, { "name": "Equipment and payload installation", "kind": "category", "unit_or_values": "Documented navigation, communications, defensive, and carriage equipment by variant and date", "why_it_matters": "Distinguishes installed hardware from advertised compatibility and actual payload." }, { "name": "Serviceability state", "kind": "state", "unit_or_values": "Unknown, awaiting inspection, restricted, released for specified activity, stored, preserved, or withdrawn", "why_it_matters": "An identified Tu-95 is not automatically serviceable or authorized to move or fly." }, { "name": "Life consumption", "kind": "measurement", "unit_or_values": "Flight hours, cycles, calendar age, and component-specific remaining life against cited limits", "why_it_matters": "Supports maintenance assessment while keeping applicable limits tied to authoritative records." } ], "affordances": [ "Classify an aircraft observation as a Tu-95 candidate and record evidence needed to resolve its variant.", "Compare an airframe's documented configuration with the applicable Tu-95 variant baseline.", "Retrieve variant-appropriate technical publications and identify missing revision or applicability information.", "Flag missing inspection, component-life, or release records before recommending handling or operation.", "Compare published dimensions and performance only when variant and measurement conditions match.", "Record preservation, demilitarization, and display changes without treating a museum configuration as an operational baseline." ] }, "sources": [], "structure": { "bundles": [ { "id": "family-and-variant-identity", "name": "Family and variant identity", "description": "Determine what counts as a Tu-95 and how a particular variant is identified.", "rationale": "Related designs, reporting names, and modernization labels can produce false equivalence.", "layers": [ { "id": "designation-and-family-boundary", "name": "Designation and family boundary", "description": "Resolve names and distinguish family membership from design ancestry.", "findings": [ { "id": "designation-evidence", "name": "Designation evidence", "description": "Require an evidence-backed mapping between the observed or recorded name and the Tu-95 registry entry.", "questions": [ { "text": "Which original designation and authoritative record establish that this aircraft belongs to the Tu-95 family?", "kind": "definition", "id": "designation-evidence-q01" }, { "text": "Does the evidence identify a Tu-95 variant or a separately designated related type such as Tu-142?", "kind": "boundary", "id": "designation-evidence-q02" } ] } ] }, { "id": "variant-and-airframe-attribution", "name": "Variant and airframe attribution", "description": "Associate visible features and dated records with a configuration and, where possible, an individual airframe.", "findings": [ { "id": "configuration-identification", "name": "Configuration identification", "description": "Treat external features as supporting evidence and preserve unresolved conflicts with documentary identification.", "questions": [ { "text": "Which nose, antenna, refuelling, and carriage-installation features support the proposed variant identification?", "kind": "definition", "id": "configuration-identification-q01" }, { "text": "Which serial record and dated modification history connect this appearance to the identified airframe?", "kind": "provenance", "id": "configuration-identification-q02" } ] } ] } ] }, { "id": "airframe-and-propulsion", "name": "Airframe and propulsion", "description": "Represent the Tu-95's physical configuration and the installed propulsion assemblies.", "rationale": "Recognition, clearance, and maintenance judgments depend on the exact airframe and engine-propeller combination.", "layers": [ { "id": "geometry-and-loading", "name": "Geometry and loading", "description": "Keep physical measurements tied to variant and loading definitions.", "findings": [ { "id": "configuration-bound-dimensions", "name": "Configuration-bound dimensions", "description": "Record dimensions and mass categories with their source, configuration, and measurement basis.", "questions": [ { "text": "What are the documented wingspan, length, and height for this variant, including any configuration-dependent projections?", "kind": "measurement", "id": "configuration-bound-dimensions-q01" }, { "text": "Which loading state and mass definition accompany each recorded weight?", "kind": "measurement", "id": "configuration-bound-dimensions-q02" } ] } ] }, { "id": "engine-gearbox-propeller-installation", "name": "Engine, gearbox, and propeller installation", "description": "Identify installed propulsion components without assuming interchangeability across Tu-95 variants.", "findings": [ { "id": "propulsion-component-applicability", "name": "Propulsion component applicability", "description": "Track the exact propulsion assembly and the approved documentation governing its installation and condition.", "questions": [ { "text": "Which engine, gearbox, and contra-rotating propeller variants are documented at each nacelle position?", "kind": "provenance", "id": "propulsion-component-applicability-q01" }, { "text": "Which approved records establish compatibility and applicable inspection requirements for those assemblies?", "kind": "action", "id": "propulsion-component-applicability-q02" } ] } ] } ] }, { "id": "role-equipment-and-performance", "name": "Role, equipment, and performance", "description": "Connect a Tu-95 configuration to its documented role and conditional capabilities.", "rationale": "Equipment and performance claims vary across the family and cannot be inferred from the Tu-95 name alone.", "layers": [ { "id": "mission-equipment-baseline", "name": "Mission equipment baseline", "description": "Describe equipment at identification level and distinguish compatibility from installation.", "findings": [ { "id": "installed-versus-supported-equipment", "name": "Installed versus supported equipment", "description": "Separate a variant's documented equipment options from the hardware and payload evidenced on a particular airframe.", "questions": [ { "text": "Which documented role and equipment baseline apply to this Tu-95 variant at the stated date?", "kind": "definition", "id": "installed-versus-supported-equipment-q01" }, { "text": "Which equipment is confirmed installed, merely supported, removed, or unknown?", "kind": "boundary", "id": "installed-versus-supported-equipment-q02" } ] } ] }, { "id": "conditional-flight-capability", "name": "Conditional flight capability", "description": "Make published performance meaningful by preserving its assumptions.", "findings": [ { "id": "performance-reference-conditions", "name": "Performance reference conditions", "description": "Record each performance figure as a conditional claim, distinguishing range, radius, and endurance.", "questions": [ { "text": "What loading, altitude, speed regime, reserves, and refuelling assumptions accompany the quoted figure?", "kind": "measurement", "id": "performance-reference-conditions-q01" }, { "text": "Does the source report a design specification, test result, record flight, or approved operating limit?", "kind": "provenance", "id": "performance-reference-conditions-q02" } ] } ] } ] }, { "id": "condition-and-authorized-handling", "name": "Condition and authorized handling", "description": "Assess the evidence required for maintenance, movement, operation, or preservation of a Tu-95 airframe.", "rationale": "Age, modifications, propulsion hazards, and military release requirements make appearance an inadequate basis for action.", "layers": [ { "id": "life-status-and-maintenance-evidence", "name": "Life status and maintenance evidence", "description": "Link structural and component condition to applicable records and limits.", "findings": [ { "id": "serviceability-evidence", "name": "Serviceability evidence", "description": "Require dated inspection and life-status records before assigning a serviceability conclusion.", "questions": [ { "text": "What flight hours, cycles, calendar limits, and inspection findings are recorded for this airframe and its life-limited components?", "kind": "measurement", "id": "serviceability-evidence-q01" }, { "text": "Which authority and applicable technical-publication revision support its current release or restrictions?", "kind": "provenance", "id": "serviceability-evidence-q02" } ] } ] }, { "id": "ground-and-preservation-state", "name": "Ground and preservation state", "description": "Distinguish a powered aircraft, a maintenance article, a stored airframe, and a static exhibit.", "findings": [ { "id": "activity-specific-readiness", "name": "Activity-specific readiness", "description": "Record verified conditions for the proposed activity, including propulsion isolation, support equipment, and any retained hazardous systems.", "questions": [ { "text": "What approved Tu-95 documentation governs propeller-area access, towing, or servicing for this configuration?", "kind": "action", "id": "activity-specific-readiness-q01" }, { "text": "Which preservation changes, system isolations, and payload-removal records determine whether inspection, movement, or display access is authorized?", "kind": "action", "id": "activity-specific-readiness-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 recall-based information; no sources were consulted.", "Dimensions, speed, payload and range depend on variant and configuration; the figures given should be verified against variant-specific documentation.", "Researchers should verify modernization labels, current service status and applicable military airworthiness requirements before adding those details." ], "questions": [ { "id": "evidence-confidence-notes-q01", "text": "Which of these check these first hold for the sense of Tupolev Tu-95 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-95: initial strategic bomber", "Tu-95M: improved early bomber", "Tu-95K: missile-carrying variant", "Tu-95RTs: maritime reconnaissance and targeting variant", "Tu-95MS: strategic cruise-missile carrier", "Tu-95MSM: modernized Tu-95MS configuration" ], "questions": [ { "id": "evidence-kinds-q01", "text": "Which of these kinds and varieties hold for the sense of Tupolev Tu-95 this model covers, and on what evidence?", "kind": "provenance" } ] }, { "id": "evidence-identifiers", "name": "Identifiers and schemes", "description": "Recalled without web access and unsourced; every item is a lead to verify.", "evidence": [ { "scheme": "Soviet aircraft design designation", "value_or_pattern": "Tu-95 / Ту-95, followed by variant suffixes", "note": "Identifies an aircraft family and its variants, not an individual airframe." }, { "scheme": "NATO reporting name", "value_or_pattern": "Bear", "note": "Letter suffixes distinguish variants; the related Tu-142 also receives Bear reporting names." } ], "questions": [ { "id": "evidence-identifiers-q01", "text": "Which of these identifiers and schemes hold for the sense of Tupolev Tu-95 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": [ "Strategic nuclear deterrence through long-range bomber and cruise-missile missions.", "Conventional long-range cruise-missile strikes by suitably equipped variants.", "Long-distance military patrols and demonstrations of strategic reach.", "Maritime reconnaissance and targeting support by the Tu-95RTs." ], "questions": [ { "id": "evidence-real-world-use-q01", "text": "Which of these real-world use hold for the sense of Tupolev Tu-95 this model covers, and on what evidence?", "kind": "provenance" } ] }, { "id": "evidence-measurements", "name": "Typical measurements", "description": "Recalled without web access and unsourced; every item is a lead to verify.", "evidence": [ { "quantity": "Wingspan", "typical_range": "Approximately 50.1", "unit": "m" }, { "quantity": "Overall length of Tu-95MS", "typical_range": "Approximately 49.5", "unit": "m" }, { "quantity": "Maximum speed of Tu-95MS", "typical_range": "Approximately 830", "unit": "km/h" }, { "quantity": "Number of turboprop engines", "typical_range": "4", "unit": "engines" } ], "questions": [ { "id": "evidence-measurements-q01", "text": "Which of these typical measurements hold for the sense of Tupolev Tu-95 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, reduction-gearbox or propeller-system failures can cause loss of thrust, severe vibration or difficulty controlling the aircraft.", "Large rotating propellers create lethal ground-handling hazards.", "High noise levels create hearing hazards for exposed personnel.", "Structural fatigue and corrosion require inspection and maintenance of aging airframes.", "Fuel fires and carried weapons create additional accident and emergency-response hazards." ], "questions": [ { "id": "evidence-failure-modes-and-hazards-q01", "text": "Which of these failure modes and hazards hold for the sense of Tupolev Tu-95 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; post-Soviet inventories included aircraft in Russia and Ukraine.", "Russian designations and NATO Bear reporting names provide different systems for distinguishing variants." ], "questions": [ { "id": "evidence-regional-variation-q01", "text": "Which of these regional variation hold for the sense of Tupolev Tu-95 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": "Tupolev Tu-142", "difference": "A related derivative developed for maritime patrol and antisubmarine warfare, with its own designation and mission equipment." }, { "name": "Tupolev Tu-114", "difference": "A civil passenger airliner derived from the Tu-95 design, with a substantially different passenger-carrying fuselage." }, { "name": "Boeing B-52 Stratofortress", "difference": "A separate American strategic bomber family powered by jet engines rather than turboprops." } ], "questions": [ { "id": "evidence-neighbours-q01", "text": "Which of these neighbouring kinds and how to tell them apart hold for the sense of Tupolev Tu-95 this model covers, and on what evidence?", "kind": "provenance" } ] } ] } ] } ] }, "openQuestions": [ "Does an existing Vercy world model already cover the Tu-95 family, requiring this registry entry to link to it instead of creating a second model?", "Which authoritative designation crosswalk settles family membership for prototypes, special conversions, reporting-name suffixes, and modernization labels?", "Which primary technical publications establish dimensions, performance conditions, crew arrangements, and approved configuration baselines for each included variant?", "Which issuing authorities, technical orders, inspection limits, and service-life extensions govern each operator's airframes, and which are publicly verifiable?", "What dated evidence distinguishes Tu-95MSM development, delivered modernization configurations, and individual-airframe adoption without extrapolating from announcements?" ], "statistics": { "bundles": 5, "layers": 9, "findings": 16, "questions": 24 } }, "draft": { "generator": "vr.draft.v3", "status": "draft-generated", "researched": false, "archetype": "chemical substance or material", "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-95, record what state it is in, and decide what may be done with it.", "whatItIs": "Enable an AI agent to recognize the Tupolev Tu-95 aircraft family, distinguish its variants, and assess documented configuration, condition, and authorized handling.", "characteristics": { "substance": "material", "origin": "natural", "agency": "inert", "mobility": "varies" }, "whatYouCanDoWithIt": [ "observed and measured", "consumed or used up" ], "distinguishingFeatures": [ "Described in 62 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-95, 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", "use it up, and then need more of it" ], "howItIsRecognised": [ "Not recognisable by sight in any reliable way. Appearance varies with grade, form and additives; identification is by label, by documentation, or by assay." ], "relatedModels": [], "standing": "Described in 62 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-95 from another, and a Tupolev Tu-95 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-95, 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-95, 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-95 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-95, 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-95, 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-95 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-95 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-95, 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-95, 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-95 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-95 from the things most often confused with it.", "questions": [ { "id": "distinguishing-features-q01", "text": "What identifies and describes what distinguishes a Tupolev Tu-95, 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-95, 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-95 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-95 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-95, 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-95, 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-95 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-95 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-95, 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-95, 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-95 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-95 is judged and by whom.", "questions": [ { "id": "condition-assessment-q01", "text": "What identifies and describes the condition of a Tupolev Tu-95, 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-95, 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-95 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-95 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-95 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-95, 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-95, 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-95 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-95 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-95, 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-95, 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-95 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-95 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-95 between them.", "questions": [ { "id": "stages-and-transitions-q01", "text": "What identifies and describes the lifecycle of a Tupolev Tu-95, 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-95, 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-95 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-95, how often and by whom.", "findings": [ { "id": "observation-record", "name": "Observation record", "description": "How an observation of a Tupolev Tu-95 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-95, 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-95, 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-95 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-95 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-95 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-95 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-95, 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-95, 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-95 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-95.", "findings": [ { "id": "procedures-and-skills", "name": "Procedures, skills and required tools", "description": "What an agent needs before it can act on a Tupolev Tu-95 at all.", "questions": [ { "id": "procedures-and-skills-q01", "text": "What identifies and describes handling a Tupolev Tu-95, 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-95, 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-95 is known, and what must it refuse?", "kind": "action", "answer_data": [ "permitted actions", "preconditions", "refusals", "escalation" ] } ] } ] }, { "id": "supply-and-consumption", "name": "Supply and consumption", "description": "Quantities, rates and what running out means.", "findings": [ { "id": "consumption-and-stock", "name": "Consumption, stock and replenishment", "description": "How much of a Tupolev Tu-95 there is and how fast it goes.", "questions": [ { "id": "consumption-and-stock-q01", "text": "What identifies and describes the supply of a Tupolev Tu-95, and in what units or vocabulary?", "kind": "definition", "answer_data": [ "identifiers", "types and classes", "values with units", "explicit unknowns" ] }, { "id": "consumption-and-stock-q02", "text": "Who or what asserted this about the supply of a Tupolev Tu-95, by which method, and when was it true?", "kind": "provenance", "answer_data": [ "authority", "method", "evidence", "event time", "knowledge time" ] }, { "id": "consumption-and-stock-q03", "text": "What may an agent decide or do once the supply of a Tupolev Tu-95 is known, and what must it refuse?", "kind": "action", "answer_data": [ "permitted actions", "preconditions", "refusals", "escalation" ] } ] } ] } ] }, { "id": "composition-and-identity", "name": "Composition, grade and chemical identity", "description": "What Tupolev Tu-95 is made of and how pure the thing in hand is.", "rationale": "Grade decides what a substance may be used for, so a model that records only the name cannot support any decision about use.", "layers": [ { "id": "chemical-identity", "name": "Chemical identity", "description": "Formula, structure and the registry numbers that name it unambiguously.", "findings": [ { "id": "identity-record", "name": "Identity and registry numbers", "description": "What identifies this substance across suppliers and regulators.", "questions": [ { "id": "identity-record-q01", "text": "What formula, structure and registry identifiers name Tupolev Tu-95 unambiguously?", "kind": "definition" }, { "id": "identity-record-q02", "text": "Which related substances share a name in common use but not an identifier?", "kind": "boundary" } ] } ] }, { "id": "grade-and-impurities", "name": "Grade, purity and impurities", "description": "The specification a batch meets and what else is in it.", "findings": [ { "id": "specification", "name": "Specification and assay", "description": "How purity is stated and measured, and which impurities matter.", "questions": [ { "id": "specification-q01", "text": "What grades of Tupolev Tu-95 exist, how is purity assayed, and which impurities are limited?", "kind": "measurement" }, { "id": "specification-q02", "text": "Which use requires which grade, and what happens when a lower grade is substituted?", "kind": "action" } ] } ] } ] }, { "id": "properties-and-behaviour", "name": "Properties and behaviour", "description": "How Tupolev Tu-95 behaves under conditions an agent can measure or change.", "rationale": "Physical constants are the part of a substance model that transfers between contexts, and each needs its unit and its conditions.", "layers": [ { "id": "physical-constants", "name": "Physical constants", "description": "Values that hold for the pure substance, with their conditions.", "findings": [ { "id": "constants-record", "name": "Constants and conditions", "description": "The quantities worth recording and the state they apply in.", "questions": [ { "id": "constants-record-q01", "text": "What are the defining physical constants of Tupolev Tu-95, in what units and under what conditions?", "kind": "measurement" }, { "id": "constants-record-q02", "text": "Which of these values change with grade or form rather than being fixed?", "kind": "boundary" } ] } ] }, { "id": "stability-and-reactivity", "name": "Stability and reactivity", "description": "What it reacts with, degrades into, and how it is stored.", "findings": [ { "id": "incompatibilities", "name": "Incompatibilities and degradation", "description": "What must not meet it, and what it becomes over time.", "questions": [ { "id": "incompatibilities-q01", "text": "What is Tupolev Tu-95 incompatible with, and what does it degrade into under storage?", "kind": "definition" }, { "id": "incompatibilities-q02", "text": "What storage and handling does that require, and who is competent to do it?", "kind": "action" } ] } ] } ] }, { "id": "hazard-and-regulation", "name": "Hazard classification and regulation", "description": "How Tupolev Tu-95 can harm, and what the law says about holding and moving it.", "rationale": "A substance model without its hazard class and its regulatory identity is unusable in exactly the situations that matter.", "layers": [ { "id": "hazard-class", "name": "Hazard classification", "description": "Classified hazards, exposure limits and protective measures.", "findings": [ { "id": "classified-hazards", "name": "Classified hazards and limits", "description": "The classification, the scheme it belongs to, and the limits set.", "questions": [ { "id": "classified-hazards-q01", "text": "How is Tupolev Tu-95 classified for hazard, under which scheme, and what exposure limits apply?", "kind": "definition" }, { "id": "classified-hazards-q02", "text": "What protection does handling require, and what must an agent refuse to do without it?", "kind": "action" } ] } ] }, { "id": "regulatory-identity", "name": "Regulatory identity and control", "description": "Registration, restriction and transport rules by jurisdiction.", "findings": [ { "id": "controls", "name": "Controls and jurisdiction", "description": "Where it is restricted and what the restriction attaches to.", "questions": [ { "id": "controls-q01", "text": "Which registrations, restrictions or transport rules cover Tupolev Tu-95, and where?", "kind": "provenance" }, { "id": "controls-q02", "text": "Does the control attach to the substance, its concentration, or its intended use?", "kind": "boundary" } ] } ] } ] }, { "id": "provenance-and-evidence", "name": "Provenance, evidence and time", "description": "Where every claim about a Tupolev Tu-95 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-95 and how confident it is.", "questions": [ { "id": "claim-provenance-q01", "text": "What identifies and describes a claim about a Tupolev Tu-95, 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-95, 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-95 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-95 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-95, 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-95, 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-95 is known, and what must it refuse?", "kind": "action", "answer_data": [ "permitted actions", "preconditions", "refusals", "escalation" ] } ] } ] } ] } ] }, "statistics": { "bundles": 9, "layers": 20, "findings": 22, "questions": 60 } } } }