Space & Orbital Objects
Satellites, orbits, debris, space weather
Bundle → Layer → Finding → Questions Incomplete
3 bundles · 8 layers · 0 findings · 0 questions
objectRegistry 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
orbit 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
environment 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
Note: Legacy card: layers named, findings and questions never written.
Classifiers Filled
- Family
- World Models
- Category
- Physical world and living systems
- Entry kind
- standalone-mm
- Navigation path
- NAV.PHY.SPC.OBJ
- Domain
- PHY.SPC.OBJ
- Industry
- Cross-industry
- Tags
- spaceobjectorbitphy.spc.obj
- Also called
- P11
What it is Derived, awaiting review
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.
Note: First sentence of the legacy card introduction.
Why it exists Filled
Satellites, orbits, debris, space weather
Distinguishing features Derived, awaiting review
- 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.
What robots and AI may and may not do Missing, in the backlog
Not described yet. This gap is in the card backlog.
Moral aspects Missing, in the backlog
Not described yet. This gap is in the card backlog.
Owners Filled
Steward
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.
Links to other meta-models Filled
references
- world.physicalItemArtifact - the object as a manufactured asset and its instruments are described there
- world.deviceSensorAndComputingHardware - the object as a manufactured asset and its instruments are described there
- world.metaObjectOwnershipAndStewardship - ownership, operator identity and custody transfer resolve there
- world.organization - ownership, operator identity and custody transfer resolve there
- world.communicationsAndDataTransmission - radio spectrum grants, ground stations and link budgets belong to that model
- world.atmosphereWeatherAndClimate - satellite-derived fields feed observation there, and upper atmosphere density conditions drag here
- world.naturalPhenomenonAndHazard - reentry and debris fall are hazards to ground exposure zones described there
- world.interstateRelationsAndTreaties - registration and liability obligations between registers are agreements held there
- world.timeAndCalendarReference - epochs, time scales and leap second handling resolve there
- world.occurrenceEvent - launches, breakups and reentries also surface as generic occurrences on the shared timeline
imports
- un-register-of-space-objects - REFERENCE: registration particulars referenced as filed rather than restated
- ccsds - EXTEND: orbit, tracking and navigation data message structures this model specializes
- iso-24113-space-debris-mitigation - ALIGN: disposal and passivation concepts used by the reentry and disposal layer
- wmo - REFERENCE: space weather observation and index definitions shared with the atmospheric register
requires
- vr.wm-com-001
- vr.wm-ear-001
- vr.wm-ear-005
- vr.wm-pol-005
- vr.wm-pol-014
What else AI and robots need to interact with it Incomplete
Identity and identifiers required Derived, awaiting review
- payload: an instrument or capability carried by an object; key attributes: payload identifier, function, operating bands reference, operational status
- orbitRegime: a band of orbital space; key attributes: regime identifier, altitude and inclination bounds, typical use, congestion indicator
Direct properties not applicable Not applicable
Not applicable
Institutional or informational subject: no invented physical properties.
Recognition optional Missing, in the backlog
Not described yet. This gap is in the card backlog.
Capabilities and actions required Derived, awaiting review
- objectLaunched: an object reached orbit and entered the catalogue
- objectRegistered: registration particulars were filed or amended for an object
- orbitDeterminationUpdated: a new state was determined from tracking, superseding the previous epoch
- maneuverExecuted: a planned burn was carried out and the resulting orbit was re-determined
- conjunctionWarningIssued: a close approach crossed the screening threshold and operators were notified
- fragmentationEventDetected: a breakup or collision produced new catalogued fragments
- reentryOccurred: an object left orbit, with the predicted and actual footprint recorded
- spaceWeatherStormOnset: geomagnetic or radiation conditions crossed a defined storm level
Legacy events listed as state transitions.
Hazards and failure modes optional Missing, in the backlog
Not described yet. This gap is in the card backlog.
Standards and interfaces required Derived, awaiting review
- catalogueAccessContract: terms for reading the object catalogue, distinguishing the public identity view from restricted high-precision ephemerides
- conjunctionNotificationContract: terms for operator to operator notification, including contact points, response windows and confidentiality of manoeuvre plans
- registrationFilingContract: terms under which an operator files or amends registration particulars with the registrar
- spaceWeatherAlertContract: terms for delivery of environment alerts to operators and dependent infrastructure
- publicObjectCatalogue: designators, class, regime and coarse elements; omits high-precision ephemerides, covariance and mission detail
- operatorEphemerisView: full state, covariance and manoeuvre history for the operator's own objects; omits other operators' holdings
- debrisEnvironmentSummary: fragment counts and flux by regime and altitude band; omits per-object identity
- reentryRiskBrief: predicted reentry window and footprint for ground authorities; omits payload and mission particulars
Context of use required Filled
- 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.
Sources Missing, in the backlog
Not described yet. This gap is in the card backlog.
Open questions
- Superseded by a researched world model? Map this legacy card to its successor or retire it.
Machine files
Provenance
legacy MMAS card (world-models v0.2) · legacy
Built from: models/world-p11-space-and-orbital-objects/spec.yaml, models/docs/planet-nature/P11-space-and-orbital-objects.md