Static view: the interactive graph runs where this page’s scripts and WebGL can; every node is also linked on this page.
Reports · Nexus Standards · Capability
capability
Trust, verification and assurance in Reports
Assurance here means evidence anyone can check: who evaluated what, against which clause, with which result and when. This page shows the series it feeds, the evidence behind it and how to contribute.
- Series
- 3
- Systems
- 3
- Areas
- 10
What this area brings to the editions.
Assurance here means evidence anyone can check: who evaluated what, against which clause, with which result and when. This subsite holds the identity, supply-chain, verification, conformance and ethics standards, the verification console and the conformance pipeline; nothing in it certifies.
From Foundry evidence to the series.
The evidence, step by step, from the systems this area reads to the series it feeds.
How Trust, verification and assurance reaches Reports: what it reads, how it reads it, the sealed cut and the series it feeds.
| Step | What happens | Source |
|---|---|---|
| 01 What it reads | Trust, verification and assurance reads NXS-NSF and NXS-NXQ (software, models and capability lifecycle): governed sources with their releases, never a value without its source. | |
| 02 The cut is sealed | Each quarter the evidence is sealed in one cut, so OBSERVED, REPORTED and ESTIMATED values stay apart and every edition can be rebuilt. | |
| 03 The series it feeds | The cut feeds Methods and Technical and Global Sector Risk and Resilience, from the Baseline Edition 2026 into the quarterly series. | |
| 04 Who decides | Decisions stay with the authorities that hold them, under their own rules; an edition informs a decision and never makes it. |
A teaching model of the evidence path, not a forecast and not a record of any run; the systems, methods and series named come from the registries. Sources: Trust, verification and assurance in Reports (2026); Trust, verification and assurance home (2026).
The series it feeds, and what backs each.
| Series | Foundry systems it draws on | Academy disciplines | Series home |
|---|---|---|---|
| Methods and Technical | NXS-GRX (canonical data, provenance and risk) the methods, indicators and validation studies behind each product NXS-LAB (research, experiments and simulations) method comparisons under transparent test conditions NXS-NXQ the fitness record of models and tools the methods use | Quantitative risk analysis and statistics Model risk and validation Risk indicators and composite indices | Methods and Technical series home |
| Global Sector Risk and Resilience | NXS-GRX one sector’s structure, dependencies and concentration measures NXS-EOP (earth observation and digital twins) observed change in the sector’s assets and their surroundings | Trade, supply chains and geoeconomics Critical infrastructure and lifelines | Global Sector Risk and Resilience series home |
| Evidence Brief | NXS-GRX the evidence behind one question, with its strength and gaps NXS-POR (public, client and partner delivery) the public-safe release of a brief and its corrections NXS-DSS (decision cases and deliberation) what the evidence settles for the decision in hand | Research, evidence and the science-policy interface Risk communication and risk literacy Uncertainty and decision making | Evidence Brief series home |
The 10 areas inside Trust, verification and assurance.
Each area is a section of this Nexus Standards subsite. Its parts, indicators and working group feed the standards progress reported each quarter.
- capabilitiesNS-12 · NS-11 · NS-1Software and supply chainSets the evidence a risk software release must carry: SBOMs in SPDX or CycloneDX, SLSA build provenance as in-toto attestations, Sigstore signatures, vulnerability…
- capabilitiesNS-11 · NS-10 · NS-9Identity, authorisation and zero trustSpecifies verified identity for people and workloads, mandates as scoped and time-boxed authority, deny-by-default authorisation with policy decision and enforcement…
- capabilitiesNS-10 · NS-11 · NS-14Policies and clausesTurns normative statements into machine-readable clauses with declared engines (JSON Schema, JSON Logic, CEL, Rego, SQL views), deterministic evaluation, failure…
- capabilitiesNS-11 · NS-10 · NS-14Verification and monitoringSpecifies continuous conformance observation: attestations with evaluator, instant, validity window and verdict (PASS, FAIL, INDETERMINATE), drift re-evaluation when…
- capabilitiesNS-14 · NS-11 · NS-10Conformance and crosswalk to external standardsSpecifies how an artefact states and evidences its relation (adopt, profile, crosswalk, cite, extend, gap) to ISO, NIST, IEC, OGC, W3C, UN and sector standards, with…
- capabilitiesNS-0 · NS-10 · NS-11 · NS-12Ethics, safeguarding and do no harmSpecifies ethical review, safeguarding and do-no-harm obligations for risk data, models, maps and interventions: harm assessment before publication, community consent…
- infrastructureNS-11 · NS-14 · NS-10Verification servicesOffers attestation, evidence checking and conformance reporting as a service for adopters and third parties: hosted conformance runs that produce EVALUATED…
- infrastructureNS-11 · NS-10 · NS-9Zero-trust fabricRuns the identity and authorisation infrastructure of NIST SP 800-207: OpenID Connect and OAuth 2.1 for people, FIDO2 for mandate holders, SCIM provisioning, SPIFFE…
- infrastructureNS-11 · NS-3b · NS-5Verified intelligence and transparencyOperates evidence-over-assertion infrastructure: an append-only Merkle transparency log of receipts with signed tree heads and consistency proofs, PROV-O and VC…
- infrastructureNS-14 · NS-11 · NS-13Conformance test suitesMaintains one open test corpus per standard and conformance class, run by three runners (browser sandbox, CI action, hosted validator), with abstract tests tied to…
Parts and open standards applied here.
Nexus Standards parts are preparatory working drafts (2026); external standards are cited, never reproduced.
The systems, methods and teaching behind it.
Where the same subject is reported elsewhere.
- Coupled areaNexus StandardsDeployment servicesDeployment refuses an image or package whose signature, SBOM or provenance predicate fails verification, so supply-chain evidence is enforced at the point of deploy.
- Coupled areaNexus StandardsVerification and monitoringEvery clause evaluation produces one attestation, so verification is the record of clause outcomes.
- Coupled areaNexus StandardsAI, models and agentsModel evaluations include subgroup harms and an impact review before use in targeting or triage.
- Coupled areaNexus StandardsProvenance and evidenceReceipts and lineage defined there are logged here; inclusion proofs make silent edits detectable.
- Coupled areaNexus StandardsZero-trust fabricThe infrastructure section runs the identity providers, SPIRE, OPA bundles and status lists that implement these rules.
- Coupled areaNexus StandardsPolicies and clausesCrosswalk rows feed derivedFrom on clauses, so a change in an external edition flags dependent clauses.
- Coupled areaNexus StandardsCommons and command roomsRooms bind policy packs to their contextual UNI and enforce onFailure effects (warn, degrade-claim, refuse, escalate, revoke).
- Coupled areaNexus StandardsConformance and crosswalk to external standardsClauses derived from external standards record derivedFrom register rows and encoding notes without reproducing the source text.
Contribute on Trust, verification and assurance.
Evidence, a case, a correction, a method or profile input on this subject. The composer tags it with this area and its series.
Write a contribution the editor can act on.
Say what it is, where its record is kept and on which licence. It arrives tagged with this page, its area and its gateway, so it reaches the editor who owns it.
Your email opens with the subject and a template already filled in for GW-STD.
- Evidence
- Correction
- Case study
- Analysis or method
- Peer review
- Translation
- Profile input
Never send personal data or sensitive infrastructure detail. A contribution is reviewed before use; sending it confers no authorship or editorial rights.
Open science for Trust, verification and assurance.
How a contribution on this subject is deposited, identified, credited, licensed and found, and the metadata for it prefilled from this page.
Trust, verification and assurance’s open record
- Area
- Trust, verification and assurance
- Feeds
- Methods and Technical, Global Sector Risk and Resilience, Evidence Brief
- Record
- A UNI for every accepted contribution; cited with its DOI in the edition that uses it
- Links
- isSupplementTo the edition it informs; isNewVersionOf its earlier version
- Licence
- CC BY 4.0 (SPDX CC-BY-4.0) for original material; metadata CC0 1.0
Credit and identity
- ORCID
- Your iD in the deposit and the contribution record; DataCite can then add the work to your ORCID record
- ROR
- Your organisation by its ROR identifier, never by a typed name alone
- CRediT
- Conceptualization, Data curation, Formal analysis, Investigation, Methodology, Software, Validation, Visualisation, Writing, review and editing
- Account
- None needed to contribute; never a password
Find and follow
Search the open indexes for Trust, verification and assurance; software is cited by its SWHID from Software Heritage. Annotation is your choice: Hypothesis opens this page in its own viewer.
Mirrors and harvest
The DOI is canonical. At release each signed bundle is also given an IPFS content identifier and a bloxberg anchor as mirrors; both are listed in the record once they exist. Zenodo exposes every record over OAI-PMH, and reviews and endorsements can arrive through COAR Notify where the repository supports it.
{
"metadata": {
"resource_type": {
"id": "dataset"
},
"title": "Evidence on Trust, verification and assurance for Nexus Reports",
"publication_date": "YYYY-MM-DD",
"creators": [
{
"person_or_org": {
"type": "personal",
"family_name": "Your family name",
"given_name": "Your given name",
"identifiers": [
{
"scheme": "orcid",
"identifier": "0000-0000-0000-0000"
}
]
},
"affiliations": [
{
"id": "ROR identifier of your organisation"
}
]
}
],
"description": "What it is, where its record is kept and how it bears on Trust, verification and assurance in Nexus Reports.",
"rights": [
{
"id": "cc-by-4.0"
}
],
"subjects": [
{
"subject": "Nexus Reports"
},
{
"subject": "Trust, verification and assurance"
},
{
"subject": "capability"
}
],
"related_identifiers": [
{
"identifier": "https://nexustandards.com/nexus-reports/areas/trust-and-assurance/",
"scheme": "url",
"relation_type": {
"id": "issupplementto"
},
"resource_type": {
"id": "other"
}
}
],
"version": "1.0.0"
},
"custom_fields": {},
"access": {
"record": "public",
"files": "public"
},
"files": {
"enabled": true
},
"parent": {
"communities": {
"default": "nexusreports"
}
}
}Releases for this area.
Releases tagged to this area appear here once released.
Send evidence on Trust, verification and assurance.
Reports is the Consortium’s quarterly publication. What you know about this subject can become evidence, a case or a correction in the next edition, credited to you and published under CC BY 4.0 where it is your own work.
- EmailGateway GW-STDSend it from this pageEvidence, a correction, a case, a method, a review, a translation or profile input. It arrives tagged with this page, so the editor who owns it receives it.
- ZenodoOpen depositDeposit it and submit to the communityPublish your own record on Zenodo with your ORCID iD, then submit it to the Reports community there. Curators review it; the DOI stays yours.
- ReportsNexus StandardsSee every way to contributeThe contribution types, how each is reviewed, what credit you receive, the licence and what is never accepted.
Never send personal data, sensitive infrastructure detail or anything you have no right to share. A contribution is reviewed before use; sending it confers no authorship or editorial rights, and sponsorship never buys a finding.
Around the reports at Nexus Standards.
Bring what you know to the next edition.
Every quarter closes on a sealed evidence cut. Contributions received before the cut are reviewed for that edition; later ones wait for the next.
Legal documents.
Maps, data and figures on this site are shown for context and general information. They are not advice, forecasts or warnings; the limits of the information are set out in the Disclaimers and Data Notices.