{ "vercy": "1.0-draft", "publication": { "status": "research-draft", "adjudicationStatus": "unreviewed", "publishableCanonical": false, "generatedAt": "2026-09-12T11:47:13Z", "providers": [ "Codex" ], "breadth": "recalled by Codex without web access - no source was read", "missingProviders": [], "pass": 2, "cost": { "grok": { "seconds": 19.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: 01a09570-6c83-77b0-a511-9ede5c1b4c37\n--------\nuser\nDescribe what is already known about one registered thing. Answer as JSON only, no prose around it.\n\nThing: orbital ring\nSense to describe: (none recorded)\nDomain code: INF.MED\nAlso known as: (none)\n\n\nContext for this batch of 1001 things:\n# Batch 044: 1001 re", "usd": 0.0, "recall": true }, "codex": { "seconds": 65.3, "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: 01a09570-6c8c-7880-9010-5ec9753e6847\n--------\nuser\nYou are drafting a Vercy meta-model for one registered thing. Answer as JSON only, no prose around it.\n\nThing: orbital ring\nRegistry id: vr.tr.orbital-ring\nPlane / domain: INF / INF.MED\nRegistry definition: (none recorded)\nNames folded into this entry: (none)\n" } }, "enrichment": { "pass": 3, "engine": "claude", "producedAt": "2026-10-06T12:00:00Z", "ingestedAt": "2026-10-06T08:46:12+00:00", "fields": [ "agent_conduct", "ethics", "owners" ] }, "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-Q4235016", "registryId": "vr.tr.orbital-ring", "name": "orbital ring", "version": "0.1.0-research.1", "entryKind": "thing", "family": "Thing Registry", "domain": [ "INF.MED" ], "status": "research-draft" }, "canonicalUrl": "https://ver.cy/models/thing/q4235016/", "model": { "registry_id": "vr.tr.orbital-ring", "name": "orbital ring", "purpose": "Enable an AI agent to identify an orbital-ring proposal, assess its engineering and evidential maturity, and determine which comparisons or further investigations its claims support.", "definition": "An orbital ring is a proposed planet-encircling megastructure in which a rapidly circulating mass provides dynamic support for a surrounding structure that can remain stationary relative to the planet's surface.", "scope_statement": "This model owns orbital ring as a proposed planetary encircling infrastructure concept, including its architecture, support mechanism, interfaces and feasibility claims; this interpretation is provisional because the registry supplies no definition and classifies the entry under INF / INF.MED.", "in_scope": [ "Definition and boundaries of the orbital-ring concept", "Proposed ring geometry, moving components and supported structures", "Coupling between orbital motion, load support and ground access", "Construction, operation, failure and retirement scenarios", "Evidence, assumptions and unresolved feasibility claims" ], "out_of_scope": [ "Natural planetary rings and their constituent particles", "Independent satellite constellations without a continuous ring architecture", "Space elevators whose defining support mechanism is a tether extending beyond geostationary orbit", "Individual launch vehicles, payloads and spacecraft using the ring", "Fictional works, editions and media items depicting an orbital ring" ], "distinguishing_features": [ "The proposal describes an engineered structure or coupled system encircling a planetary body, rather than merely objects sharing an orbital region.", "Its architecture identifies how circumferential motion or another explicitly specified mechanism supports ring-associated loads.", "It distinguishes the motion of ring components from that of any supported platform, sheath or access connection.", "Any ground connection is an interface of the ring architecture, rather than sufficient evidence that the object is a conventional space elevator.", "A depiction of an orbital ring is evidence about a representation; it does not establish that the infrastructure exists." ], "characteristics": [ { "name": "Referent type", "kind": "category", "unit_or_values": "engineering concept | specific proposal | simulation | demonstrator | claimed installation | fictional representation | unresolved", "why_it_matters": "Prevents a conceptual design or depiction from being treated as an operating structure." }, { "name": "Central body", "kind": "relation", "unit_or_values": "identified planetary body with referenced gravity, radius and rotation assumptions", "why_it_matters": "Determines the environment within which geometry and support claims must be evaluated." }, { "name": "Ring geometry", "kind": "category", "unit_or_values": "specified path, plane, inclination, continuity and reference frame", "why_it_matters": "Makes competing architectures comparable and exposes incompatible assumptions about alignment." }, { "name": "Altitude profile", "kind": "measurement", "unit_or_values": "km above a named reference surface, including variation around the ring", "why_it_matters": "Conditions atmospheric interaction, ground access and clearance requirements." }, { "name": "Component velocity profile", "kind": "measurement", "unit_or_values": "m/s for each moving component in an explicitly named reference frame", "why_it_matters": "Connects proposed motion to support calculations, stored energy and coupling requirements." }, { "name": "Support architecture", "kind": "category", "unit_or_values": "proposal-specific description of moving mass, supported mass and force-transfer mechanism", "why_it_matters": "Identifies the mechanism that must explain how the ring carries its own structure and additional loads." }, { "name": "Supported load envelope", "kind": "measurement", "unit_or_values": "kg/m distributed load and N concentrated interface loads under stated operating conditions", "why_it_matters": "Distinguishes a nominal support claim from a usable capacity claim." }, { "name": "Validation maturity", "kind": "state", "unit_or_values": "asserted | analytically examined | simulated | component-tested | system-demonstrated; assessed separately by subsystem", "why_it_matters": "Prevents evidence for one component from being generalized to the complete ring." } ], "affordances": [ "Classify a candidate description as an orbital-ring proposal, neighbouring infrastructure concept or representation.", "Compare architectures using explicit geometry, reference frames and support assumptions.", "Trace capacity and feasibility claims to calculations, simulations or experiments.", "Identify missing interfaces and dependencies in construction and operating sequences.", "Evaluate proposed changes against declared load, energy and control envelopes.", "Select further research or testing that addresses a specific unresolved system dependency." ], "agent_conduct": { "may": [ "Explain the orbital ring concept and its proposed physics from published sources.", "Make clear that it is a proposal that has never been built." ], "must_not": [ "Present the orbital ring as an existing structure or an imminent project.", "Present speculative cost or performance figures as engineering fact.", "Use the idea to solicit investment in a project that does not exist." ], "requires_human": [ "Presenting the concept to decision-makers as a basis for public spending." ] }, "ethics": { "considerations": [ "Speculative megaprojects can mislead the public and investors.", "Honest framing keeps science fiction separate from engineering." ], "affected_parties": [ "Investors", "Readers and students" ] }, "owners": { "steward": "Nobody owns the concept; its proponents and the literature keep its record.", "master_systems": [] }, "what_it_is_for": [ "Orbital rings are encountered in speculative space infrastructure studies and discussions of future planetary transport.", "Proposals explore whether circulating mass could support stationary platforms and connections between a planet's surface and space.", "They are used to investigate engineering limits and compare proposed transport architectures." ], "standards_and_regulation": [ "The United Nations Outer Space Treaty provides the international legal framework for state responsibility and authorization of activities involving an orbital ring deployed in outer space." ], "failure_modes_and_hazards": [ "Loss of dynamic support could cause structural collapse and endanger surface populations or infrastructure.", "Collisions or fragmentation could create debris that threatens spacecraft and other orbital infrastructure.", "Failures in control or energy systems could destabilize connected structures over a wide area.", "Treating speculative performance claims as demonstrated capability could lead to unsafe planning and major financial losses." ], "facets_not_applicable": { "recognition": "An orbital ring in this sense is an engineering concept whose illustrations do not establish a physically realized structure." } }, "sources": [ { "id": "wikidata", "title": "Wikidata item Q4235016: orbital ring", "url": "https://www.wikidata.org/wiki/Q4235016", "url_status": "live", "what_it_supports": "identity and sense of the item", "checked_by": "wikidata-api" }, { "id": "wikipedia-en", "title": "Wikipedia: Orbital ring", "url": "https://en.wikipedia.org/wiki/Orbital_ring", "url_status": "live", "what_it_supports": "general description of the item", "checked_by": "wikidata-api sitelink" } ], "structure": { "bundles": [ { "id": "concept-and-architecture", "name": "Concept and architecture", "description": "Establishes what the registered name denotes and which architecture a particular proposal specifies.", "rationale": "The absent definition and INF / INF.MED classification make referent resolution necessary before engineering attributes can be assigned.", "layers": [ { "id": "referent-boundary", "name": "Referent boundary", "description": "Separates the infrastructure concept from natural rings, neighbouring proposals and media representations.", "findings": [ { "id": "registered-referent", "name": "Registered referent", "description": "Record evidence identifying whether the entry denotes the engineering concept or a particular informational work.", "questions": [ { "text": "What originating registry record or linked identifier establishes the intended meaning of orbital ring?", "kind": "provenance", "id": "registered-referent-q01" }, { "text": "Does INF / INF.MED describe a conceptual representation, a named work or a classification requiring correction?", "kind": "boundary", "id": "registered-referent-q02" } ] } ] }, { "id": "encircling-system-layout", "name": "Encircling system layout", "description": "Defines the central body, ring path and distinction between moving and supported components.", "findings": [ { "id": "component-motion-map", "name": "Component motion map", "description": "Record the proposed geometry and component motions without assuming that all parts share one orbit or velocity.", "questions": [ { "text": "Which components encircle the body, and which move relative to the surface and to one another?", "kind": "definition", "id": "component-motion-map-q01" }, { "text": "What altitude profile, inclination and reference frame define the proposed ring path?", "kind": "measurement", "id": "component-motion-map-q02" } ] } ] } ] }, { "id": "support-and-dynamic-control", "name": "Support and dynamic control", "description": "Captures the proposed force balance and control conditions that make load support possible.", "rationale": "An encircling shape alone does not explain whether the architecture can sustain its supported structures and changing loads.", "layers": [ { "id": "load-support-mechanism", "name": "Load support mechanism", "description": "Connects moving mass, force transfer and supported load to explicit engineering claims.", "findings": [ { "id": "force-and-mass-budget", "name": "Force and mass budget", "description": "Record the support calculation with its assumptions, component masses and load distribution.", "questions": [ { "text": "What mechanism transfers supporting force to non-orbiting or differently moving structures?", "kind": "definition", "id": "force-and-mass-budget-q01" }, { "text": "What moving mass, velocity, structural mass and payload distribution are assumed in the claimed support margin?", "kind": "measurement", "id": "force-and-mass-budget-q02" } ] } ] }, { "id": "disturbance-response", "name": "Disturbance response", "description": "Addresses departures from the nominal ring path and force balance.", "findings": [ { "id": "stability-and-control-envelope", "name": "Stability and control envelope", "description": "Record which disturbances the design considers and what evidence supports its proposed corrective response.", "questions": [ { "text": "Which analyses address uneven loading, moving payloads, ground-connection forces and local component displacement?", "kind": "provenance", "id": "stability-and-control-envelope-q01" }, { "text": "What sensing, actuation and response limits determine when loading must stop or the system must enter a degraded operating state?", "kind": "action", "id": "stability-and-control-envelope-q02" } ] } ] } ] }, { "id": "access-energy-and-service", "name": "Access, energy and service", "description": "Defines how the ring connects to users and exchanges mass, momentum and energy.", "rationale": "Support capacity does not establish practical transport capability without compatible access and transfer interfaces.", "layers": [ { "id": "ground-and-orbital-interfaces", "name": "Ground and orbital interfaces", "description": "Describes optional ground connections and transfers between supported facilities and moving payloads.", "findings": [ { "id": "payload-transfer-conditions", "name": "Payload transfer conditions", "description": "Record how payloads reach, traverse and leave the ring, including required changes in velocity.", "questions": [ { "text": "Does this architecture include ground tethers, suspended stations or orbital transfer facilities, and where does each interface end?", "kind": "boundary", "id": "payload-transfer-conditions-q01" }, { "text": "What payload mass, transfer velocity and throughput can each access route accommodate under stated conditions?", "kind": "measurement", "id": "payload-transfer-conditions-q02" } ] } ] }, { "id": "energy-and-thermal-balance", "name": "Energy and thermal balance", "description": "Separates initial energization, continued support and transport-service demands.", "findings": [ { "id": "operating-resource-budget", "name": "Operating resource budget", "description": "Record power, energy storage and heat-rejection claims for defined operating modes.", "questions": [ { "text": "What energy and power budgets are claimed for startup, steady operation and payload acceleration, and which losses are included?", "kind": "measurement", "id": "operating-resource-budget-q01" }, { "text": "How long can the proposed architecture maintain its required support and control conditions after external power is interrupted?", "kind": "measurement", "id": "operating-resource-budget-q02" } ] } ] } ] }, { "id": "realization-failure-and-evidence", "name": "Realization, failure and evidence", "description": "Examines whether the ring can reach, maintain and leave its intended operating state, and how those claims have been substantiated.", "rationale": "A completed-ring calculation leaves construction transitions, failure propagation and whole-system validation unresolved.", "layers": [ { "id": "construction-and-retirement", "name": "Construction and retirement", "description": "Tracks intermediate configurations before full operation and during removal.", "findings": [ { "id": "supported-transition-sequence", "name": "Supported transition sequence", "description": "Record the assembly and energization sequence with the support mechanism available at each stage.", "questions": [ { "text": "How is each incomplete configuration supported before the ring reaches its intended continuity and operating speed?", "kind": "action", "id": "supported-transition-sequence-q01" }, { "text": "What proposed retirement sequence manages the moving components' energy and the removal or descent of supported structures?", "kind": "action", "id": "supported-transition-sequence-q02" } ] } ] }, { "id": "failure-containment-and-validation", "name": "Failure containment and validation", "description": "Connects failure scenarios and recovery claims to evidence at the appropriate system scale.", "findings": [ { "id": "failure-propagation-case", "name": "Failure propagation case", "description": "Record consequences and proposed containment for loss of coupling, component rupture or external impact.", "questions": [ { "text": "What analysis traces a local loss of support or moving-component rupture through the rest of the ring and its ground interfaces?", "kind": "provenance", "id": "failure-propagation-case-q01" }, { "text": "Which isolation, unloading or recovery actions are supported by that analysis, and under what initial conditions?", "kind": "action", "id": "failure-propagation-case-q02" } ] }, { "id": "claim-validation-coverage", "name": "Claim validation coverage", "description": "Distinguish assumptions, analytical results, simulations and demonstrations for each essential mechanism.", "questions": [ { "text": "Which accessible primary sources substantiate the proposed support, stability and construction mechanisms?", "kind": "provenance", "id": "claim-validation-coverage-q01" }, { "text": "What scale effects or coupled behaviours remain untested when component evidence is applied to a complete planetary ring?", "kind": "boundary", "id": "claim-validation-coverage-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 supplied INF.MED domain suggests a media classification, but no title, author or recorded sense identifies a particular work; this answer describes the engineering concept.", "This is a speculative infrastructure concept, with no operational full-scale example known from recall.", "Configurations and performance figures require checking against specific engineering proposals; the uses and hazards listed are proposed or anticipated." ], "questions": [ { "id": "evidence-confidence-notes-q01", "text": "Which of these check these first hold for the sense of orbital ring 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": [ "Studied conceptually as infrastructure for transporting payloads between a planetary surface and space.", "Proposed as a support for elevated transport networks and orbital facilities." ], "questions": [ { "id": "evidence-real-world-use-q01", "text": "Which of these real-world use hold for the sense of orbital ring 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": "Circulating mass speed", "typical_range": "Design-dependent; exceeds the local circular orbital speed in configurations that support additional stationary loads.", "unit": "km/s" }, { "quantity": "Ring altitude", "typical_range": "No established typical range; depends on the proposed configuration.", "unit": "km" } ], "questions": [ { "id": "evidence-measurements-q01", "text": "Which of these typical measurements hold for the sense of orbital ring 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": [ "Loss of levitation or guidance could cause contact between the circulating mass and its enclosure.", "Failure to control oscillations could destabilize the ring and its supported structures.", "Impacts from debris or meteoroids could damage components and initiate cascading failures.", "Failure of surface connections could release tether material or suspended loads.", "Uncontrolled release of the circulating mass's kinetic energy could produce destructive debris." ], "questions": [ { "id": "evidence-failure-modes-and-hazards-q01", "text": "Which of these failure modes and hazards hold for the sense of orbital ring 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": "Space elevator", "difference": "A conventional space elevator uses a tensioned tether extending beyond geostationary orbit; an orbital ring uses circulating mass to support a circumplanetary structure." }, { "name": "Launch loop", "difference": "A launch loop uses a circulating mass in an elongated track to support a launch path; it need not encircle the planet." }, { "name": "Ringworld", "difference": "A ringworld is a proposed star-encircling habitat; an orbital ring is usually planet-encircling infrastructure." }, { "name": "Planetary ring", "difference": "A planetary ring consists of independently orbiting particles; an orbital ring is an engineered system." } ], "questions": [ { "id": "evidence-neighbours-q01", "text": "Which of these neighbouring kinds and how to tell them apart hold for the sense of orbital ring this model covers, and on what evidence?", "kind": "provenance" } ] } ] } ] } ] }, "openQuestions": [ "Does vr.tr.orbital-ring denote the infrastructure concept assumed here, or a particular work or representation consistent with INF / INF.MED?", "Which architectural variants belong within the registry's intended orbital-ring boundary, and which require links to neighbouring concepts?", "What primary sources establish credible support and stability calculations with explicit assumptions and independently assessable results?", "Has any proposed construction sequence accounted for support and control throughout every intermediate configuration?", "What evidence supports failure containment, environmental consequences and recovery claims at the scale of a complete ring?" ], "statistics": { "bundles": 5, "layers": 9, "findings": 14, "questions": 23 } }