The space industry section of the Space and Earth Observation subsite covers satellite operators, launch providers and space data companies: how orbital, debris, space-weather and service-continuity records are identified and verified, crosswalked to the UN long-term sustainability guidelines, debris mitigation guidelines, orbit data messages and the Radio Regulations, including the dependence of terrestrial infrastructure on space services. Every artifact of the area carries a UNI (Unique Nexus Identifier), which identifies and never certifies.
Context entry PROPOSED for the Nexus Standards registry.
Nexus Standards (2026). Space industry: area brief, Space and Earth Observation (PROPOSED). https://nexustandards.com/space/space-industry/. Last reviewed 2026-10-17.
Files carry the credits and the licence line; they are generated in your browser and nothing is sent. Downloads need script.
The sectors and industries section of Space and Earth Observation. Scope as the area context entry states it (PROPOSED).
In scope 5
Out of scope 3
Jurisdictions No jurisdiction note is recorded for this area yet; jurisdiction narrows what applies and never implies that a Nexus profile satisfies a law.
The Nexus Standards the area context entry lists. Every one is proposed or specified; none is adopted by an authority.
Status proposed · 12 rules stated. Read NS-0
Status proposed · 0 rules stated. Read NS-3
Status proposed · 0 rules stated. Read NS-3b
Status proposed · 5 rules stated. Read NS-9
Status proposed · 6 rules stated. Read NS-11
Relations are register entries (NS-14), never conformance or equivalence statements; hover or focus a relation for its meaning. Names of standards bodies and their standards belong to their stewards and are used only to identify the documents; no text of an external standard is reproduced here.
Closed or paywalled standards appear by name and link only; any compatibility profile of one is built on simulated data and kept on protected pages until an institutional arrangement with the issuing body is recorded. Nexus Standards is not affiliated with, endorsed by or certified by any standards body named here.
The working group may name closed standards later; they would be listed here by name and link only.
Hazards and threats 4
Sectors 2
Each coupling names the mechanism that links this area to another; select a card on the canvas to trace it. Mechanisms are stated in the context bank (PROPOSED).
Fig.RUNNING marks the area you are reading; DONE an area in the same subsite, QUEUED an area elsewhere and GATE a subsite reached. Tags give reading order only, never a status. Design, not a record.
Sources the area reads or proposes. Delivery follows GRIx first; a source is shown live only after an owner decision admits it for public pages.
No legal register row admits any of these sources for live display on public pages yet, so nothing is read from them here. A register row that exists records the source for the governed GRIx path; admission for public pages is a separate owner decision.
CelesTrak GP orbital element setspending admission
CelesTrak · every 2 hours
CelesTrak usage policy (free public data with attribution)
GRIx governed readregister row exists
Online Index of Objects Launched into Outer Spacepending admission
UNOOSA · continuous
UN website terms (reuse terms to be recorded)
build-time snapshotproposed register row
Space Weather Prediction Center productspending admission
NOAA · real time
U.S. Government work (public domain)
GRIx governed readproposed register row
Orbital, debris and space-weather impact records with provenance become readable as evidence for GCRI Canada research under its own rules.
An operator that publishes sustainability clauses and attestations gives GRF a record trail to consider; nothing is recognised by adoption.
Space infrastructure projects can present verified debris-mitigation and continuity records to GRA, which assesses capital readiness under its own rules.
Each institution decides under its own rules what it reads as evidence; no pathway is an approval, a readiness statement or investment advice.
Pick a sector, hazard family, capability and artifact type; the registry routes the standards and says why.
Pending admissionVersion and feed state per standard; every row reads source feed pending admission until a register row admits a feed.
Today · from the registryTest suites, conformance statements and attestations per standard; no attestation is recorded yet, and none would certify.
A console computes from the registry and shows its reasons; it never decides, approves or certifies.
Indicator names and codes as their stewards publish them; values appear only from a governed GRIx source, never typed into a page.
Profile orbital, debris, space-weather and service-continuity records and crosswalk them to the UN LTS guidelines, IADC guidelines, CCSDS messages and ITU instruments.
No working group is chartered yet; a community may charter this one under NS-13 through a docket.
Peer-reviewed sources and published statistics on the publishers' own domains, as the context entry cites them.
Plain links to the faculty pages of Risk Academy; no course, credential, recognition or endorsement is implied.
Risk Academy disciplines that teach Space industry, with their courses; the GCRI Canada, The Global Risks Forum (GRF) and The Global Risks Alliance (GRA) subsites that carry those disciplines; and the Nexus Foundry systems the standards name. Mappings are proposed for review (Risk Academy standards map, 2026-10-17); a link says a page on the same subject exists, never an endorsement or a conformance statement; framework names in course titles are named and linked, never reproduced.
Propose a change, join the working group or name a source. Area entries are PROPOSED content for the Nexus Standards registry; a UNI identifies and never certifies, and nothing on this site is a certification, an approval or a readiness statement.
Nexus Standards documents CC BY 4.0 · tooling Apache-2.0 · counsel review pending (DEC-2026-10-16-NEXUS-STANDARDS-OPEN-LICENCE). External standards are named and linked under their own licences; a UNI (Unique Nexus Identifier) identifies, it never certifies. · Generated from the Nexus Standards corpus at commit 437ae044c5cb (2026-10-17); proposed and open.