{ "vercy": "1.0-draft", "publication": { "status": "research-draft", "adjudicationStatus": "unreviewed", "publishableCanonical": false, "generatedAt": "2026-09-12T11:01:56Z", "providers": [ "Codex" ], "breadth": "recalled by Codex without web access - no source was read", "missingProviders": [], "pass": 2, "cost": { "grok": { "seconds": 18.0, "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: 01a09546-c741-7cc3-adda-f47aef89fdf8\n--------\nuser\nDescribe what is already known about one registered thing. Answer as JSON only, no prose around it.\n\nThing: Long March 2A\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 r", "usd": 0.0, "recall": true }, "codex": { "seconds": 77.7, "error": "Reading additional input from stdin...\nOpenAI Codex v0.153.4\n--------\nworkdir: R:\\02_PROJECTS\\02_Meta_Models_Platforms\\Ver.cy\\current\\thing-registry-backlog\nmodel: gpt-6-astra\nprovider: openai\napproval: never\nsandbox: read-only\nreasoning effort: none\nreasoning summaries: none\nsession id: 01a09546-c744-79d3-b75c-4d02a1593a0a\n--------\nuser\nYou are drafting a Vercy meta-model for one registered thing. Answer as JSON only, no prose around it.\n\nThing: Long March 2A\nRegistry id: vr.tr.long-march-2a\nPlane / domain: PHY / PHY.OBJ\nRegistry definition: (none recorded)\nNames folded into this entry: (none" } }, "enrichment": { "pass": 3, "engine": "claude", "producedAt": "2026-10-06T12:00:00Z", "ingestedAt": "2026-10-06T08:53:13+00:00", "fields": [ "agent_conduct", "ethics", "failure_modes_and_hazards", "owners", "standards_and_regulation", "visual_identification" ] }, "gate": { "passed": true, "version": "1.0", "at": "2026-10-07T10:10:31+00:00", "evidence": [ "completeness 1.00", "sense: Wikidata description", "2 live sources", "review by codex: pass" ] } }, "metaModel": { "id": "THING-Q53700", "registryId": "vr.tr.long-march-2a", "name": "Long March 2A", "version": "0.1.0-research.1", "entryKind": "thing", "family": "Thing Registry", "domain": [ "PHY.OBJ" ], "status": "research-draft" }, "canonicalUrl": "https://ver.cy/models/thing/q53700/", "model": { "registry_id": "vr.tr.long-march-2a", "name": "Long March 2A", "purpose": "Enable an AI agent to identify Long March 2A records, distinguish their historical configuration from neighbouring launch vehicles, and assess claims about capability, flight outcomes and surviving hardware.", "definition": "Long March 2A is an early Chinese two-stage expendable orbital launch vehicle in the Long March 2 family, developed from the DF-5 ballistic missile and used to launch recoverable reconnaissance satellites into low Earth orbit.", "scope_statement": "This model owns the launch-vehicle type registered as vr.tr.long-march-2a, including its designation boundary, configuration, payload interfaces and evidence requirements; the relationship between CZ-2A and historical CZ-2 designations remains explicitly unresolved.", "in_scope": [ "Long March 2A designation, aliases and configuration attribution", "Stage architecture, propulsion and vehicle dimensions tied to the attributed configuration", "Payload accommodation and orbit-dependent launch capability", "Guidance, separation and ground-interface assurance requirements", "Flight attribution, retirement evidence and identification of surviving examples" ], "out_of_scope": [ "The entire Long March launch-vehicle family", "Separate Long March 2C, 2E and 2F vehicle models", "DF-5 missile capabilities and military employment", "Recoverable satellite imaging, re-entry and recovery systems", "Jiuquan launch-centre infrastructure and operations as independent subjects", "Individual launch events and physical vehicle inventories, except as linked evidence" ], "distinguishing_features": [ "Require documentary attribution to Long March 2A, Chang Zheng 2A, CZ-2A or LM-2A; a record saying only Long March 2 does not settle the variant.", "Check stage arrangement, engine revision and dated drawings together when distinguishing an early CZ-2 configuration from one labelled CZ-2A.", "Distinguish CZ-2A from CZ-2C through configuration and production evidence; shared family names or similar silhouettes are insufficient.", "Treat a recoverable-satellite launch from Jiuquan as contextual evidence, not unique identification of the launcher variant.", "Separate the expendable launch vehicle from its recoverable payload; payload recovery does not establish launcher reusability." ], "characteristics": [ { "name": "Designation attribution", "kind": "category", "unit_or_values": "Explicit CZ-2A attribution; CZ-2 attribution only; conflicting attribution; unresolved", "why_it_matters": "Controls which technical specifications and flights belong to this registry entry." }, { "name": "Configuration lineage", "kind": "relation", "unit_or_values": "Documented predecessor, modification baseline and successor, with source and date", "why_it_matters": "Prevents properties of later Long March variants from being inherited without evidence." }, { "name": "Stage and engine configuration", "kind": "category", "unit_or_values": "Stage count, engine designations and revisions, auxiliary propulsion and booster presence", "why_it_matters": "Provides stronger identification than external appearance alone." }, { "name": "Propellant assignment", "kind": "category", "unit_or_values": "Fuel and oxidizer identity by stage; exact configuration attribution required", "why_it_matters": "Connects propulsion evidence to compatibility and residual-hazard assessment." }, { "name": "Vehicle envelope", "kind": "measurement", "unit_or_values": "Length and diameter in m; specify fairing, adapter and measurement boundaries", "why_it_matters": "Supports identification and detects dimensions copied from another variant." }, { "name": "Mass accounting", "kind": "measurement", "unit_or_values": "kg; distinguish liftoff, dry, propellant and payload mass", "why_it_matters": "Makes mass comparisons meaningful across configurations and references." }, { "name": "Payload capability", "kind": "measurement", "unit_or_values": "kg at stated perigee and apogee in km and inclination in degrees", "why_it_matters": "A payload figure without its reference orbit cannot establish mission suitability." }, { "name": "Flight attribution and outcome", "kind": "relation", "unit_or_values": "Launch record, assigned variant, payload, insertion outcome and attribution confidence", "why_it_matters": "Allows flight statistics to be recomputed when variant boundaries change." }, { "name": "Lifecycle and specimen condition", "kind": "state", "unit_or_values": "Type: development, operational, retired or unresolved; specimen: flight article, test article, replica or unidentified", "why_it_matters": "Separates historical type status from the identity and condition of a particular object." } ], "affordances": [ "Classify a document or object as CZ-2A, another variant or unresolved using explicit evidence.", "Compare competing specifications while preserving their configuration and measurement assumptions.", "Assess a historical payload-capability claim against its orbit and interface requirements.", "Reconcile launch lists without silently assigning all early CZ-2 flights to CZ-2A.", "Identify missing provenance or condition evidence before describing a surviving article as authentic, inert or suitable for handling." ], "agent_conduct": { "may": [ "Identify launches and vehicles of this type from official records.", "Describe its history and relation to its missile ancestor from reliable sources.", "Report launch outcomes, including failures, accurately." ], "must_not": [ "Assist in developing or improving ballistic missiles.", "Present uncertain launch claims as fact.", "Downplay harm to people from falling stages or failed launches." ], "requires_human": [ "Publishing analysis that ties civil launch technology to weapons programmes." ] }, "ethics": { "considerations": [ "Launches from inland sites drop spent stages near communities.", "Launch technology and missile technology overlap, raising security concerns." ], "affected_parties": [ "People living under flight paths", "Launch crews", "Satellite operators" ] }, "owners": { "steward": "The state space programme that operated it.", "master_systems": [ "United Nations Register of Objects Launched into Outer Space" ] }, "visual_identification": [ "Two-stage rocket of the early Long March 2 family.", "Launch records and mission names settle a particular flight." ], "failure_modes_and_hazards": [ "Toxic hypergolic propellants harm people near launch and impact sites.", "Launch failure and falling debris.", "Spent stages landing near inhabited areas." ], "standards_and_regulation": [ "Treaty on Principles Governing the Activities of States in the Exploration and Use of Outer Space (Outer Space Treaty), United Nations.", "Convention on Registration of Objects Launched into Outer Space, United Nations." ], "what_it_is_for": [ "This early Chinese orbital launch vehicle was used to place recoverable reconnaissance satellites into low Earth orbit.", "It is encountered today chiefly in historical launch records, technical histories and accounts of Chinese launch vehicle development.", "Its designation and configuration matter when distinguishing individual missions from those flown by related vehicles." ] }, "sources": [ { "id": "wikidata", "title": "Wikidata item Q53700: Long March 2A", "url": "https://www.wikidata.org/wiki/Q53700", "url_status": "live", "what_it_supports": "identity and sense of the item", "checked_by": "wikidata-api" }, { "id": "wikipedia-en", "title": "Wikipedia: Long March 2A", "url": "https://en.wikipedia.org/wiki/Long_March_2A", "url_status": "live", "what_it_supports": "general description of the item", "checked_by": "wikidata-api sitelink" } ], "structure": { "bundles": [ { "id": "designation-and-lineage", "name": "Designation and lineage", "description": "Resolve what the registry name Long March 2A denotes in historical records.", "rationale": "Variant attribution determines every subsequent technical and historical claim.", "layers": [ { "id": "historical-names", "name": "Historical names", "description": "Preserve original terminology and distinguish it from later catalogue labels.", "findings": [ { "id": "cz2a-name-boundary", "name": "CZ-2A name boundary", "description": "CNSA describes the early vehicle as CZ-2 and assigns four launches to that designation; this does not independently resolve the registry's CZ-2A boundary. [CNSA: Long March 2](https://www.cnsa.gov.cn/n6758824/n6759008/n6759011/c6794032/content.html)", "questions": [ { "text": "Does CZ-2A denote a contemporary formal variant, a modification baseline or a retrospective catalogue label?", "kind": "definition", "id": "cz2a-name-boundary-q01" }, { "text": "Which original records connect the name CZ-2A to specific configurations and vehicle serials?", "kind": "provenance", "id": "cz2a-name-boundary-q02" } ] } ] }, { "id": "related-vehicle-boundaries", "name": "Related vehicle boundaries", "description": "Locate this type within its technical lineage without merging neighbouring types.", "findings": [ { "id": "variant-transition-evidence", "name": "Variant transition evidence", "description": "Require documented modifications and naming decisions before assigning predecessor or successor relationships.", "questions": [ { "text": "Which documented changes separate the original CZ-2, the vehicle called CZ-2A and CZ-2C?", "kind": "boundary", "id": "variant-transition-evidence-q01" }, { "text": "Which lineage statements are supported by manufacturer records rather than inferred from shared components?", "kind": "provenance", "id": "variant-transition-evidence-q02" } ] } ] } ] }, { "id": "vehicle-configuration", "name": "Vehicle configuration", "description": "Establish the physical baseline attributable to Long March 2A.", "rationale": "Family-level specifications cannot safely substitute for variant-specific architecture.", "layers": [ { "id": "stages-and-propulsion", "name": "Stages and propulsion", "description": "Record the propulsion arrangement and its evidential connection to this designation.", "findings": [ { "id": "propulsion-baseline", "name": "Propulsion baseline", "description": "CNSA describes the Long March 2 series as using two-stage architecture and nitrogen tetroxide with unsymmetrical dimethylhydrazine; exact CZ-2A engine revisions still require configuration-specific evidence. [CNSA: Long March launch-vehicle family](https://www.cnsa.gov.cn/n6758968/n6758973/c6771770/content.html)", "questions": [ { "text": "Which stage arrangement and engine revisions are documented for vehicles explicitly identified as CZ-2A?", "kind": "provenance", "id": "propulsion-baseline-q01" }, { "text": "Which propellant, thrust and burn-duration values belong to each stage, and under what reference conditions?", "kind": "measurement", "id": "propulsion-baseline-q02" } ] } ] }, { "id": "geometry-and-mass", "name": "Geometry and mass", "description": "Define dimensions and mass values with their configuration boundaries.", "findings": [ { "id": "comparable-physical-specifications", "name": "Comparable physical specifications", "description": "Keep overall vehicle dimensions and liftoff mass separate from stage-only measurements and later variant data.", "questions": [ { "text": "What are the verified length, core diameter and liftoff mass for the attributed CZ-2A configuration?", "kind": "measurement", "id": "comparable-physical-specifications-q01" }, { "text": "Do the reported measurements include the payload, adapter, fairing and loaded consumables?", "kind": "boundary", "id": "comparable-physical-specifications-q02" } ] } ] } ] }, { "id": "payload-and-orbit", "name": "Payload and orbit", "description": "Connect launch capability to recoverable-satellite missions and their interface requirements.", "rationale": "Satellite mission success and launcher capability have different boundaries.", "layers": [ { "id": "historical-mission-role", "name": "Historical mission role", "description": "Use identified satellite missions as evidence while preserving launcher-name uncertainty.", "findings": [ { "id": "recoverable-satellite-association", "name": "Recoverable-satellite association", "description": "CNSA records a Long March 2 launch from Jiuquan on 26 November 1975 placing China's first recoverable remote-sensing satellite into its intended orbit; the source uses Long March 2 rather than settling the CZ-2A designation. [CNSA: 1975 launch anniversary](https://www.cnsa.gov.cn/n6758968/n6758972/c6798636/content.html)", "questions": [ { "text": "Which recoverable-satellite missions can be assigned specifically to CZ-2A under the adopted naming boundary?", "kind": "provenance", "id": "recoverable-satellite-association-q01" }, { "text": "Where does launcher delivery end and the satellite's independent orbital and recovery mission begin?", "kind": "boundary", "id": "recoverable-satellite-association-q02" } ] } ] }, { "id": "capacity-and-accommodation", "name": "Capacity and accommodation", "description": "Express capability as a payload-orbit-interface combination.", "findings": [ { "id": "qualified-payload-envelope", "name": "Qualified payload envelope", "description": "Distinguish demonstrated payload delivery from rated capacity and account for adapter and fairing constraints.", "questions": [ { "text": "What payload mass is supported at a specified orbit and inclination, and is it demonstrated or calculated?", "kind": "measurement", "id": "qualified-payload-envelope-q01" }, { "text": "What evidence establishes the CZ-2A fairing envelope, adapter interface and separation compatibility for a proposed historical payload?", "kind": "action", "id": "qualified-payload-envelope-q02" } ] } ] } ] }, { "id": "control-and-assurance", "name": "Control and assurance", "description": "Capture evidence needed to understand flight control, separation and launch readiness.", "rationale": "A propulsion specification alone cannot explain whether the vehicle could complete its delivery sequence.", "layers": [ { "id": "guidance-and-sequencing", "name": "Guidance and sequencing", "description": "Identify the control chain and event sequence at a functional level.", "findings": [ { "id": "control-chain-evidence", "name": "Control-chain evidence", "description": "Associate guidance sensors, electrical power, control links and separation functions with a documented vehicle baseline.", "questions": [ { "text": "Which guidance, attitude-control and electrical-power arrangements are established for CZ-2A?", "kind": "provenance", "id": "control-chain-evidence-q01" }, { "text": "Which documented event confirmations distinguish stage separation, upper-stage operation and payload release?", "kind": "definition", "id": "control-chain-evidence-q02" } ] } ] }, { "id": "historical-acceptance", "name": "Historical acceptance", "description": "Locate the actual acceptance and ground-support requirements applicable to this vehicle.", "findings": [ { "id": "readiness-and-hazard-evidence", "name": "Readiness and hazard evidence", "description": "Require period-specific evidence for acceptance tests, ground interfaces and safety provisions rather than assigning modern certification marks.", "questions": [ { "text": "Which organizations issued the applicable CZ-2A acceptance requirements, and what surviving documents identify their scope?", "kind": "provenance", "id": "readiness-and-hazard-evidence-q01" }, { "text": "What documented evidence would support a claim that a surviving article has been drained, depressurized and rendered inert?", "kind": "action", "id": "readiness-and-hazard-evidence-q02" } ] } ] } ] }, { "id": "flight-record-and-legacy", "name": "Flight record and legacy", "description": "Make historical outcomes and surviving-object claims auditable.", "rationale": "A small, inconsistently labelled flight record makes attribution errors especially consequential.", "layers": [ { "id": "outcome-accounting", "name": "Outcome accounting", "description": "Build statistics from individually attributed launches and defined outcome criteria.", "findings": [ { "id": "attribution-sensitive-flight-record", "name": "Attribution-sensitive flight record", "description": "Keep launch success, orbital insertion and satellite recovery separate, and retain alternative variant assignments where evidence conflicts.", "questions": [ { "text": "Does the adopted CZ-2A boundary include the November 1974 launch attempt, and which evidence justifies that decision?", "kind": "boundary", "id": "attribution-sensitive-flight-record-q01" }, { "text": "For each included flight, what evidence establishes its date, vehicle identity and launcher outcome independently of payload recovery?", "kind": "provenance", "id": "attribution-sensitive-flight-record-q02" } ] } ] }, { "id": "retirement-and-survivors", "name": "Retirement and survivors", "description": "Separate the end of the vehicle programme from the condition of any remaining hardware.", "findings": [ { "id": "legacy-object-authentication", "name": "Legacy object authentication", "description": "Distinguish original flight or test hardware, composite exhibits and replicas before transferring type-level properties to a physical object.", "questions": [ { "text": "Which records establish the final CZ-2A production and flight dates under the adopted designation boundary?", "kind": "provenance", "id": "legacy-object-authentication-q01" }, { "text": "What serial, construction or custody evidence is required to classify an exhibit as authentic CZ-2A hardware?", "kind": "action", "id": "legacy-object-authentication-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": [ "Historical sources may call the initial vehicle Long March 2 or CZ-2 rather than Long March 2A; verify how the registry distinguishes these designations.", "Exact dimensions, payload capacity, engine designations and flight counts are omitted pending verification.", "This description is based on recall; no sources were consulted." ], "questions": [ { "id": "evidence-confidence-notes-q01", "text": "Which of these check these first hold for the sense of Long March 2A 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": "Chinese launch-vehicle designation", "value_or_pattern": "CZ-2A", "note": "CZ abbreviates Chang Zheng, rendered in English as Long March." }, { "scheme": "English launch-vehicle designation", "value_or_pattern": "LM-2A", "note": "English abbreviation of Long March 2A." } ], "questions": [ { "id": "evidence-identifiers-q01", "text": "Which of these identifiers and schemes hold for the sense of Long March 2A 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": [ "Launching early Chinese Fanhui Shi Weixing (FSW) recoverable reconnaissance satellites.", "Providing orbital launch capability from the Jiuquan launch site." ], "questions": [ { "id": "evidence-real-world-use-q01", "text": "Which of these real-world use hold for the sense of Long March 2A 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": "Number of propulsion stages", "typical_range": "2", "unit": "stage" } ], "questions": [ { "id": "evidence-measurements-q01", "text": "Which of these typical measurements hold for the sense of Long March 2A 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 unsymmetrical dimethylhydrazine fuel and nitrogen tetroxide oxidizer present severe toxicity and chemical exposure hazards.", "The hypergolic propellants ignite on contact, making leaks and unintended mixing fire and explosion hazards.", "Guidance, propulsion or stage-separation failure can prevent orbital insertion and cause loss of the payload.", "Expended stages and launch failures create falling-debris hazards." ], "questions": [ { "id": "evidence-failure-modes-and-hazards-q01", "text": "Which of these failure modes and hazards hold for the sense of Long March 2A this model covers, and on what evidence?", "kind": "provenance" } ] }, { "id": "evidence-regional-variation", "name": "Regional variation", "description": "Recalled without web access and unsourced; every item is a lead to verify.", "evidence": [ "Chang Zheng 2A, CZ-2A and Long March 2A are Chinese romanized and English naming forms for the same vehicle designation." ], "questions": [ { "id": "evidence-regional-variation-q01", "text": "Which of these regional variation hold for the sense of Long March 2A 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": "Long March 2 family", "difference": "The family encompasses several launch-vehicle variants; Long March 2A identifies an early member." }, { "name": "Long March 2C", "difference": "A subsequent launch-vehicle variant with its own configuration and flight history." }, { "name": "DF-5", "difference": "An intercontinental ballistic missile that supplied the technological basis, rather than an orbital satellite launcher." }, { "name": "Fanhui Shi Weixing", "difference": "The recoverable satellite payload series, rather than the rocket carrying it." } ], "questions": [ { "id": "evidence-neighbours-q01", "text": "Which of these neighbouring kinds and how to tell them apart hold for the sense of Long March 2A this model covers, and on what evidence?", "kind": "provenance" } ] } ] } ] } ] }, "openQuestions": [ "Was CZ-2A a formal contemporary designation, and does this registry entry include the original CZ-2 flight attempt of November 1974?", "Which primary records establish the exact engine revisions, dimensions and mass breakdown without importing CZ-2C specifications?", "What reference orbit, payload accounting and interface limits support the capacity figures attributed to CZ-2A?", "Which original failure-investigation and acceptance documents substantiate control-system changes and applicable safety requirements?", "What evidence establishes retirement dates and the existence, authenticity and inert condition of surviving CZ-2A hardware?" ], "statistics": { "bundles": 6, "layers": 11, "findings": 17, "questions": 27 } }