{ "model": { "rank": 6237, "code": "thing-q184870", "model_id": "vr.tr.boeing-b-29-superfortress", "name": "Boeing B-29 Superfortress", "purpose": "Enable an AI agent to identify Boeing B-29 Superfortress configurations, assess evidence about their condition and capabilities, and determine which inspection, conservation or operational actions require further authority.", "family": "Thing Registry", "category": "Physical world and living systems", "status": "research-draft", "kind": "thing", "plane": "PHY", "domain": "PHY.MAT", "industry": "", "version": "", "url": "/models/thing/q184870/", "tier": 2, "score": 61, "payload": { "layer": "wikidata", "aliases": [ "XB-44 Superfortress", "Boeing P2B Superfortress", "XB-29 Superfortress", "FIFI", "XB-39 Superfortress", "B-29A Superfortress", "B-29B Superfortress" ], "aliasCount": 7, "merged": 7, "knownIn": 61, "facets": null, "markers": [], "lexicalClass": "", "senseRank": null, "alsoRegisteredAs": null, "source": { "dataset": "wikidata", "item": "Q184870", "url": "https://www.wikidata.org/wiki/Q184870", "license": "CC0 1.0" } }, "research": { "vercy": "1.0-draft", "publication": { "status": "research-draft", "adjudicationStatus": "unreviewed", "publishableCanonical": false, "generatedAt": "2026-09-09T22:58:12Z", "providers": [ "Codex" ], "breadth": "recalled by Codex without web access - no source was read", "missingProviders": [], "pass": 2, "cost": { "grok": { "seconds": 22.8, "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: 01a08863-7271-7c31-8aea-20a6f4a7ceca\n--------\nuser\nDescribe what is already known about one registered thing. Answer as JSON only, no prose around it.\n\nThing: Boeing B-29 Superfortress\nSense to describe: (none recorded)\nDomain code: PHY.OBJ\nAlso known as: (none)\n\n\nContext for this batch of 188 things:\n# Batch ", "usd": 0, "recall": true }, "codex": { "seconds": 78.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: 01a08863-726c-7a71-8355-f894c6a77259\n--------\nuser\nYou are drafting a Vercy meta-model for one registered thing. Answer as JSON only, no prose around it.\n\nThing: Boeing B-29 Superfortress\nRegistry id: vr.tr.boeing-b-29-superfortress\nPlane / domain: PHY / PHY.OBJ\nRegistry definition: (none recorded)\nNames folde" } } }, "metaModel": { "id": "THING-Q184870", "registryId": "vr.tr.boeing-b-29-superfortress", "name": "Boeing B-29 Superfortress", "version": "0.1.0-research.1", "entryKind": "thing", "family": "Thing Registry", "domain": [ "PHY.OBJ" ], "status": "research-draft" }, "canonicalUrl": "https://ver.cy/models/thing/q184870/", "model": { "registry_id": "vr.tr.boeing-b-29-superfortress", "name": "Boeing B-29 Superfortress", "purpose": "Enable an AI agent to identify Boeing B-29 Superfortress configurations, assess evidence about their condition and capabilities, and determine which inspection, conservation or operational actions require further authority.", "definition": "The Boeing B-29 Superfortress is an American four-engine, piston-powered heavy bomber type developed by Boeing for long-range strategic bombing, featuring pressurized crew compartments and entering combat service in 1944.", "scope_statement": "This model owns the B-29 aircraft type represented by vr.tr.boeing-b-29-superfortress in PHY / PHY.OBJ, including configuration-dependent recognition and assessment requirements; individual airframes instantiate it without becoming separate definitions of the type.", "in_scope": [ "B-29 type identity, production variants and documented modifications", "Airframe geometry, crew accommodation and installed aircraft systems", "Configuration-dependent propulsion, loading and performance evidence", "Historical mission-equipment installation and removal", "Condition assessment, restoration compatibility and evidence of permitted use" ], "out_of_scope": [ "Separate aircraft types, including the B-17, B-24, B-50 and Tu-4", "Individual airframe biographies and ownership records except as linked evidence", "Engine, propeller and avionics designs beyond their B-29 installation interfaces", "Bomb and ammunition design, targeting and weapon-employment procedures", "Military campaigns, aircrew organisations and strategic bombing doctrine" ], "distinguishing_features": [ "Require a documented B-29 designation and production identity; the name Superfortress or a similar silhouette alone does not establish membership.", "Check the documented four-Wright-R-3350 installation against the observed aircraft, recording replacement engines separately. [USAF museum technical notes](https://www.nationalmuseum.af.mil/Visit/Museum-Exhibits/Fact-Sheets/Display/Article/196252/boeing-b-29-superfortress/)", "Check for the B-29's pressurized crew-compartment architecture and central control of remote gun turrets, while allowing documented equipment removals. [USAF museum development history](https://www.nationalmuseum.af.mil/Visit/Museum-Exhibits/Fact-Sheets/Display/Article/196652/development-of-the-boeing-b-29/)", "Do not reject an otherwise authenticated B-29 because most turrets are absent: Silverplate aircraft retained only the tail turret. [USAF museum configuration account](https://www.nationalmuseum.af.mil/Visit/Museum-Exhibits/Fact-Sheets/Display/Article/196252/boeing-b-29-superfortress/)" ], "characteristics": [ { "name": "Production identity", "kind": "relation", "unit_or_values": "Designation, production block, manufacturing plant and linked serial evidence", "why_it_matters": "Determines which drawings, manuals and configuration claims apply." }, { "name": "Configuration baseline", "kind": "category", "unit_or_values": "Documented production configuration; modified service configuration; restoration configuration; unresolved", "why_it_matters": "Prevents features from different periods being combined into an imaginary standard aircraft." }, { "name": "Installed propulsion", "kind": "relation", "unit_or_values": "Engine and propeller models by installed position, with modification evidence", "why_it_matters": "Connects the airframe to compatible maintenance requirements and performance evidence." }, { "name": "Airframe dimensions", "kind": "measurement", "unit_or_values": "Wingspan, length and height in m; retain source units and configuration", "why_it_matters": "Supports recognition, hangar clearance and transport assessment." }, { "name": "Mass and balance", "kind": "measurement", "unit_or_values": "Mass in kg; centre of gravity in the applicable manual's datum system; weighing date", "why_it_matters": "Equipment removal and restoration can change whether published loading data apply." }, { "name": "Performance evidence", "kind": "measurement", "unit_or_values": "Speed in kt with airspeed basis; altitude in ft; range in nmi; loading and atmospheric conditions", "why_it_matters": "Separates descriptive historical figures from limits applicable to a particular configuration." }, { "name": "Crew-pressure system condition", "kind": "state", "unit_or_values": "Not assessed; inspected; tested to identified procedure; defective; disabled", "why_it_matters": "A preserved pressure compartment does not establish functioning pressurization." }, { "name": "Mission-equipment installation", "kind": "category", "unit_or_values": "Equipment inventory by location, date, modification and functional status", "why_it_matters": "Distinguishes historical capability, present installation and display representation." }, { "name": "Permitted activity", "kind": "relation", "unit_or_values": "Activity linked to dated approval, issuing authority, limitations and configuration", "why_it_matters": "Establishes whether display, access, movement, ground operation or flight is supported by applicable evidence." } ], "affordances": [ "Classify a candidate aircraft or record as B-29, another type or unresolved using production and configuration evidence.", "Compare an observed B-29 with a dated configuration baseline and flag unexplained differences.", "Identify which B-29 manuals and modification records must be consulted for an installed system.", "Assess whether dimensions, loading and performance claims apply to the configuration under review.", "Prepare a conservation or inspection review that separates original, replacement, missing and nonfunctional components.", "Determine whether evidence supports a proposed access, movement or operating activity and refer unresolved decisions to the responsible authority." ] }, "sources": [], "structure": { "bundles": [ { "id": "b-29-identity-and-lineage", "name": "B-29 identity and lineage", "description": "Establish membership in the registered aircraft type and the configuration being described.", "rationale": "Shared names, similar aircraft and altered museum examples can obscure B-29 identity.", "layers": [ { "id": "production-identification", "name": "Production identification", "description": "Connect designation and manufacturing evidence to the type.", "findings": [ { "id": "designation-before-appearance", "name": "Designation before appearance", "description": "Require production evidence before treating resemblance or painted markings as definitive identification.", "questions": [ { "text": "Which designation, serial and manufacturing records establish this aircraft as a B-29?", "kind": "provenance", "id": "designation-before-appearance-q01" }, { "text": "What evidence distinguishes it from a B-50, Tu-4 or replica?", "kind": "boundary", "id": "designation-before-appearance-q02" } ] } ] }, { "id": "configuration-lineage", "name": "Configuration lineage", "description": "Separate production identity from subsequent changes.", "findings": [ { "id": "dated-configuration-baseline", "name": "Dated configuration baseline", "description": "Assess each example against an explicit date and documented modification state.", "questions": [ { "text": "Which production variant and modification state define the comparison baseline?", "kind": "definition", "id": "dated-configuration-baseline-q01" }, { "text": "Which records distinguish service modifications from later restoration substitutions?", "kind": "provenance", "id": "dated-configuration-baseline-q02" } ] } ] } ] }, { "id": "airframe-and-crew-environment", "name": "Airframe and crew environment", "description": "Represent the B-29's physical envelope, internal arrangement and crew-pressure provisions.", "rationale": "Exterior recognition alone cannot establish internal completeness, access suitability or pressure-system condition.", "layers": [ { "id": "geometry-and-structural-evidence", "name": "Geometry and structural evidence", "description": "Relate measured geometry and structural condition to the applicable B-29 baseline.", "findings": [ { "id": "configuration-specific-envelope", "name": "Configuration-specific envelope", "description": "Record dimensions and structural observations with the aircraft's assembly and modification state.", "questions": [ { "text": "What are the measured span, length and height, and which components were installed during measurement?", "kind": "measurement", "id": "configuration-specific-envelope-q01" }, { "text": "Which B-29 drawings or inspection records explain structural repairs and departures from the baseline?", "kind": "provenance", "id": "configuration-specific-envelope-q02" } ] } ] }, { "id": "crew-compartments-and-pressure", "name": "Crew compartments and pressure", "description": "Assess crew-space arrangement separately from pressure-system functionality.", "findings": [ { "id": "pressure-system-evidence", "name": "Pressure-system evidence", "description": "Record compartment boundaries, connecting passages, closures and installed pressure equipment against applicable documentation.", "questions": [ { "text": "Which crew compartments and passages are present, accessible and represented as pressurized in this configuration?", "kind": "definition", "id": "pressure-system-evidence-q01" }, { "text": "What inspection or test evidence supports the recorded pressure-system condition?", "kind": "provenance", "id": "pressure-system-evidence-q02" }, { "text": "What access restrictions follow from the condition of passages, closures and escape provisions?", "kind": "action", "id": "pressure-system-evidence-q03" } ] } ] } ] }, { "id": "propulsion-and-aircraft-systems", "name": "Propulsion and aircraft systems", "description": "Track installed powerplants, supporting systems and controls as a particular B-29 configuration.", "rationale": "An engine-family label cannot establish installation compatibility, serviceability or control-system completeness.", "layers": [ { "id": "powerplant-installation", "name": "Powerplant installation", "description": "Identify each engine-propeller installation and its maintenance evidence.", "findings": [ { "id": "installed-powerplant-applicability", "name": "Installed powerplant applicability", "description": "Record engine, propeller and associated installation details by position rather than assuming all four match.", "questions": [ { "text": "Which engine and propeller models occupy each position, and which records establish their installation compatibility?", "kind": "provenance", "id": "installed-powerplant-applicability-q01" }, { "text": "What unresolved cooling, lubrication, fuel-system or fire-damage findings affect each installation?", "kind": "definition", "id": "installed-powerplant-applicability-q02" }, { "text": "Which applicable maintenance documents specify consumables and inspection requirements?", "kind": "action", "id": "installed-powerplant-applicability-q03" } ] } ] }, { "id": "controls-and-system-dependencies", "name": "Controls and system dependencies", "description": "Connect crew controls to installed equipment and evidence of function.", "findings": [ { "id": "control-presence-versus-function", "name": "Control presence versus function", "description": "Distinguish complete controls from display fittings, disconnected equipment and systems awaiting verification.", "questions": [ { "text": "Which pilot and flight-engineer controls remain connected to functioning equipment?", "kind": "definition", "id": "control-presence-versus-function-q01" }, { "text": "Which power dependencies and documented interlocks govern landing gear, flaps and other movable equipment?", "kind": "provenance", "id": "control-presence-versus-function-q02" }, { "text": "What documented isolation and authorization are required before a proposed ground demonstration?", "kind": "action", "id": "control-presence-versus-function-q03" } ] } ] } ] }, { "id": "mission-configuration-and-capacity", "name": "Mission configuration and capacity", "description": "Represent historical equipment fit and configuration-dependent loading claims.", "rationale": "B-29 mission configurations differ, and historical armament or capacity summaries do not describe every airframe.", "layers": [ { "id": "mission-equipment-fit", "name": "Mission equipment fit", "description": "Inventory mission installations without reproducing weapon operation.", "findings": [ { "id": "equipment-fit-requires-evidence", "name": "Equipment fit requires evidence", "description": "Record turret, sighting, communications and payload-space equipment by dated configuration, including removals and inert representations.", "questions": [ { "text": "Which records establish the mission-equipment fit at the date being represented?", "kind": "provenance", "id": "equipment-fit-requires-evidence-q01" }, { "text": "Which installed components are original equipment, replacements, inert exhibits or absent?", "kind": "definition", "id": "equipment-fit-requires-evidence-q02" }, { "text": "Which payload facts belong to linked weapon models rather than this aircraft model?", "kind": "boundary", "id": "equipment-fit-requires-evidence-q03" } ] } ] }, { "id": "loading-and-performance-context", "name": "Loading and performance context", "description": "Attach operating conditions and applicability to capacity claims.", "findings": [ { "id": "performance-is-conditional", "name": "Performance is conditional", "description": "Keep range, speed, altitude and payload figures tied to their source configuration and assumptions.", "questions": [ { "text": "What loading, fuel, altitude and engine-rating assumptions accompany each quoted performance figure?", "kind": "measurement", "id": "performance-is-conditional-q01" }, { "text": "Does the source describe maximum range, mission radius or another distance measure?", "kind": "definition", "id": "performance-is-conditional-q02" }, { "text": "Which current weighing and modification records establish whether those figures apply to the assessed airframe?", "kind": "provenance", "id": "performance-is-conditional-q03" } ] } ] } ] }, { "id": "preservation-and-permitted-use", "name": "Preservation and permitted use", "description": "Assess surviving B-29 material and the evidence required for proposed activities.", "rationale": "Historical authenticity, mechanical condition and authority to operate are separate judgments.", "layers": [ { "id": "restoration-and-material-condition", "name": "Restoration and material condition", "description": "Evaluate completeness, deterioration and replacement work against a stated preservation objective.", "findings": [ { "id": "restoration-objective-and-evidence", "name": "Restoration objective and evidence", "description": "Record whether work aims at static interpretation, historical configuration or an approved operating configuration.", "questions": [ { "text": "Which B-29 configuration and date does the restoration intend to represent?", "kind": "definition", "id": "restoration-objective-and-evidence-q01" }, { "text": "What inspection evidence documents corrosion, cracking, deterioration or repairs in the assessed airframe?", "kind": "provenance", "id": "restoration-objective-and-evidence-q02" }, { "text": "Which proposed replacements require compatibility review or documentation of lost historical material?", "kind": "action", "id": "restoration-objective-and-evidence-q03" } ] } ] }, { "id": "activity-specific-authority", "name": "Activity-specific authority", "description": "Link each proposed activity to applicable documents and accountable decisions.", "findings": [ { "id": "documented-activity-status", "name": "Documented activity status", "description": "Record authorization separately for public access, movement, ground operation and flight; do not derive it from appearance or historical capability.", "questions": [ { "text": "Which issuing authority and dated documents govern the proposed activity for this airframe and jurisdiction?", "kind": "provenance", "id": "documented-activity-status-q01" }, { "text": "Which configuration limitations, inspections and crew qualifications remain prerequisites?", "kind": "action", "id": "documented-activity-status-q02" }, { "text": "Who is responsible for resolving missing evidence and authorizing the activity?", "kind": "action", "id": "documented-activity-status-q03" } ] } ] } ] }, { "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 entry describes an aircraft type, not an individual airframe or the broader heavy-bomber category.", "Dimensions, crew, armament and performance vary by variant and modification; verify the specific configuration before applying numerical specifications.", "Historical military acceptance requirements and present-day airworthiness rules for surviving aircraft require separate verification; no specific standard is asserted here." ], "questions": [ { "id": "evidence-confidence-notes-q01", "text": "Which of these check these first hold for the sense of Boeing B-29 Superfortress 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": [ "B-29: original production bomber variant", "B-29A: production variant with revised wing construction", "B-29B: bomber variant with most defensive guns removed", "KB-29: aerial-refueling conversions", "TB-29: training conversions", "WB-29: weather-reconnaissance conversions" ], "questions": [ { "id": "evidence-kinds-q01", "text": "Which of these kinds and varieties hold for the sense of Boeing B-29 Superfortress 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": "United States military aircraft designation", "value_or_pattern": "B-29", "note": "Identifies the aircraft type; suffixes and prefixes distinguish variants and modified roles, while military serial numbers identify individual airframes." }, { "scheme": "Boeing model number", "value_or_pattern": "Model 345", "note": "Boeing's internal model designation associated with the B-29." } ], "questions": [ { "id": "evidence-identifiers-q01", "text": "Which of these identifiers and schemes hold for the sense of Boeing B-29 Superfortress this model covers, and on what evidence?", "kind": "provenance" } ] }, { "id": "evidence-real-world-use", "name": "Real-world use", "description": "Recalled without web access and unsourced; every item is a lead to verify.", "evidence": [ "Long-range conventional bombing of Japan during the Second World War.", "Delivery of the atomic bombs used against Hiroshima and Nagasaki by specially modified aircraft.", "Aerial mining of Japanese waters during the Second World War.", "Conventional bombing during the Korean War.", "Postwar use of converted aircraft for aerial refueling, weather reconnaissance, training and research support." ], "questions": [ { "id": "evidence-real-world-use-q01", "text": "Which of these real-world use hold for the sense of Boeing B-29 Superfortress this model covers, and on what evidence?", "kind": "provenance" } ] }, { "id": "evidence-measurements", "name": "Typical measurements", "description": "Recalled without web access and unsourced; every item is a lead to verify.", "evidence": [ { "quantity": "Wingspan", "typical_range": "Approximately 43.1 for the original B-29", "unit": "m" }, { "quantity": "Overall length", "typical_range": "Approximately 30.2", "unit": "m" }, { "quantity": "Number of engines", "typical_range": "4", "unit": "engines" }, { "quantity": "Standard bomber crew complement", "typical_range": "11", "unit": "people" } ], "questions": [ { "id": "evidence-measurements-q01", "text": "Which of these typical measurements hold for the sense of Boeing B-29 Superfortress 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": [ "Wright R-3350 engine overheating and engine fires, especially significant during early service.", "Loss of cabin pressurization or oxygen-system failure during high-altitude operations.", "Asymmetric thrust and reduced performance following an engine failure.", "Fuel fires and structural damage caused by combat damage or accidents.", "For surviving airframes, fatigue, corrosion and aging components requiring inspection and specialized maintenance." ], "questions": [ { "id": "evidence-failure-modes-and-hazards-q01", "text": "Which of these failure modes and hazards hold for the sense of Boeing B-29 Superfortress this model covers, and on what evidence?", "kind": "provenance" } ] }, { "id": "evidence-regional-variation", "name": "Regional variation", "description": "Recalled without web access and unsourced; every item is a lead to verify.", "evidence": [ "The British Royal Air Force operated B-29s under the service name Washington B.1.", "The Soviet Tupolev Tu-4 was developed by reverse engineering interned B-29s; it is a separate aircraft type rather than a regional B-29 variant." ], "questions": [ { "id": "evidence-regional-variation-q01", "text": "Which of these regional variation hold for the sense of Boeing B-29 Superfortress 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 B-17 Flying Fortress", "difference": "An earlier Boeing heavy bomber type with an unpressurized crew environment and different airframe, engines and defensive arrangements." }, { "name": "Boeing B-50 Superfortress", "difference": "A separately designated development of the B-29 with Pratt & Whitney R-4360 engines and substantial structural and aerodynamic changes." }, { "name": "Tupolev Tu-4", "difference": "A Soviet-manufactured derivative with Soviet engines, equipment and production specifications, despite its close external resemblance." }, { "name": "Enola Gay", "difference": "An individual modified B-29 airframe, whereas Boeing B-29 Superfortress names the aircraft type." } ], "questions": [ { "id": "evidence-neighbours-q01", "text": "Which of these neighbouring kinds and how to tell them apart hold for the sense of Boeing B-29 Superfortress this model covers, and on what evidence?", "kind": "provenance" } ] } ] } ] } ] }, "openQuestions": [ "Which authoritative designation records establish the treatment of prototypes and converted B-29 derivatives within this registry entry?", "Which production-block manuals and modification records establish exact differences in geometry, crew arrangements, propulsion and turret installations?", "Which primary maintenance sources substantiate recurrent B-29 failure modes, inspection intervals, consumable specifications and installed safety interlocks?", "Which documented configurations and test conditions support commonly quoted B-29 mass, payload, range and speed figures?", "For any surviving airframe being assessed, which current authority-issued documents and restoration records establish its permitted activities and configuration limitations?" ], "statistics": { "bundles": 6, "layers": 11, "findings": 18, "questions": 35 } }, "draft": { "generator": "vr.draft.v3", "status": "draft-generated", "researched": false, "archetype": "chemical substance or material", "method": "Written from the archetype playbook - what this kind of thing needs beyond identity and provenance - and from the structure that recurred across 6,333 models already researched by two engines. Applied to this entry by rule. No source was read for this thing and no claim here is researched. This entry carries no facets of its own, so they were inferred from its domain - a guess about a whole domain applied to one thing.", "facetsInferred": true, "nextPass": "A researcher replaces this draft with a sourced specification. Treat every sentence below as a proposal to argue with.", "purpose": "Give an agent a durable, checkable way to recognise a Boeing B-29 Superfortress, record what state it is in, and decide what may be done with it.", "whatItIs": "Enable an AI agent to identify Boeing B-29 Superfortress configurations, assess evidence about their condition and capabilities, and determine which inspection, conservation or operational actions require further authority.", "characteristics": { "substance": "material", "origin": "natural", "agency": "inert", "mobility": "varies" }, "whatYouCanDoWithIt": [ "observed and measured", "consumed or used up" ], "distinguishingFeatures": [ "Names folded into this entry, which a task may need to split apart again: XB-44 Superfortress, Boeing P2B Superfortress, XB-29 Superfortress, FIFI, XB-39 Superfortress, B-29A Superfortress, B-29B Superfortress.", "7 finer distinctions are held as aliases rather than separate entries, because telling them apart needs a task that asks for it.", "Described in 61 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 B-29 Superfortress, and on what evidence are they told apart?" ], "whatItIsMadeOf": "matter you can touch", "physicalCharacter": [ "Mobility varies between examples.", "Does nothing on its own; everything it does, something else did to it.", "These come from the domain this entry sits in rather than from the entry itself, so treat them as a first guess about the whole domain applied to one thing." ], "whatCanBeDoneWithIt": [ "observe it, measure it, record its state", "use it up, and then need more of it" ], "howItIsRecognised": [ "Not recognisable by sight in any reliable way. Appearance varies with grade, form and additives; identification is by label, by documentation, or by assay." ], "relatedModels": [ { "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": [ "XB-44 Superfortress", "Boeing P2B Superfortress", "XB-29 Superfortress", "FIFI", "XB-39 Superfortress", "B-29A Superfortress", "B-29B Superfortress" ] } ], "standing": "Described in 61 Wikipedia languages, which measures how widely it is written about rather than how important or how common it is. 7 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 B-29 Superfortress from another, and a Boeing B-29 Superfortress 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 B-29 Superfortress, 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 B-29 Superfortress, 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 B-29 Superfortress 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 B-29 Superfortress, 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 B-29 Superfortress, 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 B-29 Superfortress 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 B-29 Superfortress 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 B-29 Superfortress, 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 B-29 Superfortress, 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 B-29 Superfortress 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 B-29 Superfortress from the things most often confused with it.", "questions": [ { "id": "distinguishing-features-q01", "text": "What identifies and describes what distinguishes a Boeing B-29 Superfortress, 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 B-29 Superfortress, 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 B-29 Superfortress 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 B-29 Superfortress 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 B-29 Superfortress, 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 B-29 Superfortress, 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 B-29 Superfortress 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 B-29 Superfortress is built from and which parts are replaceable.", "questions": [ { "id": "parts-and-materials-q01", "text": "What identifies and describes the composition of a Boeing B-29 Superfortress, 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 B-29 Superfortress, 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 B-29 Superfortress 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 B-29 Superfortress is judged and by whom.", "questions": [ { "id": "condition-assessment-q01", "text": "What identifies and describes the condition of a Boeing B-29 Superfortress, 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 B-29 Superfortress, 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 B-29 Superfortress 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 B-29 Superfortress 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 B-29 Superfortress is, and what that position is measured against.", "questions": [ { "id": "position-and-frame-q01", "text": "What identifies and describes the location of a Boeing B-29 Superfortress, 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 B-29 Superfortress, 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 B-29 Superfortress 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 B-29 Superfortress 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 B-29 Superfortress, 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 B-29 Superfortress, 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 B-29 Superfortress 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 B-29 Superfortress 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 B-29 Superfortress between them.", "questions": [ { "id": "stages-and-transitions-q01", "text": "What identifies and describes the lifecycle of a Boeing B-29 Superfortress, 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 B-29 Superfortress, 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 B-29 Superfortress 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 B-29 Superfortress, how often and by whom.", "findings": [ { "id": "observation-record", "name": "Observation record", "description": "How an observation of a Boeing B-29 Superfortress 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 B-29 Superfortress, 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 B-29 Superfortress, 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 B-29 Superfortress 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 B-29 Superfortress 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 B-29 Superfortress is for, and what it is used for anyway.", "findings": [ { "id": "function-and-purpose", "name": "Function, purpose and misuse", "description": "The function a Boeing B-29 Superfortress performs and the uses that fall outside it.", "questions": [ { "id": "function-and-purpose-q01", "text": "What identifies and describes the use of a Boeing B-29 Superfortress, 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 B-29 Superfortress, 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 B-29 Superfortress 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 B-29 Superfortress.", "findings": [ { "id": "procedures-and-skills", "name": "Procedures, skills and required tools", "description": "What an agent needs before it can act on a Boeing B-29 Superfortress at all.", "questions": [ { "id": "procedures-and-skills-q01", "text": "What identifies and describes handling a Boeing B-29 Superfortress, 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 B-29 Superfortress, 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 B-29 Superfortress is known, and what must it refuse?", "kind": "action", "answer_data": [ "permitted actions", "preconditions", "refusals", "escalation" ] } ] } ] }, { "id": "supply-and-consumption", "name": "Supply and consumption", "description": "Quantities, rates and what running out means.", "findings": [ { "id": "consumption-and-stock", "name": "Consumption, stock and replenishment", "description": "How much of a Boeing B-29 Superfortress there is and how fast it goes.", "questions": [ { "id": "consumption-and-stock-q01", "text": "What identifies and describes the supply of a Boeing B-29 Superfortress, and in what units or vocabulary?", "kind": "definition", "answer_data": [ "identifiers", "types and classes", "values with units", "explicit unknowns" ] }, { "id": "consumption-and-stock-q02", "text": "Who or what asserted this about the supply of a Boeing B-29 Superfortress, by which method, and when was it true?", "kind": "provenance", "answer_data": [ "authority", "method", "evidence", "event time", "knowledge time" ] }, { "id": "consumption-and-stock-q03", "text": "What may an agent decide or do once the supply of a Boeing B-29 Superfortress is known, and what must it refuse?", "kind": "action", "answer_data": [ "permitted actions", "preconditions", "refusals", "escalation" ] } ] } ] } ] }, { "id": "composition-and-identity", "name": "Composition, grade and chemical identity", "description": "What Boeing B-29 Superfortress is made of and how pure the thing in hand is.", "rationale": "Grade decides what a substance may be used for, so a model that records only the name cannot support any decision about use.", "layers": [ { "id": "chemical-identity", "name": "Chemical identity", "description": "Formula, structure and the registry numbers that name it unambiguously.", "findings": [ { "id": "identity-record", "name": "Identity and registry numbers", "description": "What identifies this substance across suppliers and regulators.", "questions": [ { "id": "identity-record-q01", "text": "What formula, structure and registry identifiers name Boeing B-29 Superfortress unambiguously?", "kind": "definition" }, { "id": "identity-record-q02", "text": "Which related substances share a name in common use but not an identifier?", "kind": "boundary" } ] } ] }, { "id": "grade-and-impurities", "name": "Grade, purity and impurities", "description": "The specification a batch meets and what else is in it.", "findings": [ { "id": "specification", "name": "Specification and assay", "description": "How purity is stated and measured, and which impurities matter.", "questions": [ { "id": "specification-q01", "text": "What grades of Boeing B-29 Superfortress exist, how is purity assayed, and which impurities are limited?", "kind": "measurement" }, { "id": "specification-q02", "text": "Which use requires which grade, and what happens when a lower grade is substituted?", "kind": "action" } ] } ] } ] }, { "id": "properties-and-behaviour", "name": "Properties and behaviour", "description": "How Boeing B-29 Superfortress behaves under conditions an agent can measure or change.", "rationale": "Physical constants are the part of a substance model that transfers between contexts, and each needs its unit and its conditions.", "layers": [ { "id": "physical-constants", "name": "Physical constants", "description": "Values that hold for the pure substance, with their conditions.", "findings": [ { "id": "constants-record", "name": "Constants and conditions", "description": "The quantities worth recording and the state they apply in.", "questions": [ { "id": "constants-record-q01", "text": "What are the defining physical constants of Boeing B-29 Superfortress, in what units and under what conditions?", "kind": "measurement" }, { "id": "constants-record-q02", "text": "Which of these values change with grade or form rather than being fixed?", "kind": "boundary" } ] } ] }, { "id": "stability-and-reactivity", "name": "Stability and reactivity", "description": "What it reacts with, degrades into, and how it is stored.", "findings": [ { "id": "incompatibilities", "name": "Incompatibilities and degradation", "description": "What must not meet it, and what it becomes over time.", "questions": [ { "id": "incompatibilities-q01", "text": "What is Boeing B-29 Superfortress incompatible with, and what does it degrade into under storage?", "kind": "definition" }, { "id": "incompatibilities-q02", "text": "What storage and handling does that require, and who is competent to do it?", "kind": "action" } ] } ] } ] }, { "id": "hazard-and-regulation", "name": "Hazard classification and regulation", "description": "How Boeing B-29 Superfortress can harm, and what the law says about holding and moving it.", "rationale": "A substance model without its hazard class and its regulatory identity is unusable in exactly the situations that matter.", "layers": [ { "id": "hazard-class", "name": "Hazard classification", "description": "Classified hazards, exposure limits and protective measures.", "findings": [ { "id": "classified-hazards", "name": "Classified hazards and limits", "description": "The classification, the scheme it belongs to, and the limits set.", "questions": [ { "id": "classified-hazards-q01", "text": "How is Boeing B-29 Superfortress classified for hazard, under which scheme, and what exposure limits apply?", "kind": "definition" }, { "id": "classified-hazards-q02", "text": "What protection does handling require, and what must an agent refuse to do without it?", "kind": "action" } ] } ] }, { "id": "regulatory-identity", "name": "Regulatory identity and control", "description": "Registration, restriction and transport rules by jurisdiction.", "findings": [ { "id": "controls", "name": "Controls and jurisdiction", "description": "Where it is restricted and what the restriction attaches to.", "questions": [ { "id": "controls-q01", "text": "Which registrations, restrictions or transport rules cover Boeing B-29 Superfortress, and where?", "kind": "provenance" }, { "id": "controls-q02", "text": "Does the control attach to the substance, its concentration, or its intended use?", "kind": "boundary" } ] } ] } ] }, { "id": "provenance-and-evidence", "name": "Provenance, evidence and time", "description": "Where every claim about a Boeing B-29 Superfortress 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 B-29 Superfortress and how confident it is.", "questions": [ { "id": "claim-provenance-q01", "text": "What identifies and describes a claim about a Boeing B-29 Superfortress, 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 B-29 Superfortress, 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 B-29 Superfortress 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 B-29 Superfortress is retired without being erased.", "questions": [ { "id": "validity-and-supersession-q01", "text": "What identifies and describes the validity of a claim about a Boeing B-29 Superfortress, 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 B-29 Superfortress, 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 B-29 Superfortress is known, and what must it refuse?", "kind": "action", "answer_data": [ "permitted actions", "preconditions", "refusals", "escalation" ] } ] } ] } ] } ] }, "statistics": { "bundles": 9, "layers": 20, "findings": 22, "questions": 60 } } } }