{ "model": { "rank": 3190, "code": "thing-q6387", "model_id": "vr.tr.boeing-737", "name": "Boeing 737", "purpose": "Enable an AI agent to recognise the Boeing 737 aircraft family, distinguish its variants and assess what evidence is needed to judge an individual aircraft's configuration, condition and permitted use.", "family": "Thing Registry", "category": "Physical world and living systems", "status": "research-draft", "kind": "thing", "plane": "PHY", "domain": "PHY.OBJ", "industry": "", "version": "", "url": "/models/thing/q6387/", "tier": 2, "score": 89, "payload": { "layer": "wikidata", "aliases": [ "Boeing 737 military aircraft", "Boeing 737 Original", "Boeing Business Jet 737", "Boeing 737 Next Generation", "Boeing 737 MAX", "Boeing 737-100", "Boeing 737-200", "Boeing 737 Classic", "Boeing E-7 Wedgetail", "Boeing 737-800", "Boeing 737-600", "Boeing 737-700", "Boeing 737-900", "Boeing 737 MAX 7", "Boeing 737 MAX 8", "Boeing 737 MAX 9", "Boeing 737-200 Advanced", "Boeing 737-219", "Boeing 737-300", "Boeing 737-400", "Boeing 737-500", "E-7T Peace Eagle", "Peace Eye", "Wedgetail AEW1", "E-7A Wedgetail", "Boeing 737-86N", "Boeing 737-8EH", "Boeing 737-8F2", "Boeing 737-8AS", "Boeing 737-84P", "Boeing 737-700C", "Boeing 737-752", "Boeing 737-7H4", "Boeing 737 MAX 8-200", "Boeing 737-8MAX 200" ], "aliasCount": 35, "merged": 35, "knownIn": 89, "facets": null, "markers": [], "lexicalClass": "", "senseRank": null, "alsoRegisteredAs": null, "source": { "dataset": "wikidata", "item": "Q6387", "url": "https://www.wikidata.org/wiki/Q6387", "license": "CC0 1.0" } }, "research": { "vercy": "1.0-draft", "publication": { "status": "research-draft", "adjudicationStatus": "unreviewed", "publishableCanonical": false, "generatedAt": "2026-09-07T14:05:35Z", "providers": [ "Codex" ], "breadth": "recalled by Codex without web access - no source was read", "missingProviders": [], "pass": 2, "cost": { "grok": { "seconds": 44.3, "error": "Reading additional input from stdin...\nOpenAI Codex v0.153.3\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: 01a07c2f-1da8-73d3-aacd-42b296511947\n--------\nuser\nDescribe what is already known about one registered thing. Answer as JSON only, no prose around it.\n\nThing: Boeing 737\nSense to describe: (none recorded)\nDomain code: PHY.OBJ\nAlso known as: (none)\n\n\nContext for this batch of 546 things:\n# Batch 003: 1001 regis", "usd": 0, "recall": true }, "codex": { "seconds": 78.4, "error": "Reading additional input from stdin...\nOpenAI Codex v0.153.3\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: 01a07c2f-1dae-7e80-acf0-cb546e6e079e\n--------\nuser\nYou are drafting a Vercy meta-model for one registered thing. Answer as JSON only, no prose around it.\n\nThing: Boeing 737\nRegistry id: vr.tr.boeing-737\nPlane / domain: PHY / PHY.OBJ\nRegistry definition: (none recorded)\nNames folded into this entry: (none)\n\n\nCo" } } }, "metaModel": { "id": "THING-Q6387", "registryId": "vr.tr.boeing-737", "name": "Boeing 737", "version": "0.1.0-research.1", "entryKind": "thing", "family": "Thing Registry", "domain": [ "PHY.OBJ" ], "status": "research-draft" }, "canonicalUrl": "https://ver.cy/models/thing/q6387/", "model": { "registry_id": "vr.tr.boeing-737", "name": "Boeing 737", "purpose": "Enable an AI agent to recognise the Boeing 737 aircraft family, distinguish its variants and assess what evidence is needed to judge an individual aircraft's configuration, condition and permitted use.", "definition": "The Boeing 737 is a family of twin-engine, single-aisle, short- to medium-range jet transport aircraft developed by Boeing, encompassing successive generations and multiple passenger, cargo and specialised variants rather than a single aircraft model or individual airframe.", "scope_statement": "This model owns the Boeing 737 as a registered aircraft family, including variant distinctions and the evidence required to assess member aircraft; it does not treat the family name as a single specification or an individual airframe.", "in_scope": [ "Family membership and distinctions among Original, Classic, Next-Generation and MAX aircraft", "Variant-specific airframe, engine, aerodynamic and flight-control configurations", "Passenger, cargo and special-purpose configurations where documented as members or derivatives of the family", "Variant-dependent capacity, dimensions, performance limits and airport compatibility", "Evidence of individual-aircraft configuration, maintenance condition and applicable operating restrictions", "Boundaries between family-level knowledge and aircraft-specific operational decisions" ], "out_of_scope": [ "Airline organisation, route economics and commercial scheduling", "Generic principles of aerodynamics and turbine-engine design", "Airport infrastructure management beyond compatibility with the aircraft", "Crew qualification models and executable piloting procedures", "Standalone models of engines, avionics and other installed components", "Other Boeing aircraft families and the corporate history of Boeing" ], "distinguishing_features": [ "Establish membership through an authoritative aircraft model designation; airline branding, a flight number or a photograph alone is insufficient.", "Distinguish the family label Boeing 737 from a designation such as 737-800 or 737-8; those designations must not be treated as interchangeable.", "Use the combined configuration of the fuselage, wing, empennage, landing gear and two underwing engines to support recognition, then verify against records rather than confusing it with another twin-engine narrow-body family.", "Check engine installation, wing and wingtip configuration against the identified variant; a winglet shape or nacelle appearance alone does not establish the generation.", "Separate an aircraft's original production model from subsequent cabin changes, cargo conversions and other approved modifications." ], "characteristics": [ { "name": "Certified model and family generation", "kind": "category", "unit_or_values": "Exact model designation; Original, Classic, Next-Generation or MAX where supported", "why_it_matters": "Prevents specifications and operating assumptions from being transferred between materially different 737 variants." }, { "name": "Airframe identity", "kind": "relation", "unit_or_values": "Manufacturer serial number, registration and supporting aircraft records", "why_it_matters": "Connects a family member to its actual history without treating a changeable registration as permanent identity." }, { "name": "Installed propulsion configuration", "kind": "relation", "unit_or_values": "Engine manufacturer, model, approved rating and installation applicability", "why_it_matters": "Engine compatibility, limitations and maintenance requirements depend on the particular 737 model and installation." }, { "name": "External dimensions and ground clearance", "kind": "measurement", "unit_or_values": "Length, wingspan, height and relevant clearances in m, with variant and modification applicability", "why_it_matters": "Supports gate, hangar and ground-equipment compatibility checks." }, { "name": "Approved mass limits", "kind": "measurement", "unit_or_values": "Maximum takeoff, landing and zero-fuel mass in kg for the applicable approved configuration", "why_it_matters": "A family-wide or marketing value cannot establish the limits of a particular aircraft." }, { "name": "Cabin and cargo configuration", "kind": "category", "unit_or_values": "Approved passenger, freighter or other configuration; seat layout, exits and cargo provisions", "why_it_matters": "Usable capacity and loading constraints follow the installed and approved arrangement." }, { "name": "Fuel and mission capability", "kind": "measurement", "unit_or_values": "Usable fuel in kg or L and range in nmi or km, with payload, reserves and operating assumptions", "why_it_matters": "Range claims are meaningful only when their configuration and mission assumptions are explicit." }, { "name": "Flight-control and avionics configuration", "kind": "relation", "unit_or_values": "Applicable hardware, software, installed functions and modification records", "why_it_matters": "Generation-specific control functions and updates affect which limitations and evidence apply." }, { "name": "Structural exposure", "kind": "measurement", "unit_or_values": "Flight hours, flight cycles and calendar age, with record date", "why_it_matters": "Different maintenance and structural obligations may depend on different measures of accumulated exposure." }, { "name": "Documented operating eligibility", "kind": "state", "unit_or_values": "Supported, restricted, unsupported or unknown for a specified operation, jurisdiction and date", "why_it_matters": "Eligibility requires current aircraft-specific evidence and cannot be inferred from the Boeing 737 name." } ], "affordances": [ "Resolve a Boeing 737 reference to the correct family, generation, variant or individual-aircraft level.", "Compare documented variant capabilities while preserving configuration and measurement assumptions.", "Identify the aircraft records needed to evaluate a proposed passenger, cargo or airport use.", "Flag mismatches between claimed variant, installed equipment and approved configuration.", "Trace maintenance findings and operating restrictions to the aircraft and configurations they actually cover.", "Prepare an evidence checklist for an authorised aviation professional to determine operating eligibility." ] }, "sources": [], "structure": { "bundles": [ { "id": "family-and-variant-identity", "name": "Family and variant identity", "description": "Resolve what a Boeing 737 reference denotes before attaching specifications or restrictions.", "rationale": "The registry names a family whose generations, production models and modified aircraft must remain distinguishable.", "layers": [ { "id": "designation-and-generation", "name": "Designation and generation", "description": "Connect common names to authoritative model designations and generation groupings.", "findings": [ { "id": "variant-designation-evidence", "name": "Variant designation evidence", "description": "Record the evidence that distinguishes similarly written designations, including 737-800 and 737-8.", "questions": [ { "text": "What exact aircraft model designation does the authoritative record give, and how does it map to the common generation name?", "kind": "definition", "id": "variant-designation-evidence-q01" }, { "text": "Which manufacturer or certification record supports that mapping rather than an airline label or abbreviated listing?", "kind": "provenance", "id": "variant-designation-evidence-q02" } ] } ] }, { "id": "airframe-and-derivative-boundaries", "name": "Airframe and derivative boundaries", "description": "Distinguish family membership, individual identity and changes made after production.", "findings": [ { "id": "production-and-conversion-lineage", "name": "Production and conversion lineage", "description": "Represent original model identity separately from freighter conversion, business-jet branding or special-purpose derivative status.", "questions": [ { "text": "Is the subject a production variant, a converted individual aircraft or a derivative that should relate to a neighbouring model?", "kind": "boundary", "id": "production-and-conversion-lineage-q01" }, { "text": "Which serial-number and modification records establish its original designation and subsequent approved changes?", "kind": "provenance", "id": "production-and-conversion-lineage-q02" } ] } ] } ] }, { "id": "airframe-and-propulsion-configuration", "name": "Airframe and propulsion configuration", "description": "Capture the physical differences that determine recognition, compatibility and variant applicability.", "rationale": "A 737's engines, wings and ground geometry cannot be inferred reliably from the family name.", "layers": [ { "id": "wing-and-ground-geometry", "name": "Wing and ground geometry", "description": "Record variant-specific external geometry and changes caused by approved modifications.", "findings": [ { "id": "geometry-and-wingtip-applicability", "name": "Geometry and wingtip applicability", "description": "Associate dimensions and recognition cues with the actual wing, wingtip and landing-gear configuration.", "questions": [ { "text": "What are the documented length, span, height and relevant ground clearances for this variant and wingtip configuration?", "kind": "measurement", "id": "geometry-and-wingtip-applicability-q01" }, { "text": "Which visible features support identification, and which require records because they can change through modification?", "kind": "boundary", "id": "geometry-and-wingtip-applicability-q02" } ] } ] }, { "id": "engine-installation", "name": "Engine installation", "description": "Connect propulsion characteristics to the approved installation on the identified 737 model.", "findings": [ { "id": "engine-model-and-installation-match", "name": "Engine model and installation match", "description": "Keep installed engine model, rating and nacelle configuration distinct from family-wide propulsion descriptions.", "questions": [ { "text": "Which engine models and ratings are approved for the identified aircraft model, and what is installed on the subject aircraft?", "kind": "provenance", "id": "engine-model-and-installation-match-q01" }, { "text": "Which installation-specific clearance, servicing and operating constraints must be checked before accepting a proposed use?", "kind": "action", "id": "engine-model-and-installation-match-q02" } ] } ] } ] }, { "id": "capacity-and-mission-envelope", "name": "Capacity and mission envelope", "description": "Describe what a configured 737 can accommodate and the conditions governing mission suitability.", "rationale": "Seat counts, cargo capability and range vary across the family and do not independently establish operational suitability.", "layers": [ { "id": "cabin-cargo-and-exits", "name": "Cabin, cargo and exits", "description": "Tie usable capacity to approved interior, loading and evacuation arrangements.", "findings": [ { "id": "approved-payload-arrangement", "name": "Approved payload arrangement", "description": "Distinguish advertised capacity from the limits of the installed cabin or cargo conversion.", "questions": [ { "text": "What passenger seating, exit arrangement or cargo-loading configuration is approved for the subject aircraft?", "kind": "provenance", "id": "approved-payload-arrangement-q01" }, { "text": "What seat count, compartment capacity, floor-loading and payload limits apply to that arrangement, with units where relevant?", "kind": "measurement", "id": "approved-payload-arrangement-q02" } ] } ] }, { "id": "performance-and-airport-fit", "name": "Performance and airport fit", "description": "Bind capability claims to mass, environment, aircraft configuration and airport conditions.", "findings": [ { "id": "conditional-mission-capability", "name": "Conditional mission capability", "description": "Record the assumptions needed to interpret range and runway suitability without converting brochure figures into dispatch authority.", "questions": [ { "text": "Under what payload, fuel, reserve and atmospheric assumptions were the stated range and performance figures established?", "kind": "measurement", "id": "conditional-mission-capability-q01" }, { "text": "Which approved performance data and airport constraints must an authorised planner check for the proposed mission?", "kind": "action", "id": "conditional-mission-capability-q02" } ] } ] } ] }, { "id": "controls-and-operational-configuration", "name": "Controls and operational configuration", "description": "Represent generation-specific control functions, cockpit equipment and documented system states.", "rationale": "Shared family naming does not imply identical control logic, software or operating limitations.", "layers": [ { "id": "flight-controls-and-augmentation", "name": "Flight controls and augmentation", "description": "Identify installed flight-control and augmentation functions and their configuration dependencies.", "findings": [ { "id": "control-function-applicability", "name": "Control function applicability", "description": "Associate functions such as MCAS only with configurations for which their presence and approved implementation are documented.", "questions": [ { "text": "Which flight-control, trim, autopilot and augmentation functions apply to this precise 737 variant and configuration?", "kind": "definition", "id": "control-function-applicability-q01" }, { "text": "Which approved records establish the applicable hardware, software and required updates for those functions?", "kind": "provenance", "id": "control-function-applicability-q02" } ] } ] }, { "id": "equipment-state-and-use-constraints", "name": "Equipment state and use constraints", "description": "Connect reported system states and equipment availability to documented limitations.", "findings": [ { "id": "configuration-dependent-operating-status", "name": "Configuration-dependent operating status", "description": "Record relevant electrical, hydraulic, pneumatic and avionics availability without assuming that a powered aircraft is fit to operate.", "questions": [ { "text": "What evidence establishes the current availability of required systems and the status of recorded defects?", "kind": "provenance", "id": "configuration-dependent-operating-status-q01" }, { "text": "Which applicable approved limitations and minimum-equipment provisions must authorised personnel consult before the proposed operation?", "kind": "action", "id": "configuration-dependent-operating-status-q02" } ] } ] } ] }, { "id": "continued-airworthiness-and-evidence", "name": "Continued airworthiness and evidence", "description": "Connect structural history, maintenance and regulatory applicability to a particular aircraft at a particular time.", "rationale": "The 737 family spans different designs, service histories and jurisdictions, so condition and eligibility require specific evidence.", "layers": [ { "id": "structural-life-and-maintenance", "name": "Structural life and maintenance", "description": "Record accumulated exposure and the maintenance evidence relevant to the aircraft's variant and modifications.", "findings": [ { "id": "exposure-inspection-and-repair-history", "name": "Exposure, inspection and repair history", "description": "Relate hours, cycles, corrosion observations and repairs to applicable inspection requirements, including pressurised structure and wing-to-body attachment areas.", "questions": [ { "text": "What verified flight hours, flight cycles and calendar exposure apply, and when were those totals last reconciled?", "kind": "measurement", "id": "exposure-inspection-and-repair-history-q01" }, { "text": "Which inspections, damage findings and approved repairs affect the subject aircraft under its applicable maintenance programme?", "kind": "provenance", "id": "exposure-inspection-and-repair-history-q02" } ] } ] }, { "id": "certification-and-current-restrictions", "name": "Certification and current restrictions", "description": "Track the certification basis and current requirements applicable to the model, aircraft and intended jurisdiction.", "findings": [ { "id": "dated-airworthiness-applicability", "name": "Dated airworthiness applicability", "description": "Separate type certification, aircraft-level conformity and compliance with applicable directives or operational restrictions.", "questions": [ { "text": "Which issuing authorities, type-certificate records, airworthiness directives and approved modifications govern this aircraft and intended operation as of the assessment date?", "kind": "provenance", "id": "dated-airworthiness-applicability-q01" }, { "text": "What missing compliance or release evidence requires the agent to leave operating eligibility unresolved and refer the decision to authorised personnel?", "kind": "action", "id": "dated-airworthiness-applicability-q02" } ] } ] } ] }, { "id": "evidence-and-external-alignment", "name": "Evidence and external alignment", "description": "What the world already says about this thing, gathered so the model can be checked against it.", "rationale": "A model that cannot be lined up against existing standards, identifiers and practice cannot be adopted by anyone who already uses them.", "layers": [ { "id": "reported-evidence", "name": "Reported evidence", "description": "Findings from the breadth pass, kept separate from the structural claims.", "findings": [ { "id": "evidence-confidence-notes", "name": "Check these first", "description": "Recalled without web access and unsourced; every item is a lead to verify.", "evidence": [ "This is recalled knowledge, without source consultation; dimensional and seating ranges are approximate family-level summaries.", "Generation membership does not establish a variant's current certification, production or service status.", "Exact certification bases, maintenance requirements and mandatory safety modifications must be checked for the specific model and airframe configuration." ], "questions": [ { "id": "evidence-confidence-notes-q01", "text": "Which of these check these first hold for the sense of Boeing 737 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": [ "737 Original: 737-100 and 737-200", "737 Classic: 737-300, 737-400 and 737-500", "737 Next Generation: 737-600, 737-700, 737-800 and 737-900 series", "737 MAX: MAX 7, MAX 8, MAX 9 and MAX 10" ], "questions": [ { "id": "evidence-kinds-q01", "text": "Which of these kinds and varieties hold for the sense of Boeing 737 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": "737 followed by a variant designation, such as 737-800 or 737-8", "note": "737-800 denotes a Next Generation model; 737-8 denotes a MAX model." }, { "scheme": "ICAO aircraft type designator", "value_or_pattern": "B738 for the 737-800; B38M for the 737 MAX 8", "note": "Operational designators distinguish variants; neither identifies an individual airframe." }, { "scheme": "Manufacturer serial number", "value_or_pattern": "Boeing manufacturer serial number (MSN)", "note": "Identifies an individual airframe, separately from its changeable national registration." } ], "questions": [ { "id": "evidence-identifiers-q01", "text": "Which of these identifiers and schemes hold for the sense of Boeing 737 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": [ "FAA 14 CFR Part 25 - airworthiness standards for transport-category airplanes; the applicable certification basis depends on the model and approved changes.", "FAA 14 CFR Part 39 - airworthiness directives requiring corrective action for identified unsafe conditions.", "FAA 14 CFR Part 121 - operating requirements applicable to many US airline operations using the aircraft.", "ICAO Annex 8 - international standards for airworthiness of aircraft, implemented through national authorities.", "ICAO Annex 16 - aircraft noise and emissions standards, with applicability depending on the aircraft and engine configuration." ], "questions": [ { "id": "evidence-standards-and-regulation-q01", "text": "Which of these standards and regulation hold for the sense of Boeing 737 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 passenger services, especially short- and medium-haul routes.", "Charter and leisure passenger flights.", "Freight transport using dedicated or converted freighter variants.", "Business and government transport through Boeing Business Jet derivatives.", "Specialised military missions using substantially modified derivatives." ], "questions": [ { "id": "evidence-real-world-use-q01", "text": "Which of these real-world use hold for the sense of Boeing 737 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 across family variants", "typical_range": "Approximately 28.6-43.8", "unit": "m" }, { "quantity": "Wingspan across generations and wingtip configurations", "typical_range": "Approximately 28.4-35.9", "unit": "m" }, { "quantity": "Typical passenger seating", "typical_range": "Approximately 100-200, depending on variant and cabin layout", "unit": "passengers" }, { "quantity": "Cruise speed", "typical_range": "Approximately 0.74-0.79", "unit": "Mach" } ], "questions": [ { "id": "evidence-measurements-q01", "text": "Which of these typical measurements hold for the sense of Boeing 737 this model covers, and on what evidence?", "kind": "provenance" } ] }, { "id": "evidence-failure-modes-and-hazards", "name": "Failure modes and hazards", "description": "Recalled without web access and unsourced; every item is a lead to verify.", "evidence": [ "Engine failure, bird ingestion or engine fire can reduce available thrust and require abnormal or emergency procedures.", "Structural fatigue and corrosion, including in the pressurised fuselage, require inspections and repairs tied to aircraft age and operating cycles.", "Flight-control or stabiliser-trim malfunctions can create hazardous control forces or aircraft attitudes.", "On the MAX, erroneous angle-of-attack input and the original MCAS implementation contributed to two fatal accidents; subsequent corrective requirements are configuration-specific.", "Icing, runway excursions and loss of control are operational hazards whose likelihood depends on conditions, aircraft configuration and crew response." ], "questions": [ { "id": "evidence-failure-modes-and-hazards-q01", "text": "Which of these failure modes and hazards hold for the sense of Boeing 737 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": [ "Certification validation, mandatory modifications and operating approvals depend on the responsible aviation authority.", "Cabin layouts and passenger capacities vary by airline and approved configuration.", "Airport noise restrictions and local operating rules can particularly constrain older variants." ], "questions": [ { "id": "evidence-regional-variation-q01", "text": "Which of these regional variation hold for the sense of Boeing 737 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-800", "difference": "A specific Next Generation model within the broader 737 family." }, { "name": "Boeing 737 MAX", "difference": "One generation within the 737 family, distinguished by its engines and associated airframe and system changes." }, { "name": "Airbus A320 family", "difference": "A separately designed competing single-aisle aircraft family manufactured by Airbus." }, { "name": "Boeing P-8 Poseidon", "difference": "A military maritime-patrol aircraft derived from the 737 platform, with specialised structure, systems and mission equipment." }, { "name": "An individual Boeing 737 airframe", "difference": "A physical aircraft with its own serial number, registration and maintenance history; this entry describes the product family." } ], "questions": [ { "id": "evidence-neighbours-q01", "text": "Which of these neighbouring kinds and how to tell them apart hold for the sense of Boeing 737 this model covers, and on what evidence?", "kind": "provenance" } ] } ] } ] } ] }, "openQuestions": [ "Does an existing Vercy world model already cover the Boeing 737 family, requiring this registry entry to link to it rather than produce another publication?", "Which authoritative designation crosswalk should govern generation labels and the inclusion or exclusion of business-jet, military and other special-purpose derivatives?", "Which primary documents establish dimensions, capacity and performance for each included variant, and which configuration assumptions must accompany those values?", "Which documented failure modes and inspection obligations belong at family level, and which apply only to particular models, serial-number ranges or modifications?", "Which jurisdictions and assessment dates should the model support for regulatory restrictions, directive compliance and operating-eligibility evidence?" ], "statistics": { "bundles": 6, "layers": 11, "findings": 19, "questions": 29 } }, "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 737, record what state it is in, and decide what may be done with it.", "whatItIs": "Enable an AI agent to recognise the Boeing 737 aircraft family, distinguish its variants and assess what evidence is needed to judge an individual aircraft's configuration, condition and permitted use.", "characteristics": { "substance": "material", "origin": "manufactured", "agency": "inert", "mobility": "varies" }, "whatYouCanDoWithIt": [ "observed and measured" ], "distinguishingFeatures": [ "Names folded into this entry, which a task may need to split apart again: Boeing 737 military aircraft, Boeing 737 Original, Boeing Business Jet 737, Boeing 737 Next Generation, Boeing 737 MAX, Boeing 737-100, Boeing 737-200, Boeing 737 Classic, Boeing E-7 Wedgetail, Boeing 737-800, Boeing 737-600, Boeing 737-700.", "35 finer distinctions are held as aliases rather than separate entries, because telling them apart needs a task that asks for it.", "Described in 89 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 737, 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 737 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 737 military aircraft", "Boeing 737 Original", "Boeing Business Jet 737", "Boeing 737 Next Generation", "Boeing 737 MAX", "Boeing 737-100", "Boeing 737-200", "Boeing 737 Classic", "Boeing E-7 Wedgetail", "Boeing 737-800", "Boeing 737-600", "Boeing 737-700" ] } ], "standing": "Described in 89 Wikipedia languages, which measures how widely it is written about rather than how important or how common it is. 35 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 737 from another, and a Boeing 737 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 737, 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 737, 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 737 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 737, 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 737, 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 737 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 737 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 737, 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 737, 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 737 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 737 from the things most often confused with it.", "questions": [ { "id": "distinguishing-features-q01", "text": "What identifies and describes what distinguishes a Boeing 737, 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 737, 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 737 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 737 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 737, 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 737, 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 737 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 737 is built from and which parts are replaceable.", "questions": [ { "id": "parts-and-materials-q01", "text": "What identifies and describes the composition of a Boeing 737, 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 737, 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 737 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 737 is judged and by whom.", "questions": [ { "id": "condition-assessment-q01", "text": "What identifies and describes the condition of a Boeing 737, 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 737, 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 737 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 737 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 737 is, and what that position is measured against.", "questions": [ { "id": "position-and-frame-q01", "text": "What identifies and describes the location of a Boeing 737, 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 737, 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 737 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 737 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 737, 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 737, 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 737 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 737 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 737 between them.", "questions": [ { "id": "stages-and-transitions-q01", "text": "What identifies and describes the lifecycle of a Boeing 737, 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 737, 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 737 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 737, how often and by whom.", "findings": [ { "id": "observation-record", "name": "Observation record", "description": "How an observation of a Boeing 737 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 737, 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 737, 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 737 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 737 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 737 is for, and what it is used for anyway.", "findings": [ { "id": "function-and-purpose", "name": "Function, purpose and misuse", "description": "The function a Boeing 737 performs and the uses that fall outside it.", "questions": [ { "id": "function-and-purpose-q01", "text": "What identifies and describes the use of a Boeing 737, 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 737, 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 737 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 737.", "findings": [ { "id": "procedures-and-skills", "name": "Procedures, skills and required tools", "description": "What an agent needs before it can act on a Boeing 737 at all.", "questions": [ { "id": "procedures-and-skills-q01", "text": "What identifies and describes handling a Boeing 737, 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 737, 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 737 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 737 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 737 and how confident it is.", "questions": [ { "id": "claim-provenance-q01", "text": "What identifies and describes a claim about a Boeing 737, 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 737, 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 737 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 737 is retired without being erased.", "questions": [ { "id": "validity-and-supersession-q01", "text": "What identifies and describes the validity of a claim about a Boeing 737, 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 737, 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 737 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 } } } }