{ "vercy": "1.0-draft", "publication": { "status": "research-draft", "adjudicationStatus": "unreviewed", "publishableCanonical": false, "generatedAt": "2026-09-12T08:18:55Z", "providers": [ "Codex" ], "breadth": "recalled by Codex without web access - no source was read", "missingProviders": [], "pass": 2, "cost": { "grok": { "seconds": 19.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: 01a094b1-8b20-75f3-a02b-c770a6486733\n--------\nuser\nDescribe what is already known about one registered thing. Answer as JSON only, no prose around it.\n\nThing: C-9\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 registered ", "usd": 0.0, "recall": true }, "codex": { "seconds": 78.5, "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: 01a094b1-8a5a-7363-9f7e-61108cbca5ff\n--------\nuser\nYou are drafting a Vercy meta-model for one registered thing. Answer as JSON only, no prose around it.\n\nThing: C-9\nRegistry id: vr.tr.c-9\nPlane / domain: PHY / PHY.OBJ\nRegistry definition: (none recorded)\nNames folded into this entry: (none)\n\n\nContext for this" } }, "enrichment": { "pass": 3, "engine": "claude", "producedAt": "2026-10-06T12:00:00Z", "ingestedAt": "2026-10-06T08:41:21+00:00", "fields": [ "agent_conduct", "ethics", "failure_modes_and_hazards", "owners", "visual_identification" ] }, "gate": { "passed": true, "version": "1.0", "at": "2026-10-07T10:10:30+00:00", "evidence": [ "completeness 1.00", "sense: Wikidata description", "2 live sources", "review by codex: pass" ] } }, "metaModel": { "id": "THING-Q3686766", "registryId": "vr.tr.c-9", "name": "C-9", "version": "0.1.0-research.1", "entryKind": "thing", "family": "Thing Registry", "domain": [ "PHY.OBJ" ], "status": "research-draft" }, "canonicalUrl": "https://ver.cy/models/thing/q3686766/", "model": { "registry_id": "vr.tr.c-9", "name": "C-9", "purpose": "Enable an agent to recognise a C-9 aircraft, distinguish its variant and configuration, assess its recorded condition, and identify the evidence needed for an intended transport role.", "definition": "C-9 is a United States military aircraft designation for adaptations of the McDonnell Douglas DC-9 twin-engine jet airliner used for aeromedical evacuation and transport.", "scope_statement": "Provisionally interpret vr.tr.c-9 as the McDonnell Douglas C-9 military aircraft family derived from the DC-9, pending confirmation of the registry's source identifier; this model owns family-specific recognition, configuration, operating constraints and condition evidence, while referencing individual aircraft records.", "in_scope": [ "C-9 designation evidence, manufacturer lineage and variant identification", "Variant-specific passenger, cargo, aeromedical and special-mission configurations", "Installed propulsion, cabin systems and loading interfaces", "Configuration-dependent payload, balance and operating limitations", "Aircraft condition, maintenance evidence and authorized uses" ], "out_of_scope": [ "Other objects or aircraft assigned the designation C-9 under different naming systems", "The complete civil DC-9 family and its airline operations", "Individual aircraft identity, ownership and maintenance logs as independently maintained records", "Patient diagnosis, treatment and clinical transport decisions", "Airport infrastructure, air traffic control and flight-crew qualification models" ], "distinguishing_features": [ "Require designation or manufacturer records establishing the military C-9 relationship to the DC-9; a similar appearance or a name containing '9' is insufficient. [NASA C-9B](https://espo.nasa.gov/aircraft/C-9B)", "Use twin jet engines, swept wings and a T-tail as supporting recognition features, then require documentary identification because the civil DC-9 shares the family appearance. [US Air Force C-9 description](https://www.af.mil/News/Article-Display/Article/133275/historic-c-9-heads-to-andrews-for-retirement/)", "Distinguish the C-9A aeromedical role from other C-9 configurations using the variant designation and installed patient-handling equipment. [Air Force Medical Service C-9A history](https://www.airforcemedicine.af.mil/News/Display/Article/1459865/the-cadillac-of-medevac-the-c9as-lasting-mark-on-the-aeromedical-evacuation-sys/)", "Recognise Skytrain II as the Navy's C-9B variant name; do not use that name as proof that every C-9 has the same cabin equipment or mission. [NAVAIR C-9 history](https://www.navair.navy.mil/node/21446)" ], "characteristics": [ { "name": "Designation and identification confidence", "kind": "category", "unit_or_values": "Recorded designation, naming authority and era; confirmed, provisional or conflicting", "why_it_matters": "The registry supplies neither a definition nor a source identifier, so the aircraft interpretation must remain explicit." }, { "name": "Variant and parent design", "kind": "relation", "unit_or_values": "Documented C-9 variant linked to its applicable DC-9 design baseline", "why_it_matters": "Determines which technical documents and mission capabilities apply." }, { "name": "Installed cabin configuration", "kind": "category", "unit_or_values": "Passenger, cargo, aeromedical, mixed or documented special configuration", "why_it_matters": "An aircraft's designation alone does not establish its present carrying capability." }, { "name": "Approved occupant and patient capacity", "kind": "measurement", "unit_or_values": "Number of crew positions, passenger seats, litter positions and ambulatory-patient positions, per approved layout", "why_it_matters": "Prevents combining capacities from incompatible cabin arrangements." }, { "name": "Mass and centre-of-gravity limits", "kind": "measurement", "unit_or_values": "kg or lb; centre of gravity in percent mean aerodynamic chord or the manual's specified datum", "why_it_matters": "A proposed load must satisfy the applicable configuration's weight and balance limits." }, { "name": "Loading geometry and restraint limits", "kind": "measurement", "unit_or_values": "Door clearances in mm or in; floor loading in kPa or lb/ft²; restraint ratings in the approved document's units", "why_it_matters": "Cargo or patient equipment must fit the loading path and have an approved restraint arrangement." }, { "name": "Installed engine configuration", "kind": "relation", "unit_or_values": "Engine model, installation approval and applicable operating-limit document", "why_it_matters": "Performance and maintenance requirements must follow the installed equipment." }, { "name": "Mission performance basis", "kind": "measurement", "unit_or_values": "Range in nmi or km; runway requirement in m or ft, with payload, fuel, weather and runway assumptions", "why_it_matters": "A family-level headline range cannot establish suitability for a particular flight." }, { "name": "Technical and operational disposition", "kind": "state", "unit_or_values": "Unknown, serviceable, restricted, maintenance, stored, retired or static display; dated authority evidence recorded separately", "why_it_matters": "Physical presence and historical capability do not establish permission or readiness to fly." } ], "affordances": [ "Classify a candidate aircraft against documented C-9 identity and variant evidence.", "Compare an installed cabin layout with a proposed passenger, cargo or aeromedical requirement.", "Screen proposed loads against documented access, restraint, weight and balance constraints.", "Identify configuration-specific technical manuals and unresolved maintenance dependencies.", "Flag missing evidence that prevents recommending flight, loading, conversion or ground handling.", "Separate historical mission capability from the aircraft's currently documented permitted uses." ], "agent_conduct": { "may": [ "Identify a C-9 aircraft and its variant from serial number and documentation.", "Report its configuration and status from official records." ], "must_not": [ "Recommend flight, loading or patient transport without current airworthiness and configuration records.", "Make clinical decisions about patients transported on board.", "Confuse the C-9 designation with unrelated uses of the same code.", "Share operational details of military flights beyond public records." ], "requires_human": [ "Approving the aircraft for an aeromedical mission or a conversion.", "Any decision about moving a patient by air." ] }, "ethics": { "considerations": [ "Aeromedical evacuation carries sick and wounded people whose lives depend on safe operation.", "Military flight details can put crews and passengers at risk if disclosed." ], "affected_parties": [ "Patients and medical crews", "Aircrew", "Service members" ] }, "owners": { "steward": "The military operator; the national military aircraft register holds its record.", "master_systems": [ "Military aircraft serial registers" ] }, "visual_identification": [ "A twin-jet airliner shape with engines mounted on the rear fuselage and a T-tail.", "Military markings and serial numbers, and on aeromedical versions red cross markings.", "A large forward cargo door on some variants." ], "failure_modes_and_hazards": [ "Ageing airframes need strict maintenance to stay airworthy.", "Improperly secured medical equipment or litters can endanger patients." ], "what_it_is_for": [ "The C-9 family served military aeromedical evacuation and passenger or logistical transport roles.", "Historical records, preserved aircraft and maintenance documentation distinguish medical evacuation configurations from other transport variants." ], "standards_and_regulation": [ "The United States Department of Defense Mission Design Series designation system classifies C-9 aircraft within the cargo and transport mission category." ] }, "sources": [ { "id": "wikidata", "title": "Wikidata item Q3686766: C-9", "url": "https://www.wikidata.org/wiki/Q3686766", "url_status": "live", "what_it_supports": "identity and sense of the item", "checked_by": "wikidata-api" }, { "id": "wikipedia-en", "title": "Wikipedia: McDonnell Douglas C-9", "url": "https://en.wikipedia.org/wiki/McDonnell_Douglas_C-9", "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 C-9 means and identify the applicable aircraft variant.", "rationale": "A short designation without a registry definition cannot safely determine technical applicability.", "layers": [ { "id": "registry-referent", "name": "Registry referent", "description": "Connect the registry label to a documented aircraft concept.", "findings": [ { "id": "designation-resolution", "name": "Designation resolution", "description": "Treat the McDonnell Douglas interpretation as provisional until the registry source confirms it.", "questions": [ { "text": "Which source identifier and designation authority establish what vr.tr.c-9 denotes?", "kind": "provenance", "id": "designation-resolution-q01" }, { "text": "Does this entry denote the C-9 family, a particular variant, or a different use of C-9?", "kind": "boundary", "id": "designation-resolution-q02" } ] } ] }, { "id": "variant-applicability", "name": "Variant applicability", "description": "Associate a recognized C-9 variant with its design baseline and technical evidence.", "findings": [ { "id": "variant-evidence", "name": "Variant evidence", "description": "Keep variant designation, popular name and installed modifications separately identifiable.", "questions": [ { "text": "Which records establish the variant and its relationship to the underlying DC-9 design?", "kind": "provenance", "id": "variant-evidence-q01" }, { "text": "Which capabilities belong to that variant, and which require an additional documented modification?", "kind": "boundary", "id": "variant-evidence-q02" } ] } ] } ] }, { "id": "transport-cabin-and-loading", "name": "Transport cabin and loading", "description": "Describe the approved carrying arrangement and the physical path for loading it.", "rationale": "C-9 mission suitability depends on the installed layout and loading provisions.", "layers": [ { "id": "occupant-and-patient-layout", "name": "Occupant and patient layout", "description": "Identify seating, patient positions and mission-equipment dependencies.", "findings": [ { "id": "approved-cabin-arrangement", "name": "Approved cabin arrangement", "description": "Record each approved layout without merging passenger and patient maxima.", "questions": [ { "text": "How many seats, litter positions and attendant positions are approved in the installed arrangement?", "kind": "measurement", "id": "approved-cabin-arrangement-q01" }, { "text": "Which oxygen, electrical, access and restraint provisions must be verified before accepting a proposed aeromedical fit?", "kind": "action", "id": "approved-cabin-arrangement-q02" } ] } ] }, { "id": "cargo-access-and-restraint", "name": "Cargo access and restraint", "description": "Relate payload dimensions and mass to actual door, floor and attachment provisions.", "findings": [ { "id": "load-path-compatibility", "name": "Load-path compatibility", "description": "Require configuration-specific evidence for loading and securing cargo or mission equipment.", "questions": [ { "text": "What door openings, loading heights and interior clearances constrain the proposed load?", "kind": "measurement", "id": "load-path-compatibility-q01" }, { "text": "Which approved floor limits and restraint arrangements apply to its mass and position?", "kind": "provenance", "id": "load-path-compatibility-q02" } ] } ] } ] }, { "id": "flight-envelope-and-systems", "name": "Flight envelope and systems", "description": "Connect installed aircraft systems with the limits governing a proposed transport mission.", "rationale": "A C-9 family's published capability cannot replace variant- and condition-specific performance evidence.", "layers": [ { "id": "propulsion-and-cabin-services", "name": "Propulsion and cabin services", "description": "Identify installed engines and the systems supporting flight and cabin use.", "findings": [ { "id": "installed-system-baseline", "name": "Installed system baseline", "description": "Tie propulsion, pressurization and cabin-service capability to applicable configuration documents.", "questions": [ { "text": "Which engine models and approved modifications define the aircraft's performance baseline?", "kind": "provenance", "id": "installed-system-baseline-q01" }, { "text": "Which cabin-pressure, electrical or environmental limitations constrain the intended passenger or patient mission?", "kind": "action", "id": "installed-system-baseline-q02" } ] } ] }, { "id": "payload-fuel-and-runway", "name": "Payload, fuel and runway", "description": "Record the coupled constraints on load, fuel and airfield suitability.", "findings": [ { "id": "mission-envelope-evidence", "name": "Mission envelope evidence", "description": "Keep performance values attached to their flight-manual assumptions and revision.", "questions": [ { "text": "What mass, balance and fuel limits apply to the proposed cabin layout and load?", "kind": "measurement", "id": "mission-envelope-evidence-q01" }, { "text": "Which approved performance data support the required route and runway under the stated conditions?", "kind": "provenance", "id": "mission-envelope-evidence-q02" } ] } ] } ] }, { "id": "continued-use-and-disposition", "name": "Continued use and disposition", "description": "Assess whether a particular C-9 can support the intended activity using dated technical and authority records.", "rationale": "Historical transport capability, maintenance condition and permission to operate must be evaluated separately.", "layers": [ { "id": "airframe-and-equipment-condition", "name": "Airframe and equipment condition", "description": "Connect accumulated usage and recorded defects to applicable inspection and maintenance requirements.", "findings": [ { "id": "maintenance-applicability", "name": "Maintenance applicability", "description": "Identify relevant structural, engine and mission-equipment obligations without asserting undocumented defects.", "questions": [ { "text": "What recorded flight hours, cycles, storage history and inspection results determine the applicable C-9 maintenance tasks?", "kind": "measurement", "id": "maintenance-applicability-q01" }, { "text": "Which unresolved defects, life limits or mandatory instructions restrict the intended use?", "kind": "action", "id": "maintenance-applicability-q02" } ] } ] }, { "id": "authority-and-lifecycle-state", "name": "Authority and lifecycle state", "description": "Distinguish flight authorization from storage, preservation and display status.", "findings": [ { "id": "permitted-use-evidence", "name": "Permitted-use evidence", "description": "Require current, operator-specific evidence before recommending an operational action.", "questions": [ { "text": "Which military or civil authority, governing documents and release records apply to this aircraft's present operation?", "kind": "provenance", "id": "permitted-use-evidence-q01" }, { "text": "Does its documented disposition permit flight, ground operation, towing, cabin access or static display only?", "kind": "action", "id": "permitted-use-evidence-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 registry supplies no sense or aliases; the aircraft interpretation is plausible but must be checked against the originating registry record because C-9 is an ambiguous designation.", "These statements are recalled knowledge, not researched findings.", "Dimensions, capacities, operating limits and applicable requirements should be checked for the specific variant and configuration." ], "questions": [ { "id": "evidence-confidence-notes-q01", "text": "Which of these check these first hold for the sense of C-9 this model covers, and on what evidence?", "kind": "provenance" } ] }, { "id": "evidence-kinds", "name": "Kinds and varieties", "description": "Recalled without web access and unsourced; every item is a lead to verify.", "evidence": [ "C-9A Nightingale", "C-9B Skytrain II" ], "questions": [ { "id": "evidence-kinds-q01", "text": "Which of these kinds and varieties hold for the sense of C-9 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": "United States military Mission Design Series (MDS)", "value_or_pattern": "C-9", "note": "Identifies an aircraft design family; suffixes such as A and B distinguish variants, while individual aircraft have separate serial numbers." } ], "questions": [ { "id": "evidence-identifiers-q01", "text": "Which of these identifiers and schemes hold for the sense of C-9 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": [ "Military aeromedical evacuation", "Military personnel transport", "Military cargo and logistics transport" ], "questions": [ { "id": "evidence-real-world-use-q01", "text": "Which of these real-world use hold for the sense of C-9 this model covers, and on what evidence?", "kind": "provenance" } ] }, { "id": "evidence-failure-modes-and-hazards", "name": "Failure modes and hazards", "description": "Recalled without web access and unsourced; every item is a lead to verify.", "evidence": [ "Engine failure or loss of thrust", "Structural fatigue and corrosion in aging airframes", "Loss of cabin pressurization at altitude", "Incorrect loading or cargo restraint affecting balance and flight safety" ], "questions": [ { "id": "evidence-failure-modes-and-hazards-q01", "text": "Which of these failure modes and hazards hold for the sense of C-9 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": "McDonnell Douglas DC-9", "difference": "The DC-9 is the parent commercial airliner family; C-9 denotes military adaptations." }, { "name": "C-9A Nightingale", "difference": "A particular C-9 variant configured for aeromedical evacuation." }, { "name": "C-9B Skytrain II", "difference": "A particular C-9 variant used for military passenger and cargo transport." } ], "questions": [ { "id": "evidence-neighbours-q01", "text": "Which of these neighbouring kinds and how to tell them apart hold for the sense of C-9 this model covers, and on what evidence?", "kind": "provenance" } ] } ] } ] } ] }, "openQuestions": [ "Does the registry's original source identify the McDonnell Douglas C-9, and what is that source's persistent identifier?", "Does an existing Vercy world model already own this aircraft concept, requiring a link instead of a second model?", "Which variants, including any VC-prefixed derivatives, belong within this registry entry's authoritative boundary?", "Which authoritative manuals establish variant-specific dimensions, capacities, engine installations, performance limits and approved cabin arrangements?", "Which operator-specific maintenance programs, mandatory instructions and operating authorities govern any individual aircraft being assessed?" ], "statistics": { "bundles": 5, "layers": 9, "findings": 14, "questions": 22 } }