{ "vercy": "1.0-draft", "publication": { "status": "research-draft", "adjudicationStatus": "unreviewed", "publishableCanonical": false, "generatedAt": "2026-09-12T08:48:11Z", "providers": [ "Codex" ], "breadth": "recalled by Codex without web access - no source was read", "missingProviders": [], "pass": 2, "cost": { "grok": { "seconds": 19.9, "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: 01a094cc-4e50-7c13-9193-e6df6774981b\n--------\nuser\nDescribe what is already known about one registered thing. Answer as JSON only, no prose around it.\n\nThing: common berthing mechanism\nSense to describe: (none recorded)\nDomain code: PHY.OBJ\nAlso known as: (none)\n\n\nContext for this batch of 1001 things:\n# Batch", "usd": 0.0, "recall": true }, "codex": { "seconds": 79.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: 01a094cc-4e5d-7370-997e-2cbfea98380b\n--------\nuser\nYou are drafting a Vercy meta-model for one registered thing. Answer as JSON only, no prose around it.\n\nThing: common berthing mechanism\nRegistry id: vr.tr.common-berthing-mechanism\nPlane / domain: PHY / PHY.OBJ\nRegistry definition: (none recorded)\nNames folde" } }, "enrichment": { "pass": 3, "engine": "claude", "producedAt": "2026-10-06T12:00:00Z", "ingestedAt": "2026-10-06T08:53:40+00:00", "fields": [ "agent_conduct", "ethics", "failure_modes_and_hazards", "owners", "visual_identification" ] }, "gate": { "passed": true, "version": "1.0", "at": "2026-10-07T10:10:25+00:00", "evidence": [ "completeness 1.00", "sense: Wikidata description", "2 live sources", "review by codex: pass" ] } }, "metaModel": { "id": "THING-Q1116068", "registryId": "vr.tr.common-berthing-mechanism", "name": "common berthing mechanism", "version": "0.1.0-research.1", "entryKind": "thing", "family": "Thing Registry", "domain": [ "PHY.OBJ" ], "status": "research-draft" }, "canonicalUrl": "https://ver.cy/models/thing/q1116068/", "model": { "registry_id": "vr.tr.common-berthing-mechanism", "name": "common berthing mechanism", "purpose": "Enable an AI agent to recognize a Common Berthing Mechanism interface, assess its mating and pressure-boundary state, and identify which berthing, inspection, or release actions its verified configuration permits.", "definition": "The Common Berthing Mechanism (CBM) is a paired active-passive interface used on the International Space Station to capture, bolt together and seal pressurized modules or visiting spacecraft positioned by a robotic arm.", "scope_statement": "This model owns the Common Berthing Mechanism kind registered as vr.tr.common-berthing-mechanism in PHY / PHY.OBJ, including complementary active and passive assemblies, their capture and structural connection, sealing interface, and operational evidence; individual installations supply configuration-specific values.", "in_scope": [ "Active and passive CBM identities, mating geometry, and compatibility evidence", "Alignment features, capture latches, powered bolts, and their mating fittings", "Structural joint condition, bolt engagement, and verified load capability", "Mating seals, interface leakage, and pressure-boundary readiness", "Electrical actuation, state sensing, command prerequisites, and fault recovery", "Inspection, qualification, maintenance, and mating-cycle history" ], "out_of_scope": [ "The robotic manipulator, its grapple fixture, and spacecraft approach navigation", "Complete spacecraft or station-module structure and life-support systems", "Hatch mechanisms and their independent opening or closure authority", "Docking mechanisms from other interface families, including adapters as complete products", "Intermodule utility connections beyond their effect on CBM readiness", "A particular manufacturer's product record or an individual flight unit as the definition of the kind" ], "distinguishing_features": [ "Identify the specific CBM interface family through controlled drawings or interface documentation; the ability to join spacecraft is insufficient.", "Check for complementary active and passive halves rather than assuming two identical interfaces can mate.", "Distinguish robot-positioned berthing from a mechanism intended to capture an independently approaching spacecraft.", "For the documented ISS configuration, check for four capture latches followed by engagement of 16 powered bolts. [JAXA CBM acceptance-test description](https://iss.jaxa.jp/iss/kibo/develop_status_17_e.html)", "Distinguish the module-to-module berthing joint from the hatch that closes the passage through that joint." ], "characteristics": [ { "name": "Assembly role", "kind": "category", "unit_or_values": "active CBM | passive CBM | identified mated pair", "why_it_matters": "Determines which actuators, mating fittings, and operational responsibilities the record describes." }, { "name": "Interface configuration", "kind": "relation", "unit_or_values": "controlled drawing revision, applicable interface document, counterpart configuration", "why_it_matters": "Makes compatibility an evidenced relationship rather than an inference from the CBM name." }, { "name": "Capture geometry", "kind": "measurement", "unit_or_values": "translation in mm and angular offset in degrees, relative to a named interface frame", "why_it_matters": "Allows comparison with configuration-specific alignment and capture limits." }, { "name": "Capture-latch condition", "kind": "state", "unit_or_values": "per latch: position indication, engagement evidence, fault status, observation time", "why_it_matters": "Separates successful initial capture from an incomplete or uncertain latch sequence." }, { "name": "Structural-bolt condition", "kind": "state", "unit_or_values": "per bolt: engagement, preload acceptance, sensor validity, fault status", "why_it_matters": "A single overall connected flag can conceal an incomplete structural joint." }, { "name": "Bolt preload", "kind": "measurement", "unit_or_values": "N per bolt, with measurement or estimation method and allowable range", "why_it_matters": "Supports assessment of structural fastening without treating a commanded tightening operation as proof." }, { "name": "Joint load envelope", "kind": "measurement", "unit_or_values": "forces in N and moments in N·m, with reference axes and combined-load criteria", "why_it_matters": "Relates the verified joint configuration to the loads permitted during subsequent operations." }, { "name": "Seal verification", "kind": "state", "unit_or_values": "untested | accepted | failed | indeterminate, with test record and validity conditions", "why_it_matters": "Keeps mechanical attachment distinct from evidence of pressure integrity." }, { "name": "Interface pressure differential", "kind": "measurement", "unit_or_values": "Pa between explicitly identified volumes", "why_it_matters": "Supports pressure-related readiness decisions without confusing vestibule, cabin, and external pressure." }, { "name": "Actuation supply", "kind": "measurement", "unit_or_values": "V and A at the specified electrical interface, with supply availability", "why_it_matters": "Identifies whether commanded latch and bolt operations have their required electrical support." }, { "name": "Thermal condition", "kind": "measurement", "unit_or_values": "°C at identified ring, seal, or actuator locations; temperature differences in K", "why_it_matters": "Allows assessment against configuration-specific mating and operating limits." }, { "name": "Mating and exposure history", "kind": "relation", "unit_or_values": "dated mating cycles, inspections, storage or orbital exposure, repairs, and anomalies", "why_it_matters": "Connects present readiness to accumulated wear and environmental exposure." } ], "affordances": [ "Match an active assembly to a documented compatible passive counterpart.", "Assess capture readiness from alignment, mechanism indications, and external manipulator readiness.", "Track capture and structural fastening as separate, evidenced milestones.", "Evaluate pressure-boundary readiness from applicable seal tests and pressure measurements.", "Identify applicable hold, inspection, or recovery procedures when latch, bolt, or sensor evidence disagrees.", "Assess release prerequisites and remaining life from the installed configuration and maintenance history." ], "agent_conduct": { "may": [ "Describe the common berthing mechanism and its role on the space station from official sources.", "Report publicly released berthing events and mission records." ], "must_not": [ "Disclose non-public engineering, operational or security details of the mechanism.", "Present speculation about failures or leaks as confirmed.", "Help interfere with spacecraft operations or their ground systems." ], "requires_human": [ "Any request involving operation or analysis of a live berthing." ] }, "ethics": { "considerations": [ "A sealed berth keeps the crew alive; a failure endangers lives.", "Public accounts of space incidents should be accurate and not alarmist." ], "affected_parties": [ "Space station crews", "Mission teams", "The public" ] }, "owners": { "steward": "The space station partner agencies that operate the station.", "master_systems": [] }, "visual_identification": [ "A large ring with latches and bolts around a hatch, active on one side and passive on the other.", "Seen at module joints and on visiting cargo craft held by the station's robotic arm." ], "failure_modes_and_hazards": [ "Seal damage or debris can cause air leaks.", "Bolt or latch faults can prevent safe capture or release." ], "what_it_is_for": [ "This mechanism connects compatible pressurized modules and visiting spacecraft within an orbital station.", "A robotic arm positions the mating interfaces before the mechanism secures and seals the connection.", "It supports a pressurized passage for crew and cargo transfer." ], "standards_and_regulation": [ "NASA-STD-5017, issued by the National Aeronautics and Space Administration, provides design and development requirements for spaceflight mechanisms of this type, subject to program applicability and tailoring." ] }, "sources": [ { "id": "wikidata", "title": "Wikidata item Q1116068: common berthing mechanism", "url": "https://www.wikidata.org/wiki/Q1116068", "url_status": "live", "what_it_supports": "identity and sense of the item", "checked_by": "wikidata-api" }, { "id": "wikipedia-en", "title": "Wikipedia: Common Berthing Mechanism", "url": "https://en.wikipedia.org/wiki/Common_Berthing_Mechanism", "url_status": "live", "what_it_supports": "general description of the item", "checked_by": "wikidata-api sitelink" } ], "structure": { "bundles": [ { "id": "cbm-identity-and-mating", "name": "CBM identity and mating", "description": "Establish which complementary CBM assemblies and interface configurations are being considered.", "rationale": "Recognition of the CBM family does not establish that a particular pair is ready or approved to mate.", "layers": [ { "id": "assembly-role-and-boundary", "name": "Assembly role and boundary", "description": "Separate the mechanism half, the complete mating interface, and surrounding spacecraft equipment.", "findings": [ { "id": "active-passive-identity", "name": "Active and passive identity", "description": "The documented CBM architecture uses complementary active and passive mechanisms positioned for berthing by a remote manipulator. [NASA CBM design record](https://ntrs.nasa.gov/citations/19920015843)", "questions": [ { "text": "Does this record describe an active half, a passive half, or a particular mated pair?", "kind": "definition", "id": "active-passive-identity-q01" }, { "text": "Which components belong to the CBM rather than the host module, hatch, or robotic manipulator?", "kind": "boundary", "id": "active-passive-identity-q02" } ] } ] }, { "id": "pair-compatibility", "name": "Pair compatibility", "description": "Resolve counterpart geometry and configuration applicability.", "findings": [ { "id": "controlled-mating-interface", "name": "Controlled mating interface", "description": "Record compatibility evidence for the actual revisions, installation orientation, and available passage clearance.", "questions": [ { "text": "Which controlled interface documents and revisions establish that these two assemblies can mate?", "kind": "provenance", "id": "controlled-mating-interface-q01" }, { "text": "What mating datums, orientation constraints, and clear-opening dimensions apply to this pair?", "kind": "measurement", "id": "controlled-mating-interface-q02" } ] } ] } ] }, { "id": "alignment-and-capture", "name": "Alignment and capture", "description": "Represent the transition from externally supported positioning to confirmed capture.", "rationale": "A module positioned near the ring has not necessarily entered a valid capture condition.", "layers": [ { "id": "capture-envelope", "name": "Capture envelope", "description": "Connect interface pose and readiness indications to permission to begin capture.", "findings": [ { "id": "ready-to-latch-evidence", "name": "Ready-to-latch evidence", "description": "JAXA describes a limit-switch readiness indication before capture-latch operation; applicable limits and decision logic need configuration-specific evidence. [JAXA CBM acceptance-test description](https://iss.jaxa.jp/iss/kibo/develop_status_17_e.html)", "questions": [ { "text": "What translational, angular, and relative-motion limits define the approved capture envelope?", "kind": "measurement", "id": "ready-to-latch-evidence-q01" }, { "text": "Which readiness indications and manipulator conditions must be verified before latch motion is permitted?", "kind": "action", "id": "ready-to-latch-evidence-q02" } ] } ] }, { "id": "capture-completion", "name": "Capture completion", "description": "Determine whether latch engagement supports the next connection stage.", "findings": [ { "id": "latch-by-latch-confirmation", "name": "Latch-by-latch confirmation", "description": "Record each latch's engagement evidence and the criteria for transferring support responsibilities.", "questions": [ { "text": "What observations distinguish an extended latch, an engaged latch, and a successfully completed capture?", "kind": "definition", "id": "latch-by-latch-confirmation-q01" }, { "text": "Which approved response applies if a latch stalls or capture indications disagree?", "kind": "action", "id": "latch-by-latch-confirmation-q02" } ] } ] } ] }, { "id": "structural-fastening-and-loads", "name": "Structural fastening and loads", "description": "Represent bolt engagement, accepted preload, and the resulting joint capability.", "rationale": "Capture alone does not establish the structural condition required for service.", "layers": [ { "id": "powered-bolt-closure", "name": "Powered-bolt closure", "description": "Track structural fastening independently of initial capture.", "findings": [ { "id": "bolt-engagement-and-preload", "name": "Bolt engagement and preload", "description": "Maintain individual bolt evidence, acceptance criteria, and any unresolved fastening anomaly.", "questions": [ { "text": "What engagement and preload evidence is required for each structural bolt?", "kind": "measurement", "id": "bolt-engagement-and-preload-q01" }, { "text": "Which approved tightening sequence and stop conditions apply when bolt behavior is abnormal?", "kind": "action", "id": "bolt-engagement-and-preload-q02" } ] } ] }, { "id": "joint-service-capability", "name": "Joint service capability", "description": "Relate fastening condition to permitted loads and operating conditions.", "findings": [ { "id": "accepted-load-path", "name": "Accepted load path", "description": "Record configuration-specific structural acceptance rather than inferring full capability from apparent closure.", "questions": [ { "text": "What combined force, moment, pressure, and thermal limits apply to the accepted joint?", "kind": "measurement", "id": "accepted-load-path-q01" }, { "text": "What engineering disposition, if any, permits operation with an unavailable bolt or unresolved preload indication?", "kind": "provenance", "id": "accepted-load-path-q02" } ] } ] } ] }, { "id": "sealing-and-pressure-readiness", "name": "Sealing and pressure readiness", "description": "Assess the mating seal and pressure evidence needed for use of the connected interface.", "rationale": "Structural fastening and pressure integrity require distinct evidence, while hatch actions remain externally governed.", "layers": [ { "id": "mating-seal-condition", "name": "Mating seal condition", "description": "Identify the installed sealing arrangement and its inspection criteria.", "findings": [ { "id": "seal-surface-acceptance", "name": "Seal-surface acceptance", "description": "The documented CBM connection includes a seal for airtightness; record the installed design and acceptance evidence rather than assuming a universal seal configuration. [JAXA CBM acceptance-test description](https://iss.jaxa.jp/iss/kibo/develop_status_17_e.html)", "questions": [ { "text": "Which seals and mating surfaces form the pressure boundary in this configuration?", "kind": "definition", "id": "seal-surface-acceptance-q01" }, { "text": "What inspection criteria govern debris, surface damage, seal degradation, and any protective hardware?", "kind": "action", "id": "seal-surface-acceptance-q02" } ] } ] }, { "id": "leak-and-pressure-verification", "name": "Leak and pressure verification", "description": "Connect test results to the correct interface volumes and operational handoffs.", "findings": [ { "id": "pressure-boundary-release-evidence", "name": "Pressure-boundary release evidence", "description": "Preserve the leak-test method, acceptance result, and pressure conditions supporting subsequent operations.", "questions": [ { "text": "Which test volumes, leakage limits, units, stabilization conditions, and measurement uncertainties apply?", "kind": "measurement", "id": "pressure-boundary-release-evidence-q01" }, { "text": "What verified CBM pressure-boundary evidence must be handed to hatch and vestibule procedures before they proceed?", "kind": "boundary", "id": "pressure-boundary-release-evidence-q02" } ] } ] } ] }, { "id": "control-recovery-and-reuse", "name": "Control, recovery, and reuse", "description": "Establish trustworthy mechanism state, allowable recovery, and readiness for later separation or mating.", "rationale": "Powered CBM operations depend on valid indications and configuration-specific procedures throughout the connection lifecycle.", "layers": [ { "id": "command-and-state-integrity", "name": "Command and state integrity", "description": "Separate requested actions from measured mechanical outcomes.", "findings": [ { "id": "verified-command-prerequisites", "name": "Verified command prerequisites", "description": "Associate each permitted mechanism transition with power, control authority, sensor validity, and applicable inhibits.", "questions": [ { "text": "Which electrical supply, controller configuration, and command authority apply to this installation?", "kind": "provenance", "id": "verified-command-prerequisites-q01" }, { "text": "Which transitions must be inhibited when indications are stale, contradictory, or unavailable?", "kind": "action", "id": "verified-command-prerequisites-q02" } ] } ] }, { "id": "separation-and-life-evidence", "name": "Separation and life evidence", "description": "Use service history and external readiness evidence to assess release and reuse.", "findings": [ { "id": "release-and-remating-readiness", "name": "Release and remating readiness", "description": "Record applicable separation prerequisites, approved anomaly recovery, and inspection or replacement requirements before reuse.", "questions": [ { "text": "What pressure, hatch, utility-clearance, and external-support confirmations are prerequisites for the approved unberthing procedure?", "kind": "action", "id": "release-and-remating-readiness-q01" }, { "text": "Which qualification records, cycle limits, exposure history, and post-anomaly inspections establish eligibility for another mating?", "kind": "provenance", "id": "release-and-remating-readiness-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 account is recalled knowledge, not a source-checked description.", "The passage dimension is nominal; usable clearance and interface dimensions should be checked against engineering drawings.", "Applicable interface-control documents, load ratings, leak limits and operating constraints require verification for the particular installation." ], "questions": [ { "id": "evidence-confidence-notes-q01", "text": "Which of these check these first hold for the sense of common berthing mechanism 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": [ "Active Common Berthing Mechanism (ACBM)", "Passive Common Berthing Mechanism (PCBM)" ], "questions": [ { "id": "evidence-kinds-q01", "text": "Which of these kinds and varieties hold for the sense of common berthing mechanism 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": [ "Joining pressurized modules in the International Space Station's United States Orbital Segment.", "Berthing robotically captured cargo spacecraft, including Cygnus, HTV and the first-generation Dragon.", "Providing a passage for crew and cargo transfer after the interface is sealed, checked and the hatches opened." ], "questions": [ { "id": "evidence-real-world-use-q01", "text": "Which of these real-world use hold for the sense of common berthing mechanism 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": "Nominal clear passage width and height", "typical_range": "Approximately 1.27 × 1.27", "unit": "m" }, { "quantity": "Powered structural bolts per active mechanism", "typical_range": "16", "unit": "bolts" }, { "quantity": "Capture latches per active mechanism", "typical_range": "4", "unit": "latches" } ], "questions": [ { "id": "evidence-measurements-q01", "text": "Which of these typical measurements hold for the sense of common berthing mechanism 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": [ "Misalignment during robotic positioning can prevent capture or damage mating hardware.", "Capture-latch or structural-bolt malfunction can prevent completion of the connection or subsequent separation.", "Contamination or damage to interface seals can cause pressure leakage.", "Electrical, sensing or control faults can interrupt the attachment sequence or prevent reliable verification of mechanism state.", "Opening hatches before leak checks and pressure equalization are complete can expose the crew to pressure hazards." ], "questions": [ { "id": "evidence-failure-modes-and-hazards-q01", "text": "Which of these failure modes and hazards hold for the sense of common berthing mechanism 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": "Docking mechanism", "difference": "A docking mechanism captures a spacecraft through its controlled approach; the CBM mates interfaces brought together by external robotic handling." }, { "name": "International Docking System Standard interface", "difference": "This specifies a docking interface distinct from the CBM; the two interfaces cannot mate directly." }, { "name": "Androgynous Peripheral Attach System", "difference": "APAS is a peripheral docking system; the CBM uses distinct active and passive halves for berthing." }, { "name": "Pressure hatch", "difference": "A hatch closes a passage, whereas the CBM structurally joins and seals the interface between two pressurized elements." } ], "questions": [ { "id": "evidence-neighbours-q01", "text": "Which of these neighbouring kinds and how to tell them apart hold for the sense of common berthing mechanism this model covers, and on what evidence?", "kind": "provenance" } ] } ] } ] } ] }, "openQuestions": [ "Which controlled NASA ISS program interface and verification documents, including revisions and issuing authorities, govern each operational CBM configuration?", "What are the configuration-specific clear-opening dimensions, capture envelope, electrical requirements, bolt preload targets, and combined structural and thermal limits?", "Which seal arrangements, leak-test acceptance criteria, and pressure-equalization dependencies apply to different installations?", "Which historical or proposed CBM variants belong within this registry entry, and how should their differences from operational ISS hardware be represented?", "What approved degraded-operation rules, recovery procedures, replaceable items, mating-cycle limits, and inspection intervals are supported by accessible engineering records?" ], "statistics": { "bundles": 6, "layers": 11, "findings": 16, "questions": 26 } }