{ "vercy": "1.0-draft", "publication": { "status": "research-draft", "adjudicationStatus": "unreviewed", "publishableCanonical": false, "generatedAt": "2026-09-12T11:12:12Z", "providers": [ "Codex" ], "breadth": "recalled by Codex without web access - no source was read", "missingProviders": [], "pass": 2, "cost": { "grok": { "seconds": 18.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: 01a09550-1a0f-78f1-953e-07c94ae74dde\n--------\nuser\nDescribe what is already known about one registered thing. Answer as JSON only, no prose around it.\n\nThing: MB-411\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 register", "usd": 0.0, "recall": true }, "codex": { "seconds": 83.1, "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: 01a09550-1a19-7d83-bedb-c6d5f9661dc1\n--------\nuser\nYou are drafting a Vercy meta-model for one registered thing. Answer as JSON only, no prose around it.\n\nThing: MB-411\nRegistry id: vr.tr.mb-411\nPlane / domain: PHY / PHY.OBJ\nRegistry definition: (none recorded)\nNames folded into this entry: (none)\n\n\nContext fo" } }, "enrichment": { "pass": 3, "engine": "claude", "producedAt": "2026-10-06T12:00:00Z", "ingestedAt": "2026-10-06T08:56:41+00:00", "fields": [ "agent_conduct", "ethics", "failure_modes_and_hazards", "owners", "visual_identification" ] }, "gate": { "passed": true, "version": "1.0", "at": "2026-10-07T10:10:33+00:00", "evidence": [ "completeness 1.00", "sense: Wikidata description", "2 live sources", "review by codex: pass" ] } }, "metaModel": { "id": "THING-Q830243", "registryId": "vr.tr.mb-411", "name": "MB-411", "version": "0.1.0-research.1", "entryKind": "thing", "family": "Thing Registry", "domain": [ "PHY.OBJ" ], "status": "research-draft" }, "canonicalUrl": "https://ver.cy/models/thing/q830243/", "model": { "registry_id": "vr.tr.mb-411", "name": "MB-411", "purpose": "Enable an agent to identify the aircraft type provisionally associated with MB-411, distinguish its configurations, and assess evidence for its readiness for stowage, handling or flight.", "definition": "The Besson MB.411 was a French reconnaissance floatplane designed to be carried aboard and operated in support of the submarine Surcouf.", "scope_statement": "This draft treats vr.tr.mb-411 as the Besson MB.411 aircraft type, subject to confirmation of the registry identity; it owns type-specific recognition and assessment requirements, with individual aircraft histories linked separately.", "in_scope": [ "MB.411 designation, identity evidence and boundaries with related Besson designs", "Recognition of the aircraft's flight and dismantled configurations", "Aircraft-side compatibility with submarine hangar storage and handling", "Propulsion, loading and observation equipment by documented configuration", "Evidence required to assess assembly, seaworthiness and flight readiness" ], "out_of_scope": [ "The complete design and operational history of the submarine Surcouf", "Independent models of predecessor aircraft such as the MB.35", "Individual aircraft ownership, movements and accident histories", "General floatplane aerodynamics and pilot training", "Scale models, replicas and illustrations as independent objects" ], "distinguishing_features": [ "Require an explicit documentary association between MB-411 or MB.411 and Besson; the bare designation is insufficient.", "Check the proposed identification against the two-seat observation floatplane described in the preliminary identification source: [Besson MB.411](https://en.wikipedia.org/wiki/Besson_MB.411).", "Use the reported low-wing layout, central main float and two stabilizing floats as a combined recognition test, pending confirmation from drawings.", "Check evidence of dismantling for cylindrical submarine-hangar storage; compact dimensions alone do not establish MB.411 identity.", "Resolve MB.35, MB.41 and MB.410 references through documented design relationships rather than treating them automatically as MB.411 aliases." ], "characteristics": [ { "name": "Identity confidence", "kind": "state", "unit_or_values": "provisional identification | primary-source confirmed | disputed", "why_it_matters": "The registry supplies no definition or external identifier establishing which MB-411 it means." }, { "name": "Documented configuration", "kind": "relation", "unit_or_values": "Aircraft type linked to drawing revision, modification record and applicable serials", "why_it_matters": "A photograph or specification may describe only one aircraft or period." }, { "name": "Float arrangement", "kind": "category", "unit_or_values": "Main and stabilizing float count, position and attachment arrangement", "why_it_matters": "Supports recognition and assessment of water-support geometry." }, { "name": "Flight and stowage envelope", "kind": "measurement", "unit_or_values": "m; dimensions recorded separately for assembled aircraft and stowed components", "why_it_matters": "Hangar compatibility depends on the dismantled package and insertion clearances." }, { "name": "Assembly verification", "kind": "state", "unit_or_values": "stowed | assembly incomplete | assembled unchecked | inspected; checklist evidence attached", "why_it_matters": "Physical assembly does not establish that detachable connections are secure." }, { "name": "Installed propulsion", "kind": "relation", "unit_or_values": "Engine and propeller identities linked to configuration-specific documentation", "why_it_matters": "Related designs or modifications must not supply unsupported engine specifications." }, { "name": "Mass and balance envelope", "kind": "measurement", "unit_or_values": "kg and documented centre-of-gravity reference in m or percentage of reference chord", "why_it_matters": "Crew, fuel and observation equipment affect both flight and handling assessments." }, { "name": "Water-operation limits", "kind": "measurement", "unit_or_values": "Wind in m/s, wave height in m and other limits only where documented", "why_it_matters": "Water launch and recovery require operating conditions tied to an authoritative procedure." }, { "name": "Structural and float condition", "kind": "state", "unit_or_values": "unassessed | defects recorded | inspected serviceable | restricted", "why_it_matters": "Marine exposure and repeated dismantling require inspection evidence before handling or operation." } ], "affordances": [ "Classify a record or image as a supported, provisional or rejected MB.411 identification.", "Compare an aircraft configuration with documented MB.411 drawings and modification records.", "Assess a proposed stowage arrangement against measured component envelopes and hangar clearances.", "Identify missing evidence for assembly, lifting, water handling or flight readiness.", "Separate type-wide characteristics from modifications or events affecting one aircraft.", "Formulate targeted archival requests for unresolved dimensions, procedures and configuration limits." ], "agent_conduct": { "may": [ "Describe the small floatplane and its unusual role aboard a submarine.", "Support historians in cataloguing records about it." ], "must_not": [ "Present uncertain details about its operational use as fact.", "Confuse it with other types with similar designations.", "Misattribute photographs or documents." ], "requires_human": [ "Publishing interpretations where sources disagree." ] }, "ethics": { "considerations": [ "The submarine it served was lost with all hands; history should be told with respect for the crew." ], "affected_parties": [ "Families of lost crew", "Historians" ] }, "owners": { "steward": "Nobody owns the design history; archives and naval museums hold the surviving records.", "master_systems": [] }, "visual_identification": [ "A small, single-engine floatplane designed to be partly dismantled for stowage in a watertight hangar.", "Twin floats under a compact fuselage." ], "failure_modes_and_hazards": [ "Launch and recovery from a submarine at sea was hazardous for crews." ], "what_it_is_for": [ "The MB-411 was intended for reconnaissance in support of a submarine, extending observation beyond the vessel's immediate surroundings.", "It is now chiefly encountered in aviation and naval history through photographs, drawings and service records.", "Identifying the type supports interpretation of submarine-carried aviation and its constraints on aircraft storage and operation." ], "facets_not_applicable": { "interfaces": "No specific applicable standard or regulation can be established from the historical aircraft designation alone." } }, "sources": [ { "id": "wikidata", "title": "Wikidata item Q830243: MB-411", "url": "https://www.wikidata.org/wiki/Q830243", "url_status": "live", "what_it_supports": "identity and sense of the item", "checked_by": "wikidata-api" }, { "id": "wikipedia-en", "title": "Wikipedia: Besson MB.411", "url": "https://en.wikipedia.org/wiki/Besson_MB.411", "url_status": "live", "what_it_supports": "general description of the item", "checked_by": "wikidata-api sitelink" } ], "structure": { "bundles": [ { "id": "identity-and-design-boundary", "name": "Identity and design boundary", "description": "Establish what MB-411 denotes and which related design records apply.", "rationale": "The undefined registry label cannot safely inherit every specification attached to similar Besson designations.", "layers": [ { "id": "designation-evidence", "name": "Designation evidence", "description": "Connect the registry entry to an evidenced aircraft identity.", "findings": [ { "id": "registry-to-aircraft-link", "name": "Registry-to-aircraft link", "description": "Record the evidence establishing that this entry denotes the Besson aircraft rather than another use of MB-411.", "questions": [ { "text": "Which original registry import record or external identifier establishes the manufacturer and aircraft identity?", "kind": "provenance", "id": "registry-to-aircraft-link-q01" }, { "text": "Which documentary uses establish that MB-411 and MB.411 denote the same aircraft type?", "kind": "definition", "id": "registry-to-aircraft-link-q02" } ] } ] }, { "id": "related-designs-and-examples", "name": "Related designs and examples", "description": "Separate design lineage from type identity and individual aircraft.", "findings": [ { "id": "predecessor-and-serial-boundaries", "name": "Predecessor and serial boundaries", "description": "Require explicit applicability before transferring information from MB.35, MB.41, MB.410 or a particular MB.411.", "questions": [ { "text": "Which documented changes distinguish MB.411 from each predecessor designation?", "kind": "boundary", "id": "predecessor-and-serial-boundaries-q01" }, { "text": "Which specifications or alterations apply to the whole type, and which apply only to a named serial?", "kind": "provenance", "id": "predecessor-and-serial-boundaries-q02" } ] } ] } ] }, { "id": "airframe-and-water-support", "name": "Airframe and water support", "description": "Describe the geometry needed to recognize the aircraft and assess its support on water.", "rationale": "Wing and float geometry provide stronger identification and handling evidence than the designation alone.", "layers": [ { "id": "recognition-geometry", "name": "Recognition geometry", "description": "Establish configuration-specific recognition references.", "findings": [ { "id": "wing-fuselage-float-signature", "name": "Wing, fuselage and float signature", "description": "Capture a sourced recognition set covering wing placement, cockpit arrangement, float geometry and attachment points.", "questions": [ { "text": "Which authenticated drawings or photographs establish the MB.411 recognition signature?", "kind": "provenance", "id": "wing-fuselage-float-signature-q01" }, { "text": "What span, length and height apply to the depicted assembled configuration?", "kind": "measurement", "id": "wing-fuselage-float-signature-q02" } ] } ] }, { "id": "flotation-integrity", "name": "Flotation integrity", "description": "Assess the aircraft's water-support components and their attachment condition.", "findings": [ { "id": "float-condition-and-loading", "name": "Float condition and loading", "description": "Record evidence for float watertightness, attachment integrity and allowable loading without inventing buoyancy margins.", "questions": [ { "text": "What inspection evidence establishes the condition of the main float, stabilizing floats and their attachments?", "kind": "action", "id": "float-condition-and-loading-q01" }, { "text": "Which loading and flotation limits are documented for MB.411?", "kind": "measurement", "id": "float-condition-and-loading-q02" } ] } ] } ] }, { "id": "submarine-stowage-and-assembly", "name": "Submarine stowage and assembly", "description": "Model the aircraft-side transition between hangar storage and assembled flight configuration.", "rationale": "Dismantled storage makes component completeness and reconnection evidence central to assessing this type.", "layers": [ { "id": "stowage-package", "name": "Stowage package", "description": "Establish what is detached and how the resulting package fits its documented hangar.", "findings": [ { "id": "detached-components-and-clearances", "name": "Detached components and clearances", "description": "Record the documented dismantling arrangement, component supports and insertion envelope.", "questions": [ { "text": "Which MB.411 components were detached, repositioned or secured for submarine storage?", "kind": "definition", "id": "detached-components-and-clearances-q01" }, { "text": "What package dimensions and handling clearances are established by aircraft and hangar documentation?", "kind": "measurement", "id": "detached-components-and-clearances-q02" } ] } ] }, { "id": "reassembly-verification", "name": "Reassembly verification", "description": "Distinguish rapid assembly claims from evidence of an inspected aircraft.", "findings": [ { "id": "connections-and-release-checks", "name": "Connections and release checks", "description": "Identify required structural fastening and any control or service reconnections affected by dismantling.", "questions": [ { "text": "Which connections require inspection after the MB.411 is removed from storage and assembled?", "kind": "action", "id": "connections-and-release-checks-q01" }, { "text": "What original procedure defines completion, personnel requirements and the conditions behind any quoted assembly time?", "kind": "provenance", "id": "connections-and-release-checks-q02" } ] } ] } ] }, { "id": "lifting-and-water-operations", "name": "Lifting and water operations", "description": "Assess transitions between carrier handling, water support and flight.", "rationale": "Aircraft readiness depends on distinct lifting, launch and recovery constraints at the carrier interface.", "layers": [ { "id": "carrier-handling-interface", "name": "Carrier handling interface", "description": "Establish the aircraft-side requirements for documented lifting arrangements.", "findings": [ { "id": "lifting-configuration", "name": "Lifting configuration", "description": "Require evidence for lifting points, tackle, supported mass and configuration before judging a proposed lift.", "questions": [ { "text": "Which MB.411 lifting points and sling arrangements are supported by original handling instructions or trial records?", "kind": "provenance", "id": "lifting-configuration-q01" }, { "text": "What aircraft mass, balance and assembly state were permitted during lifting?", "kind": "measurement", "id": "lifting-configuration-q02" } ] } ] }, { "id": "launch-and-recovery-envelope", "name": "Launch and recovery envelope", "description": "Keep water-operation limits separate from airborne performance.", "findings": [ { "id": "water-operation-evidence", "name": "Water-operation evidence", "description": "Record documented conditions for water takeoff, landing and recovery, including the evidence needed to assess each transition.", "questions": [ { "text": "What wind, wave and loading conditions were demonstrated or authorized for MB.411 water operations?", "kind": "measurement", "id": "water-operation-evidence-q01" }, { "text": "Which checks govern the transition from afloat to flight-ready and from landed to recoverable?", "kind": "action", "id": "water-operation-evidence-q02" } ] } ] } ] }, { "id": "propulsion-and-observation-configuration", "name": "Propulsion and observation configuration", "description": "Connect installed equipment and loading to the aircraft's observation role.", "rationale": "Engine, crew and mission-equipment assumptions can otherwise be inherited incorrectly from related aircraft.", "layers": [ { "id": "powerplant-and-endurance", "name": "Powerplant and endurance", "description": "Record only configuration-supported propulsion and performance information.", "findings": [ { "id": "engine-fuel-performance-applicability", "name": "Engine, fuel and performance applicability", "description": "Link engine identity, fuel provision and performance figures to the exact MB.411 configuration and test conditions.", "questions": [ { "text": "Which engine and propeller installations are documented specifically for MB.411?", "kind": "provenance", "id": "engine-fuel-performance-applicability-q01" }, { "text": "What fuel capacity, power and endurance figures are supported, with units, loading and operating conditions?", "kind": "measurement", "id": "engine-fuel-performance-applicability-q02" } ] } ] }, { "id": "crew-and-observation-fit", "name": "Crew and observation fit", "description": "Establish how the documented crew and equipment supported observation.", "findings": [ { "id": "observation-and-reporting-capability", "name": "Observation and reporting capability", "description": "Record seating roles, visibility and evidenced reporting equipment without assuming radio or photographic installations.", "questions": [ { "text": "Which crew duties and observation or communication equipment are documented for each configuration?", "kind": "provenance", "id": "observation-and-reporting-capability-q01" }, { "text": "How do crew, fuel and equipment loads constrain the documented mass and balance envelope?", "kind": "measurement", "id": "observation-and-reporting-capability-q02" } ] } ] } ] }, { "id": "condition-and-operation-evidence", "name": "Condition and operation evidence", "description": "Define the evidence needed to distinguish completeness, serviceability and authorization to operate.", "rationale": "A historic aircraft's apparent completeness cannot establish structural condition or operational permission.", "layers": [ { "id": "marine-exposure-and-detachable-joints", "name": "Marine exposure and detachable joints", "description": "Focus inspection records on the documented construction and dismantling interfaces.", "findings": [ { "id": "construction-specific-inspection", "name": "Construction-specific inspection", "description": "Tie inspection needs to verified materials, float attachments and repeatedly disconnected joints.", "questions": [ { "text": "Which original construction records establish materials and inspection requirements for the airframe and floats?", "kind": "provenance", "id": "construction-specific-inspection-q01" }, { "text": "What evidence is needed to assess deterioration or wear at the documented stowage and assembly interfaces?", "kind": "action", "id": "construction-specific-inspection-q02" } ] } ] }, { "id": "acceptance-and-restoration-boundaries", "name": "Acceptance and restoration boundaries", "description": "Separate historical acceptance evidence from assessments of surviving material or reconstructions.", "findings": [ { "id": "authority-and-evidence-applicability", "name": "Authority and evidence applicability", "description": "Record the issuing authority, aircraft applicability and scope of any acceptance, inspection or operating document.", "questions": [ { "text": "Which contemporary naval acceptance or operating documents apply to MB.411, and who issued them?", "kind": "provenance", "id": "authority-and-evidence-applicability-q01" }, { "text": "What additional evidence would a restored aircraft or reconstruction require before historical performance claims could inform an operational assessment?", "kind": "boundary", "id": "authority-and-evidence-applicability-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": [ "The identification assumes MB-411 denotes the Besson aircraft; the registry supplies no sense or aliases to confirm this.", "Production count, crew complement, dimensions, engine specification, and service chronology require verification.", "The hazards listed are operational risks associated with this configuration, not recalled documented MB.411 incidents." ], "questions": [ { "id": "evidence-confidence-notes-q01", "text": "Which of these check these first hold for the sense of MB-411 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": "Aircraft model designation", "value_or_pattern": "Besson MB.411", "note": "Also written MB-411; 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 MB-411 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": [ "Aerial reconnaissance in support of Surcouf.", "Storage aboard the submarine in a dedicated aircraft hangar between operations." ], "questions": [ { "id": "evidence-real-world-use-q01", "text": "Which of these real-world use hold for the sense of MB-411 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": [ "Saltwater corrosion of the airframe and mechanical components.", "Damage during water takeoff, landing, or recovery in rough seas.", "Errors when assembling or securing components after compact onboard storage." ], "questions": [ { "id": "evidence-failure-modes-and-hazards-q01", "text": "Which of these failure modes and hazards hold for the sense of MB-411 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": "Surcouf", "difference": "Surcouf was the submarine that carried the aircraft; MB.411 names the aircraft design." }, { "name": "Floatplane", "difference": "Floatplane is the broader aircraft category; MB.411 is a particular design within it." }, { "name": "Flying boat", "difference": "A flying boat floats principally on its hull; the MB.411 used floats separate from its fuselage." } ], "questions": [ { "id": "evidence-neighbours-q01", "text": "Which of these neighbouring kinds and how to tell them apart hold for the sense of MB-411 this model covers, and on what evidence?", "kind": "provenance" } ] } ] } ] } ] }, "openQuestions": [ "Does the registry's original external identifier confirm that MB-411 means the Besson MB.411 aircraft?", "Which primary records resolve the relationships among MB.35, MB.41, MB.410 and MB.411, including serial-specific modifications?", "What authoritative drawings establish assembled dimensions, stowage dimensions, detachable components and lifting arrangements?", "Which original manuals or trial reports establish propulsion, loading, endurance, assembly procedures and water-operation limits?", "What original acceptance and maintenance requirements applied, and what authenticated aircraft material or technical documentation survives?" ], "statistics": { "bundles": 7, "layers": 13, "findings": 17, "questions": 29 } }