Deployment services: standards that apply
The 2 standards listed for deployment services in the registry, each with its status, UNI (Unique Nexus Identifier) and the rules stated in its text.
- Nexus Standards: NS-9, NS-11, NS-12.
- Open standards: Supply-chain Levels for Software Artifacts (SLSA); Sigstore (Cosign, Fulcio, Rekor); CycloneDX Bill of Materials (ECMA-424); OCI Image and Distribution Specifications; The Update Framework (TUF).
- Data and feeds: endoflife.date API; OSV.dev vulnerability API; deps.dev API.
- Couples with: Software and supply chain; Identification (the UNI); Monitoring services.
- Nexus Standards
- 3
- NS-9, NS-11, NS-12
- Open standards
- 5
- named, never copied
- Data and feeds
- 3
- listed for reference
- Couplings
- 3
- with other areas
Kontekstuele UNI's (ontplooiings, instansies, programinstansies)
Status proposed · trust, authorisation and assurance · NXS-STD-ST-000005.
| Rule | Text |
|---|---|
NS9-R1 | Each deployment or programme instance shall have one context record; the concept keeps its own UNI; context.ofUni is required and shall resolve. |
NS9-R2 | Context identifiers shall be allocated by the catalogue for their SCOPE; they shall not be derived from names or typed by hand. |
NS9-R3 | The supported claim level, legal state and conformance evidence of a context are its own; they shall not be inherited from the concept or from another context. |
NS9-R4 | Closing a context shall not delete it: context.validUntil is set and the status becomes WITHDRAWN or SUPERSEDED met supersededBy. |
NS9-R5 | Display names in context shall follow the marks policy; the UNI, not the name, is the key everywhere. |
Sagteware-, model- en KI/ML-artefakte (voorsieningsketting, modelkaarte, datastelblaaie)
Status proposed · software, models and capability lifecycle; trust, authorisation and assurance · NXS-STD-ST-000012.
| Rule | Text |
|---|---|
NS12-R1 | Each software release shall carry a bill of materials, a build attestation and signatures as evidence of the UNI version. |
NS12-R2 | Each model shall carry a model card and each dataset a dataset sheet; both shall cite their sources by UNI. |
NS12-R3 | Agents shall act under recorded mandates and shall be credited as agents; they shall not adopt or certify. |
NS12-R4 | AI governance obligations shall be clauses bound to contextual UNIs and evaluated, not prose assurances. |
Questions and answers.
Are these all the rules for deployment services?
What does a rule identifier such as NS1-R5 denote?
Around deployment services.
Shape the standards for deployment services.
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.
Status en gebruik. Die Nexus Standards is voorgestelde standaarde wat deur 'n oop proses onder NS-13 ontwikkel en vir vrywillige gebruik gepubliseer word; hulle maak nie sertifisering, akkreditasie of regulatoriese goedkeuring uit nie, en aanvaarding bly 'n besluit van die Wêreldwye Standaarderaad en, in elke land, van sy Nasionale Standaarderaad. 'n UNI (Unique Nexus Identifier) identifiseer 'n artefak; dit sertifiseer dit nie. Name van standaardliggame en hul standaarde behoort aan hul rentmeesters en word slegs gebruik om die dokumente te identifiseer; geen teks van 'n eksterne standaard word hier gereproduseer nie. Nexus Standards is nie geaffilieer met, onderskryf deur of gesertifiseer deur enige standaardliggaam wat hier genoem word nie.
Lisensies: CC BY 4.0 vir standaardteks, registers, skemas en data; Apache-2.0 vir verwysingskode. Eksterne standaarde word volgens naam, nommer en skakel onder hul eie lisensies aangehaal. Derdeparty-data, -biblioteke en -lettertipes behou hul eie lisensies: sien Kennisgewings van derde partye.