How an adopter in finance, insurance and capital markets shows conformance: a self-assessment against the rules, clauses evaluated from evidence, attestations and a generated report. No step is a certification, and every result names its evaluator and evaluation instant. Identifiers are UNIs (Unique Nexus Identifier). 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.
The subsites of this tier against the standards they list in the registry; the row for this area is the self-assessment's starting scope. A listed standard is never a conformance claim.
Coverage matrixA filled cell means registry/subsites.yaml lists that standard under the area. PROPOSED, SPECIFIED, OPEN, PLANNED and WIRED are registry words; no cell is a conformance, certification or readiness statement.
A consumer conforms to NS-0 when it (1) names the canonical repository and the versions of the standards it applies, (2) never forks a registry, (3) runs the repository validator or an equivalent on its vendored copies, (4) records its implementation status per standard in registry/consumers.yaml honestly, and (5) carries the honesty fields on every record it publishes. Conformance to NS-0 is a statement by the consumer, verifiable under NS-11; it is not a certification by the trust and assurance system.
Fig.Subject, clauses, evaluator, attestation and report; any authority decision stays outside. Design, not a record.
The first rules of each standard that applies. A self-assessment is a statement by the adopter, verifiable under NS-11; it is not a certification.
| Rule | What it requires | Standard |
|---|---|---|
NS0-P1 | Open · The standards, their registries, schemas, catalogs and reference tools are published in the canonical repository under a licence recorded by counsel; participation in development is open to every community and stakeholder under GOVERNANCE.md; no standard depends on a proprietary artifact to be applied. | NS-0 |
NS0-P2 | Machine-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. | NS-0 |
NS0-P3 | Identified · Every artifact, record, deployment, policy and clause carries a UNI (NS-1, NS-3, NS-9). Nothing is cited by a name alone. | NS-0 |
NS9-R1 | One context record per deployment or programme instance; the concept keeps its own UNI; context.ofUni is required and must resolve. | NS-9 |
NS9-R2 | Context identifiers are allocated by the catalog for their SCOPE, never derived from names or typed by hand. | NS-9 |
NS9-R3 | A context's claim ceiling, legal state and conformance evidence are its own; they are never inherited from the concept or from another context. | NS-9 |
NS10-R1 | Every obligation enforced anywhere in the ecosystem is a clause with a UNI; no hidden rule in code without a clause record (the code may implement it, the clause names it). | NS-10 |
NS10-R2 | Subjects are contextual UNIs; names, labels or free text never bind. | NS-10 |
NS10-R3 | The predicate is data in a declared language; evaluators record engine and version; the same clause evaluated by two conformant evaluators yields the same result for the same inputs. | NS-10 |
NS11-R1 | No conformance statement without an attestation; no attestation without an evaluator, a mandate, evidence references and a digest. | NS-11 |
NS11-R2 | Zero trust: subject and evaluator are distinct; production evaluations run outside the subject's trust boundary. | NS-11 |
NS11-R3 | Missing or unresolvable evidence is INDETERMINATE or REFUSED, never PASS (NS0-P12). | NS-11 |
NS14-R1 | No reproduction of external standard text; cite by identifier, clause number and URL. | NS-14 |
NS14-R2 | Relation claims come from the register and clause sets, never from prose. | NS-14 |
NS14-R3 | "Compliant" and "certified" appear only as quotations of an authority decision by reference. | NS-14 |
One attestation per clause per subject per evaluation (AT category, append-only). Results: PASS, FAIL, INDETERMINATE (evidence missing or unresolvable), NOT_APPLICABLE (subject outside the clause's selectors at that instant), REFUSED (evaluator lacked a mandate or the evidence was not accessible; the refusal is itself recorded). An attestation carries a canonical digest and optionally a signature; certifiesTruth is always false. A later attestation supersedes an earlier one for the same clause and subject; history is kept.
Crosswalks: an attestation can be exported as a W3C Verifiable Credential (subject = contextual UNI, issuer = evaluator, evidence = refs), as an in-toto attestation (software subjects) or as a PROV-O activity (NS-3b). The Nexus record stays the key.
Monitoring is continuous evaluation plus observation records: for each bound policy and context, the monitoring service records (a) the latest attestation per clause, (b) coverage (which clauses have no current attestation and why), (c) drift (a change in a subject's records that invalidates an attestation), and (d) availability of evaluators and evidence sources. Monitoring records are observations with record UNIs; dashboards and room surfaces are projections of them and show the timestamp and evaluator for every value (no standing verdict).
A conformance report for a context is generated, not written: policy by policy, clause by clause, with attestation UNIs, evidence refs, levels per NS-10 §3, and the honesty fields. Reports are catalogued artifacts (RP) and may be published (NS-8) only when their legalState allows. A report never says "certified" or "compliant" unless quoting an authority decision by reference.
A context (NS-9) or artifact may claim relation to an external standard only through a clause set (NS-10) that cites that standard and is evaluated (NS-11). The claim is displayed as "implements clauses derived from <standard> (n of m current PASS)" with attestation UNIs, never as "compliant with" or "certified to" unless an authority decision by the body entitled to say so is referenced. Where a body operates its own certification, Nexus conformance is explicitly not that certification.
Risk Academy disciplines that teach Finance, insurance and capital markets, 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.
Every standard here is proposed. Changes enter as proposals under NS-13; conformance is shown by attestations under NS-11; 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.