{ "model": { "rank": 5144, "code": "thing-q6409", "model_id": "vr.tr.boeing-727", "name": "Boeing 727", "purpose": "Enable an AI agent to recognise the Boeing 727 aircraft family, distinguish its variants and individual airframes, assess evidence of condition and approval, and identify which operations or interventions require further verification.", "family": "Thing Registry", "category": "Physical world and living systems", "status": "research-draft", "kind": "thing", "plane": "PHY", "domain": "PHY.OBJ", "industry": "", "version": "", "url": "/models/thing/q6409/", "tier": 2, "score": 69, "payload": { "layer": "wikidata", "aliases": [ "Boeing 727-100", "Boeing 727-200", "Boeing 727-200 Advanced" ], "aliasCount": 3, "merged": 3, "knownIn": 69, "facets": null, "markers": [], "lexicalClass": "", "senseRank": null, "alsoRegisteredAs": null, "source": { "dataset": "wikidata", "item": "Q6409", "url": "https://www.wikidata.org/wiki/Q6409", "license": "CC0 1.0" } }, "research": { "vercy": "1.0-draft", "publication": { "status": "research-draft", "adjudicationStatus": "unreviewed", "publishableCanonical": false, "generatedAt": "2026-09-09T21:45:41Z", "providers": [ "Codex" ], "breadth": "recalled by Codex without web access - no source was read", "missingProviders": [], "pass": 2, "cost": { "grok": { "seconds": 25, "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: 01a08821-2e8a-7b91-bf0e-3bd428a6997a\n--------\nuser\nDescribe what is already known about one registered thing. Answer as JSON only, no prose around it.\n\nThing: Boeing 727\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 regi", "usd": 0, "recall": true }, "codex": { "seconds": 70.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: 01a08821-2e78-7c52-8aea-3705ce96547b\n--------\nuser\nYou are drafting a Vercy meta-model for one registered thing. Answer as JSON only, no prose around it.\n\nThing: Boeing 727\nRegistry id: vr.tr.boeing-727\nPlane / domain: PHY / PHY.OBJ\nRegistry definition: (none recorded)\nNames folded into this entry: (none)\n\n\nCo" } } }, "metaModel": { "id": "THING-Q6409", "registryId": "vr.tr.boeing-727", "name": "Boeing 727", "version": "0.1.0-research.1", "entryKind": "thing", "family": "Thing Registry", "domain": [ "PHY.OBJ" ], "status": "research-draft" }, "canonicalUrl": "https://ver.cy/models/thing/q6409/", "model": { "registry_id": "vr.tr.boeing-727", "name": "Boeing 727", "purpose": "Enable an AI agent to recognise the Boeing 727 aircraft family, distinguish its variants and individual airframes, assess evidence of condition and approval, and identify which operations or interventions require further verification.", "definition": "The Boeing 727 is a family of Boeing narrow-body, swept-wing jet transport aircraft with three rear-mounted Pratt & Whitney JT8D turbofan engines and a T-tail, developed for short- and medium-haul airline service.", "scope_statement": "This model owns the Boeing 727 as a registered aircraft family and the family-specific information needed to interpret a variant or individual airframe; it distinguishes original design characteristics from modifications, current condition and jurisdiction-dependent operating permissions.", "in_scope": [ "Boeing 727 family identity, variant distinctions and airframe identification evidence", "Three-engine rear-fuselage installation, T-tail, swept wing and high-lift configuration", "Passenger, freighter and converted configurations with their applicable limitations", "Propulsion, flight controls, landing gear, pressurisation and supporting aircraft systems", "Airworthiness evidence, structural ageing, maintenance status and modification history", "Runway suitability, loading constraints, crew requirements and environmental operating restrictions" ], "out_of_scope": [ "Generic aerodynamics and jet-airliner principles owned by broader aircraft models", "The Boeing company, its corporate history and manufacturing organisation", "Engine-family design knowledge beyond its installation and applicability to the Boeing 727", "Airline business operations, route economics and ticketing", "Airport infrastructure except its compatibility with a specified 727 configuration", "Independent models of individual airframes, flights or accidents" ], "distinguishing_features": [ "Check for three rear-mounted jet engines, including a centre engine supplied through an intake at the vertical-tail base; this separates the 727 from common rear-engined twins.", "Check the combination of a T-tail, swept low wing and the three-engine installation; no single silhouette feature establishes Boeing 727 identity.", "Use manufacturer identification and approved records to distinguish the 727 family and its variants from visually similar aircraft.", "Distinguish the shorter 727-100 series from the stretched 727-200 series using the recorded model and configuration-specific dimensions.", "Treat the aft ventral stair arrangement as supporting identification evidence, while checking whether the particular aircraft retains or has modified that installation." ], "characteristics": [ { "name": "Certified model and series", "kind": "category", "unit_or_values": "Exact model designation from applicable identification and certification records", "why_it_matters": "Selects the correct design baseline, limitations and maintenance applicability." }, { "name": "Airframe identity", "kind": "relation", "unit_or_values": "Manufacturer serial number linked to registration and identity records", "why_it_matters": "Prevents a registration change or visual resemblance from being mistaken for a different design or airframe." }, { "name": "Mission configuration", "kind": "category", "unit_or_values": "Passenger, factory freighter, converted freighter or other documented configuration", "why_it_matters": "Determines which cabin, cargo, loading and emergency provisions require examination." }, { "name": "Installed propulsion configuration", "kind": "relation", "unit_or_values": "Engine model at each of three positions, installation approval and associated modifications", "why_it_matters": "Performance, maintenance and noise compliance depend on the installed configuration." }, { "name": "Airframe dimensions", "kind": "measurement", "unit_or_values": "Length, wingspan and height in metres, tied to variant and modifications", "why_it_matters": "Supports identification and checks of stand, hangar and ground-clearance compatibility." }, { "name": "Approved mass limits", "kind": "measurement", "unit_or_values": "Applicable take-off, landing and zero-fuel mass limits in kilograms", "why_it_matters": "Family-level nominal weights cannot establish a particular aircraft's loading limits." }, { "name": "Centre-of-gravity envelope", "kind": "measurement", "unit_or_values": "Approved limits in percent mean aerodynamic chord or the units used by the applicable loading documentation", "why_it_matters": "Passenger layouts and cargo conversions alter the loading evidence needed for dispatch." }, { "name": "High-lift and flight-control status", "kind": "state", "unit_or_values": "Documented configuration, serviceability, defects and applicable restrictions", "why_it_matters": "The observed condition must be interpreted against the 727's specific control and high-lift arrangements." }, { "name": "Accumulated utilisation", "kind": "measurement", "unit_or_values": "Flight hours, flight cycles and calendar age with record completeness", "why_it_matters": "Different structural and component obligations depend on different measures of exposure." }, { "name": "Airworthiness evidence status", "kind": "state", "unit_or_values": "Verified, incomplete, expired, conflicting or unknown, with supporting records and dates", "why_it_matters": "Physical appearance alone does not establish eligibility for flight." }, { "name": "Noise and operating approval", "kind": "relation", "unit_or_values": "Applicable certificates, modifications, jurisdiction, airport restrictions and validity dates", "why_it_matters": "A noise-related modification does not establish unrestricted access to every airport." }, { "name": "Flight-deck configuration and crew basis", "kind": "relation", "unit_or_values": "Installed flight-deck equipment linked to approved crew requirements and operating documentation", "why_it_matters": "Crew and equipment assumptions must follow the actual approved aircraft configuration." } ], "affordances": [ "Identify a candidate aircraft as a Boeing 727 and resolve its series using physical and documentary evidence.", "Compare an airframe's engines, cabin, cargo installation and flight deck with its approved configuration.", "Screen a proposed airport or mission for dimensional, loading, performance and environmental constraints.", "Identify missing maintenance, structural-life or modification evidence that blocks a readiness assessment.", "Prepare configuration-specific inspection and records-review questions for qualified personnel.", "Separate preservation, ground handling and flight-use decisions according to documented condition and approval." ] }, "sources": [], "structure": { "bundles": [ { "id": "family-and-configuration", "name": "Family and configuration", "description": "Establish which Boeing 727 design and configuration the available evidence describes.", "rationale": "The family name alone cannot select the correct dimensions, limits or maintenance requirements.", "layers": [ { "id": "family-and-series-identity", "name": "Family and series identity", "description": "Connect physical recognition to authoritative model identification.", "findings": [ { "id": "series-identification-evidence", "name": "Series identification evidence", "description": "Require agreement between the aircraft's identification records and its observed 727 configuration before assigning variant-specific properties.", "questions": [ { "text": "Which recorded model designation establishes the aircraft as a 727-100 or 727-200 series variant?", "kind": "definition", "id": "series-identification-evidence-q01" }, { "text": "Which manufacturer or certification record supports that designation, and does it agree with the airframe identification plate?", "kind": "provenance", "id": "series-identification-evidence-q02" } ] } ] }, { "id": "airframe-configuration-baseline", "name": "Airframe configuration baseline", "description": "Separate original production configuration from later approved changes.", "findings": [ { "id": "conversion-and-modification-lineage", "name": "Conversion and modification lineage", "description": "Interpret passenger layouts, freighter conversions, engine changes and flight-deck alterations through their documented approval history.", "questions": [ { "text": "Was this 727 delivered in its present mission configuration, or which approved conversion established it?", "kind": "provenance", "id": "conversion-and-modification-lineage-q01" }, { "text": "Which present characteristics belong to the Boeing 727 family baseline and which belong only to this modified airframe?", "kind": "boundary", "id": "conversion-and-modification-lineage-q02" } ] } ] } ] }, { "id": "trijet-propulsion-and-aircraft-systems", "name": "Trijet propulsion and aircraft systems", "description": "Capture the implications of three rear-mounted engines and their supporting systems.", "rationale": "Engine position, centre-engine intake geometry and system dependencies affect inspection, fault interpretation and performance applicability.", "layers": [ { "id": "engine-installations", "name": "Engine installations", "description": "Identify each installed engine and its position-specific interfaces.", "findings": [ { "id": "three-position-propulsion-baseline", "name": "Three-position propulsion baseline", "description": "Associate each engine with installation records, applicable thrust data and any exhaust or noise-related modification.", "questions": [ { "text": "Which engine model, rating and modification standard is installed at each of the three engine positions?", "kind": "definition", "id": "three-position-propulsion-baseline-q01" }, { "text": "What inspection evidence covers the centre-engine intake duct and the interfaces of the two side-mounted engines?", "kind": "provenance", "id": "three-position-propulsion-baseline-q02" } ] } ] }, { "id": "system-dependencies", "name": "System dependencies", "description": "Relate propulsion and auxiliary equipment to aircraft services and degraded configurations.", "findings": [ { "id": "power-and-service-availability", "name": "Power and service availability", "description": "Require configuration-specific evidence for electrical, hydraulic and pneumatic availability, including auxiliary power and dispatch restrictions.", "questions": [ { "text": "Which installed sources supply electrical, hydraulic and pneumatic services in the documented ground and flight configurations?", "kind": "definition", "id": "power-and-service-availability-q01" }, { "text": "Which approved limitations apply when an engine-driven source, auxiliary power unit or related service is unavailable?", "kind": "action", "id": "power-and-service-availability-q02" } ] } ] } ] }, { "id": "flight-envelope-and-airfield-fit", "name": "Flight envelope and airfield fit", "description": "Relate the 727's wing, tail and control configuration to verified operating limits and airport compatibility.", "rationale": "A general reputation for runway capability cannot establish suitability for a particular aircraft, load or airfield.", "layers": [ { "id": "wing-tail-and-controls", "name": "Wing, tail and controls", "description": "Interpret the swept-wing, T-tail and high-lift arrangements through applicable operating documentation.", "findings": [ { "id": "high-lift-and-envelope-evidence", "name": "High-lift and envelope evidence", "description": "Link leading-edge devices, trailing-edge flaps, stabiliser and stall-related provisions to the aircraft's documented configuration and condition.", "questions": [ { "text": "Which approved documentation defines the installed high-lift devices, permitted configurations and associated speed limits?", "kind": "provenance", "id": "high-lift-and-envelope-evidence-q01" }, { "text": "Which defects or modifications affect the 727's stall-warning provisions, stabiliser operation or high-lift configuration?", "kind": "boundary", "id": "high-lift-and-envelope-evidence-q02" } ] } ] }, { "id": "runway-and-ground-compatibility", "name": "Runway and ground compatibility", "description": "Assess performance and physical fit using variant-specific inputs.", "findings": [ { "id": "mission-specific-airfield-assessment", "name": "Mission-specific airfield assessment", "description": "Use approved performance data and actual dimensions to identify whether a proposed operation needs further calculation or restriction.", "questions": [ { "text": "What runway performance follows from the actual mass, engine configuration, weather, elevation and runway condition using applicable approved data?", "kind": "measurement", "id": "mission-specific-airfield-assessment-q01" }, { "text": "Do the aircraft's dimensions, landing-gear loading and rear-engine clearances fit the proposed taxi route, stand and servicing arrangements?", "kind": "action", "id": "mission-specific-airfield-assessment-q02" } ] } ] } ] }, { "id": "payload-access-and-occupant-protection", "name": "Payload, access and occupant protection", "description": "Describe how the configured 727 carries people or cargo and how its access arrangements affect safe use.", "rationale": "Passenger and freighter 727s require different loading, restraint, fire-protection and evacuation evidence.", "layers": [ { "id": "cabin-and-cargo-loading", "name": "Cabin and cargo loading", "description": "Connect the approved interior or cargo installation to mass distribution and restraint limits.", "findings": [ { "id": "configuration-specific-payload-envelope", "name": "Configuration-specific payload envelope", "description": "Treat seating capacity, cargo positions, floor loading and centre-of-gravity limits as configuration-dependent properties.", "questions": [ { "text": "What seating layout or cargo conversion defines the approved payload arrangement for this 727?", "kind": "provenance", "id": "configuration-specific-payload-envelope-q01" }, { "text": "What payload, compartment, floor-loading and centre-of-gravity limits apply to the proposed distribution?", "kind": "measurement", "id": "configuration-specific-payload-envelope-q02" } ] } ] }, { "id": "doors-stairs-and-emergency-provisions", "name": "Doors, stairs and emergency provisions", "description": "Account for the aft ventral stairs, other exits and configuration-specific protective equipment.", "findings": [ { "id": "access-and-protection-configuration", "name": "Access and protection configuration", "description": "Verify the presence, modification status and serviceability of access mechanisms, protective devices and emergency provisions.", "questions": [ { "text": "Are the aft ventral stairs retained, and what documented locking or protective modifications apply to their operation?", "kind": "provenance", "id": "access-and-protection-configuration-q01" }, { "text": "Which exit, evacuation, oxygen and fire-protection provisions are required by the present passenger or freighter configuration?", "kind": "action", "id": "access-and-protection-configuration-q02" } ] } ] } ] }, { "id": "continued-airworthiness-and-use-eligibility", "name": "Continued airworthiness and use eligibility", "description": "Determine what the available records establish about continued operation of an ageing Boeing 727.", "rationale": "Physical completeness, maintenance compliance and permission to conduct a particular flight are distinct assessments.", "layers": [ { "id": "structural-ageing-and-maintenance", "name": "Structural ageing and maintenance", "description": "Relate utilisation and repair history to applicable inspections and limitations.", "findings": [ { "id": "life-and-compliance-evidence", "name": "Life and compliance evidence", "description": "Track evidence concerning pressure-fuselage fatigue, corrosion, repairs, engine-support structure and applicable component obligations without assuming every issue affects every airframe.", "questions": [ { "text": "What flight-hour, cycle and calendar records support the current structural inspection and component-life assessment?", "kind": "measurement", "id": "life-and-compliance-evidence-q01" }, { "text": "Which applicable airworthiness directives, structural programmes and repair approvals remain unresolved or lack compliance evidence?", "kind": "provenance", "id": "life-and-compliance-evidence-q02" } ] } ] }, { "id": "operational-and-environmental-permission", "name": "Operational and environmental permission", "description": "Connect the actual aircraft configuration to crew, equipment and jurisdiction-specific operating requirements.", "findings": [ { "id": "proposed-use-eligibility", "name": "Proposed-use eligibility", "description": "Assess flight eligibility from dated approvals and restrictions, including noise evidence and any relevant modification certificates.", "questions": [ { "text": "Which current records establish the approved crew requirements, required equipment and operating limitations for this 727?", "kind": "provenance", "id": "proposed-use-eligibility-q01" }, { "text": "Do its documented noise status and other applicable approvals permit the proposed operation at the intended airports and date?", "kind": "action", "id": "proposed-use-eligibility-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, seating limits and performance should be checked against the specific variant and configuration.", "Applicable certification bases, airworthiness directives, noise compliance and present operating status require separate verification." ], "questions": [ { "id": "evidence-confidence-notes-q01", "text": "Which of these check these first hold for the sense of Boeing 727 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": [ "727-100: original shorter-fuselage series", "727-100C: convertible passenger/cargo variant", "727-100QC: quick-change passenger/cargo variant", "727-200: stretched-fuselage series", "727-200 Advanced: improved-performance development", "Freighter conversions of passenger aircraft" ], "questions": [ { "id": "evidence-kinds-q01", "text": "Which of these kinds and varieties hold for the sense of Boeing 727 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": "Boeing model designation", "value_or_pattern": "727-100 or 727-200, with additional variant or customer suffixes", "note": "Identifies a model or configuration, not an individual airframe." }, { "scheme": "ICAO aircraft type designator", "value_or_pattern": "B721; B722", "note": "B721 denotes the 727-100 series; B722 denotes the 727-200 series." }, { "scheme": "Manufacturer serial number", "value_or_pattern": "Boeing manufacturer serial number (MSN)", "note": "Identifies an individual airframe; distinct from its changeable national registration." } ], "questions": [ { "id": "evidence-identifiers-q01", "text": "Which of these identifiers and schemes hold for the sense of Boeing 727 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 short- and medium-haul passenger transport", "Cargo transport using dedicated or converted freighters", "Charter and executive transport", "Operations at airports benefiting from its high-lift wing and integral rear boarding stairs" ], "questions": [ { "id": "evidence-real-world-use-q01", "text": "Which of these real-world use hold for the sense of Boeing 727 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 40.6 for the 727-100; 46.7 for the 727-200", "unit": "m" }, { "quantity": "Wingspan", "typical_range": "Approximately 32.9", "unit": "m" }, { "quantity": "Passenger seating capacity", "typical_range": "Approximately 100-189, depending on variant and cabin configuration", "unit": "passengers" }, { "quantity": "Cruise Mach number", "typical_range": "Approximately 0.80-0.85", "unit": "Mach" }, { "quantity": "Standard flight-deck crew", "typical_range": "3: captain, first officer and flight engineer", "unit": "people" } ], "questions": [ { "id": "evidence-measurements-q01", "text": "Which of these typical measurements hold for the sense of Boeing 727 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": [ "Deep-stall risk at excessive angles of attack associated with the T-tail configuration.", "Incorrect flap, slat or trim configuration during takeoff can compromise lift and controllability.", "Engine failure or fire can reduce available thrust and damage nearby systems.", "Fatigue cracking and corrosion require inspection and maintenance as airframes age.", "Airborne deployment of the rear airstair was a historical security hazard that prompted preventive modifications." ], "questions": [ { "id": "evidence-failure-modes-and-hazards-q01", "text": "Which of these failure modes and hazards hold for the sense of Boeing 727 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": [ "Noise restrictions at destination airports have influenced the use of hush kits and the retirement of unmodified aircraft.", "Individual airframes carry registrations issued by their state of registry." ], "questions": [ { "id": "evidence-regional-variation-q01", "text": "Which of these regional variation hold for the sense of Boeing 727 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 737", "difference": "A separate narrow-body aircraft family with two underwing engines, rather than the 727's three rear-mounted engines." }, { "name": "Boeing 707", "difference": "A separate jet transport family with four underwing engines." }, { "name": "Hawker Siddeley Trident", "difference": "A separately designed British rear-engined trijet with a T-tail; similar layout does not make it a 727 variant." }, { "name": "Individual Boeing 727 airframe", "difference": "A physical aircraft identified by its serial number and registration; this entry describes the aircraft family." } ], "questions": [ { "id": "evidence-neighbours-q01", "text": "Which of these neighbouring kinds and how to tell them apart hold for the sense of Boeing 727 this model covers, and on what evidence?", "kind": "provenance" } ] } ] } ] } ] }, "openQuestions": [ "Does an existing Vercy world model already cover the Boeing 727 family, requiring this registry entry to link to it?", "Which authoritative certification records establish the complete variant taxonomy and the applicability of dimensions, mass limits and engine installations?", "Which factory freighter configurations, cargo conversions, engine modifications and noise-reduction installations warrant explicit branches within this family model?", "Which Boeing 727-specific structural concerns, failure modes and mandatory actions are supported by primary records, and to which airframes do they apply?", "Which current jurisdiction-specific operating restrictions and approved flight-deck changes affect crew requirements, required equipment and airport access?" ], "statistics": { "bundles": 6, "layers": 11, "findings": 18, "questions": 28 } }, "draft": { "generator": "vr.draft.v3", "status": "draft-generated", "researched": false, "archetype": "unclassified", "method": "Written from the archetype playbook - what this kind of thing needs beyond identity and provenance - and from the structure that recurred across 6,333 models already researched by two engines. Applied to this entry by rule. No source was read for this thing and no claim here is researched. This entry carries no facets of its own, so they were inferred from its domain - a guess about a whole domain applied to one thing.", "facetsInferred": true, "nextPass": "A researcher replaces this draft with a sourced specification. Treat every sentence below as a proposal to argue with.", "purpose": "Give an agent a durable, checkable way to recognise a Boeing 727, record what state it is in, and decide what may be done with it.", "whatItIs": "Enable an AI agent to recognise the Boeing 727 aircraft family, distinguish its variants and individual airframes, assess evidence of condition and approval, and identify which operations or interventions require further verification.", "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: Boeing 727-100, Boeing 727-200, Boeing 727-200 Advanced.", "3 finer distinctions are held as aliases rather than separate entries, because telling them apart needs a task that asks for it.", "Described in 69 Wikipedia languages, which is a measure of how widely the thing is known, not of how important it is." ], "openQuestionsForResearch": [ "Which of the bundles below does a real task actually need, and which are ceremony?", "What does this thing have that the facets do not capture at all?", "Which neighbouring kind is most often confused with a Boeing 727, 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 Boeing 727 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": [ "Boeing 727-100", "Boeing 727-200", "Boeing 727-200 Advanced" ] } ], "standing": "Described in 69 Wikipedia languages, which measures how widely it is written about rather than how important or how common it is. 3 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 Boeing 727 from another, and a Boeing 727 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 Boeing 727, 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 Boeing 727, 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 Boeing 727 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 Boeing 727, 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 Boeing 727, 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 Boeing 727 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 Boeing 727 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 Boeing 727, 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 Boeing 727, 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 Boeing 727 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 Boeing 727 from the things most often confused with it.", "questions": [ { "id": "distinguishing-features-q01", "text": "What identifies and describes what distinguishes a Boeing 727, 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 Boeing 727, 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 Boeing 727 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 Boeing 727 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 Boeing 727, 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 Boeing 727, 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 Boeing 727 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 Boeing 727 is built from and which parts are replaceable.", "questions": [ { "id": "parts-and-materials-q01", "text": "What identifies and describes the composition of a Boeing 727, 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 Boeing 727, 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 Boeing 727 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 Boeing 727 is judged and by whom.", "questions": [ { "id": "condition-assessment-q01", "text": "What identifies and describes the condition of a Boeing 727, 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 Boeing 727, 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 Boeing 727 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 Boeing 727 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 Boeing 727 is, and what that position is measured against.", "questions": [ { "id": "position-and-frame-q01", "text": "What identifies and describes the location of a Boeing 727, 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 Boeing 727, 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 Boeing 727 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 Boeing 727 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 Boeing 727, 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 Boeing 727, 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 Boeing 727 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 Boeing 727 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 Boeing 727 between them.", "questions": [ { "id": "stages-and-transitions-q01", "text": "What identifies and describes the lifecycle of a Boeing 727, 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 Boeing 727, 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 Boeing 727 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 Boeing 727, how often and by whom.", "findings": [ { "id": "observation-record", "name": "Observation record", "description": "How an observation of a Boeing 727 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 Boeing 727, 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 Boeing 727, 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 Boeing 727 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 Boeing 727 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 Boeing 727 is for, and what it is used for anyway.", "findings": [ { "id": "function-and-purpose", "name": "Function, purpose and misuse", "description": "The function a Boeing 727 performs and the uses that fall outside it.", "questions": [ { "id": "function-and-purpose-q01", "text": "What identifies and describes the use of a Boeing 727, 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 Boeing 727, 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 Boeing 727 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 Boeing 727.", "findings": [ { "id": "procedures-and-skills", "name": "Procedures, skills and required tools", "description": "What an agent needs before it can act on a Boeing 727 at all.", "questions": [ { "id": "procedures-and-skills-q01", "text": "What identifies and describes handling a Boeing 727, 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 Boeing 727, 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 Boeing 727 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 Boeing 727 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 Boeing 727 and how confident it is.", "questions": [ { "id": "claim-provenance-q01", "text": "What identifies and describes a claim about a Boeing 727, 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 Boeing 727, 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 Boeing 727 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 Boeing 727 is retired without being erased.", "questions": [ { "id": "validity-and-supersession-q01", "text": "What identifies and describes the validity of a claim about a Boeing 727, 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 Boeing 727, 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 Boeing 727 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 } } } }