Skip to content
StandardsSpace weather, spectrum and timing risk standardsStandards that apply
Space weather, spectrum and timing risk

Space weather, spectrum and timing risk: standards that apply

The 3 standards listed for space weather, spectrum and timing risk in the registry, each with its status, UNI (Unique Nexus Identifier) and the rules stated in its text.

মহাকাশ আবহাওয়া, বর্ণালি ও সময় নির্ধারণ ঝুঁকির মান
What this area is built from: the Nexus Standards it applies (marked), the open standards it names and the data and feeds it reads, then the areas it couples with.Source: the Nexus Standards registry: the area record.
  • Nexus Standards: NS-0, NS-3, NS-9, NS-11.
  • Open standards: Common Alerting Protocol Version 1.2; UNDRR-ISC Hazard Information Profiles; RFC 7946 The GeoJSON Format; Sendai Framework for Disaster Risk Reduction 2015–2030.
  • Data and feeds: NOAA SWPC space weather products (JSON services); CelesTrak GP orbital element sets (OMM).
  • Couples with: Energy; Critical infrastructure and critical entities; Extraterrestrial hazard; Cyber and digital.
Nexus Standards
4
NS-0, NS-3, NS-9
Open standards
4
named, never copied
Data and feeds
2
listed for reference
Couplings
4
with other areas
01NS-0

সংবিধান ও নীতিমালা

Status proposed · trust, authorisation and assurance · NXS-STD-ST-000004.

RuleText
NS0-P1Open · The standards, their registries, schemas, catalogues and reference tools are published in the canonical repository under the licences recorded in LICENSING.md. Participation in development is open to every community and stakeholder under GOVERNANCE.md. No standard depends on a proprietary artefact, product, account or mark to be applied.
NS0-P2Machine-readable first · Every normative element exists as data (registry, schema, clause) before it exists as prose; prose explains, data governs. A standard with no machine form is not a Nexus Standard.
NS0-P3Identified · Every artefact, record, deployment, policy and clause carries a UNI (NS-1, NS-3, NS-9). Nothing is cited by a name alone.
NS0-P4Verified, not asserted · Conformance is a claim with evidence: receipts, digests, signed attestations and observations (NS-11). A claim without evidence is recorded as a claim, never as a fact, and the supported claim level of the implementation bounds every statement it makes.
NS0-P5Zero trust · Authenticated is not authorised; entitled is not authorised; access is denied by default. Every verification, monitoring and enforcement path assumes no implicit trust between systems, tenants, sites or agents, and records who verified what under which mandate.
NS0-P6Real-time · Standards express obligations that can be evaluated continuously against live records (observations, releases, corrections, deployments), and the standards themselves are versioned so that an implementation can state exactly which version it conforms to at any instant.
NS0-P7Provenance everywhere · Every artefact records what it was derived from, who produced it, under which release and policy decision, and what corrected it (NS-3b, PROV-O profile). Corrections supersede; nothing is silently rewritten.
NS0-P8Honest · A UNI identifies and resolves; it never certifies. legalState defaults to review-required. Readiness, approval and production status are never implied by a standard, a status, a page, a score or a badge.
NS0-P9Nexus-aware · Standards address cross-domain interdependence (water, energy, food, health, biodiversity, climate and the sectors they touch) explicitly: an obligation can reference artefacts in another domain, and cascades are first-class.
NS0-P10Names are governed · Codes are never names. Public names follow the marks policy (governance/OPEN_BOUNDARY_IPR_AND_LICENSING.md, section 7). A system or component is shown by its neutral display name and its UNI; the UNI may change with context (NS-9), and no name infringes anyone’s mark.
NS0-P11Community-owned development · Proposals, comments, decisions and versions of every standard are themselves artefacts with UNIs. The development process is specified (NS-13) and open, and authority to adopt is recorded, never assumed.
NS0-P12Fail closed · Missing evidence, a missing legal state, a missing policy decision or unavailable verification results in a refusal with a typed reason, never in a pass.

Read NS-0 in full

02NS-3

