Organizaciones internacionales y multilaterales: conformidad
How an implementer in international organisations and multilaterals demonstrates conformance: a self-assessment against the rules, clauses evaluated from evidence, attestations and a generated report. Each result names its evaluator and the time of evaluation, and each artefact is identified by a UNI (Unique Nexus Identifier).
- Nexus Standards: NS-0, NS-9, NS-10, NS-11, NS-14.
- Open standards: Sendai Framework for Disaster Risk Reduction 2015–2030; Statistical Data and Metadata eXchange (SDMX); IATI Standard 2.03; Standard country or area codes for statistical use (M49); International Public Sector Accounting Standards.
- Datos y fuentes: SDG Global Database; UNdata; OECD Data Explorer (incl. Creditor Reporting System, estadísticas de seguros y pensiones); IATI Datastore; Indicadores del Desarrollo Mundial.
- Se acopla con: sector público y gobierno; instituciones de financiación del desarrollo; sector humanitario y sociedad civil; para los responsables de políticas.
Resumen
- 01Autoevaluaciónfrente a las reglas
- 02Conjunto de cláusulasNS-10
- 03Evidenciareferenciada, no incorporada
- 04AtestaciónNS-11, evaluador designado
- 05Informegenerado a partir de los resultados
- Nexus Standards
- 5
- NS-0, NS-9, NS-10
- Estándares abiertos
- 5
- citado, nunca copiado
- Datos y flujos
- 5
- indicado como referencia
- Acoplamientos
- 4
- con otras áreas
Estándares incluidos en el nivel de sectores e industrias
Las áreas de programa de este nivel frente a las normas que enumeran en el registro; la fila de esta área fija el alcance inicial de una autoevaluación.
Matriz de coberturaUna celda rellena indica que el área incluye el estándar en el registro. Los términos de estado son los del registro.
Conformidad con NS-0
An implementation conforms to NS-0 when it:
- names the canonical repository and the versions of the standards it applies;
- does not fork a registry;
- runs the repository validator, or an equivalent, on the copies of the registries it uses;
- records its implementation status per standard in
registry/consumers.yamltruthfully;and - carries the honesty fields (
legalState,claimCeiling,status) on every record it publishes.
Conformance to NS-0 is a statement by the implementation, verifiable under NS-11. It is not a certification by the Secretariat or by the Global Standards Council.
Initial self-assessment for international organisations and multilaterals
Las primeras reglas de cada norma aplicable. Una autoevaluación es una declaración del implementador, verificable conforme a NS-11.
| Regla | Requisito | Estándar |
|---|---|---|
NS0-P1 | Open · 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. | NS-0 |
NS0-P2 | Primero legible por máquina · Todo elemento normativo existe como datos (registro, esquema, cláusula) antes de existir como prosa; la prosa explica, los datos rigen. Una norma sin forma legible por máquina no es un Nexus Standard. | NS-0 |
NS0-P3 | Identified · Every artefact, 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 | Each deployment or programme instance shall have one context record; the concept keeps its own UNI; context.ofUni is required and shall resolve. | NS-9 |
NS9-R2 | Context identifiers shall be allocated by the catalogue for their SCOPE; they shall not be derived from names or typed by hand. | NS-9 |
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. | NS-9 |
NS10-R1 | Every obligation that an implementation enforces shall be a clause with a UNI; code may implement a rule, but no rule shall be enforced without a clause record that names it. | NS-10 |
NS10-R2 | Subjects shall be contextual UNIs; names, labels or free text shall not bind. | NS-10 |
NS10-R3 | The predicate shall be data in a declared language; evaluators shall record the engine and its version; two conformant evaluators shall reach the same result for the same clause and the same inputs. | NS-10 |
NS11-R1 | A conformance statement shall rest on an attestation, and an attestation shall name an evaluator, a mandate, evidence references and a digest. | NS-11 |
NS11-R2 | Under zero trust, subject and evaluator shall be distinct, and production evaluations shall run outside the subject’s trust boundary. | NS-11 |
NS11-R3 | Missing or unresolvable evidence shall yield INDETERMINATE or REFUSED, never PASS (NS0-P12). | NS-11 |
NS14-R1 | The text of an external standard shall not be reproduced; it shall be cited by identifier, clause number and URL. | NS-14 |
NS14-R2 | Relation claims shall come from the register and from clause sets, not from prose. | NS-14 |
NS14-R3 | "Compliant" and "certified" shall appear only as quotations of an authority decision cited by reference. | NS-14 |
Atestaciones
One attestation is recorded per clause, per subject, per evaluation (AT categoría, solo de adición). Resultados: PASS; FAIL; INDETERMINATE (evidence missing or unresolvable); NOT_APPLICABLE (the subject was outside the clause’s selectors at that instant); REFUSED (the 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 es siempre false. A later attestation supersedes an earlier one for the same clause and subject, and the history is kept.
Crosswalks: an attestation can be exported as a W3C Verifiable Credential under the Verifiable Credentials Data Model 2.0 (subject: the contextual UNI; issuer: the evaluator; evidence: the refs), as an in-toto attestation (for software subjects) or as a PROV-O activity (NS-3b). The Nexus attestation remains the key and the record of truth.
Seguimiento
Monitoring is continuous evaluation together with 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) the availability of evaluators and evidence sources. Monitoring records are observations with record UNIs. Dashboards and panels are projections of them and show the timestamp and the evaluator for every value; no verdict is stored.
Informes
A conformance report for a context is generated, not written: policy by policy and clause by clause, with attestation UNIs, evidence refs, conformance levels (NS-10 section 3) and the honesty fields. Reports are catalogued artefacts (RP) y pueden publicarse (NS-8) solo cuando su legalState allows. A report does not say "certified" or "compliant" except when it quotes an authority decision by reference.
Presentación de las declaraciones de conformidad
A context (NS-9) or artefact claims a 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 with a current PASS)", with attestation UNIs. It is never displayed as "compliant with" or "certified to" unless a decision of the body entitled to say so is referenced. Where a body operates its own certification, conformance under the Nexus Standards is explicitly not that certification.
Preguntas y respuestas.
¿Cómo se relaciona un informe de conformidad en organizaciones internacionales y multilaterales con las decisiones de otros órganos?
¿Qué ocurre cuando falta evidencia?
En torno a las organizaciones internacionales y multilaterales.
Contribuya a configurar los estándares para organizaciones internacionales y multilaterales.
Se invita a los gobiernos, los reguladores, los organismos de normalización, la industria, el mundo académico y las comunidades a dar forma al catálogo antes de su primera versión oficial, prevista para 2030: comentar un borrador, proponer un cambio, unirse a un grupo de trabajo o acoger un ejercicio sobre el terreno.
Estado y uso. Las Nexus Standards son normas propuestas, elaboradas mediante un proceso abierto según NS-13 y publicadas para uso voluntario; no constituyen certificación, acreditación ni aprobación regulatoria, y su adopción sigue siendo una decisión del Global Standards Council y, en cada país, de su Consejo Nacional de Normas. Un UNI (Unique Nexus Identifier) identifica un artefacto; no lo certifica. Los nombres de los organismos de normalización y de sus normas pertenecen a sus titulares y se usan solo para identificar los documentos; aquí no se reproduce ningún texto de una norma externa. Nexus Standards no está afiliada a ningún organismo de normalización aquí nombrado, ni respaldada o certificada por él.
Licencias: CC BY 4.0 para el texto de los estándares, los registros, los esquemas y los datos; Apache-2.0 para el código de referencia. Los estándares externos se citan por nombre, número y enlace, conforme a sus propias licencias. Los datos, bibliotecas y fuentes tipográficas de terceros conservan sus propias licencias: véanse los Avisos de terceros.