{ "vercy": "1.0-draft", "publication": { "status": "research-draft", "adjudicationStatus": "unreviewed", "publishableCanonical": false, "generatedAt": "2026-09-12T10:10:19Z", "providers": [ "Codex" ], "breadth": "recalled by Codex without web access - no source was read", "missingProviders": [], "pass": 2, "cost": { "grok": { "seconds": 18.9, "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: 01a09517-8cb0-7380-b666-5907ab9b348d\n--------\nuser\nDescribe what is already known about one registered thing. Answer as JSON only, no prose around it.\n\nThing: Halberstadt D.II\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: 100", "usd": 0.0, "recall": true }, "codex": { "seconds": 76.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: 01a09517-8ca7-7062-9163-bb4c94c5d070\n--------\nuser\nYou are drafting a Vercy meta-model for one registered thing. Answer as JSON only, no prose around it.\n\nThing: Halberstadt D.II\nRegistry id: vr.tr.halberstadt-d-ii\nPlane / domain: PHY / PHY.OBJ\nRegistry definition: (none recorded)\nNames folded into this entry:" } }, "enrichment": { "pass": 3, "engine": "claude", "producedAt": "2026-10-06T12:00:00Z", "ingestedAt": "2026-10-06T08:52:34+00:00", "fields": [ "agent_conduct", "ethics", "failure_modes_and_hazards", "owners", "visual_identification" ] }, "gate": { "passed": true, "version": "1.0", "at": "2026-10-07T10:10:32+00:00", "evidence": [ "completeness 1.00", "sense: Wikidata description", "2 live sources", "review by codex: pass" ] } }, "metaModel": { "id": "THING-Q671400", "registryId": "vr.tr.halberstadt-d-ii", "name": "Halberstadt D.II", "version": "0.1.0-research.1", "entryKind": "thing", "family": "Thing Registry", "domain": [ "PHY.OBJ" ], "status": "research-draft" }, "canonicalUrl": "https://ver.cy/models/thing/q671400/", "model": { "registry_id": "vr.tr.halberstadt-d-ii", "name": "Halberstadt D.II", "purpose": "Enable an agent to identify the Halberstadt D.II aircraft type, assess evidence about its configuration and surviving representations, and judge which comparisons or interventions that evidence supports.", "definition": "The Halberstadt D.II was a German single-seat, single-engine biplane fighter aircraft type built by Halberstädter Flugzeugwerke and used during the First World War, entering service in 1916.", "scope_statement": "This model owns the identifying configuration, operating dependencies, historical configuration changes and evidence requirements of the Halberstadt D.II registered as vr.tr.halberstadt-d-ii in PHY / PHY.OBJ; individual airframes provide evidence without becoming separate type definitions.", "in_scope": [ "Evidence establishing the Halberstadt D.II designation and its boundaries within the Halberstadt D-series", "Type-defining airframe, engine-installation, control and armament configurations", "Performance claims tied to a documented configuration and test conditions", "Operating and maintenance dependencies supported by period or restoration documentation", "Criteria for distinguishing original airframes, reconstructions, replicas and scale representations" ], "out_of_scope": [ "Complete models of neighbouring Halberstadt aircraft types", "Individual airframe ownership, custody and maintenance histories beyond their relevance as type evidence", "Standalone models of engines, weapons and instruments fitted to the aircraft", "General histories of air warfare, military units or pilots", "Modern replica certification and operating permissions as independently governed records" ], "distinguishing_features": [ "Require a designation-bearing record or a traceable attribution to Halberstadt D.II; a generic Halberstadt fighter caption is insufficient.", "Compare documented engine identity, mounting, cowling, exhaust and cooling arrangements when distinguishing D.II from neighbouring D-series types.", "Check the combined wing, interplane-strut, fuselage and tail geometry against D.II-specific drawings or securely attributed photographs.", "Cross-check armament mounting and undercarriage details against the attributed configuration rather than treating either feature alone as decisive.", "Separate a historically documented D.II configuration from a replica whose external resemblance conceals substituted propulsion, structure or controls." ], "characteristics": [ { "name": "Designation evidence", "kind": "relation", "unit_or_values": "Designation linked to a manufacturer, military, archival or scholarly record", "why_it_matters": "Prevents an uncertain caption or a neighbouring variant from establishing the type identity." }, { "name": "Configuration attribution", "kind": "category", "unit_or_values": "Documented production configuration; documented modification; reconstruction; unresolved", "why_it_matters": "Keeps incompatible details from being combined into an aircraft configuration that never existed." }, { "name": "Engine and installation identity", "kind": "relation", "unit_or_values": "Engine designation and evidence for mounting, cooling, exhaust and propeller compatibility", "why_it_matters": "Supports differentiation within the D-series and constrains performance comparisons." }, { "name": "Airframe geometry", "kind": "measurement", "unit_or_values": "Span and length in m; wing area in m²; angles in degrees; configuration and source required", "why_it_matters": "Provides measurable identification checks and reveals discrepancies among drawings or replicas." }, { "name": "Mass condition", "kind": "measurement", "unit_or_values": "kg, explicitly identified as empty, equipped or loaded with the source's definition", "why_it_matters": "Prevents misleading comparisons between performance figures using different loading assumptions." }, { "name": "Control and bracing arrangement", "kind": "category", "unit_or_values": "Documented control-surface layout, actuation routes and structural bracing configuration", "why_it_matters": "Connects recognition features to inspection and handling dependencies." }, { "name": "Armament installation", "kind": "relation", "unit_or_values": "Weapon identity, quantity, mounting and any firing-synchronization mechanism, each supported by evidence", "why_it_matters": "Distinguishes supported installations from generalized fighter descriptions." }, { "name": "Performance evidence", "kind": "measurement", "unit_or_values": "Speed in km/h; altitude in m; climb time in min; endurance in h, with loading and conditions", "why_it_matters": "Makes conflicting historical figures comparable without presenting one context-free value as definitive." }, { "name": "Represented-airframe authenticity", "kind": "state", "unit_or_values": "Original material; restored original; reconstruction; replica; scale representation; unresolved", "why_it_matters": "Controls which observations may support claims about the historical aircraft type." } ], "affordances": [ "Evaluate whether an aircraft, drawing or photograph can be attributed to Halberstadt D.II and explain the evidence gaps.", "Compare a proposed D.II configuration with documented neighbouring D-series configurations.", "Reconcile dimensional and performance claims while preserving their configuration and measurement conditions.", "Identify which technical documents and inspections are needed before handling, restoration or operation of a represented airframe.", "Assess whether a replica or reconstruction can support a particular historical claim.", "Flag unsupported mixtures of airframe, engine, armament and markings in a proposed reconstruction." ], "agent_conduct": { "may": [ "Describe the fighter's design and its role in First World War air combat.", "Support historians and museums in cataloguing records and replicas." ], "must_not": [ "Glorify killing when describing its combat service.", "Present uncertain victory claims or production figures as fact.", "Misattribute photographs or documents." ], "requires_human": [ "Publishing interpretations where sources disagree." ] }, "ethics": { "considerations": [ "The airmen who flew it on both sides died young; their history deserves accuracy and respect." ], "affected_parties": [ "Descendants of airmen", "Historians", "Museum visitors" ] }, "owners": { "steward": "Nobody owns the design history; archives and museums hold the surviving records.", "master_systems": [] }, "visual_identification": [ "A single-seat biplane with a slim fuselage and single-bay wings.", "A nose-mounted inline engine and a synchronised machine gun ahead of the cockpit." ], "failure_modes_and_hazards": [ "Scarce sources mean errors about the type are easily repeated." ], "what_it_is_for": [ "This aircraft type is encountered in research on First World War aviation, archival photographs and museum representations.", "Documented construction details support comparisons of early fighter designs and assessments of reconstruction accuracy." ], "standards_and_regulation": [ "ISO 21127, issued by the International Organization for Standardization, provides a reference ontology for exchanging cultural heritage information about aircraft specimens and associated records." ] }, "sources": [ { "id": "wikidata", "title": "Wikidata item Q671400: Halberstadt D.II", "url": "https://www.wikidata.org/wiki/Q671400", "url_status": "live", "what_it_supports": "identity and sense of the item", "checked_by": "wikidata-api" }, { "id": "wikipedia-en", "title": "Wikipedia: Halberstadt D.II", "url": "https://en.wikipedia.org/wiki/Halberstadt_D.II", "url_status": "live", "what_it_supports": "general description of the item", "checked_by": "wikidata-api sitelink" } ], "structure": { "bundles": [ { "id": "designation-and-type-boundary", "name": "Designation and type boundary", "description": "Establishes what the Halberstadt D.II name identifies and which evidence separates it from neighbouring aircraft.", "rationale": "A model-specific registry entry must avoid absorbing the whole D-series or treating every attributed airframe as an independent type.", "layers": [ { "id": "designation-evidence", "name": "Designation evidence", "description": "Connects the registered name to records that actually identify the aircraft type.", "findings": [ { "id": "documented-d-ii-attribution", "name": "Documented D.II attribution", "description": "Record the basis of each D.II identification, preserving distinctions between contemporary designation and later attribution.", "questions": [ { "text": "What contemporary record explicitly identifies this aircraft configuration as Halberstadt D.II?", "kind": "provenance", "id": "documented-d-ii-attribution-q01" }, { "text": "Which spelling or designation variants refer to this same type, and which denote a different aircraft?", "kind": "definition", "id": "documented-d-ii-attribution-q02" } ] } ] }, { "id": "neighbouring-type-comparison", "name": "Neighbouring type comparison", "description": "Tests D.II attribution against documented alternatives within the Halberstadt D-series.", "findings": [ { "id": "combined-variant-identification", "name": "Combined variant identification", "description": "Use a combination of documented installation and airframe features instead of relying on a single silhouette detail.", "questions": [ { "text": "Which documented engine-installation and airframe differences distinguish D.II from D.I and D.III?", "kind": "boundary", "id": "combined-variant-identification-q01" }, { "text": "Which of those differences are visible or recorded for the item being identified?", "kind": "measurement", "id": "combined-variant-identification-q02" } ] } ] } ] }, { "id": "airframe-and-installed-systems", "name": "Airframe and installed systems", "description": "Describes the mutually compatible structural and mechanical features of a supported D.II configuration.", "rationale": "A plausible-looking combination of D-series components is insufficient evidence of an authentic D.II configuration.", "layers": [ { "id": "geometry-structure-and-controls", "name": "Geometry, structure and controls", "description": "Relates external geometry to construction, bracing and control arrangements.", "findings": [ { "id": "supported-airframe-arrangement", "name": "Supported airframe arrangement", "description": "Capture dimensions and construction details only with their configuration attribution and documentary basis.", "questions": [ { "text": "What D.II-specific evidence establishes wing geometry, strut arrangement, tail form and undercarriage layout?", "kind": "provenance", "id": "supported-airframe-arrangement-q01" }, { "text": "What dimensions and control-surface arrangements can be established, and with what measurement uncertainty?", "kind": "measurement", "id": "supported-airframe-arrangement-q02" } ] } ] }, { "id": "propulsion-and-armament-integration", "name": "Propulsion and armament integration", "description": "Connects the engine, propeller, cooling and weapon installations to the airframe configuration.", "findings": [ { "id": "compatible-installed-equipment", "name": "Compatible installed equipment", "description": "Distinguish equipment documented for D.II from equipment inferred from related aircraft or fitted to modern representations.", "questions": [ { "text": "Which engine, propeller, cooling and exhaust arrangements are documented together on a D.II?", "kind": "provenance", "id": "compatible-installed-equipment-q01" }, { "text": "What evidence establishes the weapon mounting and any synchronization arrangement for that same configuration?", "kind": "provenance", "id": "compatible-installed-equipment-q02" }, { "text": "Which equipment substitutions would prevent this airframe from serving as evidence of the historical D.II installation?", "kind": "boundary", "id": "compatible-installed-equipment-q03" } ] } ] } ] }, { "id": "performance-and-operating-dependencies", "name": "Performance and operating dependencies", "description": "Organizes evidence about D.II performance, handling prerequisites and maintenance-sensitive systems.", "rationale": "Historical capability figures and present-day operating decisions require different evidence, both tied to the actual configuration.", "layers": [ { "id": "conditional-performance", "name": "Conditional performance", "description": "Preserves the loading, altitude and measurement conditions behind reported capabilities.", "findings": [ { "id": "traceable-performance-claims", "name": "Traceable performance claims", "description": "Treat speed, climb, ceiling and endurance as attributed claims with conditions rather than universal constants.", "questions": [ { "text": "What loading, engine configuration, altitude and test method accompany each reported D.II performance figure?", "kind": "measurement", "id": "traceable-performance-claims-q01" }, { "text": "Do conflicting figures describe different conditions, different configurations or an unresolved source disagreement?", "kind": "provenance", "id": "traceable-performance-claims-q02" } ] } ] }, { "id": "inspection-and-handling-dependencies", "name": "Inspection and handling dependencies", "description": "Identifies the evidence needed to assess systems before an airframe is handled, maintained or operated.", "findings": [ { "id": "configuration-specific-readiness", "name": "Configuration-specific readiness", "description": "Link assessment of bracing, controls, propulsion and fitted armament to applicable technical evidence and the particular airframe.", "questions": [ { "text": "Which documented D.II inspection or rigging requirements apply to the bracing and control arrangement under assessment?", "kind": "action", "id": "configuration-specific-readiness-q01" }, { "text": "What engine-service, cooling, lubrication and propeller information is required for the installed configuration?", "kind": "action", "id": "configuration-specific-readiness-q02" }, { "text": "Which readiness decisions require individual-airframe inspection or modern authorization beyond this historical type model?", "kind": "boundary", "id": "configuration-specific-readiness-q03" } ] } ] } ] }, { "id": "historical-configuration-and-authenticity", "name": "Historical configuration and authenticity", "description": "Tracks evidence of configuration change and determines what surviving material or representations can establish.", "rationale": "Later illustrations, restorations and replicas can reproduce some D.II features while introducing unsupported details.", "layers": [ { "id": "dated-configuration-evidence", "name": "Dated configuration evidence", "description": "Associates configuration claims with identifiable airframes, dates and records where available.", "findings": [ { "id": "configuration-change-attribution", "name": "Configuration change attribution", "description": "Keep documented production differences and field changes distinct from errors in identification or depiction.", "questions": [ { "text": "Which dated records or securely identified photographs establish changes within the D.II type?", "kind": "provenance", "id": "configuration-change-attribution-q01" }, { "text": "Does an observed difference represent a D.II modification, another D-series type or an unresolved attribution?", "kind": "boundary", "id": "configuration-change-attribution-q02" } ] } ] }, { "id": "surviving-evidence-and-representations", "name": "Surviving evidence and representations", "description": "Evaluates the evidentiary value of surviving components, drawings, restorations and replicas.", "findings": [ { "id": "claim-specific-authenticity", "name": "Claim-specific authenticity", "description": "Assess authenticity against the particular claim: external appearance, construction, installed systems or flight behaviour.", "questions": [ { "text": "What provenance supports the identification of surviving material or a reference drawing as D.II evidence?", "kind": "provenance", "id": "claim-specific-authenticity-q01" }, { "text": "Which replica or restoration features reproduce documented D.II details, and which are substitutions or interpretations?", "kind": "boundary", "id": "claim-specific-authenticity-q02" }, { "text": "What additional evidence is needed before using this representation to support a historical or performance claim?", "kind": "action", "id": "claim-specific-authenticity-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 description is recalled knowledge; no sources have been consulted.", "Exact performance, dimensions, production totals, and service dates should be checked against aircraft-specific historical references.", "The hazards listed are consequences of the aircraft's configuration, not claims about documented failure frequencies." ], "questions": [ { "id": "evidence-confidence-notes-q01", "text": "Which of these check these first hold for the sense of Halberstadt D.II 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": "German military aircraft type designation", "value_or_pattern": "Halberstadt D.II", "note": "The manufacturer name and designation identify an aircraft type, not an individual airframe; D was the wartime German designation category for single-seat armed biplanes." } ], "questions": [ { "id": "evidence-identifiers-q01", "text": "Which of these identifiers and schemes hold for the sense of Halberstadt D.II 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": [ "Fighter patrols and aerial combat with German military aviation units during the First World War.", "Part of the transition from early German monoplane fighters to biplane fighters." ], "questions": [ { "id": "evidence-real-world-use-q01", "text": "Which of these real-world use hold for the sense of Halberstadt D.II 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", "typical_range": "1", "unit": "person" } ], "questions": [ { "id": "evidence-measurements-q01", "text": "Which of these typical measurements hold for the sense of Halberstadt D.II this model covers, and on what evidence?", "kind": "provenance" } ] }, { "id": "evidence-failure-modes-and-hazards", "name": "Failure modes and hazards", "description": "Recalled without web access and unsourced; every item is a lead to verify.", "evidence": [ "Engine failure in a single-engine aircraft requires an immediate glide and forced landing.", "Stalling or spinning at low altitude can leave insufficient height for recovery.", "Damage or deterioration of the fabric covering, wooden structure, or external bracing can compromise flight safety.", "Failure of the gun synchronization mechanism can allow bullets to strike the propeller." ], "questions": [ { "id": "evidence-failure-modes-and-hazards-q01", "text": "Which of these failure modes and hazards hold for the sense of Halberstadt D.II 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": "Halberstadt D.III", "difference": "A closely related fighter type distinguished principally by its Argus engine; the D.II used a Mercedes engine." }, { "name": "Fokker E.III", "difference": "An earlier German single-seat fighter with a monoplane wing arrangement and rotary engine, whereas the Halberstadt D.II was a biplane with a stationary inline engine." }, { "name": "Albatros D.II", "difference": "A separate manufacturer's fighter design, distinguished by its plywood-skinned semi-monocoque fuselage rather than the Halberstadt's fabric-covered framework." } ], "questions": [ { "id": "evidence-neighbours-q01", "text": "Which of these neighbouring kinds and how to tell them apart hold for the sense of Halberstadt D.II this model covers, and on what evidence?", "kind": "provenance" } ] } ] } ] } ] }, "openQuestions": [ "Which accessible primary records establish the D.II designation, production configurations and precise distinctions from D.I and D.III?", "Which engine, cooling, propeller and armament combinations are documented for D.II, and did they vary during production or service?", "Which published dimensions and performance figures have traceable measurement conditions, and how should conflicting values be reconciled?", "What original D.II material, technical drawings or operating instructions survive, and how securely are they attributed?", "Which D.II-specific inspection requirements and failure modes are documented, and which commonly repeated claims are extrapolated from related aircraft?" ], "statistics": { "bundles": 5, "layers": 9, "findings": 14, "questions": 25 } }