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 · Foundations
foundations
Foundations and governance in Reports
Every area rests on the same few commitments: one identifier that identifies and never certifies, a public process that decides with written reasons, open licences, conformance shown from evidence, and closed standards named but never reproduced. This page shows the series it feeds, the evidence behind it and how to contribute.
- Series
- 3
- Systems
- 2
- Areas
- 10
What this area brings to the editions.
Every area rests on the same few commitments: one identifier that identifies and never certifies, a public process that decides with written reasons, open licences, conformance shown from evidence, and closed standards named but never reproduced. This subsite holds those commitments and the machinery that keeps them.
From Foundry evidence to the series.
The evidence, step by step, from the systems this area reads to the series it feeds.
How Foundations and governance 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 | Foundations and governance reads NXS-NSF (trust, authorisation and assurance) and NXS-HUB (knowledge, records and learning): 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: Foundations and governance in Reports (2026); Foundations and governance 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 (software, models and capability lifecycle) 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 Foundations and governance.
Each area is a section of this Nexus Standards subsite. Its parts, indicators and working group feed the standards progress reported each quarter.
- capabilitiesNS-0 · NS-13Open standards developmentDefines how anyone proposes, debates, versions and takes up a Nexus Standard: the open-to-adoption track, chartered working groups, consensus with recorded dissent,…
- capabilitiesNS-0 · NS-9 · NS-1Naming, marks and intellectual propertySets neutral display names, contextual naming for national and regional use, nominative use of other bodies’ names, trademark safety checks, the legal state of every…
- foundationsNS-1 · NS-10 · NS-11Constitution and principlesSets out the founding commitments every Nexus Standard inherits (NS-0): participation without a fee, consensus with recorded dissent, nominative use of other bodies’…
- foundationsNS-1 · NS-3 · NS-7 · NS-9The UNI and the artefact catalogueExplains the UNI (Unique Nexus Identifier, NS-1): the grammar NXS-SCOPE-CAT[-REGION]-SERIAL[@VERSION], allocation only through the catalogue CLI, never deleted or…
- foundationsNS-1 · NS-10 · NS-11How a standard is madeDescribes the NS-13 track decided on 2026-10-16: OPEN, COMMUNITY DRAFT, PROPOSED, CANDIDATE, ADOPTED (and SUPERSEDED or WITHDRAWN), with the entry condition for each…
- foundationsNS-9 · NS-10 · NS-11Governance and liaisonDescribes who governs the track and how other bodies are related to it: a technical steering committee of working-group chairs and the three institutions’ technical…
- foundationsNS-1 · NS-10Licensing and intellectual propertyStates the decided licence set and why: CC BY 4.0 for documents, profiles, clauses and site content; Apache-2.0 for the CLI, validators, SDK snippets and conformance…
- foundationsNS-10 · NS-11 · NS-1Conformance programmeExplains conformance without certification: each standard names conformance classes and rule anchors (NS-n-Rm); every PROPOSED standard ships an open, executable test…
- foundationsNS-10 · NS-11Compatibility profiles for closed standardsParts NS-10, NS-11.
- foundationsNS-1 · NS-9Start here and contributeThe entry point for anyone who wants to build: what Nexus Standards is and is not, which areas are OPEN, how a community adopts an area by chartering a working group,…
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 StandardsConformance test suitesA standard cannot enter PROPOSED without a test suite or CANDIDATE without two independent implementations passing it.
- Coupled areaNexus StandardsNaming, marks and intellectual propertyContribution agreements (OWFa 1.0, DCO 1.1) and the licence stack decide what may be merged and published.
- Coupled areaNexus StandardsCommunities, learning and contributionWorking groups and chapters in the Communities, Learning and Contribution subsite are the bodies that move drafts along the track.
- Coupled areaNexus StandardsIdentification (the UNI)Codes stay internal under NS1-R7; display names come from the name architecture and are bound to the UNI record.
- Coupled areaNexus StandardsData and datasetsLicence register states gate data ingest and publication; PROHIBITED and legal review required block use.
- Coupled areaNexus StandardsOpen standards developmentContribution agreements and licence choices determine what text, code and data can be accepted.
- Coupled areaNexus StandardsHow a standard is madeA contribution enters the track as an issue or proposal with a UNI and moves through the stages; this section explains the path, the track enforces it.
- Coupled areaNexus StandardsLicensing and intellectual propertyContributors meet the OWFa and DCO requirements here before their first contribution is accepted, so IPR is settled at the door.
Contribute on Foundations and governance.
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 Foundations and governance.
How a contribution on this subject is deposited, identified, credited, licensed and found, and the metadata for it prefilled from this page.
Foundations and governance’s open record
- Area
- Foundations and governance
- 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 Foundations and governance; 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 Foundations and governance 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 Foundations and governance in Nexus Reports.",
"rights": [
{
"id": "cc-by-4.0"
}
],
"subjects": [
{
"subject": "Nexus Reports"
},
{
"subject": "Foundations and governance"
},
{
"subject": "foundations"
}
],
"related_identifiers": [
{
"identifier": "https://nexustandards.com/nexus-reports/areas/foundations/",
"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 Foundations and governance.
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.
