Space Object / Orbit
Describe one artificial space object and its attributed identity, physical context, orbit products and lifecycle evidence.
Bundle → Layer → Finding → Questions Filled
7 bundles · 14 layers · 14 findings · 56 questions
Identity and accountability Resolve the object separately from filings and responsible-party assertions.
Object identity
Context for object identity.
Object identity
Maintain a persistent local subject with namespace-qualified, time-qualified aliases and explicitly unresolved correlations. A fragment has its own identity; neither a name nor an orbit proves equivalence.
- Which master identity anchors this object when catalogue designators are missing or change? identity
- Which object class is asserted and how is unknown or disputed classification represented? classification
- What evidence permits or prevents merging two catalogue records into this object? validation
- Which alias revision supersedes an earlier identifier association without erasing its history? provenance
Registration and accountable roles
Context for registration and accountable roles.
Registration and accountable roles
Keep filed registration particulars separate from catalogue estimates and party-role assertions. Applicability, filing status and ownership remain qualified; missing registration is representable.
- Which filed registration reference and legal basis support the asserted state of registry? authority
- Which owner, operator, custodian and launching-state roles are evidenced for each effective interval? ownership
- Which orbital particulars were filed and how are they distinguished from later orbit estimates? measurement
- How are absent filings, multiple launching states or unresolved changes of operator recorded? exception
Physical and functional context Qualify the object description while keeping hardware and mission masters external.
Physical characteristics
Context for physical characteristics.
Physical characteristics
Describe sourced physical attributes with their configuration and measurement context. Unknown mass or dimensions stay unknown; fitted model parameters are not direct measurements.
- What mass, geometry or effective area is known for the stated object configuration? measurement
- Was each physical value measured, declared, inferred or assumed in a dynamics model? provenance
- Which physical unit or component reference owns the detailed hardware description? composition
- Which conflicting or missing physical values prevent a proposed downstream use? constraint
Mission association and capability
Context for mission association and capability.
Mission association and capability
Associate mission and carried payloads without absorbing programme ownership. Operational state, maneuverability, evidence of behavior and authority to act remain distinct.
- Which missions and payloads are associated with this object during the interval? relationship
- What functional state and maneuverability are asserted at the observation time? state
- Which declared capability differs from observed behavior or a proposed operation? definition
- Which responsible role can approve an external action when capability exists? authority
Orbit solutions and uncertainty Make position assertions interpretable and preserve competing determinations.
Orbit representation
Context for orbit representation.
Orbit representation
Retain attributed orbit solutions with native epoch and time system, center, frame, units and representation. Mean elements, state vectors and ephemerides are not interchangeable without a validated transformation.
- Which center, reference frame and representation define this orbit solution? spatial
- What native epoch, time system and validity interval accompany the solution? temporal
- Which theory, interpolation method or conversion is required to interpret the orbit product? interoperability
- Which use-specific evidence supports selection among competing or stale orbit solutions? quality
Uncertainty and determination provenance
Context for uncertainty and determination provenance.
Uncertainty and determination provenance
Keep uncertainty tied to its orbit solution and declared basis. Missing covariance is not zero uncertainty, and mathematical validity does not certify prediction accuracy.
- Which uncertainty representation belongs to this orbit solution and epoch? measurement
- Which tracking arc, determination process and assumptions produced the solution? provenance
- Which frame, unit, dimension and numerical checks passed for the uncertainty product? validation
- How are incompatible, absent or unusable uncertainty estimates carried to downstream consumers? exception
Observation and product evidence Distinguish measurements, correlations and versioned exchange products.
Tracking and recognition evidence
Context for tracking and recognition evidence.
Tracking and recognition evidence
Link observations to candidate object associations while preserving measurement context. A detection and its object correlation have different certainty and may be corrected separately.
- Which observation set and sensing participants support recognition of this object? evidence
- Which measurement type, units, reference context and corrections qualify the tracking evidence? measurement
- What ambiguity remains between this object and other candidate correlations? quality
- Which observation details can this recipient access under the source terms? access
Product provenance and exchange
Context for product provenance and exchange.
Product provenance and exchange
Preserve source message identity and immutable versions, with explicit mappings for imported products. The proposed schema is format-neutral and does not claim CCSDS conformance.
- Which originator-scoped message identity and revision identify the imported product? identity
- Which pinned import mapping preserves native values and flags unsupported fields? interoperability
- What evidence distinguishes schema acceptance from semantic and operational acceptance? validation
- Which retention and access rules govern original products, derived views and superseded revisions? retention
Lifecycle and lineage Maintain object continuity without collapsing events or newly separated objects.
Object lifecycle and maneuver evidence
Context for object lifecycle and maneuver evidence.
Object lifecycle and maneuver evidence
Represent launch, deployment, operational changes and maneuver evidence as distinct assertions. Launch is not cataloguing or successful orbit insertion; planned action is not execution.
- Which launch, deployment and operational events are supported rather than merely planned? lifecycle
- How do event time, observation time and recorded time differ for the lifecycle claim? temporal
- Which approved external maneuver record is planned, executed, cancelled or unconfirmed? process
- What evidence confirms an action outcome without treating a plan or receipt as execution? validation
Separation, docking and fragment lineage
Context for separation, docking and fragment lineage.
Separation, docking and fragment lineage
Track changing relations between distinct objects. Parentage does not copy the parent identity to fragments; docking does not automatically merge identities.
- Which objects are attached, contained or independently separated during each interval? composition
- Which separation or fragmentation event supports a proposed parent-child relation? event
- Which surviving object or new fragment retains or receives a distinct identity after change? identity
- How is disputed parentage or a later correlation correction represented without rewriting history? exception
Conjunction and end-of-life context Record external assessment and disposition evidence without exercising operational authority.
Conjunction assessment association
Context for conjunction assessment association.
Conjunction assessment association
Attach paired-object assessment products and their revisions. Predicted proximity, collision probability and operational response are distinct; absent probability is not zero risk.
- Which two object identities and orbit-product revisions were used in the conjunction assessment? relationship
- What closest-approach time and screening interval apply to this assessment revision? temporal
- Which miss-distance and probability estimates include methods, assumptions and uncertainty? measurement
- Which external review or response record addresses the advisory under an applicable policy? decision
End-of-life, disposal and reentry
Context for end-of-life, disposal and reentry.
End-of-life, disposal and reentry
Separate end of function, disposal intent, disposal evidence and predicted or observed reentry. Local record retirement does not dispose of the object or close external duties.
- Which applicable debris-mitigation and end-of-mission profile governs the object? requirement
- What evidence distinguishes a disposal plan, an attempted action and its verified outcome? state
- Which reentry window is predicted and what separate evidence supports an observed reentry? quality
- What records and external obligations survive the object leaving orbit or losing function? retention
Environment and evidence governance Bind relevant environmental context and govern the use of attributed records.
Environmental context
Context for environmental context.
Environmental context
Reference external environment products only where relevant to this object and interval. Drag-related conditions qualify orbit assumptions; weather or flux products remain independently mastered.
- Which external environmental product is relevant to this object and orbital interval? relationship
- Is the environmental context observed, forecast or simulated and at what version? provenance
- Which orbit or lifetime assumptions depend on environmental inputs that are missing or stale? constraint
- Which claimed effect on this object lacks evidence despite an environmental alert? exception
Evidence stewardship and safe use
Context for evidence stewardship and safe use.
Evidence stewardship and safe use
Apply proposed local governance to assertions and artifacts. Public catalogue visibility does not grant redistribution rights for precision products or authority for external action.
- Which policy distinguishes public identification from restricted precision or operational records? security
- Which role may accept, correct or retire a local assertion with evidence? authority
- Which operator contact or other personal data should be minimized in each projection? privacy
- Which unresolved evidence and review holds must travel with every exported object view? validation
Classifiers Filled
- Family
- World Models
- Category
- Physical world and living systems
- Entry kind
- entity
- Navigation path
- NAV.PHY.SPC.OBJ
- Domain
- PHY.SPC.OBJ
- Industry
- Cross-industry
- Tags
- spaceobjectorbitphy.spc.obj
- Also called
- P11
What it is Filled
One artificial space object, including an unregistered, untracked or no-longer-orbiting object when evidence permits identification. Orbit solutions, registration assertions and risk products describe the object but do not define its identity. Earth-orbit evidence is the strongest profile; beyond-Earth use requires additional validation. This is a proposed research model, not a flight dynamics or spacecraft control system.
In scope
- Object identity and catalogue aliases, class, physical measurements and mission or payload references
- Time-qualified registration and party-role assertions, tracking and orbit-product provenance
- Lifecycle and fragment lineage, conjunction and disposal evidence, object-specific environmental context
Out of scope
- Natural celestial-body and astronomical-observation masters
- Mission programme planning, physical asset manufacture, ownership and party master lifecycles
- Orbit determination, propagation, collision-risk computation, maneuver design or execution, spacecraft command and public warning issuance
- Legal registration filing, spectrum licensing and adjudication of ownership or liability
- Population-wide debris simulations and space-weather observation or forecast masters; weapon-related subjects remain at policy level
Why it exists Filled
Describe one artificial space object and its attributed identity, physical context, orbit products and lifecycle evidence.
Distinguishing features Derived, awaiting review
- Unlike WM-SPC-004 Satellite Mission / Programme: Incoming candidate CONTAINS is reconciled as mission association with separately identified objects. Mission planning and mission-wide lifecycle remain external; an unknown fragment need not have a resolved mission.
- Unlike WM-OBJ-001 Physical Item Instance: Reference the manufactured unit when known; this model owns space-context assertions, not manufacturing, inventory or hardware maintenance.
- Unlike WM-XCT-001 Ownership / Stewardship: Owner, operator, custodian, launching state and state of registry are different qualified roles. Registration or operation alone is not ownership proof.
- Unlike WM-XCT-009 Time / Calendar: Use external time-reference bindings for conversion. Keep native dynamical time systems and epochs; RFC 3339 metadata timestamps do not permit relabelling non-UTC epochs as UTC.
- Unlike WM-SPC-002 Celestial Body and WM-SPC-003 Astronomical Observation: Natural bodies and their observations remain external; artificial-object track correlation does not create a natural-body master.
- Unlike Environmental products and conjunction assessment masters: Reference externally issued environmental and paired-object assessment products; object-specific association does not own population models, weather forecasting or another object.
Note: Derived from boundary notes against neighbouring models.
What robots and AI may and may not do Derived, awaiting review
May
- Reconcile identity assertions: Proposed, unimplemented local operation. Stage a reversible alias or correlation decision without silently merging object masters.
- Record qualified characterization: Proposed, unimplemented local operation. Attach physical or capability assertions with source and applicability qualifiers.
- Register orbit evidence: Proposed, unimplemented local operation. Index an externally produced orbit solution; do not calculate or propagate it.
- Associate tracking evidence: Proposed, unimplemented local operation. Record a proposed observation-object association with uncertainty.
- Append lifecycle and lineage evidence: Proposed, unimplemented local operation. Record externally evidenced state or relationship changes without executing an action.
- Index risk and disposition evidence: Proposed, unimplemented local operation. Attach conjunction or disposal products and external review references.
- Project an authorized object view: Proposed, unimplemented local operation. Prepare a local recipient-scoped view with mandatory uncertainty and review qualifications.
Note: Derived from functions, policies, CRUD and access rules; prohibitions were not authored for agents as such.
Moral aspects Missing, in the backlog
Not described yet. This gap is in the card backlog.
Owners Filled
Steward
A role-based accountable steward and scoped authority policy; no named company or brand is the owner
Roles
- Object record steward
- Maintain local identity, evidence associations and reversible corrections.
- Orbit evidence reviewer
- Assess intended use, time/frame meaning and uncertainty qualifications without operating spacecraft.
- Registration liaison
- Verify filed references and role assertions without locally amending official registers.
- Policy custodian
- Approve scoped access and retention based on source terms and applicable authority.
- Independent reviewer
- Review omissions and conformance when external review becomes available; currently unfilled.
Links to other meta-models Filled
references
- WM-SPC-004 - Reconcile incoming candidate mission containment through optional time-qualified mission associations; preserve separate roots and mission-owned planning.
- WM-OBJ-001 - Bind manufactured physical-unit identity and description when known; retain only space-specific assertions here.
- WM-XCT-001 - Resolve ownership and stewardship authority externally; retain qualified subject-role assertions only.
- WM-XCT-009 - Bind time-system definitions and validated conversions; never relabel native dynamical epochs as UTC.
- WM-SPC-002 - Resolve central-body or natural-body reference without owning celestial-body identity.
- External environment and debris assessment profiles - Resolve independently mastered environmental, population and mitigation products with version and applicability.
aligned
- CCSDS 502.0-B-3 / 503.0-B-2 / 508.0-B-1 - Candidate message mappings only; pin issue, corrections and profile before implementation or conformance claims.
neighbor
- WM-SPC-004 Satellite Mission / Programme - Incoming candidate CONTAINS is reconciled as mission association with separately identified objects. Mission planning and mission-wide lifecycle remain external; an unknown fragment need not have a resolved mission.
- WM-OBJ-001 Physical Item Instance - Reference the manufactured unit when known; this model owns space-context assertions, not manufacturing, inventory or hardware maintenance.
- WM-XCT-001 Ownership / Stewardship - Owner, operator, custodian, launching state and state of registry are different qualified roles. Registration or operation alone is not ownership proof.
- WM-XCT-009 Time / Calendar - Use external time-reference bindings for conversion. Keep native dynamical time systems and epochs; RFC 3339 metadata timestamps do not permit relabelling non-UTC epochs as UTC.
- WM-SPC-002 Celestial Body and WM-SPC-003 Astronomical Observation - Natural bodies and their observations remain external; artificial-object track correlation does not create a natural-body master.
- Environmental products and conjunction assessment masters - Reference externally issued environmental and paired-object assessment products; object-specific association does not own population models, weather forecasting or another object.
What else AI and robots need to interact with it Incomplete
Identity and identifiers required Filled
- Authoritative master-system identifier scoped to its issuing authority
- Governed global identifier or IRI
- UUID or ULID assigned by the adopting Dimension
Direct properties required Missing, in the backlog
Not described yet. This gap is in the card backlog.
Recognition required Missing, in the backlog
Not described yet. This gap is in the card backlog.
Capabilities and actions required Filled
- Reconcile identity assertions: Proposed, unimplemented local operation. Stage a reversible alias or correlation decision without silently merging object masters.
- Record qualified characterization: Proposed, unimplemented local operation. Attach physical or capability assertions with source and applicability qualifiers.
- Register orbit evidence: Proposed, unimplemented local operation. Index an externally produced orbit solution; do not calculate or propagate it.
- Associate tracking evidence: Proposed, unimplemented local operation. Record a proposed observation-object association with uncertainty.
- Append lifecycle and lineage evidence: Proposed, unimplemented local operation. Record externally evidenced state or relationship changes without executing an action.
- Index risk and disposition evidence: Proposed, unimplemented local operation. Attach conjunction or disposal products and external review references.
- Project an authorized object view: Proposed, unimplemented local operation. Prepare a local recipient-scoped view with mandatory uncertainty and review qualifications.
Hazards and failure modes required Missing, in the backlog
Not described yet. This gap is in the card backlog.
Standards and interfaces required Missing, in the backlog
Not described yet. This gap is in the card backlog.
Context of use required Filled
- UN registration guidance supports conceptual roles but treaty participation and national obligations require qualified review.
- The selected debris-mitigation overview describes a scoped programme framework, not a universal deadline or threshold.
- Operational thresholds and response authority belong to the adopting profile; none is fabricated here.
Sources Filled
- Orbit Data Messages - Consultative Committee for Space Data Systems
- Conjunction Data Message - Consultative Committee for Space Data Systems
- Tracking Data Message - Consultative Committee for Space Data Systems
- DISCOS 3: An improved data model for ESA's Database and Information System Characterising Objects in Space - European Space Agency Space Debris Office
- Toolkit on Good Registration Practices - United Nations Office for Outer Space Affairs
- Debris Mitigation - National Aeronautics and Space Administration Orbital Debris Program Office
- Satellite Drag - National Oceanic and Atmospheric Administration Space Weather Prediction Center
Open questions
- Verify full registration guidance and applicable law, latest standards and corrigenda, source rights and the current status of each cited URL outside the sandbox.
- Develop pinned instance profiles and tested mappings covering ambiguous identity, fragments, docking, non-UTC epochs, inconsistent covariance, stale products, unregistered objects and uncertain reentry.
- Extend and independently review deep-space and specialist profiles without absorbing neighboring mission, environment or physical-asset masters.
- Restore independent external review before any canonical or publishable-draft promotion.
- Independent external review is absent; a later local self-audit cannot substitute for it.
- Direct HTTP verification is unattempted under the owner-reported sandbox block. Six documents opened through the web tool; registration toolkit evidence is indexed-excerpt only with failed full retrieval.
- Latest standard versions, corrigenda, source licensing and current legal applicability are not comprehensively verified.
- Nested instance schemas, explicit per-profile required fields, pinned neighbor versions, time/frame transformations, executable message mappings and adversarial fixtures remain to be developed.
- No validated orbit propagation, collision probability, disposal analysis or public warning capability.
- Deep-space, lunar, tethered and novel servicing profiles, attitude dynamics and detailed radiation effects need further evidence and review.
Machine files
Provenance
world-models research · reviewable-draft
Built from: models/wm-spc-001-space-object-orbit/spec.yaml