Near-Earth object impacts are rare but potentially catastrophic, and orbital debris threatens the satellites on which warning, navigation and communications depend; both require long-lead detection and international coordination. This section of the Hazards and disaster risk reduction subsite sets records for impact-risk assessments, orbital object catalogues and conjunction events so that space agencies, civil protection and infrastructure operators share evidence with orbit solution versions and uncertainty. Every artifact of the area carries a UNI (Unique Nexus Identifier), which identifies and never certifies.
Nexus Standards (2026). Extraterrestrial hazard standards: area brief, Hazards and Disaster Risk Reduction (PROPOSED). https://nexustandards.com/hazards/extraterrestrial-hazard-standards/. 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 hazard and threat families section of Hazards and Disaster Risk Reduction. 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.
Hazards and threats 4
Sectors 4
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 sets (OMM)pending admission
CelesTrak · several times daily
CelesTrak usage policy (free with attribution); Foundry register: LEGAL_REVIEW_REQUIRED
build-time snapshotregister row exists
Minor Planet Center observations and orbitspending admission
IAU Minor Planet Center · daily
MPC data policy; licence to be recorded by Legal
build-time snapshotproposed register row
Sentry impact monitoring APIpending admission
NASA JPL Center for Near Earth Object Studies · daily
NASA/JPL public data; terms to be recorded by Legal
build-time snapshotproposed register row
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.
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.
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.
Indicator names and codes as their stewards publish them; values appear only from a governed GRIx source, never typed into a page.
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 · 6 rules stated. Read NS-11
Version and feed state per standard; every row reads source feed pending admission until a register row admits a feed.
Today · in your browserPick a sector, hazard family, capability and artifact type; the registry routes the standards and says why.
A console computes from the registry and shows its reasons; it never decides, approves or certifies.
GCRI Canada may admit impact and conjunction records with orbit solution version and covariance as research evidence; GCRI Canada decides under its own evidence and research rules, and no approval is implied.
GRF may record agencies publishing on the shared records as part of a planetary defence dialogue; GRF decides under its own recognition rules, and no recognition or endorsement is implied.
GRA may read orbital risk records when it considers space-dependent infrastructure finance; GRA decides under its own capital-readiness rules, and no approval, rating or investment view is implied.
Each institution decides under its own rules what it reads as evidence; no pathway is an approval, a readiness statement or investment advice.
Records for impact risk, orbital catalogues and conjunctions for civil risk communication.
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. No Risk Academy faculty pathway is linked to this area yet; one is linked when a faculty publishes a pathway that fits.
Risk Academy disciplines that teach Extraterrestrial hazard standards, 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.