{ "vercy": "1.0-draft", "publication": { "status": "research-draft", "adjudicationStatus": "unreviewed", "publishableCanonical": false, "generatedAt": "2026-09-12T11:01:14Z", "providers": [ "Codex" ], "breadth": "recalled by Codex without web access - no source was read", "missingProviders": [], "pass": 2, "cost": { "grok": { "seconds": 17.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: 01a09545-eecd-79c1-b1f2-b08c10c91b80\n--------\nuser\nDescribe what is already known about one registered thing. Answer as JSON only, no prose around it.\n\nThing: Lockheed YP-24\nSense to describe: (none recorded)\nDomain code: PHY.OBJ\nAlso known as: (none)\n\n\nContext for this batch of 1001 things:\n# Batch 044: 1001 ", "usd": 0.0, "recall": true }, "codex": { "seconds": 92.0, "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: 01a09545-eed9-7db0-96b4-5a876496c55a\n--------\nuser\nYou are drafting a Vercy meta-model for one registered thing. Answer as JSON only, no prose around it.\n\nThing: Lockheed YP-24\nRegistry id: vr.tr.lockheed-yp-24\nPlane / domain: PHY / PHY.OBJ\nRegistry definition: (none recorded)\nNames folded into this entry: (no" } }, "enrichment": { "pass": 3, "engine": "claude", "producedAt": "2026-10-06T12:00:00Z", "ingestedAt": "2026-10-06T08:52:22+00:00", "fields": [ "agent_conduct", "ethics", "failure_modes_and_hazards", "owners", "visual_identification" ] }, "gate": { "passed": true, "version": "1.0", "at": "2026-10-07T10:10:31+00:00", "evidence": [ "completeness 1.00", "sense: Wikidata description", "2 live sources", "review by codex: pass" ] } }, "metaModel": { "id": "THING-Q4450165", "registryId": "vr.tr.lockheed-yp-24", "name": "Lockheed YP-24", "version": "0.1.0-research.1", "entryKind": "thing", "family": "Thing Registry", "domain": [ "PHY.OBJ" ], "status": "research-draft" }, "canonicalUrl": "https://ver.cy/models/thing/q4450165/", "model": { "registry_id": "vr.tr.lockheed-yp-24", "name": "Lockheed YP-24", "purpose": "Enable an agent to identify the Lockheed YP-24 aircraft design, distinguish its documented prototype configuration from proposals and related aircraft, and judge what historical or technical conclusions the evidence permits.", "definition": "The Lockheed YP-24 was an American experimental two-seat, single-engine, low-wing fighter aircraft with retractable landing gear, first flown in 1931 and built as a single prototype for evaluation by the United States Army Air Corps.", "scope_statement": "This model owns the aircraft-type identity registered as vr.tr.lockheed-yp-24 in PHY / PHY.OBJ, including configuration, intended role, development relationships and evidence boundaries; individual-airframe events serve as evidence about the design.", "in_scope": [ "YP-24 designation, manufacturer attribution and association with the XP-900 designation", "Airframe configuration and distinguishing relationships to the Lockheed Altair and subsequent pursuit designs", "Propulsion, retractable undercarriage, crew stations and intended military equipment", "Configuration-specific dimensions, performance and evaluation evidence", "Prototype history and the distinction between proposed, ordered, built and demonstrated capabilities" ], "out_of_scope": [ "Independent lifecycle records for individual airframes, surviving components or replicas", "Complete models of the Lockheed Altair and related Consolidated aircraft", "Separate publication of proposed attack derivatives as though they were built YP-24 configurations", "General histories of Lockheed, Detroit Aircraft Corporation or the Army Air Corps", "Generic aircraft operation, maintenance procedures and present-day flight authorization" ], "distinguishing_features": [ "Check documentary identification against the museum's Detroit-Lockheed YP-24 attribution rather than accepting an isolated P-24 label. [National Museum of the USAF](https://www.nationalmuseum.af.mil/Upcoming/Photos/igphoto/2000543708/)", "Require the combination of a two-seat pursuit role, low-wing monoplane layout and retractable undercarriage; no single feature establishes YP-24 identity.", "Distinguish an Altair-derived pursuit configuration from an Altair transport by checking crew accommodation, fuselage configuration and military design documentation.", "Separate XP-900/YP-24 designation continuity from later Consolidated development: resemblance or shared ancestry alone does not establish the same aircraft type.", "Require evidence of an actual YP-24 installation before assigning equipment described for a proposed attack derivative to this entry." ], "characteristics": [ { "name": "Designation and documentary identity", "kind": "relation", "unit_or_values": "Registry identity linked to dated manufacturer and military designations", "why_it_matters": "Prevents alternate names from becoming duplicate models or unrelated P-24 designations from being merged." }, { "name": "Configuration evidence state", "kind": "state", "unit_or_values": "proposed | ordered | built | installed | ground-tested | flight-tested | uncertain", "why_it_matters": "A prototype programme can have specifications that were never embodied or demonstrated." }, { "name": "Crew arrangement", "kind": "category", "unit_or_values": "Seat count, station arrangement, enclosure and documented duties", "why_it_matters": "The two-seat pursuit arrangement affects identification, visibility, equipment and loading." }, { "name": "Airframe construction", "kind": "category", "unit_or_values": "Material and structural method recorded separately for wing, fuselage and tail", "why_it_matters": "Construction details help distinguish the YP-24 from its antecedents and subsequent developments." }, { "name": "Powerplant installation", "kind": "relation", "unit_or_values": "Engine designation, cooling arrangement, propeller configuration and installation date", "why_it_matters": "Performance comparisons require the correct engine variant and installed configuration." }, { "name": "Engine power rating", "kind": "measurement", "unit_or_values": "kW and source-stated hp, with rating conditions", "why_it_matters": "Nominal power cannot be compared reliably without the rating basis." }, { "name": "Geometry and loading", "kind": "measurement", "unit_or_values": "Span and length in m; wing area in m²; mass in kg, each with configuration and loading basis", "why_it_matters": "Supports recognition and performance interpretation without conflating empty and loaded conditions." }, { "name": "Undercarriage configuration", "kind": "category", "unit_or_values": "Retraction arrangement, actuation method, position indication and documented emergency provisions", "why_it_matters": "The retractable gear is both an identifying feature and a system requiring specific historical investigation." }, { "name": "Performance evidence", "kind": "measurement", "unit_or_values": "Speed in km/h, altitude and range in m or km, climb in m/s; measured or estimated status required", "why_it_matters": "Keeps design expectations distinct from demonstrated prototype performance." } ], "affordances": [ "Assess whether a photograph, drawing or catalogue record represents the YP-24 and report the confidence of that attribution.", "Reconcile manufacturer and military designations without creating additional registry entries.", "Compare the YP-24 with its transport antecedent and pursuit successors using documented configuration differences.", "Classify performance and equipment claims as proposed, installed or demonstrated.", "Identify which archival records are needed before accepting a reconstruction, technical comparison or historical claim." ], "agent_conduct": { "may": [ "Identify photographs or drawings as this single experimental fighter.", "Describe its innovations, such as retractable gear, and its loss from historical sources." ], "must_not": [ "Present later production derivatives as the same aircraft.", "Invent details where the record of a single prototype is thin.", "Assign blame for the prototype's loss to named people without evidence." ], "requires_human": [ "Attributing parts or artefacts to the prototype." ] }, "ethics": { "considerations": [ "Prototype history credits designers and test pilots; misattribution wrongs them.", "Speculation fills gaps that sources do not support." ], "affected_parties": [ "Historians", "Descendants of designers and test pilots" ] }, "owners": { "steward": "Nobody: the only example was lost; archives hold its records.", "master_systems": [] }, "visual_identification": [ "Low-wing monoplane with a two-seat cockpit and retractable main gear.", "Liquid-cooled engine with a pointed nose.", "Early 1930s experimental markings in photographs." ], "failure_modes_and_hazards": [ "Mechanical failure of novel landing gear led to the loss of the prototype.", "Untested combinations of features carried high test-flight risk." ], "what_it_is_for": [ "This aircraft was a single prototype developed for military evaluation as a two-seat pursuit aircraft in the early 1930s.", "It is encountered primarily in aviation histories, archival photographs and studies of aircraft design development.", "Its documented trials support discussion of the prototype configuration, while proposed capabilities require separate historical evidence." ], "standards_and_regulation": [ "The United States Army Air Corps assigned the official designation YP-24 within its pursuit aircraft designation system." ] }, "sources": [ { "id": "wikidata", "title": "Wikidata item Q4450165: Lockheed YP-24", "url": "https://www.wikidata.org/wiki/Q4450165", "url_status": "live", "what_it_supports": "identity and sense of the item", "checked_by": "wikidata-api" }, { "id": "wikipedia-en", "title": "Wikipedia: Lockheed YP-24", "url": "https://en.wikipedia.org/wiki/Lockheed_YP-24", "url_status": "live", "what_it_supports": "general description of the item", "checked_by": "wikidata-api sitelink" } ], "structure": { "bundles": [ { "id": "identity-and-design-boundaries", "name": "Identity and design boundaries", "description": "Establish which design the YP-24 entry denotes and which related names require separate treatment.", "rationale": "Manufacturer naming, military designations and derivative proposals can otherwise produce duplicate or overextended models.", "layers": [ { "id": "designation-continuity", "name": "Designation continuity", "description": "Connect names to the design through dated documentary evidence.", "findings": [ { "id": "xp-900-yp-24-correspondence", "name": "XP-900 and YP-24 correspondence", "description": "Determine the documented relationship between company and military labels without treating a designation change as a new type.", "questions": [ { "text": "Which contemporary records establish whether XP-900 and YP-24 identify the same design and prototype?", "kind": "provenance", "id": "xp-900-yp-24-correspondence-q01" }, { "text": "Which manufacturer attribution and designation spelling should be preferred, and which should remain searchable aliases?", "kind": "definition", "id": "xp-900-yp-24-correspondence-q02" } ] } ] }, { "id": "antecedents-and-derivatives", "name": "Antecedents and derivatives", "description": "Locate the YP-24 within its design lineage without absorbing neighbouring aircraft.", "findings": [ { "id": "related-design-separation", "name": "Related-design separation", "description": "Record inherited features and substantive changes relative to the Altair, proposed attack derivative and subsequent Consolidated designs.", "questions": [ { "text": "Which Altair components or design features were retained, and which changes define the YP-24 pursuit configuration?", "kind": "boundary", "id": "related-design-separation-q01" }, { "text": "Which records distinguish the proposed Y1A-9 and subsequent Consolidated Y1P-25 from the YP-24 rather than treating them as interchangeable names?", "kind": "boundary", "id": "related-design-separation-q02" } ] } ] } ] }, { "id": "airframe-and-crew-configuration", "name": "Airframe and crew configuration", "description": "Describe the physical arrangement needed to recognise and compare the YP-24.", "rationale": "Its configuration must be reconstructed from evidence specific to this design, including changes from the transport antecedent.", "layers": [ { "id": "structure-and-geometry", "name": "Structure and geometry", "description": "Resolve external form, dimensions and construction by major assembly.", "findings": [ { "id": "airframe-identification-baseline", "name": "Airframe identification baseline", "description": "Build a configuration baseline from dimensioned drawings and attributable photographs.", "questions": [ { "text": "What span, length, height and wing area are documented, and do the values describe the built prototype or a proposal?", "kind": "measurement", "id": "airframe-identification-baseline-q01" }, { "text": "What evidence establishes the wing, fuselage and tail construction separately, particularly any wood-versus-metal distinctions?", "kind": "provenance", "id": "airframe-identification-baseline-q02" } ] } ] }, { "id": "crew-stations-and-visibility", "name": "Crew stations and visibility", "description": "Record how the pursuit mission shaped accommodation and observation.", "findings": [ { "id": "two-seat-mission-arrangement", "name": "Two-seat mission arrangement", "description": "Resolve crew positions, duties, enclosure and access without importing arrangements from derivatives.", "questions": [ { "text": "How were the two crew stations arranged, and what duties and controls were assigned to each?", "kind": "definition", "id": "two-seat-mission-arrangement-q01" }, { "text": "Which photographs or drawings establish canopy arrangement, access and visibility restrictions for the YP-24 itself?", "kind": "provenance", "id": "two-seat-mission-arrangement-q02" } ] } ] } ] }, { "id": "propulsion-and-retractable-gear", "name": "Propulsion and retractable gear", "description": "Capture the installations that determine power delivery, ground handling and configuration changes in flight.", "rationale": "Engine-variant confusion and incomplete accounts of the landing gear can distort both identification and interpretation of the programme.", "layers": [ { "id": "engine-and-propeller", "name": "Engine and propeller", "description": "Establish the installed propulsion configuration and its supporting systems.", "findings": [ { "id": "conqueror-installation-evidence", "name": "Conqueror installation evidence", "description": "Resolve the reported Curtiss Conqueror installation through engine and airframe records.", "questions": [ { "text": "Which records confirm the installed Curtiss engine designation and distinguish it from engines specified for related proposals?", "kind": "provenance", "id": "conqueror-installation-evidence-q01" }, { "text": "What power rating, propeller arrangement, cooling provisions and fuel specifications apply to the documented installation?", "kind": "measurement", "id": "conqueror-installation-evidence-q02" } ] } ] }, { "id": "landing-gear-system", "name": "Landing gear system", "description": "Describe retraction, extension and the evidence for abnormal gear states.", "findings": [ { "id": "gear-operation-and-failure-evidence", "name": "Gear operation and failure evidence", "description": "Separate the documented mechanism and failure observations from later explanations.", "questions": [ { "text": "How was the YP-24 undercarriage actuated, locked and indicated, and what emergency extension provisions are documented?", "kind": "definition", "id": "gear-operation-and-failure-evidence-q01" }, { "text": "What contemporary evidence supports accounts linking a landing-gear malfunction to the prototype's loss?", "kind": "provenance", "id": "gear-operation-and-failure-evidence-q02" } ] } ] } ] }, { "id": "pursuit-role-and-performance", "name": "Pursuit role and performance", "description": "Relate intended military use to equipment, loading and demonstrated capability.", "rationale": "The YP-24 must be evaluated as a pursuit prototype without presenting proposed armament or estimated performance as operational achievement.", "layers": [ { "id": "mission-equipment", "name": "Mission equipment", "description": "Distinguish pursuit requirements from equipment actually fitted.", "findings": [ { "id": "armament-and-role-baseline", "name": "Armament and role baseline", "description": "Track the status of each military equipment claim and its effect on the crew and loading configuration.", "questions": [ { "text": "What pursuit tasks were specified, and how was the second crew member intended to contribute?", "kind": "definition", "id": "armament-and-role-baseline-q01" }, { "text": "Which weapons and associated equipment were proposed, installed or tested on the YP-24, and which claims belong only to the attack derivative?", "kind": "boundary", "id": "armament-and-role-baseline-q02" } ] } ] }, { "id": "flight-evaluation", "name": "Flight evaluation", "description": "Tie reported capability to test conditions and evidence quality.", "findings": [ { "id": "measured-versus-predicted-performance", "name": "Measured versus predicted performance", "description": "Retain the distinction between specification figures and flight-test results.", "questions": [ { "text": "Which speed, climb, ceiling and range figures were measured, and at what mass, altitude and engine setting?", "kind": "measurement", "id": "measured-versus-predicted-performance-q01" }, { "text": "Which Army Air Corps evaluation requirements or acceptance criteria are documented, and what evidence shows whether the prototype met them?", "kind": "provenance", "id": "measured-versus-predicted-performance-q02" } ] } ] } ] }, { "id": "programme-record-and-evidence-use", "name": "Programme record and evidence use", "description": "Connect the prototype's history to defensible statements about the aircraft type.", "rationale": "A short experimental programme requires careful separation of airframe events, procurement intentions and conclusions about design capability.", "layers": [ { "id": "prototype-and-procurement-history", "name": "Prototype and procurement history", "description": "Resolve what existed, what was ordered and why development ended.", "findings": [ { "id": "built-versus-planned-aircraft", "name": "Built versus planned aircraft", "description": "Establish the chronology and evidence status of prototype construction, evaluation and follow-on plans.", "questions": [ { "text": "Which serial, delivery and flight records establish the number of completed YP-24 airframes and their chronology?", "kind": "provenance", "id": "built-versus-planned-aircraft-q01" }, { "text": "Which documents distinguish technical setbacks, procurement decisions and corporate financial events in the programme's termination?", "kind": "provenance", "id": "built-versus-planned-aircraft-q02" } ] } ] }, { "id": "attribution-and-permitted-inference", "name": "Attribution and permitted inference", "description": "Define the evidence needed to classify representations and use technical claims responsibly.", "findings": [ { "id": "historical-identification-confidence", "name": "Historical identification confidence", "description": "Require traceable evidence when attributing photographs, drawings, components or reconstructed configurations to the YP-24.", "questions": [ { "text": "What combination of caption provenance, configuration details and date is sufficient to attribute an image or drawing to the YP-24?", "kind": "action", "id": "historical-identification-confidence-q01" }, { "text": "Which comparisons or reconstruction decisions must remain unresolved when configuration drawings, test reports or component provenance are missing?", "kind": "action", "id": "historical-identification-confidence-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 a recall-based description; no sources were consulted.", "Check the precise landing-gear failure sequence and prototype loss date against an authoritative aircraft history.", "This entry describes the aircraft design, not a separate registry entry for its sole physical prototype." ], "questions": [ { "id": "evidence-confidence-notes-q01", "text": "Which of these check these first hold for the sense of Lockheed YP-24 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 Army aircraft designation", "value_or_pattern": "YP-24", "note": "An experimental service-test pursuit designation in the Army's pre-1948 aircraft designation system." } ], "questions": [ { "id": "evidence-identifiers-q01", "text": "Which of these identifiers and schemes hold for the sense of Lockheed YP-24 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": [ "Prototype flight testing and evaluation as a two-seat pursuit aircraft for the United States Army Air Corps.", "Development of a fighter combining an enclosed cockpit, monoplane layout and retractable landing gear." ], "questions": [ { "id": "evidence-real-world-use-q01", "text": "Which of these real-world use hold for the sense of Lockheed YP-24 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": "Crew complement", "typical_range": "2", "unit": "people" }, { "quantity": "Completed aircraft", "typical_range": "1", "unit": "aircraft" } ], "questions": [ { "id": "evidence-measurements-q01", "text": "Which of these typical measurements hold for the sense of Lockheed YP-24 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": [ "The sole prototype was lost following a landing-gear malfunction during testing." ], "questions": [ { "id": "evidence-failure-modes-and-hazards-q01", "text": "Which of these failure modes and hazards hold for the sense of Lockheed YP-24 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": "Lockheed Altair", "difference": "The Altair was a civilian aircraft that contributed to the YP-24's design ancestry; the YP-24 was a military pursuit prototype." }, { "name": "Consolidated Y1P-25", "difference": "The Y1P-25 was a subsequent related fighter development under Consolidated, with its own designation and airframe design." }, { "name": "PZL P.24", "difference": "The PZL P.24 was a Polish single-seat gull-wing fighter with fixed landing gear, unrelated to the American Lockheed YP-24." } ], "questions": [ { "id": "evidence-neighbours-q01", "text": "Which of these neighbouring kinds and how to tell them apart hold for the sense of Lockheed YP-24 this model covers, and on what evidence?", "kind": "provenance" } ] } ] } ] } ] }, "openQuestions": [ "Which primary records settle designation chronology, prototype serial identity and the number of completed airframes?", "What were the exact airframe materials, dimensions, engine variant and loading conditions of the flight-tested configuration?", "Which military equipment was physically installed or tested, rather than specified for a proposed pursuit or attack version?", "What does the contemporary accident record establish about the landing-gear malfunction, crew escape and prototype loss?", "Which performance figures and programme-termination explanations are supported by contemporary records rather than repeated retrospective accounts?" ], "statistics": { "bundles": 6, "layers": 11, "findings": 16, "questions": 26 } }