This meta-model describes the near-Earth space environment as a populated register: the objects placed in orbit and their registration particulars, the orbital states, manoeuvres and conjunctions that describe where they are and where they are going, the fragments they leave behind, and the space weather that acts on all of them. It is its own model because an orbital object has an identity that survives fragmentation, transfer and reentry, and because position here is a time-parameterized state rather than a fixed geometry. The object as a manufactured asset is described in M2 and M8, its radio use in F9.
Which objects exist, what they are for and who answers for them
objectIdentity`: designators, catalogue numbers, object class and physical characteristics · `missionAndPayload`: mission purpose, payloads, instruments and operational status · `registrationAndCustody`: registration entries, registering and operating party references and custody changes
Where an object is, where it is going and what it might hit
orbitalState`: elements, state vectors and ephemerides at epoch with covariance · `maneuverAndStationKeeping`: planned and executed burns, drift control and disposal manoeuvres · `conjunctionAndReentry`: close approach assessments, collision probability, reentry prediction and disposal outcome
What the surrounding space is doing
spaceWeather`: solar activity, geomagnetic conditions, radiation and drag-relevant indices · `debrisEnvironment`: fragment populations, flux models by regime and altitude
Catalogue-native findings must describe the information grouped by each layer. This legacy version does not declare them separately.
Questions, artifact requirements and serial naming rules are required by Vercy vNext; they remain unassigned in this reference version.
Format-independent core. Concrete artifact formats and naming prefixes are not declared in this legacy version.
CRUD procedures and interface bindings are not declared in this legacy version.
A space object registrar keeps the catalogue and registration record, and a space environment steward publishes tracking, conjunction screening and space weather products, each accountable for what it issues. Objects themselves stay owned by their operators through S1, restricted ephemerides and manoeuvre plans are released only under S2 access contracts, and every read of restricted precision data is logged in S4.