{ "vercy": "1.0-draft", "publication": { "status": "research-draft", "adjudicationStatus": "unreviewed", "publishableCanonical": false, "generatedAt": "2026-09-12T11:15:54Z", "providers": [ "Codex" ], "breadth": "recalled by Codex without web access - no source was read", "missingProviders": [], "pass": 2, "cost": { "grok": { "seconds": 15.4, "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: 01a09553-b114-7e41-8ff4-e4964a552ede\n--------\nuser\nDescribe what is already known about one registered thing. Answer as JSON only, no prose around it.\n\nThing: Messerschmitt Bf 163\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:", "usd": 0.0, "recall": true }, "codex": { "seconds": 69.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: 01a09553-b10c-74e0-bafb-1bb72250f138\n--------\nuser\nYou are drafting a Vercy meta-model for one registered thing. Answer as JSON only, no prose around it.\n\nThing: Messerschmitt Bf 163\nRegistry id: vr.tr.messerschmitt-bf-163\nPlane / domain: PHY / PHY.OBJ\nRegistry definition: (none recorded)\nNames folded into thi" } }, "enrichment": { "pass": 3, "engine": "claude", "producedAt": "2026-10-06T12:00:00Z", "ingestedAt": "2026-10-06T08:50:46+00:00", "fields": [ "agent_conduct", "ethics", "failure_modes_and_hazards", "owners", "visual_identification" ] }, "gate": { "passed": true, "version": "1.0", "at": "2026-10-07T10:10:27+00:00", "evidence": [ "completeness 1.00", "sense: Wikidata description", "2 live sources", "review by codex: pass" ] } }, "metaModel": { "id": "THING-Q1786265", "registryId": "vr.tr.messerschmitt-bf-163", "name": "Messerschmitt Bf 163", "version": "0.1.0-research.1", "entryKind": "thing", "family": "Thing Registry", "domain": [ "PHY.OBJ" ], "status": "research-draft" }, "canonicalUrl": "https://ver.cy/models/thing/q1786265/", "model": { "registry_id": "vr.tr.messerschmitt-bf-163", "name": "Messerschmitt Bf 163", "purpose": "Enable an agent to identify the Messerschmitt Bf 163 aircraft design, distinguish its proposed capabilities from demonstrated prototype behavior, and assess what its surviving evidence supports.", "definition": "The Messerschmitt Bf 163 was a German experimental, single-engine, propeller-driven short-takeoff-and-landing liaison aircraft developed in the 1930s for a requirement also addressed by the Fieseler Fi 156 Storch.", "scope_statement": "This model owns the aircraft-design identity registered as vr.tr.messerschmitt-bf-163 in PHY / PHY.OBJ, including configuration, intended short-field role, prototype development and evidence-dependent capabilities; individual airframes instantiate this design.", "in_scope": [ "Bf 163 designation and attribution across design and construction organizations", "Configuration evidence for the airframe, propulsion and flight controls", "The reported variable-incidence wing and its relationship to short-field operation", "Prototype-specific construction, modification and flight-test records", "Distinction between intended, calculated and demonstrated performance" ], "out_of_scope": [ "The Messerschmitt Me 163 Komet rocket interceptor", "The Fieseler Fi 156 design and its operational history", "General aircraft aerodynamics and STOL classification", "Complete histories of Messerschmitt, Rohrbach and Weserflug", "Custody, condition and maintenance records of individual physical artifacts", "Scale models, replicas and artistic representations as independent products" ], "distinguishing_features": [ "Require the full Bf 163 designation and corroborating configuration evidence; the number 163 alone cannot distinguish it from the Me 163.", "Check photographs or drawings for the propeller-driven liaison-aircraft configuration associated with Bf 163 records before accepting an identification.", "Investigate evidence of whole-wing incidence adjustment when distinguishing the Bf 163 from a superficially similar Fi 156; appearance alone is insufficient.", "Separate organizational attribution from aircraft identity: a Weserflug attribution is a candidate link to investigate, not grounds to create another registered design.", "Require prototype provenance before treating a drawing, performance table or model-kit depiction as evidence of an aircraft actually built." ], "characteristics": [ { "name": "Designation and documentary aliases", "kind": "category", "unit_or_values": "Exact recorded designation, document date and alias status", "why_it_matters": "Prevents conflation with the Me 163 and preserves historically meaningful naming." }, { "name": "Design and construction responsibility", "kind": "relation", "unit_or_values": "Organization linked to a documented role and period", "why_it_matters": "Separates origin, development responsibility and physical manufacture." }, { "name": "Configuration maturity", "kind": "state", "unit_or_values": "Proposed, drawn, constructed, ground-tested, flight-tested or unresolved", "why_it_matters": "Prevents a design proposal from becoming an asserted prototype feature." }, { "name": "Wing-incidence range", "kind": "measurement", "unit_or_values": "Degrees relative to a specified fuselage datum; unknown until documented", "why_it_matters": "Characterizes the reported distinctive mechanism without confusing incidence with aircraft attitude or angle of attack." }, { "name": "High-lift and incidence-control configuration", "kind": "category", "unit_or_values": "Documented arrangement of wing movement, slats, flaps, actuation and limits", "why_it_matters": "Supports recognition and interpretation of short-field test results." }, { "name": "Installed propulsion configuration", "kind": "relation", "unit_or_values": "Engine variant and propeller installation tied to an airframe and date", "why_it_matters": "Performance cannot be assigned reliably from an engine-family name alone." }, { "name": "Short-field performance", "kind": "measurement", "unit_or_values": "Takeoff and landing distances in m, with mass in kg, wind in m/s and obstacle height in m", "why_it_matters": "Makes performance claims comparable only when test definitions and conditions match." }, { "name": "Prototype evidence coverage", "kind": "state", "unit_or_values": "Documented, indirectly supported, disputed or unknown for each airframe and event", "why_it_matters": "Keeps incomplete development records from implying production or service history." } ], "affordances": [ "Classify a candidate record or image as Bf 163, another aircraft or unresolved.", "Associate a technical claim with the particular proposed or tested configuration it describes.", "Compare Bf 163 short-field claims with Fi 156 results under matched conditions.", "Trace discrepancies in designation, organizational responsibility and prototype chronology.", "Identify which missing records prevent a reconstruction or capability assessment.", "Determine whether evidence supports historical description, dimensional reconstruction or an operational claim." ], "agent_conduct": { "may": [ "Describe the experimental aircraft and the liaison requirement it competed for.", "Distinguish it clearly from the competing design that was adopted." ], "must_not": [ "Present uncertain details about prototypes as established fact.", "Confuse it with similarly named types in records.", "Glorify the military regime it was developed for." ], "requires_human": [ "Publishing interpretations where sources disagree." ] }, "ethics": { "considerations": [ "Histories of wartime aircraft development should be accurate and avoid glorifying aggression." ], "affected_parties": [ "Historians", "Readers of aviation history" ] }, "owners": { "steward": "Nobody owns the design history; archives hold the surviving records.", "master_systems": [] }, "visual_identification": [ "A small single-engine liaison aircraft with long-span wings and stalky undercarriage for short take-off and landing.", "A glazed cabin giving the crew a wide downward view." ], "failure_modes_and_hazards": [ "Sparse records make it easy to repeat errors from secondary sources." ], "what_it_is_for": [ "This reconnaissance and liaison aircraft prototype is encountered in historical accounts of German military aviation development during the 1930s.", "It supports study of short takeoff and landing design, with proposed performance distinguished from documented prototype trials." ], "facets_not_applicable": { "interfaces": "No specific applicable standard, law or official classification is established here for this historical prototype." } }, "sources": [ { "id": "wikidata", "title": "Wikidata item Q1786265: Messerschmitt Bf 163", "url": "https://www.wikidata.org/wiki/Q1786265", "url_status": "live", "what_it_supports": "identity and sense of the item", "checked_by": "wikidata-api" }, { "id": "wikipedia-en", "title": "Wikipedia: Messerschmitt Bf 163", "url": "https://en.wikipedia.org/wiki/Messerschmitt_Bf_163", "url_status": "live", "what_it_supports": "general description of the item", "checked_by": "wikidata-api sitelink" } ], "structure": { "bundles": [ { "id": "designation-and-design-boundary", "name": "Designation and design boundary", "description": "Establishes which aircraft project a Bf 163 record describes.", "rationale": "The shared number with Me 163 and multiple organizational attributions create specific identification risks.", "layers": [ { "id": "designation-disambiguation", "name": "Designation disambiguation", "description": "Separates exact designations from ambiguous references.", "findings": [ { "id": "bf-163-record-identity", "name": "Bf 163 record identity", "description": "Require designation, date and configuration evidence to resolve records mentioning Messerschmitt and 163.", "questions": [ { "text": "What contemporaneous designation record establishes the identity of the Bf 163 project?", "kind": "definition", "id": "bf-163-record-identity-q01" }, { "text": "Which configuration or documentary evidence excludes the Me 163 Komet when a source says only Messerschmitt 163?", "kind": "boundary", "id": "bf-163-record-identity-q02" } ] } ] }, { "id": "organizational-attribution", "name": "Organizational attribution", "description": "Records responsibility without multiplying aircraft identities.", "findings": [ { "id": "design-development-and-build-roles", "name": "Design, development and build roles", "description": "Resolve reported BFW, Messerschmitt, Rohrbach and Weserflug associations into dated responsibilities.", "questions": [ { "text": "Which records establish each organization's responsibility for design, development, construction and testing?", "kind": "provenance", "id": "design-development-and-build-roles-q01" }, { "text": "Do differently attributed Bf 163 records concern the same project, a changed configuration or merely a naming convention?", "kind": "boundary", "id": "design-development-and-build-roles-q02" } ] } ] } ] }, { "id": "wing-incidence-and-high-lift-system", "name": "Wing incidence and high-lift system", "description": "Defines the evidence needed to characterize the reported movable-wing arrangement.", "rationale": "The relationship between wing incidence and high-lift devices is central to recognizing and evaluating this design.", "layers": [ { "id": "wing-motion-geometry", "name": "Wing motion geometry", "description": "Distinguishes the proposed mechanism from its realized implementation.", "findings": [ { "id": "incidence-adjustment-mechanism", "name": "Incidence adjustment mechanism", "description": "Establish the wing pivot, travel limits, actuation and accommodation of movement by supporting structure.", "questions": [ { "text": "Which drawings or inspection records show how the Bf 163 wing changed incidence and how its supporting members moved?", "kind": "provenance", "id": "incidence-adjustment-mechanism-q01" }, { "text": "What incidence range and reference datum were specified, and what range was demonstrated on a built prototype?", "kind": "measurement", "id": "incidence-adjustment-mechanism-q02" } ] } ] }, { "id": "high-lift-control-integration", "name": "High-lift control integration", "description": "Relates wing movement to lift devices and pilot control.", "findings": [ { "id": "incidence-and-device-coordination", "name": "Incidence and device coordination", "description": "Determine how slats, flaps and flight controls interacted with incidence adjustment in each documented configuration.", "questions": [ { "text": "Which high-lift devices were installed, and were their movements independent of or coupled to wing-incidence adjustment?", "kind": "definition", "id": "incidence-and-device-coordination-q01" }, { "text": "What documented operating limits, locks or procedures governed incidence changes during ground and flight testing?", "kind": "action", "id": "incidence-and-device-coordination-q02" } ] } ] } ] }, { "id": "installed-configuration-and-short-field-capability", "name": "Installed configuration and short-field capability", "description": "Connects propulsion, airframe dimensions and loading to evidence of intended mission performance.", "rationale": "Short-field claims are meaningful only for a known Bf 163 configuration and explicitly defined test conditions.", "layers": [ { "id": "prototype-installation", "name": "Prototype installation", "description": "Identifies the physical configuration underlying a specification or test.", "findings": [ { "id": "configuration-baseline", "name": "Configuration baseline", "description": "Bind engine, propeller, dimensions, landing gear and loading to a dated drawing or airframe record.", "questions": [ { "text": "Which engine variant, propeller and landing-gear arrangement are evidenced for each built or proposed Bf 163 configuration?", "kind": "provenance", "id": "configuration-baseline-q01" }, { "text": "What wingspan, wing area, mass and center-of-gravity limits belong to that configuration, with which units and loading assumptions?", "kind": "measurement", "id": "configuration-baseline-q02" } ] } ] }, { "id": "mission-and-test-performance", "name": "Mission and test performance", "description": "Separates liaison-aircraft requirements from demonstrated outcomes.", "findings": [ { "id": "short-field-claim-comparability", "name": "Short-field claim comparability", "description": "Evaluate takeoff, landing and low-speed claims with their measurement definitions and evidential status.", "questions": [ { "text": "Which Bf 163 short-field figures are requirements, calculations or measured flight-test results?", "kind": "provenance", "id": "short-field-claim-comparability-q01" }, { "text": "What loading, wind, surface, obstacle criterion and wing settings accompanied each measured distance or speed?", "kind": "measurement", "id": "short-field-claim-comparability-q02" }, { "text": "Are the available Fi 156 comparison figures sufficiently matched to support a performance comparison?", "kind": "boundary", "id": "short-field-claim-comparability-q03" } ] } ] } ] }, { "id": "prototype-history-and-evidence-limits", "name": "Prototype history and evidence limits", "description": "Tracks project realization and determines what surviving records can justify.", "rationale": "A prototype design requires explicit separation of ordered, completed and flown aircraft, and of historical evidence from operating authority.", "layers": [ { "id": "airframes-and-development-events", "name": "Airframes and development events", "description": "Reconstructs development without treating orders or drawings as completed aircraft.", "findings": [ { "id": "prototype-realization", "name": "Prototype realization", "description": "Associate airframe identifiers with construction, modifications, tests and disposition only where evidence permits.", "questions": [ { "text": "How many Bf 163 airframes were ordered, started, completed and flown, and what evidence distinguishes those counts?", "kind": "provenance", "id": "prototype-realization-q01" }, { "text": "Which dated records establish first flight, subsequent changes, termination of development and final disposition?", "kind": "provenance", "id": "prototype-realization-q02" } ] } ] }, { "id": "permitted-evidence-use", "name": "Permitted evidence use", "description": "Defines the conclusions and actions supported by incomplete technical records.", "findings": [ { "id": "reconstruction-and-operation-boundary", "name": "Reconstruction and operation boundary", "description": "Distinguish evidence sufficient for identification or illustration from evidence needed for physical reconstruction and operation.", "questions": [ { "text": "Which Bf 163 details are supported by original drawings or test records, and which depend on later artwork or repeated secondary accounts?", "kind": "provenance", "id": "reconstruction-and-operation-boundary-q01" }, { "text": "What additional structural, control-system and test documentation would be required before using this model to support a functional reconstruction?", "kind": "action", "id": "reconstruction-and-operation-boundary-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 entry concerns an aircraft type, not an individual prototype.", "Prototype counts, first-flight date, engine specification and performance figures require verification and are omitted.", "The respective design and construction roles of Bayerische Flugzeugwerke and Weser Flugzeugbau should be checked before assigning manufacturer attribution." ], "questions": [ { "id": "evidence-confidence-notes-q01", "text": "Which of these check these first hold for the sense of Messerschmitt Bf 163 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": "Reich Air Ministry aircraft designation", "value_or_pattern": "Bf 163", "note": "The Bf prefix refers to Bayerische Flugzeugwerke; this aircraft is distinct from the rocket-powered Me 163." } ], "questions": [ { "id": "evidence-identifiers-q01", "text": "Which of these identifiers and schemes hold for the sense of Messerschmitt Bf 163 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 of a short-takeoff-and-landing liaison aircraft design." ], "questions": [ { "id": "evidence-real-world-use-q01", "text": "Which of these real-world use hold for the sense of Messerschmitt Bf 163 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": "Fieseler Fi 156 Storch", "difference": "A competing liaison aircraft design that entered series production and operational service." }, { "name": "Messerschmitt Me 163 Komet", "difference": "A rocket-powered interceptor, rather than a piston-engine liaison aircraft; the shared number does not indicate a variant relationship." }, { "name": "Liaison aircraft", "difference": "The broader functional category; Bf 163 identifies a particular experimental aircraft design." } ], "questions": [ { "id": "evidence-neighbours-q01", "text": "Which of these neighbouring kinds and how to tell them apart hold for the sense of Messerschmitt Bf 163 this model covers, and on what evidence?", "kind": "provenance" } ] } ] } ] } ] }, "openQuestions": [ "Which primary records resolve the allocation and transfer of design responsibility among BFW, Rohrbach and Weserflug?", "What wing-incidence mechanism, adjustment range and high-lift configuration were actually built and flight-tested?", "Which engine installation, dimensions and performance figures can be tied to a specific prototype configuration rather than repeated specification tables?", "What primary evidence establishes prototype counts, identifiers, first-flight chronology and final disposition?", "What documented evaluation explains the end of Bf 163 development, and does it substantiate comparisons with the Fi 156?" ], "statistics": { "bundles": 5, "layers": 9, "findings": 12, "questions": 21 } }