ঝুঁকি রেকর্ড UNI (ব্যাকরণ, পূর্বতন ক্রসওয়াক, বরাদ্দ কর্তৃপক্ষ)

Status proposed · trust, authorisation and assurance; canonical risk data, records and provenance · NXS-STD-ST-000003.

NS-3 states its requirements in sections rather than in a table of rules.

Read NS-3 in full

03NS-11

যাচাইকরণ ও পর্যবেক্ষণ (প্রমাণ, প্রত্যয়ন, জিরো-ট্রাস্ট সামঞ্জস্য পর্যবেক্ষণ)

Status proposed · trust, authorisation and assurance · NXS-STD-ST-000007.

RuleText
NS11-R1A conformance statement shall rest on an attestation, and an attestation shall name an evaluator, a mandate, evidence references and a digest.
NS11-R2Under zero trust, subject and evaluator shall be distinct, and production evaluations shall run outside the subject’s trust boundary.
NS11-R3Missing or unresolvable evidence shall yield INDETERMINATE or REFUSED, never PASS (NS0-P12).
NS11-R4Attestations shall be append-only and superseded rather than changed; monitoring records shall be observations with record UNIs.
NS11-R5Every displayed conformance value shall carry its evaluation instant and its evaluator; projections shall not store verdicts.
NS11-R6Exports to Verifiable Credentials, in-toto or PROV-O are crosswalks; the Nexus attestation shall remain the record of truth.

Read NS-11 in full

04প্রশ্ন

Questions and answers.

Are these all the rules for space weather, spectrum and timing risk?
They are the rules stated by the listed standards. The principles of NS-0 bind every standard; clauses specific to the area, where needed, are written under NS-10 and evaluated under NS-11.
What does a rule identifier such as NS1-R5 denote?
The number of the standard and the number of the rule within it. Rule identifiers are stable so that clauses, attestations and publications can cite them.
মানদণ্ড

Shape the standards for space weather, spectrum and timing risk.

Governments, regulators, standards bodies, industry, academia and communities are invited to shape the catalogue ahead of its first official release, targeted for 2030: comment on a draft, propose a change, join a working group or host a field exercise.

অবস্থা ও ব্যবহার। Nexus Standards হলো NS-13-এর অধীনে একটি উন্মুক্ত প্রক্রিয়ায় তৈরি এবং স্বেচ্ছামূলক ব্যবহারের জন্য প্রকাশিত প্রস্তাবিত মানদণ্ড; এগুলো প্রত্যয়ন, স্বীকৃতিদান বা নিয়ন্ত্রক অনুমোদন নয়, এবং গ্রহণের সিদ্ধান্ত বৈশ্বিক মানদণ্ড পরিষদের এবং প্রতিটি দেশে তার জাতীয় মানদণ্ড পরিষদের। একটি UNI (Unique Nexus Identifier) একটি নিদর্শন শনাক্ত করে; এটি তা প্রত্যয়ন করে না। মানদণ্ড সংস্থা ও তাদের মানদণ্ডের নাম তাদের তত্ত্বাবধায়কদের এবং কেবল নথি শনাক্ত করতে ব্যবহৃত; এখানে কোনো বহিরাগত মানদণ্ডের পাঠ পুনরুৎপাদিত হয়নি। Nexus Standards এখানে উল্লিখিত কোনো মানদণ্ড সংস্থার সঙ্গে সম্পর্কিত নয়, তাদের দ্বারা অনুমোদিত বা প্রত্যয়িত নয়।

লাইসেন্স: মানের পাঠ্য, নিবন্ধ, স্কিমা ও ডেটার জন্য CC BY 4.0; রেফারেন্স কোডের জন্য Apache-2.0। বহিরাগত মান নিজ নিজ লাইসেন্সের অধীনে নাম, সংখ্যা ও লিংকসহ উদ্ধৃত হয়। তৃতীয় পক্ষের ডেটা, লাইব্রেরি ও ফন্ট নিজস্ব লাইসেন্স বজায় রাখে: তৃতীয় পক্ষের বিজ্ঞপ্তি দেখুন।