{ "vercy": "1.0-draft", "publication": { "status": "research-draft", "adjudicationStatus": "unreviewed", "publishableCanonical": false, "generatedAt": "2026-09-12T11:21:11Z", "providers": [ "Codex" ], "breadth": "recalled by Codex without web access - no source was read", "missingProviders": [], "pass": 2, "cost": { "grok": { "seconds": 16.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: 01a09558-8b68-71b2-a7b0-07e8d2e70504\n--------\nuser\nDescribe what is already known about one registered thing. Answer as JSON only, no prose around it.\n\nThing: Mitsubishi 1MT\nSense to describe: (none recorded)\nDomain code: PHY.OBJ\nAlso known as: (none)\n\n\nContext for this batch of 1001 things:\n# Batch 044: 1001 ", "usd": 0.0, "recall": true }, "codex": { "seconds": 68.8, "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: 01a09558-8b59-74d1-aa01-e427b31867e7\n--------\nuser\nYou are drafting a Vercy meta-model for one registered thing. Answer as JSON only, no prose around it.\n\nThing: Mitsubishi 1MT\nRegistry id: vr.tr.mitsubishi-1mt\nPlane / domain: PHY / PHY.OBJ\nRegistry definition: (none recorded)\nNames folded into this entry: (no" } }, "enrichment": { "pass": 3, "engine": "claude", "producedAt": "2026-10-06T12:00:00Z", "ingestedAt": "2026-10-06T08:52:22+00:00", "fields": [ "agent_conduct", "ethics", "failure_modes_and_hazards", "owners", "visual_identification" ] }, "gate": { "passed": true, "version": "1.0", "at": "2026-10-07T10:10:28+00:00", "evidence": [ "completeness 1.00", "sense: Wikidata description", "2 live sources", "review by codex: pass" ] } }, "metaModel": { "id": "THING-Q1994755", "registryId": "vr.tr.mitsubishi-1mt", "name": "Mitsubishi 1MT", "version": "0.1.0-research.1", "entryKind": "thing", "family": "Thing Registry", "domain": [ "PHY.OBJ" ], "status": "research-draft" }, "canonicalUrl": "https://ver.cy/models/thing/q1994755/", "model": { "registry_id": "vr.tr.mitsubishi-1mt", "name": "Mitsubishi 1MT", "purpose": "Enable an agent to identify the Mitsubishi 1MT aircraft type, assess evidence about its configurations and service limitations, and distinguish historical capability from intended use.", "definition": "The Mitsubishi 1MT was a Japanese single-seat, single-engine triplane torpedo-bomber type developed for the Imperial Japanese Navy in the early 1920s.", "scope_statement": "This model owns the type-level identity and distinguishing configuration of Mitsubishi 1MT, registry entry vr.tr.mitsubishi-1mt in PHY / PHY.OBJ, including evidence requirements for relating individual aircraft, technical records and historical claims to that type.", "in_scope": [ "Designation relationships among Mitsubishi 1MT, 1MT1N and Navy Type 10 torpedo-aircraft names", "Recognition of its single-seat triplane torpedo-aircraft configuration", "Configuration-dependent dimensions, propulsion, loading and performance", "Evidence separating intended carrier employment from demonstrated capability", "Development, acceptance, withdrawal and surviving-material provenance" ], "out_of_scope": [ "Individual airframes' maintenance logs, ownership and current condition", "The general theory and operation of torpedo bombers", "Internal design and operation of the carried torpedo", "Hōshō's ship design and operational history", "Other Mitsubishi aircraft sharing Type 10 terminology", "Replica construction instructions and authorization to fly" ], "distinguishing_features": [ "Test for the combined identity of Mitsubishi manufacture, three main wing planes, one pilot and a torpedo-aircraft role; matching only the manufacturer or wing count is insufficient. [Mitsubishi 1MT overview](https://en.wikipedia.org/wiki/Mitsubishi_1MT)", "Require designation evidence connecting 1MT or 1MT1N to the torpedo aircraft; a Type 10 label alone leaves the aircraft's identity unresolved. [Designation listing](https://commons.wikimedia.org/wiki/Category:Mitsubishi_1MT)", "Check that the record describes an aircraft type, rather than a photographed airframe, replica or scale model. [Type classification](https://commons.wikimedia.org/wiki/Category:Mitsubishi_1MT)", "Treat a carrier-role label as intended employment requiring separate capability evidence; the consulted overview reports restrictions when carrying a torpedo. [Service account](https://en.wikipedia.org/wiki/Mitsubishi_1MT)" ], "characteristics": [ { "name": "Designation and configuration attribution", "kind": "relation", "unit_or_values": "Registry identity ↔ documented designation ↔ prototype or production configuration", "why_it_matters": "Prevents specifications for a particular configuration from becoming universal claims about the type." }, { "name": "Recognition configuration", "kind": "category", "unit_or_values": "Wing arrangement, crew accommodation, propulsion arrangement and undercarriage form, each with evidence", "why_it_matters": "Supports identification when captions or abbreviated designations are ambiguous." }, { "name": "Airframe dimensions", "kind": "measurement", "unit_or_values": "Span, length and height in m; wing area in m²; configuration and source required", "why_it_matters": "Enables comparison of drawings, reported specifications and carrier-space requirements." }, { "name": "Mass and loading basis", "kind": "measurement", "unit_or_values": "kg; distinguish empty, equipped, test-loaded and maximum permitted mass", "why_it_matters": "A mass figure without its loading definition cannot support a carrier-performance judgment." }, { "name": "Installed propulsion", "kind": "relation", "unit_or_values": "Engine designation and installation; rated output in kW with original rating units and conditions", "why_it_matters": "Connects performance claims to the engine configuration actually described." }, { "name": "Torpedo carriage configuration", "kind": "relation", "unit_or_values": "Aircraft configuration ↔ torpedo identity, mass in kg, diameter in mm and carriage evidence", "why_it_matters": "Separates evidence of physical carriage from evidence of successful operational employment." }, { "name": "Carrier capability evidence", "kind": "state", "unit_or_values": "Proposed; tested; demonstrated under stated conditions; restricted; disputed; unknown", "why_it_matters": "Prevents the intended carrier role from being treated as proof of loaded carrier operation." }, { "name": "Historical disposition", "kind": "state", "unit_or_values": "Development, acceptance, service, withdrawal and disposal claims, dated and sourced", "why_it_matters": "Distinguishes the history of the type from the fate of any particular airframe." } ], "affordances": [ "Match an archival designation or photograph to the 1MT with an explicit confidence assessment.", "Compare competing 1MT specifications while retaining configuration, units and source differences.", "Evaluate whether a carrier-capability claim describes intention, a test or demonstrated service.", "Link an individual airframe or surviving component to the type without transferring its condition to the whole type.", "Identify missing evidence before accepting a reconstruction, museum attribution or historical performance claim." ], "agent_conduct": { "may": [ "Identify photographs, drawings or remains as this naval triplane type from documented features.", "Describe its development and short service from historical sources, noting gaps in the record." ], "must_not": [ "Present a model, replica or a related design as an original airframe.", "Invent specifications or service history where records are missing.", "Misuse its military history to glorify war or for propaganda." ], "requires_human": [ "Attributing found remains or artefacts to this type." ] }, "ethics": { "considerations": [ "Early carrier aircraft history touches on the people who flew and built them in a militarized era.", "Fabricated details pollute the historical record others depend on." ], "affected_parties": [ "Historians and museums", "Descendants of aircrew", "Readers" ] }, "owners": { "steward": "The museum or owner of any surviving example or remains; the state for items in public collections.", "master_systems": [] }, "visual_identification": [ "Single-engine aircraft with three stacked wings.", "Fittings for carrying a torpedo under the fuselage.", "Early 1920s naval markings in period photographs." ], "failure_modes_and_hazards": [ "Triplane layouts were heavy and drag-prone, limiting performance.", "Early carrier operations carried high accident risk for crews." ], "what_it_is_for": [ "This aircraft type is encountered in histories of early Japanese naval aviation and carrier aircraft development.", "It was developed for torpedo attack, making it relevant to studies of how payload requirements affected early naval aircraft designs.", "Historical assessments distinguish intended carrier use from demonstrated operating capability." ], "facets_not_applicable": { "interfaces": "No specific applicable design standard or regulatory classification is established here for this historical military aircraft type." } }, "sources": [ { "id": "wikidata", "title": "Wikidata item Q1994755: Mitsubishi 1MT", "url": "https://www.wikidata.org/wiki/Q1994755", "url_status": "live", "what_it_supports": "identity and sense of the item", "checked_by": "wikidata-api" }, { "id": "wikipedia-en", "title": "Wikipedia: Mitsubishi 1MT", "url": "https://en.wikipedia.org/wiki/Mitsubishi_1MT", "url_status": "live", "what_it_supports": "general description of the item", "checked_by": "wikidata-api sitelink" } ], "structure": { "bundles": [ { "id": "designation-and-recognition", "name": "Designation and recognition", "description": "Establish which names and visual evidence identify the registered 1MT type.", "rationale": "Abbreviated naval names and photographs can conflate the torpedo aircraft with neighbouring aircraft or individual examples.", "layers": [ { "id": "designation-resolution", "name": "Designation resolution", "description": "Resolve manufacturer and naval designations at their documented scope.", "findings": [ { "id": "designation-equivalence", "name": "Designation equivalence", "description": "Record evidence for each name relationship without assuming that 1MT and every more specific designation have identical scope.", "questions": [ { "text": "Which contemporary record connects 1MT, 1MT1N and the Japanese naval service designation?", "kind": "provenance", "id": "designation-equivalence-q01" }, { "text": "Does 1MT1N identify the complete registered type or a particular configuration within it?", "kind": "boundary", "id": "designation-equivalence-q02" } ] } ] }, { "id": "visual-attribution", "name": "Visual attribution", "description": "Use the aircraft's configuration together with documentary provenance.", "findings": [ { "id": "recognition-evidence", "name": "Recognition evidence", "description": "Assess the conjunction of wing arrangement, cockpit, engine installation and payload accommodation rather than trusting a caption alone.", "questions": [ { "text": "Which visible features and archival identifiers jointly support attribution to the 1MT?", "kind": "definition", "id": "recognition-evidence-q01" }, { "text": "Could the image instead show a reconstruction, a modified airframe or another aircraft carrying a Type 10 label?", "kind": "boundary", "id": "recognition-evidence-q02" } ] } ] } ] }, { "id": "airframe-and-propulsion", "name": "Airframe and propulsion", "description": "Describe the configuration needed to interpret 1MT dimensions and performance.", "rationale": "Triplane geometry and the installed powerplant must be tied to a specific configuration before technical comparisons are meaningful.", "layers": [ { "id": "triplane-geometry", "name": "Triplane geometry", "description": "Establish dimensional and construction evidence for the three-wing arrangement.", "findings": [ { "id": "geometry-and-construction-basis", "name": "Geometry and construction basis", "description": "Record configuration-specific dimensions, structural materials and drawing provenance; leave unsupported construction details unresolved.", "questions": [ { "text": "What span, length, height and wing-area values are documented, and which configuration does each describe?", "kind": "measurement", "id": "geometry-and-construction-basis-q01" }, { "text": "Which drawings or inspection records establish wing bracing, materials and structural differences between examples?", "kind": "provenance", "id": "geometry-and-construction-basis-q02" } ] } ] }, { "id": "powerplant-and-controls", "name": "Powerplant and controls", "description": "Connect the installed engine and pilot controls to documented operating evidence.", "findings": [ { "id": "installation-specific-evidence", "name": "Installation-specific evidence", "description": "Require installation evidence for engine ratings, cooling, fuel, lubrication and controls instead of importing generic engine specifications.", "questions": [ { "text": "Which engine version, propeller and power-rating conditions are documented for each 1MT configuration?", "kind": "measurement", "id": "installation-specific-evidence-q01" }, { "text": "Which original instructions establish control functions, consumables and maintenance requirements for that installation?", "kind": "provenance", "id": "installation-specific-evidence-q02" } ] } ] } ] }, { "id": "torpedo-load-and-carrier-use", "name": "Torpedo load and carrier use", "description": "Separate torpedo accommodation, loaded performance and carrier suitability.", "rationale": "The defining role of the 1MT cannot be evaluated from a payload listing or carrier designation alone.", "layers": [ { "id": "payload-compatibility", "name": "Payload compatibility", "description": "Establish what carriage evidence actually demonstrates.", "findings": [ { "id": "documented-torpedo-fit", "name": "Documented torpedo fit", "description": "Distinguish a photographed installation, an approved load and a tested load; keep torpedo internals in a neighbouring model.", "questions": [ { "text": "Which torpedo identity, dimensions and mass are supported by aircraft-specific documentation?", "kind": "measurement", "id": "documented-torpedo-fit-q01" }, { "text": "Does each cited record demonstrate static fit, flight carriage or formally accepted compatibility?", "kind": "boundary", "id": "documented-torpedo-fit-q02" } ] } ] }, { "id": "carrier-performance-evidence", "name": "Carrier performance evidence", "description": "Evaluate claims about operating from Hōshō under explicitly stated loading and test conditions.", "findings": [ { "id": "intention-versus-demonstration", "name": "Intention versus demonstration", "description": "Maintain separate judgments for intended employment, actual tests and accepted capability; do not infer an operating envelope from a historical summary.", "questions": [ { "text": "Which carrier or shore trials document aircraft loading, environmental conditions and measured performance?", "kind": "provenance", "id": "intention-versus-demonstration-q01" }, { "text": "What evidence is required before an agent may label torpedo-loaded carrier operation demonstrated, restricted or unresolved?", "kind": "action", "id": "intention-versus-demonstration-q02" } ] } ] } ] }, { "id": "service-evidence-and-material-legacy", "name": "Service evidence and material legacy", "description": "Establish the type's historical status and the evidential value of surviving records or objects.", "rationale": "Acceptance, practical usefulness, withdrawal and the survival of authentic material require different evidence.", "layers": [ { "id": "development-and-acceptance", "name": "Development and acceptance", "description": "Separate milestones and procurement decisions from operational claims.", "findings": [ { "id": "service-status-and-limitations", "name": "Service status and limitations", "description": "Record dates, quantities and reported handling problems with their source basis; identify the actual historical acceptance authority rather than assuming modern certification.", "questions": [ { "text": "Which dated records establish first flight, naval acceptance, production totals and withdrawal?", "kind": "provenance", "id": "service-status-and-limitations-q01" }, { "text": "Which naval requirements or trial reports document handling deficiencies and their effect on acceptance or employment?", "kind": "provenance", "id": "service-status-and-limitations-q02" } ] } ] }, { "id": "survival-and-authenticity", "name": "Survival and authenticity", "description": "Determine whether material attributed to the 1MT is original, reconstructed or merely illustrative.", "findings": [ { "id": "material-attribution-and-use", "name": "Material attribution and use", "description": "Link alleged survivors, components and replicas to the type through provenance while leaving object-specific condition and permissions to individual records.", "questions": [ { "text": "What chain of custody or original marking supports attribution of any surviving component or airframe to the 1MT?", "kind": "provenance", "id": "material-attribution-and-use-q01" }, { "text": "What additional evidence is needed before attributed material can support reconstruction or conservation decisions?", "kind": "action", "id": "material-attribution-and-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, without consulted sources.", "Verify the full service designation, variant designations, production total and dates before publication.", "Carrier operation was an intended role; actual embarkation, operational service and reasons for withdrawal require verification." ], "questions": [ { "id": "evidence-confidence-notes-q01", "text": "Which of these check these first hold for the sense of Mitsubishi 1MT 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": "1MT", "note": "Identifies the aircraft design, not an individual airframe." }, { "scheme": "Imperial Japanese Navy aircraft type designation", "value_or_pattern": "Type 10 torpedo bomber", "note": "Historical naval service designation associated with the Mitsubishi 1MT." } ], "questions": [ { "id": "evidence-identifiers-q01", "text": "Which of these identifiers and schemes hold for the sense of Mitsubishi 1MT 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 to deliver an aerial torpedo against surface ships.", "Intended for aircraft-carrier operations by the Imperial Japanese Navy." ], "questions": [ { "id": "evidence-real-world-use-q01", "text": "Which of these real-world use hold for the sense of Mitsubishi 1MT 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 Mitsubishi 1MT 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": "Mitsubishi 1MF", "difference": "The 1MF was a carrier fighter with a biplane configuration; the 1MT was a torpedo bomber with a triplane configuration." }, { "name": "Mitsubishi 2MR", "difference": "The 2MR was a reconnaissance biplane; the 1MT was a single-seat torpedo-bomber triplane." } ], "questions": [ { "id": "evidence-neighbours-q01", "text": "Which of these neighbouring kinds and how to tell them apart hold for the sense of Mitsubishi 1MT this model covers, and on what evidence?", "kind": "provenance" } ] } ] } ] } ] }, "openQuestions": [ "What contemporary Japanese records settle the exact relationship between 1MT, 1MT1N and translated Type 10 service names?", "Which original drawings and test reports establish configuration-specific dimensions, engine installation, loading definitions and performance?", "What trials substantiate the reported restriction on carrier operation with a torpedo, and under which conditions did it apply?", "Which documented control, structural or maintenance problems explain the reported handling difficulties and withdrawal?", "How many prototypes and production aircraft were completed, and does authenticated original material survive?" ], "statistics": { "bundles": 5, "layers": 9, "findings": 13, "questions": 21 } }