{ "model": { "rank": 5367, "code": "thing-q172957", "model_id": "vr.tr.tupolev-tu-154", "name": "Tupolev Tu-154", "purpose": "Enable an AI agent to identify the Tupolev Tu-154 aircraft family, interpret variant-specific condition and capability evidence, and determine which proposed uses require further technical or operational authorization.", "family": "Thing Registry", "category": "Physical world and living systems", "status": "research-draft", "kind": "thing", "plane": "PHY", "domain": "PHY.OBJ", "industry": "", "version": "", "url": "/models/thing/q172957/", "tier": 2, "score": 68, "payload": { "layer": "wikidata", "aliases": [ "Tupolev Tu-154M" ], "aliasCount": 1, "merged": 1, "knownIn": 68, "facets": null, "markers": [], "lexicalClass": "", "senseRank": null, "alsoRegisteredAs": null, "source": { "dataset": "wikidata", "item": "Q172957", "url": "https://www.wikidata.org/wiki/Q172957", "license": "CC0 1.0" } }, "research": { "vercy": "1.0-draft", "publication": { "status": "research-draft", "adjudicationStatus": "unreviewed", "publishableCanonical": false, "generatedAt": "2026-09-09T22:13:15Z", "providers": [ "Codex" ], "breadth": "recalled by Codex without web access - no source was read", "missingProviders": [], "pass": 2, "cost": { "grok": { "seconds": 24.3, "error": "Reading additional input from stdin...\nOpenAI Codex v0.153.4\n--------\nworkdir: R:\\02_PROJECTS\\02_Meta_Models_Platforms\\Ver.cy\\current\\thing-registry-backlog\nmodel: gpt-6-astra\nprovider: openai\napproval: never\nsandbox: read-only\nreasoning effort: none\nreasoning summaries: none\nsession id: 01a0883a-5bff-73c3-992e-02034b928ab0\n--------\nuser\nDescribe what is already known about one registered thing. Answer as JSON only, no prose around it.\n\nThing: Tupolev Tu-154\nSense to describe: (none recorded)\nDomain code: PHY.OBJ\nAlso known as: (none)\n\n\nContext for this batch of 1001 things:\n# Batch 005: 1001 ", "usd": 0, "recall": true }, "codex": { "seconds": 74.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: 01a0883a-5c03-79d3-95b5-8224ae8d2814\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-154\nRegistry id: vr.tr.tupolev-tu-154\nPlane / domain: PHY / PHY.OBJ\nRegistry definition: (none recorded)\nNames folded into this entry: (no" } } }, "metaModel": { "id": "THING-Q172957", "registryId": "vr.tr.tupolev-tu-154", "name": "Tupolev Tu-154", "version": "0.1.0-research.1", "entryKind": "thing", "family": "Thing Registry", "domain": [ "PHY.OBJ" ], "status": "research-draft" }, "canonicalUrl": "https://ver.cy/models/thing/q172957/", "model": { "registry_id": "vr.tr.tupolev-tu-154", "name": "Tupolev Tu-154", "purpose": "Enable an AI agent to identify the Tupolev Tu-154 aircraft family, interpret variant-specific condition and capability evidence, and determine which proposed uses require further technical or operational authorization.", "definition": "The Tupolev Tu-154 is a Soviet-designed family of swept-wing, three-engine, narrow-body jet airliners developed for medium-range passenger transport, with three rear-mounted turbofan engines and a T-tail.", "scope_statement": "This model owns the type-family knowledge for registry entry vr.tr.tupolev-tu-154 in PHY / PHY.OBJ, including variant distinctions and the evidence needed to assess an associated aircraft; individual airframe histories remain linked instance records.", "in_scope": [ "Tu-154 family identity, variant membership and approved modifications", "Airframe, propulsion and flight-control configuration differences affecting applicability", "Variant-specific loading, performance and airport compatibility", "Installed equipment, crew requirements and operational eligibility", "Maintenance status, life limits and evidence supporting continued use" ], "out_of_scope": [ "Generic aerodynamics and transport-aircraft principles owned by broader aircraft models", "Individual aircraft ownership, registration and complete maintenance logs", "Standalone engine models and their detailed overhaul procedures", "Airline business operations, route economics and fleet scheduling", "Airport infrastructure models and air traffic control procedures", "Accident-event narratives and attribution of responsibility" ], "distinguishing_features": [ "Require manufacturer or approved aircraft records identifying Tu-154 family membership; a registration, paint scheme or operator name is insufficient.", "Use the three-engine aft-fuselage arrangement, swept wing and T-tail as a recognition combination, then verify documentary identity because other aircraft share this layout.", "Distinguish Tu-154M from earlier variants through documented propulsion and configuration: Aviacor identifies three D-30KU-154 series II engines for its described M configuration. [Aviacor Tu-154M](https://www.aviacor.ru/services/samolety/tu-154m/)", "Distinguish the family from a particular aircraft by keeping variant designations separate from manufacturer serial numbers and registrations.", "Treat passenger, VIP and specially modified examples as configurations requiring applicability evidence rather than assuming identical cabin capacities or operating permissions." ], "characteristics": [ { "name": "Documented variant", "kind": "category", "unit_or_values": "Exact approved designation, including suffix; unresolved if unsupported", "why_it_matters": "Determines which manuals, performance data and maintenance requirements apply." }, { "name": "Design and modification authority", "kind": "relation", "unit_or_values": "Links to type-design holder, production records and approved modification documents", "why_it_matters": "Separates original family characteristics from later changes." }, { "name": "Installed engine configuration", "kind": "relation", "unit_or_values": "Engine model, series and approved installation for each of three positions", "why_it_matters": "Controls propulsion, servicing and performance-data applicability." }, { "name": "External dimensions", "kind": "measurement", "unit_or_values": "Length, wingspan and height in m, with variant and source", "why_it_matters": "Supports stand, hangar and ground-clearance assessment." }, { "name": "Approved mass and balance envelope", "kind": "measurement", "unit_or_values": "Mass limits in kg; center of gravity in percent mean aerodynamic chord; configuration and conditions", "why_it_matters": "Prevents a family-level capacity figure from being treated as a loading authorization." }, { "name": "Cabin and payload configuration", "kind": "category", "unit_or_values": "Approved seating count, cabin role, exits and baggage or cargo arrangement", "why_it_matters": "Determines usable capacity and the applicable loading and evacuation constraints." }, { "name": "Conditional flight performance", "kind": "measurement", "unit_or_values": "Speed in explicitly identified units, altitude in m or ft, range in km or NM, fuel consumption in kg/h, runway distance in m", "why_it_matters": "Makes performance comparable only when mass, atmosphere, configuration and reserve assumptions match." }, { "name": "Flight-control and navigation configuration", "kind": "category", "unit_or_values": "Installed control-system, autopilot, navigation and warning-equipment versions", "why_it_matters": "Prevents equipment capability from being inferred solely from the Tu-154 name." }, { "name": "Accumulated structural usage", "kind": "measurement", "unit_or_values": "Flight hours, flight cycles and calendar age against applicable approved limits", "why_it_matters": "Supports assessment of remaining life and required inspections." }, { "name": "Evidence-backed operational state", "kind": "state", "unit_or_values": "Unknown, serviceable, restricted, maintenance due, grounded, stored or withdrawn; dated evidence required", "why_it_matters": "Separates physical existence from readiness and permission to fly." } ], "affordances": [ "Classify a documented aircraft within the Tu-154 family and identify unresolved variant evidence.", "Select the applicable flight, loading and maintenance documentation for a stated configuration.", "Screen a proposed payload and airport pairing using configuration-specific limits and declared conditions.", "Flag missing equipment or approval evidence for a proposed operation.", "Identify maintenance, life-limit or storage-record gaps that require qualified review.", "Compare Tu-154 variants while preserving differences in engines, equipment and approval basis." ] }, "sources": [], "structure": { "bundles": [ { "id": "family-identity-and-applicability", "name": "Family identity and applicability", "description": "Establish what the Tu-154 designation covers and which requirements apply to a documented configuration.", "rationale": "A family name alone cannot select the correct technical limits or establish aircraft identity.", "layers": [ { "id": "designation-and-membership", "name": "Designation and membership", "description": "Resolve family membership through authoritative designations.", "findings": [ { "id": "documented-tu-154-identity", "name": "Documented Tu-154 identity", "description": "Require designation evidence and separate family, variant and airframe identity.", "questions": [ { "text": "Which manufacturer or approved design record establishes the Tu-154 designation and exact variant?", "kind": "provenance", "id": "documented-tu-154-identity-q01" }, { "text": "Does the referenced name identify the family, a variant, a modified configuration or an individual airframe?", "kind": "boundary", "id": "documented-tu-154-identity-q02" } ] } ] }, { "id": "variant-and-modification-effectivity", "name": "Variant and modification effectivity", "description": "Determine applicability across production differences and subsequent changes.", "findings": [ { "id": "configuration-controlled-documentation", "name": "Configuration-controlled documentation", "description": "Associate technical evidence with its variant, serial-number coverage and modification state.", "questions": [ { "text": "Which serial-number ranges and modifications are covered by the selected Tu-154 manuals?", "kind": "boundary", "id": "configuration-controlled-documentation-q01" }, { "text": "Which approved changes alter the aircraft's propulsion, cabin role or operating limitations?", "kind": "provenance", "id": "configuration-controlled-documentation-q02" } ] } ] } ] }, { "id": "airframe-and-propulsion", "name": "Airframe and propulsion", "description": "Represent the Tu-154's physical recognition features and configuration-dependent propulsion.", "rationale": "Recognition and engineering compatibility require more than the aircraft's silhouette.", "layers": [ { "id": "geometry-and-ground-interface", "name": "Geometry and ground interface", "description": "Connect external configuration to identification and airport handling.", "findings": [ { "id": "verified-airframe-configuration", "name": "Verified airframe configuration", "description": "Record wing, tail, engine-placement and landing-gear evidence alongside sourced dimensions.", "questions": [ { "text": "Which documented features distinguish this Tu-154 configuration from visually similar aft-engined trijets?", "kind": "definition", "id": "verified-airframe-configuration-q01" }, { "text": "What dimensions, turning clearances and ground-load constraints apply to this variant?", "kind": "measurement", "id": "verified-airframe-configuration-q02" } ] } ] }, { "id": "engine-installation-and-servicing", "name": "Engine installation and servicing", "description": "Resolve installed engines and their aircraft-level support requirements.", "findings": [ { "id": "applicable-propulsion-package", "name": "Applicable propulsion package", "description": "Keep engine series, installation position, fuel requirements and servicing evidence tied to the exact configuration.", "questions": [ { "text": "Which engine model and series are approved and installed at each position on this Tu-154 variant?", "kind": "provenance", "id": "applicable-propulsion-package-q01" }, { "text": "Which fuel, oil, starting-support and inspection requirements follow from that installation?", "kind": "action", "id": "applicable-propulsion-package-q02" } ] } ] } ] }, { "id": "loading-and-mission-envelope", "name": "Loading and mission envelope", "description": "Determine what a particular Tu-154 configuration can carry and under which flight and airport conditions.", "rationale": "Published family-level capacities cannot establish feasibility for a particular load or runway.", "layers": [ { "id": "cabin-payload-and-balance", "name": "Cabin, payload and balance", "description": "Connect interior configuration with loading limits.", "findings": [ { "id": "approved-load-envelope", "name": "Approved load envelope", "description": "Require an approved cabin layout and mass-and-balance basis before interpreting passenger or payload capacity.", "questions": [ { "text": "Which seating, baggage and special-equipment configuration is approved for the assessed aircraft?", "kind": "provenance", "id": "approved-load-envelope-q01" }, { "text": "What mass, compartment-load and center-of-gravity limits constrain that configuration?", "kind": "measurement", "id": "approved-load-envelope-q02" } ] } ] }, { "id": "conditional-performance", "name": "Conditional performance", "description": "Qualify range and runway claims by their operating assumptions.", "findings": [ { "id": "mission-feasibility-evidence", "name": "Mission feasibility evidence", "description": "Use the applicable Tu-154 performance documentation with explicit mass, weather, runway and fuel assumptions.", "questions": [ { "text": "Under what payload, fuel-reserve and atmospheric assumptions were the quoted range and fuel-consumption values established?", "kind": "measurement", "id": "mission-feasibility-evidence-q01" }, { "text": "Which approved performance assessment is required for the proposed runway, obstacles and aircraft configuration?", "kind": "action", "id": "mission-feasibility-evidence-q02" } ] } ] } ] }, { "id": "controls-and-operational-eligibility", "name": "Controls and operational eligibility", "description": "Connect installed Tu-154 systems and crew requirements to supported operations.", "rationale": "Equipment and approvals can differ substantially between aircraft carrying the same family designation.", "layers": [ { "id": "control-and-warning-capability", "name": "Control and warning capability", "description": "Establish configuration-specific control, automation and protective functions.", "findings": [ { "id": "documented-system-behavior", "name": "Documented system behavior", "description": "Record installed control and warning systems, their dependencies and the implications of degraded states without assuming undocumented protections.", "questions": [ { "text": "Which flight-control, autopilot and warning-system versions are installed, and which approved manuals describe them?", "kind": "provenance", "id": "documented-system-behavior-q01" }, { "text": "Which interlocks, warnings and degraded-system restrictions are documented for that configuration?", "kind": "definition", "id": "documented-system-behavior-q02" } ] } ] }, { "id": "crew-equipment-and-permissions", "name": "Crew, equipment and permissions", "description": "Separate installed capability from authorization for a proposed flight.", "findings": [ { "id": "operation-specific-eligibility", "name": "Operation-specific eligibility", "description": "Require current evidence of crew qualification, equipment serviceability and applicable operational approvals.", "questions": [ { "text": "What flight-deck complement and variant-specific qualifications does the applicable Tu-154 documentation require?", "kind": "provenance", "id": "operation-specific-eligibility-q01" }, { "text": "Which issuing authorities and current requirements govern navigation, surveillance, noise and airspace eligibility for the proposed operation?", "kind": "boundary", "id": "operation-specific-eligibility-q02" }, { "text": "Which equipment defects or missing approvals prevent the proposed operation under the applicable dispatch rules?", "kind": "action", "id": "operation-specific-eligibility-q03" } ] } ] } ] }, { "id": "continued-airworthiness-and-lifecycle", "name": "Continued airworthiness and lifecycle", "description": "Interpret Tu-154 aging, maintenance and storage evidence when assessing permitted use.", "rationale": "An aircraft's age or apparent completeness does not establish remaining life or serviceability.", "layers": [ { "id": "life-limits-and-maintenance", "name": "Life limits and maintenance", "description": "Tie accumulated use and defects to applicable limits and approved maintenance actions.", "findings": [ { "id": "remaining-life-and-defect-evidence", "name": "Remaining life and defect evidence", "description": "Assess airframe and component usage, repairs, inspections and any individually approved life extensions.", "questions": [ { "text": "What hour, cycle and calendar limits apply to this Tu-154 configuration, and what approvals support any extensions?", "kind": "provenance", "id": "remaining-life-and-defect-evidence-q01" }, { "text": "Which documented fatigue, corrosion, propulsion or control-system failure modes require recurring inspections or mandatory corrective actions?", "kind": "definition", "id": "remaining-life-and-defect-evidence-q02" }, { "text": "What remaining life and overdue work follow from the linked aircraft and component records?", "kind": "measurement", "id": "remaining-life-and-defect-evidence-q03" } ] } ] }, { "id": "storage-and-return-to-service", "name": "Storage and return to service", "description": "Distinguish preserved, withdrawn and operational examples through dated technical evidence.", "findings": [ { "id": "lifecycle-transition-evidence", "name": "Lifecycle transition evidence", "description": "Identify the documentation, inspections and release authority required before changing an aircraft's supported use.", "questions": [ { "text": "What preservation, component-removal and environmental-exposure records exist for a stored Tu-154?", "kind": "provenance", "id": "lifecycle-transition-evidence-q01" }, { "text": "Which approved inspections, maintenance releases and authority decisions are required for its proposed return to service or restricted movement?", "kind": "action", "id": "lifecycle-transition-evidence-q02" } ] } ] } ] }, { "id": "evidence-and-external-alignment", "name": "Evidence and external alignment", "description": "What the world already says about this thing, gathered so the model can be checked against it.", "rationale": "A model that cannot be lined up against existing standards, identifiers and practice cannot be adopted by anyone who already uses them.", "layers": [ { "id": "reported-evidence", "name": "Reported evidence", "description": "Findings from the breadth pass, kept separate from the structural claims.", "findings": [ { "id": "evidence-confidence-notes", "name": "Check these first", "description": "Recalled without web access and unsourced; every item is a lead to verify.", "evidence": [ "This description is recalled knowledge, not source-verified research.", "Dimensions, seating and mass limits should be checked against the specific variant and approved aircraft documentation.", "Current fleet status, exact certification bases and jurisdiction-specific operating restrictions require verification." ], "questions": [ { "id": "evidence-confidence-notes-q01", "text": "Which of these check these first hold for the sense of Tupolev Tu-154 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-154: initial production variant", "Tu-154A: improved early variant", "Tu-154B: variant with structural and capacity changes", "Tu-154B-2: further development of the Tu-154B", "Tu-154M: substantially revised variant with more efficient Soloviev D-30KU-154 engines" ], "questions": [ { "id": "evidence-kinds-q01", "text": "Which of these kinds and varieties hold for the sense of Tupolev Tu-154 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": "Tupolev aircraft designation", "value_or_pattern": "Tu-154, with variant suffixes such as B-2 or M", "note": "Identifies the aircraft family or variant, rather than an individual airframe." }, { "scheme": "ICAO aircraft type designator", "value_or_pattern": "T154", "note": "Operational type designator used in flight planning." }, { "scheme": "Aircraft nationality and registration marks", "value_or_pattern": "State-issued nationality prefix followed by an individual registration", "note": "Identifies a registered airframe; the registration can change during its service life." } ], "questions": [ { "id": "evidence-identifiers-q01", "text": "Which of these identifiers and schemes hold for the sense of Tupolev Tu-154 this model covers, and on what evidence?", "kind": "provenance" } ] }, { "id": "evidence-standards-and-regulation", "name": "Standards and regulation", "description": "Recalled without web access and unsourced; every item is a lead to verify.", "evidence": [ "ICAO Annex 8, Airworthiness of Aircraft: international airworthiness framework implemented by national aviation authorities.", "ICAO Annex 6, Operation of Aircraft: international operational framework implemented by national aviation authorities.", "ICAO Annex 16, Volume I, Aircraft Noise: noise certification provisions; applicable requirements and airport restrictions depend on variant, certification history and jurisdiction." ], "questions": [ { "id": "evidence-standards-and-regulation-q01", "text": "Which of these standards and regulation hold for the sense of Tupolev Tu-154 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": [ "Scheduled domestic and international passenger services, particularly within the Soviet Union and successor states.", "Passenger charter operations.", "Government and military passenger transport.", "Special-purpose aircraft conversions, including reconnaissance and observation missions." ], "questions": [ { "id": "evidence-real-world-use-q01", "text": "Which of these real-world use hold for the sense of Tupolev Tu-154 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 47.9", "unit": "m" }, { "quantity": "Wingspan", "typical_range": "Approximately 37.55", "unit": "m" }, { "quantity": "Passenger seating capacity", "typical_range": "Approximately 150-180, depending on variant and cabin configuration", "unit": "passengers" }, { "quantity": "Maximum takeoff mass", "typical_range": "Approximately 90-104, depending on variant", "unit": "tonnes" }, { "quantity": "Cruise speed", "typical_range": "Approximately 850-950", "unit": "km/h" } ], "questions": [ { "id": "evidence-measurements-q01", "text": "Which of these typical measurements hold for the sense of Tupolev Tu-154 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": [ "High-angle-of-attack flight can produce a deep stall, with severely reduced pitch-control effectiveness.", "Airframe icing or contaminated lifting surfaces can degrade lift and controllability.", "Engine failure, fire or foreign-object ingestion can reduce available thrust and require emergency procedures.", "Hydraulic or flight-control system failures can impair aircraft control.", "Age-related fatigue and corrosion require inspection and maintenance to preserve structural integrity." ], "questions": [ { "id": "evidence-failure-modes-and-hazards-q01", "text": "Which of these failure modes and hazards hold for the sense of Tupolev Tu-154 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 family was especially prominent in Soviet and post-Soviet airline networks and was also exported to other regions.", "Airport noise restrictions have constrained operations, especially for earlier engine variants.", "Airworthiness oversight, registration and operating permissions depend on the responsible national authorities." ], "questions": [ { "id": "evidence-regional-variation-q01", "text": "Which of these regional variation hold for the sense of Tupolev Tu-154 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": "Boeing 727", "difference": "A separate American aircraft family with a similar rear-mounted three-engine and T-tail layout; manufacturer and type design distinguish it." }, { "name": "Tupolev Tu-134", "difference": "A smaller, twin-engine airliner intended primarily for shorter routes." }, { "name": "Tupolev Tu-204", "difference": "A later Tupolev airliner family with two underwing engines." }, { "name": "Individual Tu-154 airframe", "difference": "A physical aircraft identified by serial number and registration; this entry describes the family rather than a particular unit." } ], "questions": [ { "id": "evidence-neighbours-q01", "text": "Which of these neighbouring kinds and how to tell them apart hold for the sense of Tupolev Tu-154 this model covers, and on what evidence?", "kind": "provenance" } ] } ] } ] } ] }, "openQuestions": [ "Which authoritative family and variant records establish the complete Tu-154 designation hierarchy and the treatment of experimental or special-purpose derivatives?", "Which approved manuals and revisions are available for each variant, and how do their engine, crew, loading and performance requirements differ?", "Which currently applicable authorities, mandatory instructions and operational restrictions govern each relevant jurisdiction and configuration?", "Which primary maintenance sources establish recurring Tu-154 failure modes, inspection requirements and the basis for individual life extensions?", "Does an existing Vercy world-model publication already cover this aircraft family, requiring this registry entry to link to that source of truth?" ], "statistics": { "bundles": 6, "layers": 11, "findings": 19, "questions": 31 } }, "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-154, record what state it is in, and decide what may be done with it.", "whatItIs": "Enable an AI agent to identify the Tupolev Tu-154 aircraft family, interpret variant-specific condition and capability evidence, and determine which proposed uses require further technical or operational authorization.", "characteristics": { "substance": "material", "origin": "manufactured", "agency": "inert", "mobility": "varies" }, "whatYouCanDoWithIt": [ "observed and measured" ], "distinguishingFeatures": [ "Names folded into this entry, which a task may need to split apart again: Tupolev Tu-154M.", "1 finer distinctions are held as aliases rather than separate entries, because telling them apart needs a task that asks for it.", "Described in 68 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-154, 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-154 looks like has to come from research." ], "relatedModels": [ { "relation": "covers", "note": "Finer kinds folded into this entry because telling them apart needs a task that asks for it. Each is a model waiting to be split out when one does.", "targets": [ "Tupolev Tu-154M" ] } ], "standing": "Described in 68 Wikipedia languages, which measures how widely it is written about rather than how important or how common it is. 1 finer distinctions are held inside this entry as names rather than as separate models.", "structure": { "bundles": [ { "id": "identity-and-classification", "name": "Identity, naming and classification", "description": "How an agent tells one Tupolev Tu-154 from another, and a Tupolev Tu-154 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-154, 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-154, 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-154 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-154, 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-154, 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-154 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-154 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-154, 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-154, 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-154 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-154 from the things most often confused with it.", "questions": [ { "id": "distinguishing-features-q01", "text": "What identifies and describes what distinguishes a Tupolev Tu-154, 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-154, 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-154 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-154 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-154, 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-154, 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-154 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-154 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-154, 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-154, 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-154 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-154 is judged and by whom.", "questions": [ { "id": "condition-assessment-q01", "text": "What identifies and describes the condition of a Tupolev Tu-154, 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-154, 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-154 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-154 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-154 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-154, 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-154, 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-154 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-154 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-154, 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-154, 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-154 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-154 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-154 between them.", "questions": [ { "id": "stages-and-transitions-q01", "text": "What identifies and describes the lifecycle of a Tupolev Tu-154, 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-154, 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-154 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-154, how often and by whom.", "findings": [ { "id": "observation-record", "name": "Observation record", "description": "How an observation of a Tupolev Tu-154 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-154, 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-154, 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-154 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-154 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-154 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-154 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-154, 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-154, 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-154 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-154.", "findings": [ { "id": "procedures-and-skills", "name": "Procedures, skills and required tools", "description": "What an agent needs before it can act on a Tupolev Tu-154 at all.", "questions": [ { "id": "procedures-and-skills-q01", "text": "What identifies and describes handling a Tupolev Tu-154, 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-154, 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-154 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-154 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-154 and how confident it is.", "questions": [ { "id": "claim-provenance-q01", "text": "What identifies and describes a claim about a Tupolev Tu-154, 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-154, 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-154 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-154 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-154, 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-154, 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-154 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 } } } }