{ "vercy": "1.0-draft", "publication": { "status": "research-draft", "adjudicationStatus": "unreviewed", "publishableCanonical": false, "generatedAt": "2026-09-12T09:38:06Z", "providers": [ "Codex" ], "breadth": "recalled by Codex without web access - no source was read", "missingProviders": [], "pass": 2, "cost": { "grok": { "seconds": 15.6, "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: 01a094f9-f29c-7ac0-b07c-48b969e58db6\n--------\nuser\nDescribe what is already known about one registered thing. Answer as JSON only, no prose around it.\n\nThing: Fairey Fantôme\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: 1001 ", "usd": 0.0, "recall": true }, "codex": { "seconds": 83.6, "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: 01a094f9-f2a7-7391-a00d-6ad89b56fe8f\n--------\nuser\nYou are drafting a Vercy meta-model for one registered thing. Answer as JSON only, no prose around it.\n\nThing: Fairey Fantôme\nRegistry id: vr.tr.fairey-fant-me\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:51:39+00:00", "fields": [ "agent_conduct", "ethics", "failure_modes_and_hazards", "owners", "visual_identification" ] }, "gate": { "passed": true, "version": "1.0", "at": "2026-10-07T10:10:29+00:00", "evidence": [ "completeness 1.00", "sense: Wikidata description", "2 live sources", "review by codex: pass" ] } }, "metaModel": { "id": "THING-Q3064547", "registryId": "vr.tr.fairey-fant-me", "name": "Fairey Fantôme", "version": "0.1.0-research.1", "entryKind": "thing", "family": "Thing Registry", "domain": [ "PHY.OBJ" ], "status": "research-draft" }, "canonicalUrl": "https://ver.cy/models/thing/q3064547/", "model": { "registry_id": "vr.tr.fairey-fant-me", "name": "Fairey Fantôme", "purpose": "Enable an agent to recognise the Fairey Fantôme aircraft type, distinguish its documented configurations, and judge which historical or technical conclusions its evidence supports.", "definition": "The Fairey Fantôme was a British-designed, single-seat, single-engine biplane fighter developed by Fairey Aviation in the 1930s to meet a Belgian military requirement, but built only in very small numbers.", "scope_statement": "This model owns the type-level identity and configuration boundaries of Fairey Fantôme, registry vr.tr.fairey-fant-me in PHY / PHY.OBJ, including the relationship to the Féroce designation; individual aircraft supply evidence without becoming separate registry concepts.", "in_scope": [ "Fantôme type identity and the documented relationship to the Féroce name", "Single-seat fighter configuration and Belgian competition context", "Airframe recognition and configuration differences", "Hispano-Suiza propulsion installation and reported armament arrangements", "Performance evidence qualified by aircraft, configuration and test conditions", "Evidence needed to assess an attributed surviving component, reconstruction or technical claim" ], "out_of_scope": [ "The Fairey Aviation and Avions Fairey organisations themselves", "The Fairey Firefly aircraft types and other competing fighters", "The Hispano-Suiza 12Y engine family as an independent product", "Individual aircraft ownership, maintenance and flight-log records", "General aerial combat doctrine or weapon operating procedures", "Scale models, game representations and replicas as instances of the original type" ], "distinguishing_features": [ "Require a documented Fairey Fantôme attribution: resemblance to an interwar fighter biplane alone cannot establish identity.", "Check the single-seat biplane layout against period photographs or drawings; distinguish it from Fairey aircraft with different crew or wing arrangements.", "Check the liquid-cooled Hispano-Suiza installation against period evidence; its engine designation and rating must remain configuration-specific. [Flight, June-July 1935, reproduced captions](https://aviadejavu.ru/Site/Crafts/Craft26417.htm)", "Treat Féroce as a designation relationship to investigate within this entry, rather than automatically creating another aircraft type. [Jane's 1938, reproduced caption](https://aviadejavu.ru/Site/Crafts/Craft26417.htm)", "Exclude McDonnell Phantom aircraft through manufacturer, period and propulsion evidence despite the similar English spelling." ], "characteristics": [ { "name": "Designation and configuration attribution", "kind": "relation", "unit_or_values": "Name → dated source → aircraft or configuration; Fantôme, Fantome and Féroce relationships", "why_it_matters": "Prevents spelling variants and potentially configuration-specific names from creating duplicate models." }, { "name": "Crew and aerodynamic layout", "kind": "category", "unit_or_values": "Single-seat fighter biplane; finer geometry requires an attributed drawing or photograph", "why_it_matters": "Provides an initial recognition test without relying on markings alone." }, { "name": "Airframe dimensions", "kind": "measurement", "unit_or_values": "Span, length and height in m; wing area in m²; source and configuration required", "why_it_matters": "Supports identification and comparison while preventing incompatible published dimensions from being silently combined." }, { "name": "Engine installation", "kind": "relation", "unit_or_values": "Hispano-Suiza engine designation, cooling arrangement, propeller and installation evidence", "why_it_matters": "Engine-family membership does not settle the installed subtype or associated systems." }, { "name": "Engine power rating", "kind": "measurement", "unit_or_values": "kW with original hp or metric-horsepower notation, altitude, rpm and rating duration where known", "why_it_matters": "Reported power figures cannot be compared reliably without their rating basis." }, { "name": "Armament configuration evidence", "kind": "state", "unit_or_values": "Proposed, provisioned, reported installed, physically documented, removed or unresolved", "why_it_matters": "A description of cannon provision does not establish installation on every aircraft." }, { "name": "Performance evidence status", "kind": "category", "unit_or_values": "Competition requirement, prediction, manufacturer claim, measured result or later compilation", "why_it_matters": "Prevents a target speed from being presented as demonstrated performance." }, { "name": "Mass and loading condition", "kind": "measurement", "unit_or_values": "kg, with fuel, ammunition, equipment and crew assumptions", "why_it_matters": "Performance comparisons require a defined loading condition." }, { "name": "Artifact attribution and condition", "kind": "state", "unit_or_values": "Original attributed material, uncertain attribution, reconstruction or replica; condition separately documented", "why_it_matters": "Historical identification and physical fitness require different evidence." } ], "affordances": [ "Classify a photograph, drawing or catalogue reference as a supported, tentative or rejected Fantôme attribution.", "Reconcile Fantôme and Féroce references while retaining differences in dates and configurations.", "Compare published specifications only after matching engine, loading and evidence status.", "Trace an armament claim to its aircraft and distinguish intended equipment from documented installation.", "Identify missing drawings, test records or material evidence before accepting a reconstruction or condition claim." ], "agent_conduct": { "may": [ "Describe the fighter's design and its development for a foreign air force requirement.", "Support historians in cataloguing records about the few examples built." ], "must_not": [ "Present uncertain production or service details as established fact.", "Confuse it with the related designs developed from it.", "Misattribute photographs or documents." ], "requires_human": [ "Publishing interpretations where sources disagree." ] }, "ethics": { "considerations": [ "Accurate history of small-production military types protects the record from repeated errors." ], "affected_parties": [ "Historians", "Readers of aviation history" ] }, "owners": { "steward": "Nobody owns the design history; archives and museums hold the surviving records.", "master_systems": [] }, "visual_identification": [ "A single-seat biplane fighter with a streamlined, enclosed liquid-cooled engine installation.", "Single-bay wings with neat struts and a fixed, spatted undercarriage." ], "failure_modes_and_hazards": [ "Very small production means sources are scarce and errors spread easily." ], "what_it_is_for": [ "This aircraft type was developed in the 1930s as a single-seat biplane fighter for a Belgian military requirement.", "It is now encountered chiefly in aviation history, archival photographs and technical studies of interwar fighter development.", "Its limited production makes individual aircraft records important when interpreting configurations and service histories." ], "facets_not_applicable": { "interfaces": "No single operating standard or regulation applies to the historical aircraft type independently of a particular airframe, jurisdiction and use." } }, "sources": [ { "id": "wikidata", "title": "Wikidata item Q3064547: Fairey Fantôme", "url": "https://www.wikidata.org/wiki/Q3064547", "url_status": "live", "what_it_supports": "identity and sense of the item", "checked_by": "wikidata-api" }, { "id": "wikipedia-en", "title": "Wikipedia: Fairey Fantôme", "url": "https://en.wikipedia.org/wiki/Fairey_Fant%C3%B4me", "url_status": "live", "what_it_supports": "general description of the item", "checked_by": "wikidata-api sitelink" } ], "structure": { "bundles": [ { "id": "identity-and-designation", "name": "Identity and designation", "description": "Establish the aircraft type represented by the registry entry and resolve neighbouring names.", "rationale": "Fantôme spelling variants and Féroce references can fragment one concept or conceal configuration differences.", "layers": [ { "id": "name-boundaries", "name": "Name boundaries", "description": "Connect historical names to the type without assuming complete equivalence.", "findings": [ { "id": "fantome-feroce-relationship", "name": "Fantôme-Féroce relationship", "description": "Record each designation with its source, date and referent before deciding whether it denotes the type or a particular configuration.", "questions": [ { "text": "Does the source use Féroce for the complete Fantôme design or specifically for Belgian-built aircraft?", "kind": "definition", "id": "fantome-feroce-relationship-q01" }, { "text": "Which contemporary document explicitly connects the two names?", "kind": "provenance", "id": "fantome-feroce-relationship-q02" } ] } ] }, { "id": "type-and-aircraft", "name": "Type and aircraft", "description": "Separate the registry concept from individual machines and misleading namesakes.", "findings": [ { "id": "individual-evidence-boundary", "name": "Individual evidence boundary", "description": "An aircraft registration or serial anchors evidence but does not make every recorded feature universal to the type.", "questions": [ { "text": "Which particular aircraft supports this identification or specification?", "kind": "provenance", "id": "individual-evidence-boundary-q01" }, { "text": "What evidence permits this aircraft-specific detail to be generalised to the Fantôme type?", "kind": "boundary", "id": "individual-evidence-boundary-q02" } ] } ] } ] }, { "id": "belgian-requirement-and-evaluation", "name": "Belgian requirement and evaluation", "description": "Explain the design's intended role through its competition and evaluation evidence.", "rationale": "The intended fighter requirement supplies a meaningful performance baseline but does not establish procurement or operational acceptance.", "layers": [ { "id": "competition-role", "name": "Competition role", "description": "Distinguish the design objective from subsequent outcomes.", "findings": [ { "id": "requirement-versus-achievement", "name": "Requirement versus achievement", "description": "Contemporary reporting identifies a Belgian single-seat fighter competition and a minimum speed stipulation; these are requirements, not measured results. [Flight, June 1935, reproduced caption](https://aviadejavu.ru/Site/Crafts/Craft26417.htm)", "questions": [ { "text": "What did the original Belgian specification require of the Fantôme submission?", "kind": "provenance", "id": "requirement-versus-achievement-q01" }, { "text": "Which reported figures are competition thresholds rather than achieved test values?", "kind": "measurement", "id": "requirement-versus-achievement-q02" } ] } ] }, { "id": "evaluation-outcomes", "name": "Evaluation outcomes", "description": "Keep demonstrations, trials, purchases and service acceptance distinct.", "findings": [ { "id": "evaluation-status", "name": "Evaluation status", "description": "Attach an institution, date and supporting record to each claimed evaluation or acceptance event.", "questions": [ { "text": "Which records establish whether an aircraft was demonstrated, tested, purchased or accepted for service?", "kind": "provenance", "id": "evaluation-status-q01" }, { "text": "Does a claimed operator relationship indicate evaluation custody or operational use?", "kind": "boundary", "id": "evaluation-status-q02" } ] } ] } ] }, { "id": "airframe-recognition-and-structure", "name": "Airframe recognition and structure", "description": "Describe the geometric and structural evidence needed to identify the Fantôme.", "rationale": "Similar fighter biplanes require a combined identification test, while reconstruction needs evidence beyond external appearance.", "layers": [ { "id": "recognition-geometry", "name": "Recognition geometry", "description": "Use attributed views to establish the airframe's distinctive proportions and arrangements.", "findings": [ { "id": "combined-visual-signature", "name": "Combined visual signature", "description": "Record wing arrangement, interplane bracing, cockpit position, undercarriage, nose and tail together rather than treating one feature as decisive.", "questions": [ { "text": "Which combination of visible details separates this aircraft from a Fairey Firefly II or another contemporary fighter biplane?", "kind": "boundary", "id": "combined-visual-signature-q01" }, { "text": "Which attributed photographs or drawings support the proposed recognition features?", "kind": "provenance", "id": "combined-visual-signature-q02" } ] } ] }, { "id": "structure-and-dimensions", "name": "Structure and dimensions", "description": "Connect dimensions and construction claims to their documentary basis.", "findings": [ { "id": "structural-evidence", "name": "Structural evidence", "description": "Separate visible covering from underlying structure, and retain the measurement basis for dimensions.", "questions": [ { "text": "What drawings or construction descriptions establish the materials and load-bearing arrangement of each airframe region?", "kind": "provenance", "id": "structural-evidence-q01" }, { "text": "Do quoted length and height values use the same propeller, attitude and reference points?", "kind": "measurement", "id": "structural-evidence-q02" } ] } ] } ] }, { "id": "propulsion-and-armament-configuration", "name": "Propulsion and armament configuration", "description": "Resolve the engine installation and weapon provisions for each documented configuration.", "rationale": "The reported engine and cannon arrangement is especially identifying, but published descriptions must not be treated as a universal equipment list.", "layers": [ { "id": "engine-and-cooling", "name": "Engine and cooling", "description": "Record the installed powerplant as an evidenced configuration.", "findings": [ { "id": "engine-rating-attribution", "name": "Engine rating attribution", "description": "Preserve original engine suffixes and power statements pending comparison with installation records; do not silently harmonise inconsistent transcriptions.", "questions": [ { "text": "Which engine subtype is documented for each aircraft and date?", "kind": "provenance", "id": "engine-rating-attribution-q01" }, { "text": "What altitude, rpm, duration and horsepower convention underlie each quoted rating?", "kind": "measurement", "id": "engine-rating-attribution-q02" }, { "text": "Which cooling and propeller details are confirmed by installation drawings?", "kind": "definition", "id": "engine-rating-attribution-q03" } ] } ] }, { "id": "weapon-provision-and-fit", "name": "Weapon provision and fit", "description": "Separate design accommodation from verified installed equipment.", "findings": [ { "id": "cannon-and-machine-gun-evidence", "name": "Cannon and machine-gun evidence", "description": "Track hub-firing cannon and machine-gun claims independently, with aircraft-specific installation status.", "questions": [ { "text": "Does the evidence show a cannon installed, an installation provision or only an advertised arrangement?", "kind": "boundary", "id": "cannon-and-machine-gun-evidence-q01" }, { "text": "Which records establish machine-gun count, calibre and location for the configuration being described?", "kind": "provenance", "id": "cannon-and-machine-gun-evidence-q02" } ] } ] } ] }, { "id": "performance-and-material-assessment", "name": "Performance and material assessment", "description": "Bound performance conclusions and actions involving attributed material by the available evidence.", "rationale": "Historical specifications cannot establish an operating envelope or demonstrate the fitness of surviving material or a reconstruction.", "layers": [ { "id": "qualified-performance", "name": "Qualified performance", "description": "Make performance comparisons conditional on configuration and test basis.", "findings": [ { "id": "comparable-test-results", "name": "Comparable test results", "description": "Associate speed, climb, ceiling and endurance values with loading, altitude, engine rating and evidence status.", "questions": [ { "text": "Which Fantôme performance figures come from identifiable flight-test records?", "kind": "provenance", "id": "comparable-test-results-q01" }, { "text": "Are loading, altitude and engine conditions sufficiently aligned to compare the reported values?", "kind": "measurement", "id": "comparable-test-results-q02" } ] } ] }, { "id": "artifact-and-action-boundaries", "name": "Artifact and action boundaries", "description": "Determine what an attributed component or reconstruction can support without assuming any original aircraft survives.", "findings": [ { "id": "evidence-before-physical-use", "name": "Evidence before physical use", "description": "Require component attribution and relevant technical records before accepting claims of faithful reconstruction or physical fitness.", "questions": [ { "text": "What provenance distinguishes original Fantôme material from a replica or a component shared with another aircraft?", "kind": "provenance", "id": "evidence-before-physical-use-q01" }, { "text": "Which missing drawings, inspection results or applicable approvals prevent the proposed restoration, ground operation or flight?", "kind": "action", "id": "evidence-before-physical-use-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 description is based on recall; no sources were consulted.", "Check exact production numbers, individual airframe histories and evaluation destinations before publication.", "The hazards listed are consequences of the aircraft's general configuration, not documented Fantôme-specific defects or accident findings." ], "questions": [ { "id": "evidence-confidence-notes-q01", "text": "Which of these check these first hold for the sense of Fairey Fantôme 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": "Manufacturer aircraft designation", "value_or_pattern": "Fairey Fantôme", "note": "Identifies an aircraft design, rather than an individual airframe." } ], "questions": [ { "id": "evidence-identifiers-q01", "text": "Which of these identifiers and schemes hold for the sense of Fairey Fantôme 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": [ "Developed as a prospective fighter for Belgian military aviation.", "Used for demonstration, testing and evaluation rather than widespread operational service." ], "questions": [ { "id": "evidence-real-world-use-q01", "text": "Which of these real-world use hold for the sense of Fairey Fantôme 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": [ "Its single-engine configuration meant engine failure could require a forced landing.", "Its liquid-cooled piston engine depended on coolant circulation; coolant loss could cause overheating and engine failure." ], "questions": [ { "id": "evidence-failure-modes-and-hazards-q01", "text": "Which of these failure modes and hazards hold for the sense of Fairey Fantôme 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": "Fairey Firefly II", "difference": "An earlier Fairey biplane fighter used by Belgium; the Fantôme was a separate, later design intended as a replacement." }, { "name": "Fairey Fox", "difference": "The Fox was principally a two-seat light bomber and reconnaissance aircraft; the Fantôme was a single-seat fighter." } ], "questions": [ { "id": "evidence-neighbours-q01", "text": "Which of these neighbouring kinds and how to tell them apart hold for the sense of Fairey Fantôme this model covers, and on what evidence?", "kind": "provenance" } ] } ] } ] } ] }, "openQuestions": [ "Did contemporary manufacturers and authorities use Fantôme and Féroce interchangeably, or did the names identify consistent configuration differences?", "What engine suffixes, rating conditions, propellers and actual armament installations are confirmed for each completed aircraft?", "Which original Belgian requirements and flight-test reports survive, and how do they distinguish required, advertised and measured performance?", "What primary records settle the production total, individual aircraft identities, subsequent transfers and disputed accounts of Spanish service?", "Do any original components, construction drawings or maintenance instructions survive, and what can they establish about materials, controls and inspection requirements?" ], "statistics": { "bundles": 6, "layers": 11, "findings": 15, "questions": 26 } }