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 · Infrastructure
infrastructure
Open infrastructure and developers in Reports
Standards are used through registries, resolvers, APIs, deployments and monitors. This page shows the series it feeds, the evidence behind it and how to contribute.
- Series
- 3
- Systems
- 5
- Areas
- 11
What this area brings to the editions.
Standards are used through registries, resolvers, APIs, deployments and monitors. This subsite holds that infrastructure, the monitoring console and its sandbox, and the developer paths that make the standards usable in code.
From Foundry evidence to the series.
The evidence, step by step, from the systems this area reads to the series it feeds.
How Open infrastructure and developers 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 | Open infrastructure and developers reads NXS-FAC (blueprints, builds and signing) 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: Open infrastructure and developers in Reports (2026); Open infrastructure and developers 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 11 areas inside Open infrastructure and developers.
Each area is a section of this Nexus Standards subsite. Its parts, indicators and working group feed the standards progress reported each quarter.
- audiencesNS-1 · NS-3 · NS-3b · NS-11 · NS-12For developersThe developer entry section of the Open Infrastructure and Developers subsite is written for software engineers in every community who need schemas, a resolver, a…
- capabilitiesNS-9 · NS-10 · NS-11 · NS-0Sovereign deployment and data residencySpecifies the normative requirements for running Nexus Standards on national or regional infrastructure: residency regions on every record, refusal of cross-region…
- infrastructureNS-1 · NS-7 · NS-3 · NS-6Registries and the resolverOperates the machine registries, catalogues and the UNI resolver as persistent-identifier infrastructure in the DataCite, ROR and ORCID mould: one stable URL per UNI,…
- infrastructureNS-9 · NS-12 · NS-11Deployment servicesProvides standard-conformant deployment of systems and components as catalogued contexts: blueprints, reproducible builds, signed images with SBOMs and SLSA…
- infrastructureNS-11 · NS-10 · NS-9Monitoring servicesRuns continuous observation of conformance and risk records across contexts, sectors and regions: scheduled and on-record clause evaluation, attestation freshness and…
- infrastructureNS-6 · NS-12 · NS-1Developers and APIsPublishes the reference tools, APIs, schemas and open-source stack adopters build on: OpenAPI 3.1 and AsyncAPI 3.0 contracts, JSON Schemas, SDKs per polyglot plane…
- infrastructureNS-9 · NS-10 · NS-11 · NS-6Commons and command roomsProvides the rooms where policies and clauses are implemented and enforced: each commons or command room is a catalogued context that binds policy packs, projects…
- infrastructureNS-7 · NS-8 · NS-3b · NS-2Indexing and discoveryMakes every public standard, record and artefact findable through the open indexing ecosystem: DataCite, Crossref, ORCID, ROR, OpenAlex, OpenAIRE, Software Heritage,…
- infrastructureNS-3 · NS-6 · NS-9Real-time fabricOperates the self-hostable real-time layer: MQTT 5 brokers on a WIS2-modelled topic hierarchy, WIS2-style notifications pointing at the resolver, CAP candidate…
- infrastructureNS-11 · NS-14 · NS-3Sandbox and simulated dataProvides a sandbox per profile with simulated, clearly labelled data so adopters can try records, clauses, CAP messages, STAC items and SBOMs without touching…
- infrastructureNS-9 · NS-12 · NS-11Sovereign stackPublishes the self-hostable reference deployment: Compose and Helm charts for PostgreSQL with PostGIS and h3-pg, the API, Rust evaluators, Go scheduler, Mosquitto and…
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.
- NXS-FACNXS-FACNXS-FACNXS-FAC
- NXS-NXQNXS-NXQNXS-NXQRooms: Capabilities, Competence.
- NXS-COR (compute, nodes and runtimes)NXS-CORNXS-CORNXS-COR
- NXS-NSF (trust, authorisation and assurance)NXS-NSFNXS-NSFRooms: Authority, Assurance.
- NXS-CMD (integrated posture and executive synthesis)NXS-CMDNXS-CMDRooms: Portfolios, Council.
Where the same subject is reported elsewhere.
- Coupled areaNexus StandardsDevelopers and APIsThe developer and API area documents the schemas, resolver and APIs this path starts from.
- Coupled areaNexus StandardsSandbox and simulated dataDevelopers try every API against simulated data before touching governed records.
- Coupled areaNexus StandardsSoftware and supply chainAdmission verifies signatures, SBOMs and provenance predicates defined by NS-12 and refuses images that fail.
- Coupled areaNexus StandardsConformance programmeDevelopers publish implementation conformance statements for their implementations.
- Coupled areaNexus StandardsSovereign stackNational resolvers run on the reference stack for their own scopes; the global resolver delegates by scope and region and returns the peer’s receipt.
- Coupled areaNexus StandardsRegistries and the resolverIndexes are fed from object_current via the resolver so that every index entry points at a stable UNI URL.
- Coupled areaNexus StandardsPrivacy and data protectionSimulated data replaces personal data for training and demos, with the synthetic label carried on every record.
- Coupled areaNexus StandardsIdentification (the UNI)Each deployment receives a contextual UNI (NS-9, category DP) and records its own status as the host’s statement.
Contribute on Open infrastructure and developers.
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 Open infrastructure and developers.
How a contribution on this subject is deposited, identified, credited, licensed and found, and the metadata for it prefilled from this page.
Open infrastructure and developers’s open record
- Area
- Open infrastructure and developers
- 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 Open infrastructure and developers; 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 Open infrastructure and developers 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 Open infrastructure and developers in Nexus Reports.",
"rights": [
{
"id": "cc-by-4.0"
}
],
"subjects": [
{
"subject": "Nexus Reports"
},
{
"subject": "Open infrastructure and developers"
},
{
"subject": "infrastructure"
}
],
"related_identifiers": [
{
"identifier": "https://nexustandards.com/nexus-reports/areas/open-infrastructure-and-developers/",
"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 Open infrastructure and developers.
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.