{ "vercy": "1.0-draft", "publication": { "status": "research-draft", "adjudicationStatus": "unreviewed", "publishableCanonical": false, "generatedAt": "2026-09-12T08:50:59Z", "providers": [ "Codex" ], "breadth": "recalled by Codex without web access - no source was read", "missingProviders": [], "pass": 2, "cost": { "grok": { "seconds": 23.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: 01a094ce-c73c-78e2-9da3-94925245bd61\n--------\nuser\nDescribe what is already known about one registered thing. Answer as JSON only, no prose around it.\n\nThing: Convair R3Y Tradewind\nSense to describe: (none recorded)\nDomain code: PHY.OBJ\nAlso known as: (none)\n\n\nContext for this batch of 1001 things:\n# Batch 043", "usd": 0.0, "recall": true }, "codex": { "seconds": 85.7, "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: 01a094ce-c731-7592-8ad4-375f35253571\n--------\nuser\nYou are drafting a Vercy meta-model for one registered thing. Answer as JSON only, no prose around it.\n\nThing: Convair R3Y Tradewind\nRegistry id: vr.tr.convair-r3y-tradewind\nPlane / domain: PHY / PHY.OBJ\nRegistry definition: (none recorded)\nNames folded into t" } }, "enrichment": { "pass": 3, "engine": "claude", "producedAt": "2026-10-06T12:00:00Z", "ingestedAt": "2026-10-06T08:48:24+00:00", "fields": [ "agent_conduct", "ethics", "owners" ] }, "gate": { "passed": true, "version": "1.0", "at": "2026-10-07T10:10:28+00:00", "evidence": [ "completeness 1.00", "sense: Wikidata description", "2 live sources", "review by codex: pass" ] } }, "metaModel": { "id": "THING-Q195803", "registryId": "vr.tr.convair-r3y-tradewind", "name": "Convair R3Y Tradewind", "version": "0.1.0-research.1", "entryKind": "thing", "family": "Thing Registry", "domain": [ "PHY.OBJ" ], "status": "research-draft" }, "canonicalUrl": "https://ver.cy/models/thing/q195803/", "model": { "registry_id": "vr.tr.convair-r3y-tradewind", "name": "Convair R3Y Tradewind", "purpose": "Enable an agent to identify the Convair R3Y Tradewind, distinguish its configurations, and assess what documented condition and operating limitations permit.", "definition": "The Convair R3Y Tradewind was an American four-engine turboprop military transport flying boat developed by Convair for the United States Navy and operated during the 1950s.", "scope_statement": "This model owns the aircraft-type identity and configuration-dependent assessment of vr.tr.convair-r3y-tradewind within PHY / PHY.OBJ, encompassing R3Y-1 and R3Y-2 while relating individual airframes, predecessor designs, and installed equipment to their separate records.", "in_scope": [ "R3Y type recognition and the distinction between R3Y-1 and R3Y-2 configurations", "Flying-boat hull, water handling, and interfaces with shore support", "Four turboprop installations, contra-rotating propellers, and propulsion condition", "Transport accommodation, cargo access, and configuration-dependent loading", "Documented tanker modifications and their applicability to particular airframes", "Evidence needed to assess historical serviceability and permitted activities" ], "out_of_scope": [ "The XP5Y-1 patrol prototype as an independently described aircraft design", "Individual aircraft biographies, ownership histories, and accident events", "The Allison T40 engine family beyond its installation in the R3Y", "Naval transport squadrons, bases, and logistics campaigns", "General flying-boat operating procedures and pilot training", "Scale models, replicas, and flight-simulator representations" ], "distinguishing_features": [ "Require an R3Y designation or equivalent manufacturer evidence; the Tradewind name alone does not distinguish a transport from its XP5Y predecessor.", "Look for a flying-boat hull and four turboprop installations driving contra-rotating propellers; this combination distinguishes the R3Y from superficially similar piston-powered transports. [NASA propulsion history](https://ntrs.nasa.gov/api/citations/19830002859/downloads/19830002859.pdf)", "Use the opening nose and associated loading arrangement to investigate an R3Y-2 identification; confirm the subtype from an identified photograph or airframe record. [U.S. Navy R3Y-2 photograph](https://commons.wikimedia.org/wiki/File%3AConvair_R3Y-2_Tradewind_in_flight.JPG)", "Treat visible beaching wheels as handling equipment unless documentation establishes an installed landing system; wheels in a photograph do not establish amphibious flight capability.", "Separate transport identity from mission equipment: a tanker depiction requires evidence of the refueling installation and its date, rather than a new aircraft-type identity." ], "characteristics": [ { "name": "Documented subtype", "kind": "category", "unit_or_values": "R3Y-1 | R3Y-2 | unresolved", "why_it_matters": "Determines which nose, loading, and configuration evidence applies." }, { "name": "Airframe applicability", "kind": "relation", "unit_or_values": "Bureau Number and dated configuration record", "why_it_matters": "Prevents modifications or incidents affecting one aircraft from being attributed to the entire type." }, { "name": "Propulsion installation", "kind": "category", "unit_or_values": "Four Allison T40-family turboprop installations; exact engine and propeller versions require documentation", "why_it_matters": "Supports recognition and selects the relevant maintenance and operating evidence." }, { "name": "Installed mission configuration", "kind": "category", "unit_or_values": "Cargo | personnel | casualty evacuation | documented tanker fit | mixed | unresolved", "why_it_matters": "The R3Y-1 was intended for military cargo, personnel transport, and evacuation; actual accommodation must be established separately. [Naval aviation chronology](https://www.history.navy.mil/content/dam/nhhc/research/histories/naval-aviation/pdf/part08.pdf)" }, { "name": "Loading access configuration", "kind": "category", "unit_or_values": "Recorded side access; recorded opening-nose access; dimensions and restrictions unresolved", "why_it_matters": "Controls whether a proposed load can enter the aircraft and which loading arrangements require assessment." }, { "name": "Mass and balance envelope", "kind": "measurement", "unit_or_values": "Mass in kg or lb; center of gravity in source-defined datum units or percent mean aerodynamic chord", "why_it_matters": "Connects payload, fuel, and loading sequence to configuration-specific limits." }, { "name": "Water-operation envelope", "kind": "measurement", "unit_or_values": "Wave height and water depth in m; wind in kn; source-defined operating conditions", "why_it_matters": "Separates waterborne capability from suitability for a particular site and sea condition." }, { "name": "Hull and closure condition", "kind": "state", "unit_or_values": "Inspected serviceable | defects recorded | uninspected | unknown, with inspection date", "why_it_matters": "Hull damage, corrosion, or defective access closures can constrain floating, loading, and flight." }, { "name": "Propulsion control condition", "kind": "state", "unit_or_values": "Documented satisfactory | restricted | defective | unknown", "why_it_matters": "Assessment must cover engines, transmission, propellers, and controls as an installed system." }, { "name": "Applicable technical authority", "kind": "relation", "unit_or_values": "Dated U.S. Navy or manufacturer manual, modification instruction, inspection requirement, or restriction", "why_it_matters": "Establishes the basis for an action rather than inferring permission from historical capability." } ], "affordances": [ "Classify an archival record or photograph as R3Y-1, R3Y-2, or unresolved using designation and configuration evidence.", "Associate loading, performance, and maintenance evidence with the applicable subtype and modification state.", "Screen a proposed cargo arrangement against documented access, mass, balance, and restraint constraints.", "Assess whether a described water or shore-handling setting falls within documented R3Y limitations.", "Identify missing inspections or propulsion evidence that prevent a serviceability conclusion.", "Distinguish a demonstrated mission capability from an installed, serviceable, and authorized configuration." ], "agent_conduct": { "may": [ "Describe the aircraft, its history and specifications from reliable sources.", "Help museums and historians catalogue surviving parts and records." ], "must_not": [ "Present unverified accident or operational details as fact.", "Publish personal information about crews involved in accidents beyond official records.", "Remove or trade parts from wreck sites that may be war graves or protected sites." ], "requires_human": [ "Disturbing or recovering material from an aircraft wreck site." ] }, "ethics": { "considerations": [ "Accidents with this type cost lives; accounts should respect those who died.", "Wreck sites can be protected military property or graves." ], "affected_parties": [ "Families of crews", "Historians", "Museums" ] }, "owners": { "steward": "Nobody now: the type is retired; the naval archives of its operator keep its records.", "master_systems": [] }, "what_it_is_for": [ "This flying boat family was developed for naval transport of personnel and cargo during the 1950s.", "It is encountered today in historical records and aircraft identification work concerning large turboprop flying boats." ], "standards_and_regulation": [ "The pre-1962 naval aircraft designation system, administered by the United States Navy, classified this family under the R3Y designation." ], "visual_identification": [ "A boat-shaped fuselage and high-mounted wing identify its basic flying boat configuration.", "Four wing-mounted turboprop engines with paired counter-rotating propellers provide a distinctive recognition cue.", "The loading configuration of the R3Y-2 has a raised cockpit and an opening bow that distinguish it from the R3Y-1." ], "failure_modes_and_hazards": [ "Propeller or drivetrain failures can compromise propulsion and aircraft control.", "Hull damage or water ingress can threaten flotation and structural integrity.", "Incorrect cargo distribution can compromise stability and handling.", "Historical specifications alone cannot establish the airworthiness of an individual aircraft." ] }, "sources": [ { "id": "wikidata", "title": "Wikidata item Q195803: Convair R3Y Tradewind", "url": "https://www.wikidata.org/wiki/Q195803", "url_status": "live", "what_it_supports": "identity and sense of the item", "checked_by": "wikidata-api" }, { "id": "wikipedia-en", "title": "Wikipedia: Convair R3Y Tradewind", "url": "https://en.wikipedia.org/wiki/Convair_R3Y_Tradewind", "url_status": "live", "what_it_supports": "general description of the item", "checked_by": "wikidata-api sitelink" } ], "structure": { "bundles": [ { "id": "tradewind-identity", "name": "Tradewind identity", "description": "Recognize the R3Y transport type and resolve its internal variants.", "rationale": "Shared lineage and the Tradewind name can cause prototype, production, and individual-aircraft evidence to be combined incorrectly.", "layers": [ { "id": "designation-and-lineage", "name": "Designation and lineage", "description": "Separate registry identity from related Convair designs.", "findings": [ { "id": "r3y-identity-evidence", "name": "R3Y identity evidence", "description": "Require designation evidence before importing characteristics from records labeled only Tradewind.", "questions": [ { "text": "Which manufacturer or Navy record identifies the subject as an R3Y?", "kind": "provenance", "id": "r3y-identity-evidence-q01" }, { "text": "Does the evidence describe an R3Y transport or the related XP5Y-1 prototype?", "kind": "boundary", "id": "r3y-identity-evidence-q02" } ] } ] }, { "id": "subtype-and-modification", "name": "Subtype and modification", "description": "Resolve production subtype separately from subsequent equipment changes.", "findings": [ { "id": "dated-configuration", "name": "Dated configuration", "description": "Use subtype, Bureau Number, and observation date together when assigning loading arrangements or mission equipment.", "questions": [ { "text": "What evidence distinguishes R3Y-1 from R3Y-2 for this subject?", "kind": "definition", "id": "dated-configuration-q01" }, { "text": "Which dated modification record supports the configuration shown or described?", "kind": "provenance", "id": "dated-configuration-q02" } ] } ] } ] }, { "id": "water-and-shore-interface", "name": "Water and shore interface", "description": "Assess the R3Y as a hull-supported aircraft operating between water and shore facilities.", "rationale": "Its transport usefulness depends on water conditions and handling arrangements that runway-aircraft models do not capture.", "layers": [ { "id": "hull-and-afloat-condition", "name": "Hull and afloat condition", "description": "Connect structural and watertight condition to the proposed waterborne activity.", "findings": [ { "id": "hull-integrity", "name": "Hull integrity", "description": "Record inspection evidence for the hull, water-contact structures, and relevant access closures before assessing afloat suitability.", "questions": [ { "text": "What corrosion, impact damage, leakage, or closure defects are documented?", "kind": "measurement", "id": "hull-integrity-q01" }, { "text": "Which R3Y inspection criteria determine whether those defects restrict floating, loading, or flight?", "kind": "action", "id": "hull-integrity-q02" } ] } ] }, { "id": "site-and-handling", "name": "Site and handling", "description": "Evaluate water conditions and the interfaces used to secure or move the aircraft.", "findings": [ { "id": "water-site-compatibility", "name": "Water-site compatibility", "description": "Treat taxiing, takeoff, landing, mooring, and shore transfer as separately evidenced capabilities.", "questions": [ { "text": "What wave, wind, depth, and clearance limits apply to the intended R3Y activity?", "kind": "measurement", "id": "water-site-compatibility-q01" }, { "text": "What documented beaching gear, towing equipment, mooring arrangement, or pier interface does it require?", "kind": "action", "id": "water-site-compatibility-q02" }, { "text": "Does the observed wheeled equipment support ground handling only?", "kind": "boundary", "id": "water-site-compatibility-q03" } ] } ] } ] }, { "id": "t40-propulsion-system", "name": "T40 propulsion system", "description": "Represent the installed turboprop, transmission, and contra-rotating propeller system.", "rationale": "Engine count alone does not capture the R3Y's propulsion architecture or the evidence needed to judge controllability.", "layers": [ { "id": "installed-power-train", "name": "Installed power train", "description": "Identify the equipment and ratings applicable to the aircraft configuration.", "findings": [ { "id": "engine-propeller-applicability", "name": "Engine and propeller applicability", "description": "Keep engine version, transmission configuration, and propeller assembly linked; avoid assigning an unsourced family-wide power rating.", "questions": [ { "text": "Which engine, transmission, and propeller versions are documented for this R3Y configuration?", "kind": "provenance", "id": "engine-propeller-applicability-q01" }, { "text": "What power ratings, rotational limits, and rating durations does the applicable manual specify?", "kind": "measurement", "id": "engine-propeller-applicability-q02" } ] } ] }, { "id": "control-and-failure-state", "name": "Control and failure state", "description": "Assess propulsion response and the implications of recorded defects.", "findings": [ { "id": "propulsion-controllability", "name": "Propulsion controllability", "description": "Require evidence for thrust control, propeller governing, and documented protective functions rather than treating engine operation as proof of serviceability.", "questions": [ { "text": "What tests or records establish satisfactory propeller governing, feathering, and any installed reverse-thrust function?", "kind": "provenance", "id": "propulsion-controllability-q01" }, { "text": "Which recorded engine, transmission, or propeller defects restrict the proposed activity?", "kind": "action", "id": "propulsion-controllability-q02" }, { "text": "Which protective functions or interlocks are actually documented for this installation?", "kind": "definition", "id": "propulsion-controllability-q03" } ] } ] } ] }, { "id": "transport-and-loading", "name": "Transport and loading", "description": "Assess what the R3Y can carry through its particular loading interfaces.", "rationale": "Cargo access and load distribution can constrain a mission independently of nominal payload.", "layers": [ { "id": "cargo-access", "name": "Cargo access", "description": "Relate the actual opening and loading equipment to the intended cargo.", "findings": [ { "id": "opening-and-transfer-fit", "name": "Opening and transfer fit", "description": "Evaluate side access or the R3Y-2 nose-loading arrangement using documented geometry and support conditions.", "questions": [ { "text": "What are the clear opening dimensions, floor limits, and loading-equipment capacities for the documented configuration?", "kind": "measurement", "id": "opening-and-transfer-fit-q01" }, { "text": "Can the proposed cargo follow the loading path without exceeding structural or handling limits?", "kind": "action", "id": "opening-and-transfer-fit-q02" } ] } ] }, { "id": "payload-and-accommodation", "name": "Payload and accommodation", "description": "Connect mission fit to load distribution and occupant provisions.", "findings": [ { "id": "configuration-specific-load", "name": "Configuration-specific load", "description": "Keep cargo, seating, evacuation equipment, fuel, and any tanker installation within one dated weight-and-balance assessment.", "questions": [ { "text": "What payload and center-of-gravity limits apply with the recorded fuel and accommodation fit?", "kind": "measurement", "id": "configuration-specific-load-q01" }, { "text": "Which restraint, seating, evacuation, and emergency-exit provisions support the proposed occupants or cargo?", "kind": "action", "id": "configuration-specific-load-q02" }, { "text": "Does a quoted capacity represent a design proposal, trial arrangement, or approved service configuration?", "kind": "provenance", "id": "configuration-specific-load-q03" } ] } ] } ] }, { "id": "mission-capability-and-authority", "name": "Mission capability and authority", "description": "Distinguish documented R3Y mission performance from permission to conduct an activity.", "rationale": "Transport demonstrations, tanker trials, and historical operation provide different kinds of evidence.", "layers": [ { "id": "tanker-configuration", "name": "Tanker configuration", "description": "Investigate refueling capability as a documented modification with its own interfaces and limits.", "findings": [ { "id": "refueling-fit-evidence", "name": "Refueling fit evidence", "description": "Require installation and trial records before assigning receiver compatibility or simultaneous refueling capability.", "questions": [ { "text": "Which R3Y airframes and dates have documented aerial-refueling equipment?", "kind": "provenance", "id": "refueling-fit-evidence-q01" }, { "text": "What receiver interfaces, station limits, transfer rates, and flight conditions were demonstrated or authorized?", "kind": "measurement", "id": "refueling-fit-evidence-q02" }, { "text": "Was the described activity a trial, a proposed capability, or operational service?", "kind": "boundary", "id": "refueling-fit-evidence-q03" } ] } ] }, { "id": "serviceability-and-restrictions", "name": "Serviceability and restrictions", "description": "Determine which dated technical evidence supports an operational-state judgment.", "findings": [ { "id": "action-evidence-threshold", "name": "Action evidence threshold", "description": "Assess handling, maintenance, engine operation, water operation, and flight separately against applicable records and restrictions.", "questions": [ { "text": "Which Navy or manufacturer instructions, inspections, and restrictions govern the activity at the date being assessed?", "kind": "provenance", "id": "action-evidence-threshold-q01" }, { "text": "What unresolved defects or missing maintenance records prevent a supported serviceability conclusion?", "kind": "action", "id": "action-evidence-threshold-q02" }, { "text": "Does the evidence establish historical capability, historical authorization, or a present permission?", "kind": "boundary", "id": "action-evidence-threshold-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 is recalled knowledge, without consulted sources.", "Check variant-specific payload, dimensions, performance and service dates before adding numerical specifications.", "Distinguish operational transport service from refuelling trials and intended assault-transport capabilities." ], "questions": [ { "id": "evidence-confidence-notes-q01", "text": "Which of these check these first hold for the sense of Convair R3Y Tradewind 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": [ "R3Y-1 transport variant", "R3Y-2 assault transport variant with an opening bow for loading" ], "questions": [ { "id": "evidence-kinds-q01", "text": "Which of these kinds and varieties hold for the sense of Convair R3Y Tradewind 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 Navy aircraft designation system before 1962", "value_or_pattern": "R3Y; R3Y-1; R3Y-2", "note": "These designate the aircraft design and its variants, not individual airframes; Tradewind is its name." }, { "scheme": "United States Navy Bureau Number", "value_or_pattern": "Individual airframes have numeric Bureau Numbers (BuNos).", "note": "Specific airframe numbers require verification." } ], "questions": [ { "id": "evidence-identifiers-q01", "text": "Which of these identifiers and schemes hold for the sense of Convair R3Y Tradewind 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": [ "United States Navy overwater transport of personnel and cargo", "Development and demonstration of bow-loading transport operations", "Aerial refuelling trials, including simultaneous refuelling of multiple aircraft" ], "questions": [ { "id": "evidence-real-world-use-q01", "text": "Which of these real-world use hold for the sense of Convair R3Y Tradewind 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": "Turboprop engine count", "typical_range": "4", "unit": "engines" } ], "questions": [ { "id": "evidence-measurements-q01", "text": "Which of these typical measurements hold for the sense of Convair R3Y Tradewind 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": [ "Allison T40 propulsion-system reliability problems, including transmission difficulties, compromised service viability.", "Contra-rotating propeller and coupled-engine drive arrangements introduced mechanical complexity and maintenance demands.", "Saltwater operations exposed the airframe and systems to corrosion.", "Water takeoffs, landings and loading operations depended on suitable sea conditions." ], "questions": [ { "id": "evidence-failure-modes-and-hazards-q01", "text": "Which of these failure modes and hazards hold for the sense of Convair R3Y Tradewind 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": "Convair XP5Y", "difference": "The XP5Y was the preceding patrol flying-boat prototype design; the R3Y was developed as a transport." }, { "name": "Flying boat", "difference": "A flying boat is an aircraft category defined by a hull that supports water operations; the R3Y is one specific design within that category." }, { "name": "Amphibious aircraft", "difference": "An amphibious aircraft can take off and land on both land and water; the R3Y was a flying boat whose beaching equipment did not provide runway operating capability." }, { "name": "Allison T40", "difference": "The T40 is the turboprop engine type powering the aircraft, not the aircraft itself." } ], "questions": [ { "id": "evidence-neighbours-q01", "text": "Which of these neighbouring kinds and how to tell them apart hold for the sense of Convair R3Y Tradewind this model covers, and on what evidence?", "kind": "provenance" } ] } ] } ] } ] }, "openQuestions": [ "Which original R3Y-1 and R3Y-2 manuals establish dimensions, weights, cargo-opening geometry, payload-range conditions, and water-operation limits?", "Which engine and propeller versions, control protections, fuel and lubricant specifications, and maintenance intervals applied to each production or modified configuration?", "What evidence distinguishes intended R3Y-2 shore-loading capability from demonstrated and operationally authorized loading arrangements?", "Which airframes received tanker equipment, and what receiver combinations, simultaneous-use limits, and fuel-transfer performance were actually demonstrated?", "Which primary accident reports and Navy directives establish the propulsion failure mechanisms, resulting restrictions, and final operational withdrawal chronology?" ], "statistics": { "bundles": 6, "layers": 11, "findings": 17, "questions": 32 } }