{ "vercy": "1.0-draft", "publication": { "status": "research-draft", "adjudicationStatus": "unreviewed", "publishableCanonical": false, "generatedAt": "2026-09-12T09:34:35Z", "providers": [ "Codex" ], "breadth": "recalled by Codex without web access - no source was read", "missingProviders": [], "pass": 2, "cost": { "grok": { "seconds": 21.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: 01a094f6-d99d-7cc2-8137-4cdab420caf9\n--------\nuser\nDescribe what is already known about one registered thing. Answer as JSON only, no prose around it.\n\nThing: European Data Relay System\nSense to describe: (none recorded)\nDomain code: PHY.OBJ\nAlso known as: (none)\n\n\nContext for this batch of 1001 things:\n# Batc", "usd": 0.0, "recall": true }, "codex": { "seconds": 75.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: 01a094f6-d9aa-79f1-bf34-57286985e156\n--------\nuser\nYou are drafting a Vercy meta-model for one registered thing. Answer as JSON only, no prose around it.\n\nThing: European Data Relay System\nRegistry id: vr.tr.european-data-relay-system\nPlane / domain: PHY / PHY.OBJ\nRegistry definition: (none recorded)\nNames fol" } }, "enrichment": { "pass": 3, "engine": "claude", "producedAt": "2026-10-06T12:00:00Z", "ingestedAt": "2026-10-06T08:49:44+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:32+00:00", "evidence": [ "completeness 1.00", "sense: Wikidata description", "2 live sources", "review by codex: pass" ] } }, "metaModel": { "id": "THING-Q784808", "registryId": "vr.tr.european-data-relay-system", "name": "European Data Relay System", "version": "0.1.0-research.1", "entryKind": "thing", "family": "Thing Registry", "domain": [ "PHY.OBJ" ], "status": "research-draft" }, "canonicalUrl": "https://ver.cy/models/thing/q784808/", "model": { "registry_id": "vr.tr.european-data-relay-system", "name": "European Data Relay System", "purpose": "Enable an agent to recognise the European Data Relay System, assess a proposed satellite-data relay service, and identify the evidence and authority needed to request or modify that service.", "definition": "The European Data Relay System (EDRS) is a satellite communications infrastructure developed through a European Space Agency-Airbus public-private partnership that uses geostationary relay nodes, laser intersatellite links and radio downlinks to transfer data from supported spacecraft to ground stations with reduced delivery delay.", "scope_statement": "This model owns the system-level identity, constituent relationships, relay paths, service constraints and operational assessment of European Data Relay System infrastructure registered as vr.tr.european-data-relay-system.", "in_scope": [ "EDRS geostationary relay nodes and their membership in the named system", "Optical intersatellite links, radio downlinks and participating ground infrastructure", "Compatibility between customer spacecraft terminals and EDRS relay services", "Contact planning, resource allocation and delivery-performance assessment", "Operational dependencies, service interruptions and authority boundaries" ], "out_of_scope": [ "Earth-observation instruments and interpretation of their measurements", "Complete engineering models of host spacecraft and individual laser terminals", "Corporate models of ESA, Airbus and component suppliers", "Generic satellite communications networks unrelated to EDRS", "Downstream processing and distribution of customer mission products" ], "distinguishing_features": [ "Identity must resolve to the named European relay infrastructure, rather than to the general class of data-relay satellites.", "Its defining relay path connects customer spacecraft to ground infrastructure through geostationary relay nodes; direct spacecraft-to-ground reception alone does not constitute EDRS.", "Optical intersatellite communication and the subsequent ground-delivery path must be distinguished; describing the entire path as a laser downlink is insufficient.", "EDRS-A and EDRS-C are constituent nodes, not interchangeable names for the whole system.", "References to SpaceDataHighway require a dated scope check before treating every associated asset or proposed extension as part of this registry entry." ], "characteristics": [ { "name": "System configuration", "kind": "relation", "unit_or_values": "Dated membership links to relay payloads, host spacecraft, ground stations and control centres", "why_it_matters": "Separates the enduring system identity from changes to its deployed infrastructure." }, { "name": "Relay-node orbital position", "kind": "measurement", "unit_or_values": "Geostationary longitude in degrees east, with epoch and source", "why_it_matters": "Constrains customer visibility and ground-station accessibility." }, { "name": "Relay-path interface", "kind": "category", "unit_or_values": "Optical intersatellite link, radio intersatellite link if supported, radio ground link or terrestrial handoff; qualified by node", "why_it_matters": "Prevents capabilities of one segment or node from being assumed across the system." }, { "name": "Customer-terminal compatibility", "kind": "relation", "unit_or_values": "Spacecraft terminal configuration linked to an approved EDRS interface and qualification record", "why_it_matters": "A spacecraft carrying a laser terminal is not automatically an eligible customer." }, { "name": "Usable relay window", "kind": "measurement", "unit_or_values": "UTC start and end; usable duration in seconds", "why_it_matters": "Distinguishes geometric visibility from allocated and operationally usable contact time." }, { "name": "Delivered data rate", "kind": "measurement", "unit_or_values": "bit/s at a named interface, with averaging interval and operating conditions", "why_it_matters": "Supports capacity assessment without confusing terminal capability with customer throughput." }, { "name": "Delivery latency", "kind": "measurement", "unit_or_values": "Seconds between explicitly identified acquisition, relay and delivery events", "why_it_matters": "Makes near-real-time delivery assessable rather than a blanket service claim." }, { "name": "Relay-service state", "kind": "state", "unit_or_values": "Unknown, planned, available, allocated, acquiring, relaying, degraded or unavailable", "why_it_matters": "Determines whether an agent can propose a contact or must seek operational confirmation." } ], "affordances": [ "Resolve a named EDRS asset to its role and dated system membership.", "Assess whether a customer spacecraft has evidence of terminal and service compatibility.", "Compare candidate relay windows against volume and delivery-deadline requirements.", "Prepare a relay-service request for an authorised scheduling interface.", "Trace a missed delivery to the intersatellite, ground-link, control or terrestrial segment.", "Identify documented alternative contacts or delivery routes when a planned path is unavailable." ], "agent_conduct": { "may": [ "Describe the European Data Relay System, its purpose and its public mission record from official sources.", "Report publicly announced service status and capability." ], "must_not": [ "Help interfere with, jam or intercept its links.", "Help gain access to its ground or space segments without authorization.", "Disclose non-public operational or security details of the system." ], "requires_human": [ "Any request involving its operation, tasking or the data it relays." ] }, "ethics": { "considerations": [ "It relays data for earth observation, including emergency and security use.", "Interference with space infrastructure affects many users across borders." ], "affected_parties": [ "Users of earth observation data", "Emergency services", "Operators and partner agencies" ] }, "owners": { "steward": "The operator of the relay system under its public-private partnership.", "master_systems": [ "Satellite registration with the United Nations", "International frequency registers" ] }, "visual_identification": [ "Not visible in ordinary use; consists of satellites in geostationary orbit and ground stations.", "Ground stations show large dish antennas within secured sites." ], "failure_modes_and_hazards": [ "Loss of a relay node interrupts time-critical data delivery.", "Laser terminals and links are targets for interference." ], "standards_and_regulation": [ "Radio Regulations, International Telecommunication Union.", "Convention on Registration of Objects Launched into Outer Space, United Nations." ], "what_it_is_for": [ "This infrastructure relays data from supported spacecraft through geostationary nodes to ground stations when direct contact with a suitable receiving station is unavailable.", "It supports timely delivery of Earth observation data for applications such as environmental monitoring and emergency response." ] }, "sources": [ { "id": "wikidata", "title": "Wikidata item Q784808: European Data Relay System", "url": "https://www.wikidata.org/wiki/Q784808", "url_status": "live", "what_it_supports": "identity and sense of the item", "checked_by": "wikidata-api" }, { "id": "wikipedia-en", "title": "Wikipedia: European Data Relay System", "url": "https://en.wikipedia.org/wiki/European_Data_Relay_System", "url_status": "live", "what_it_supports": "general description of the item", "checked_by": "wikidata-api sitelink" } ], "structure": { "bundles": [ { "id": "system-identity-and-composition", "name": "System identity and composition", "description": "Represent EDRS as a named distributed infrastructure. ESA describes geostationary nodes and European ground and control infrastructure: [ESA infrastructure](https://www.esa.int/Applications/Connectivity_and_Secure_Communications/EDRS/Infrastructure).", "rationale": "The registry entry names a particular system whose payloads, spacecraft and service branding must remain distinguishable.", "layers": [ { "id": "named-system-boundary", "name": "Named system boundary", "description": "Anchor the registry identity and distinguish infrastructure from programme and service names.", "findings": [ { "id": "edrs-identity-resolution", "name": "EDRS identity resolution", "description": "Record which names denote this infrastructure and which denote related programmes or commercial offerings.", "questions": [ { "text": "Which authoritative identifiers and descriptions establish the boundary of European Data Relay System?", "kind": "definition", "id": "edrs-identity-resolution-q01" }, { "text": "Under which dated descriptions is SpaceDataHighway coextensive with EDRS rather than a broader offering?", "kind": "boundary", "id": "edrs-identity-resolution-q02" } ] } ] }, { "id": "node-and-ground-membership", "name": "Node and ground membership", "description": "Track the assets that constitute each dated operational configuration.", "findings": [ { "id": "payload-host-and-site-roles", "name": "Payload, host and site roles", "description": "Separate relay payload membership from host-platform ownership and ground-site participation.", "questions": [ { "text": "Which payloads, host spacecraft and ground facilities belong to the configuration being assessed?", "kind": "boundary", "id": "payload-host-and-site-roles-q01" }, { "text": "Which commissioning, reassignment or retirement records establish each asset's participation dates?", "kind": "provenance", "id": "payload-host-and-site-roles-q02" } ] } ] } ] }, { "id": "relay-path-and-interoperability", "name": "Relay path and interoperability", "description": "Represent the customer-to-GEO-to-ground path and its interface requirements. ESA describes optical collection from lower-orbit spacecraft followed by relay to European ground stations: [ESA laser communications](https://www.esa.int/Applications/Connectivity_and_Secure_Communications/EDRS/Laser_communications).", "rationale": "Successful service requires compatible interfaces across multiple distinct communication segments.", "layers": [ { "id": "customer-to-relay-link", "name": "Customer-to-relay link", "description": "Assess the terminal pairing and conditions needed to establish an intersatellite connection.", "findings": [ { "id": "terminal-pair-qualification", "name": "Terminal-pair qualification", "description": "Require evidence for the particular customer terminal and EDRS node pairing.", "questions": [ { "text": "Which interface specifications and qualification results establish compatibility with the selected EDRS node?", "kind": "provenance", "id": "terminal-pair-qualification-q01" }, { "text": "Which pointing, acquisition, tracking and spacecraft-attitude constraints govern establishment of this link?", "kind": "measurement", "id": "terminal-pair-qualification-q02" } ] } ] }, { "id": "relay-to-customer-handoff", "name": "Relay-to-customer handoff", "description": "Follow data through the ground link and onward to the agreed customer endpoint.", "findings": [ { "id": "ground-delivery-chain", "name": "Ground delivery chain", "description": "Identify the receiving station, terrestrial route and interface at which delivery is recognised.", "questions": [ { "text": "Which ground-link band, receiving station and terrestrial handoff apply to the selected relay service?", "kind": "definition", "id": "ground-delivery-chain-q01" }, { "text": "At which interface does EDRS responsibility for data delivery end and customer responsibility begin?", "kind": "boundary", "id": "ground-delivery-chain-q02" } ] } ] } ] }, { "id": "contact-planning-and-capacity", "name": "Contact planning and capacity", "description": "Translate orbital access and shared relay resources into feasible customer contacts.", "rationale": "A visible relay node does not by itself establish that capacity is available or a delivery deadline can be met.", "layers": [ { "id": "geometric-access", "name": "Geometric access", "description": "Determine usable visibility for a specified spacecraft, node and epoch.", "findings": [ { "id": "usable-contact-envelope", "name": "Usable contact envelope", "description": "Combine line of sight with terminal steering limits and documented exclusion conditions.", "questions": [ { "text": "What contact intervals follow from the customer's orbit and the selected node's dated position?", "kind": "measurement", "id": "usable-contact-envelope-q01" }, { "text": "Which occultations, terminal limits or operational exclusions reduce those intervals?", "kind": "measurement", "id": "usable-contact-envelope-q02" } ] } ] }, { "id": "scheduled-resource-allocation", "name": "Scheduled resource allocation", "description": "Determine whether relay and ground resources can support a requested transfer.", "findings": [ { "id": "contact-request-feasibility", "name": "Contact request feasibility", "description": "Evaluate transfer volume, usable duration, overhead and competing commitments together.", "questions": [ { "text": "What data volume can the allocated contact deliver after acquisition time, protocol overhead and ground-path limits?", "kind": "measurement", "id": "contact-request-feasibility-q01" }, { "text": "Through which authorised process are contacts requested, prioritised, confirmed and rescheduled?", "kind": "action", "id": "contact-request-feasibility-q02" } ] } ] } ] }, { "id": "delivery-evidence-and-continuity", "name": "Delivery evidence and continuity", "description": "Assess actual delivery outcomes and the consequences of segment failures.", "rationale": "EDRS utility depends on timely receipt of mission data, which cannot be inferred from successful optical acquisition alone.", "layers": [ { "id": "delivery-performance", "name": "Delivery performance", "description": "Define measurable service outcomes at named observation points.", "findings": [ { "id": "latency-and-completeness-evidence", "name": "Latency and completeness evidence", "description": "Distinguish advertised capability, contracted targets and observed contact results.", "questions": [ { "text": "Which timestamps and endpoints define the reported delivery latency?", "kind": "definition", "id": "latency-and-completeness-evidence-q01" }, { "text": "Which counters or receipt records establish delivered volume, completeness and effective throughput for a contact?", "kind": "measurement", "id": "latency-and-completeness-evidence-q02" } ] } ] }, { "id": "interruption-and-recovery", "name": "Interruption and recovery", "description": "Trace loss of service and identify evidenced recovery options.", "findings": [ { "id": "segment-failure-response", "name": "Segment failure response", "description": "Separate acquisition failure, pointing loss, radio-link degradation and ground-network interruption when evidence permits.", "questions": [ { "text": "Which telemetry and event records identify the segment responsible for a failed or incomplete transfer?", "kind": "provenance", "id": "segment-failure-response-q01" }, { "text": "Which documented recovery options permit reacquisition, another contact, another node or customer direct downlink?", "kind": "action", "id": "segment-failure-response-q02" } ] } ] } ] }, { "id": "service-authority-and-operating-constraints", "name": "Service authority and operating constraints", "description": "Record who may procure, schedule and operate EDRS services and which constraints govern the selected configuration.", "rationale": "An agent must distinguish assessing or requesting relay service from commanding infrastructure operated by different parties.", "layers": [ { "id": "operational-responsibility", "name": "Operational responsibility", "description": "Map customer, service operator, payload-control and host-spacecraft responsibilities.", "findings": [ { "id": "request-and-command-authority", "name": "Request and command authority", "description": "Associate each proposed action with the actor and interface authorised to perform it.", "questions": [ { "text": "Which current agreements identify the service provider and responsibility for each relay and ground segment?", "kind": "provenance", "id": "request-and-command-authority-q01" }, { "text": "Which actions may a customer agent submit directly, and which require operator or spacecraft-control approval?", "kind": "action", "id": "request-and-command-authority-q02" } ] } ] }, { "id": "configuration-specific-constraints", "name": "Configuration-specific constraints", "description": "Collect applicable spectrum, optical-operation, access-control and platform constraints.", "findings": [ { "id": "authorised-operating-envelope", "name": "Authorised operating envelope", "description": "Attach documented requirements to the exact node, terminal and ground route rather than assume universal certifications.", "questions": [ { "text": "Which spectrum authorisations, interface standards and optical operating restrictions apply, with issuing bodies and versions?", "kind": "provenance", "id": "authorised-operating-envelope-q01" }, { "text": "Which access permissions, host-platform power or thermal restrictions and maintenance exclusions must be satisfied before contact execution?", "kind": "action", "id": "authorised-operating-envelope-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 entry describes a particular named infrastructure, not a generic device class; its relay nodes are components rather than kinds.", "The quoted laser rate is a nominal capability, not a guaranteed end-to-end delivery rate; verify terminal-specific performance and service conditions.", "Current operational spacecraft, customers, coverage and contractual responsibilities require verification; these statements are recalled knowledge, not newly researched findings." ], "questions": [ { "id": "evidence-confidence-notes-q01", "text": "Which of these check these first hold for the sense of European Data Relay System 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": "Programme abbreviation", "value_or_pattern": "EDRS", "note": "Identifies the European Data Relay System as a whole, rather than an individual satellite." }, { "scheme": "Space-segment designation", "value_or_pattern": "EDRS-A; EDRS-C", "note": "Names distinct relay nodes within the system." } ], "questions": [ { "id": "evidence-identifiers-q01", "text": "Which of these identifiers and schemes hold for the sense of European Data Relay System this model covers, and on what evidence?", "kind": "provenance" } ] }, { "id": "evidence-standards-and-regulation", "name": "Standards and regulation", "description": "Recalled without web access and unsourced; every item is a lead to verify.", "evidence": [ "International Telecommunication Union (ITU) Radio Regulations govern spectrum use and coordination for the system's radio-frequency satellite links." ], "questions": [ { "id": "evidence-standards-and-regulation-q01", "text": "Which of these standards and regulation hold for the sense of European Data Relay System 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": [ "Relaying Earth-observation data from suitably equipped Copernicus Sentinel spacecraft.", "Delivering imagery sooner than would be possible by waiting for a spacecraft's next direct ground-station contact.", "Supporting time-sensitive environmental monitoring and emergency-response information services." ], "questions": [ { "id": "evidence-real-world-use-q01", "text": "Which of these real-world use hold for the sense of European Data Relay System 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": "Laser intersatellite link data rate", "typical_range": "Up to approximately 1.8", "unit": "Gbit/s" }, { "quantity": "Geostationary relay altitude above Earth's equator", "typical_range": "Approximately 35,786", "unit": "km" } ], "questions": [ { "id": "evidence-measurements-q01", "text": "Which of these typical measurements hold for the sense of European Data Relay System 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": [ "Laser-link acquisition or tracking failure caused by insufficient pointing accuracy or disturbed spacecraft attitude.", "Loss of relay availability following spacecraft power, thermal-control or communications-payload faults.", "Rain attenuation and other propagation losses affecting high-frequency radio downlinks.", "Ground-station or terrestrial-network outages delaying delivery of relayed data.", "Orbital debris impacts or radiation-induced equipment faults affecting space-segment operation." ], "questions": [ { "id": "evidence-failure-modes-and-hazards-q01", "text": "Which of these failure modes and hazards hold for the sense of European Data Relay System 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": "EDRS-A", "difference": "A relay payload hosted on a satellite; it is one component of EDRS, not the complete infrastructure." }, { "name": "EDRS-C", "difference": "A dedicated relay satellite within EDRS, rather than the system as a whole." }, { "name": "Copernicus Sentinel satellites", "difference": "Earth-observation spacecraft that generate observation data; compatible members use EDRS to relay that data." }, { "name": "Tracking and Data Relay Satellite System", "difference": "NASA's separate satellite relay infrastructure, with its own spacecraft, ground segment and service arrangements." }, { "name": "Direct-to-ground satellite communications", "difference": "Transfers data directly from the originating spacecraft to a visible ground station without an intermediate relay satellite." } ], "questions": [ { "id": "evidence-neighbours-q01", "text": "Which of these neighbouring kinds and how to tell them apart hold for the sense of European Data Relay System this model covers, and on what evidence?", "kind": "provenance" } ] } ] } ] } ] }, "openQuestions": [ "What is the authoritative operational asset inventory at the assessment date, including whether any extensions belong to EDRS or a broader SpaceDataHighway offering?", "Which customer-terminal implementations are currently qualified for each node, and what interface documentation is available to service users?", "What latency, availability, throughput and delivery-completeness commitments apply to each service class and customer handoff?", "Which buffering, retransmission and alternative-node capabilities are actually implemented and contractually available?", "Which current technical standards, spectrum authorisations, optical restrictions and security requirements govern each operational route?" ], "statistics": { "bundles": 6, "layers": 11, "findings": 17, "questions": 27 } }