Public-safe records of programmes, evidence, publication status and correction histories, subject to owner authority. Nexus Registry is an established platform published by The Global Centre for Risk and Innovation.
GCRI · Established · service level R0
Research record integrity is the property of records that can be traced to who issued them, when, by what method and from which sources, and that change only through visible corrections. Nexus Registry covers programme status, provenance, correction and versioning, persistent identifiers, evidence classes, participation, rights and interoperability, with the standards that govern each.
Programme stewards; librarians; auditors; technical reviewers; contributors.
Record schemas; reference resolution; provenance and rights; correction trails.
Verified public record views; record methods; status glossary.
The working screen behind this platform: its structure, terms and states. Names are placeholders and values illustrative.
Registry · Ledger head 5355844
| NX-R-47092 | Programme status | v1 | 4258505 | Registered |
| NX-P-62248 | Publication | v2 | 9388917 | Registered |
| NX-E-95255 | Evidence record | v4 | 0174133 | Correction open |
| NX-C-49731 | Participation | v1 | 9437640 | Rights hold |
For nexus registry, in GCRI's spatial-intelligence reading, the map opens on true-colour imagery, night lights and population density with true colour from NASA GIBS, framed on World; every other NASA layer, live feed and forecast waits in the layer list.
The interactive map needs JavaScript; the layer list and sources are below.
Layers 3
People and hazards, for this page
Keyboard, with the map focused
Hold Ctrl or ⌘ and scroll to zoom
Latest available
NASA GIBS / EOSDIS · ASTER GDEM (METI, NASA) · Blue Marble (NASA) · © OpenStreetMap contributors (ODbL) · Natural Earth
Loading the latest NASA imagery.
Drag to move. Ctrl or ⌘ and scroll, pinch or the buttons to zoom; hover for the values under the pointer; reset returns to the region.
For nexus registry, in GCRI's spatial-intelligence reading, the map opens on true-colour imagery, night lights and population density with true colour from NASA GIBS, framed on World; every other NASA layer, live feed and forecast waits in the layer list.Satellite and model products as NASA publishes them, each with its own date; indicators, not assessments of any place; claim ceiling INTEGRATED.
Layers and dates
What a programme state does and does not mean.
TopicIssuer, date, method and source lineage.
TopicSuperseded assertions and correction routes.
TopicPublication metadata and identifiers.
TopicEvidence type, reliance limits and confidence.
TopicConsent, recognition and programme boundaries.
TopicPublication rights, withdrawal and audience.
TopicStable references, exports and API semantics.
The platform does not set standards. It reads its evidence against the frameworks that competent bodies have adopted, so a finding can be placed where a decision-maker already works.
| Framework or standard | Body | What it sets |
|---|---|---|
| FAIR Guiding Principles | FORCE11 community, published in Scientific Data | Findability, accessibility, interoperability and reusability of data and metadata, for people and machines |
| CARE Principles for Indigenous Data Governance | Global Indigenous Data Alliance | Collective benefit, authority to control, responsibility and ethics for data about Indigenous peoples, lands and knowledge |
| TRUST Principles for digital repositories | Research Data Alliance community, published in Scientific Data | Transparency, responsibility, user focus, sustainability and technology as the basis of repository trustworthiness |
| COPE Core Practices and retraction guidelines | Committee on Publication Ethics | How editors and publishers handle allegations, corrections, retractions, expressions of concern and authorship disputes |
| PROV data model and ontology | World Wide Web Consortium (W3C) | A common vocabulary of entities, activities and agents for recording how a record was produced and changed |
| Data Catalog Vocabulary (DCAT) version 3 | World Wide Web Consortium (W3C) | How datasets, data services, distributions and their versions are described in catalogues and exchanged |
| OAIS reference model (ISO 14721) | CCSDS and the International Organization for Standardization | Functions, information packages and preservation description information for archives that keep records usable over the long term |
| ISO 19115 and ISO 19157 | ISO Technical Committee 211 | Metadata, lineage and data quality elements for geographic information, widely reused for the provenance of spatial records |
| DOI system (ISO 26324) | DOI Foundation and the International Organization for Standardization | Syntax, resolution and governance of digital object identifiers, operated through agencies such as Crossref and DataCite |
| CoreTrustSeal requirements | CoreTrustSeal Standards and Certification Board | Core requirements for trustworthy data repositories, covering organisation, digital object management and technology |
The Registry applies three methods from the STEM Commons: data engineering, interoperability and stewardship, which governs schemas, lineage and exchange formats; digital identity and public digital systems, which governs how people and institutions are identified without over-collecting personal data; and cybersecurity and cryptography, which governs integrity checks, access control and tamper evidence. Each is described with its limits on the STEM foundation of Nexus Registry.
Inside Nexus Foundry, the Registry works with the GRIx system for risk-data lineage, NSF, Rails and Portals. Its methods notes are designed for the Methods and Technical report series, and in the annual Nexus Universe programme it is designed to keep the evidence records across an edition.
The same questions are governed and applied elsewhere. Research Nexus at The Global Risks Forum (GRF) and Governance Nexus at The Global Risks Forum (GRF) convene institutions on research integrity and accountable governance, while Financial Regulation Nexus at The Global Risks Alliance (GRA) builds shared industry understanding of record-keeping and supervisory evidence in finance. All counterparts are listed on counterparts across the Consortium.
Every claim a public programme makes rests on a record somewhere: an agreement that constituted it, a dataset behind a figure, a review that cleared a report, a decision that corrected an error. When those records are missing, scattered or silently changed, three failures follow. Readers cannot tell an estimate from an observation. A programme announced as active may never have been constituted. And a correction made in one place does not reach the copies, citations and summaries that have already spread elsewhere.
Records science, the shared ground of archivists, librarians, data engineers and auditors, treats these as structural problems rather than lapses of care. A record is trustworthy when its identity is stable, its origin can be traced, its integrity can be verified and its history is kept. Failures cascade because records are linked: a superseded dataset quietly feeds a model, the model feeds a report, and the report feeds a decision. Without lineage, no one can find which downstream records an error has touched.
Consortium programmes add a further difficulty. Work is carried out by many institutions across six regions, each with its own authority over what it produces. A shared registry cannot override that authority. It can only make each owner's records consistent, citable and honest about their status.
Nexus Registry is designed for programme stewards, librarians, auditors, technical reviewers and contributors who need to cite, check or maintain the records behind Consortium work.
Released records of programme states, publications, evidence and corrections, each with its validity, issuer and evidence label, published on public records.
Versioned schemas, reference resolution, provenance and rights rules and correction trails, set out in the record model.
One meaning for each programme state across the three pillar institutions, set out on programme states.
No public record has been released yet. Records appear only when their owners release them and they pass review; the Registry never shows sample records presented as real.
Nexus Registry studies how research and programme records stay trustworthy over time: who issued an assertion, when, by what method and from which sources, how it is identified and linked, who may see it, and how it is corrected. Its pages set out the standards, identifiers, failure mechanisms, measures and decision holders for each part of the record, with every assertion labelled by its evidence and every correction kept visible.
What a programme status asserts, who attests it, and why a stated target is not a delivered result.
Issuer, date, method and source chain for every assertion, recorded so a reader can trace it back.
Errata, retractions, superseded versions and the routes by which corrections reach everyone who relied on a record.
DOIs, ORCID iDs, ROR IDs and other identifiers that keep references stable when names, locations and systems change.
Evidence classes, reliance limits and confidence statements that stop a weak source being read as a strong one.
Consent, contributor roles and programme boundaries for the people and organisations named in a record.
Licences, embargoes, audience classes and withdrawal, and the balance between an open record and the duty to protect.
Metadata schemas, crosswalks, interfaces and export formats that let registries exchange records without losing meaning.
Each term as this page uses it. Where a standard-setting body defines the term, the wording follows that body.
| Term | Definition |
|---|---|
| Provenance | Information about the entities, activities and people involved in producing a record, used to judge its quality and reliability, in the W3C PROV model. |
| Persistent identifier | A long-lasting reference to a digital object, person or organisation, such as a DOI, ORCID iD or ROR ID, that resolves even when locations change. |
| FAIR principles | Guiding principles that make data findable, accessible, interoperable and reusable by people and machines. |
| Versioning | Keeping each changed state of a record as a distinct, dated version linked to the ones before and after it. |
Every claim on Nexus Registry rests on methods with a canonical page in the STEM Commons, so readers can see what a finding depends on and where its limits lie.
A question becomes evidence, a governed build, an organized community, a controlled test, a reviewed publication and, finally, a decision taken by the competent authority under its own rules.
Fig.The Nexus cycle on this platform, from question to renewal. Design, not a record of a run.
GCRI studies a field as science, GRF governs it and GRA builds shared financial understanding of it. Nexus Registry links to its counterparts so that work on one side is visible on the others.
The current service level is R0: information and enquiries. An enquiry receives a reference and names the next step; applications, payments, compute allocations and registrations open only when their team, terms and review capacity exist.