GCRI · Foundations
Evidence records and archive: how annual technical work becomes institutional memory
An annual programme learns only if each year can start from what the last one established. This page explains the records each Nexus Universe edition is designed to leave, what every record carries, and how corrections and the archive work.
- As of
- 21 October 2026
- Reading
- 12 minutes
- Evidence
- 18 sources, cited in order
Methods and evidence
- Evidence
- 18 sources, cited in order and listed under References
- Figures
- 4 figures
- Data availability
- Every chart's data is published as a table on this page.
- Replication
- 36%
- of 100 replicated psychology studies had significant results, against 97% of originals3
01What evidence records are
What evidence records are
Evidence records are the dated, attributed and versioned entries through which the Nexus Consortium keeps what was prepared, tested, observed, decided, corrected and withdrawn in its annual programme. The Nexus Consortium is the public-good programme through which The Global Centre for Risk and Innovation (GCRI), The Global Risks Forum (GRF) and The Global Risks Alliance (GRA) help countries examine interconnected risk with shared methods. GCRI sets out the model on therisk.global, and the evidence stage of how Nexus works explains where records enter the cycle. Its archive is the set of those records kept so that they can be found, read and corrected long after the people who made them have moved on.
The record model of the Registry sets out the NS-1 identifier grammar, the 32 fields of an artefact record in the catalogue schema, and the flat record that the snapshot publishes for all 12 record types 2,5.
The model identifies and describes; it does not decide whether a record is true or may be used. Legal state and claim limit are honesty fields, not readiness claims 2.
02Why a programme without records cannot learn
Why a programme without records cannot learn
An annual programme is a learning system only if each year can begin from what the last one established. Without records, a technical exercise becomes an anecdote, a dashboard becomes a screenshot and a simulation becomes a presentation. The same artifact can mean different things to different participants: a prototype to its builders, a validation to a sponsor, an observation to a public authority. A record fixes which it was.
The scientific literature shows what happens when findings travel without their trail. The Open Science Collaboration replicated 100 experimental and correlational studies published in three psychology journals: 97% of the original studies had statistically significant results, 36% of the replications did, 47% of original effect sizes were in the 95% confidence interval of the replication effect size, and replication effects were half the magnitude of original effects 3. The lesson for a risk programme is not about psychology. It is that a result can be checked only when its data, method and version are kept with it.
Exercise practice reaches the same conclusion from the other side. The World Health Organization’s Simulation Exercise Manual is a guide to planning, conducting and evaluating exercises 6. An exercise that leaves no record of its evaluation cannot be improved on.
Fig. 02Results that are not recorded cannot be checked
Figure 2 in words, and its data
Vertical bars on a scale from 0 to 100 per cent of the 100 studies. Original studies with significant results: 97. Replications with significant results: 36, highlighted. Original effect size inside the 95 per cent confidence interval of the replication: 47. Effects subjectively rated as replicated: 39. A side note says replication effects were half the magnitude of the originals and that a finding which cannot be traced to its data, method and version cannot be checked. The data are tabulated below the figure.
| Measure | Share of the 100 studies |
|---|---|
| Original studies with statistically significant results | 97% 3 |
| Replications with statistically significant results | 36% 3 |
| Original effect size inside the 95 per cent confidence interval of the replication | 47% 3 |
| Effects subjectively rated as replicated | 39% 3 |
03The trail each edition is designed to leave
The trail each edition is designed to leave
Nexus Universe, the annual programme that GRF stewards through its annual programme cycle, is designed so that every gate produces a record, released on its own terms 1. The annual mandate and its G0 record are released when an edition is authorised. The G1 record lists the admitted missions with reasons, released as participants agree. The Core Build Report, with measured readiness and known defects, is summarised after G3 while restricted detail stays restricted. Run, decision and observation records and the after-action record follow review of Action Week. The stand-down receipt, the evidence manifest and the open exceptions are released after G5, reviewed findings with their limitations and corrections after the G6 authorisation, and the renewal review and improvement items after G7 1.
GCRI’s Universe technical office produces the technical part of that trail: mission scopes, qualification records for data, methods and contributed resources, build evidence and known defects for the temporary Core, run, decision and observation records sealed for review, and a technical closeout with an improvement backlog 7. Its outputs are records that the programme’s governance, evaluators and reviewers can inspect.
Some records are designed never to appear. Invented editions, dates or outcomes, attendance figures or impact claims without a source and date, restricted data, personal information, security-sensitive detail and rankings of countries or institutions are all excluded 1. No edition is on record yet, so the trail is described here as designed, not as a log 1.
Fig. 01The trail an edition is designed to leave
Figure 1 in words
Seven cards along a line of gates. Authorisation, G0: annual mandate and gate record, released when the edition is authorised. Admission, G1: record of admitted missions with reasons, released as participants agree. Build, G3: Core Build Report with measured readiness and known defects, summary after G3 and restricted detail kept restricted. Action Week, G4: run, decision and observation records and the after-action record, released after review. Stand-down, G5, highlighted: stand-down receipt, evidence manifest and open exceptions, released after G5. Publication, G6: reviewed findings, limitations and corrections, after authorisation. Renewal, G7: renewal review and improvement items.
04What the evidence record model carries
What the evidence record model carries
The record model has three layers 2. The first is the identifier: a UNI under the NS-1 grammar, version 0.2, built as NXS-SCOPE-CAT with optional domain, sector, region and environment segments, a six-digit serial and an optional version after an at sign. The serial is allocated by the catalogue or the UNI fabric and is never reused. The second is the catalogue schema: an artefact record of 32 fields, 12 of them required, among them title, scope, category, status, creators, publisher, publication date, rights, legal state, claim level and locations. The third is the snapshot record, one flat record for every type so that one table, one search and one export serve all twelve types. The model’s own reference list names the W3C Data Catalog Vocabulary (DCAT) version 3 2, an RDF vocabulary designed to facilitate interoperability between data catalogs published on the Web 9.
The identifier is a UNI under NS-1, the UNI and the artifact catalog of the Nexus Standards, which is at the proposed stage 10. The identifiers and records page names a template for each object of the year, from an annual cycle to a country profile edition, a course or a credential issuance, but the programme never mints identifiers itself: a UNI is allocated through a catalog, never typed by hand, and it identifies rather than certifies 11. A suffix cites one state of a versioned record; citing without it cites the record as a whole 11.
Origin is where most of the trust sits. A steward keeps a register, and the generator reads the register and writes a record with its source named; it adds no value of its own and never rewrites a status 12. A record carries evidence as pairs of label and link, to the issuing body, the licence and the site, and relations as pairs of a relation word and the registry id of another record 2,12. In the JSON-LD, programme records are typed as activities and the relations between records are Dublin Core relations; a fuller W3C PROV ontology graph, with agents and generation times, is deliberately not carried by the snapshot 12,13.
Fig. 03Three layers of the record model
Figure 3 in words
Three horizontal bands. One, identifier: the UNI under the NS-1 grammar, version 0.2, with a six-digit serial that is never reused. Two, catalogue schema, highlighted: an artefact record of 32 fields, 12 of them required, including rights, legal state and claim level. Three, snapshot record: one flat record for all twelve record types, with evidence as pairs of label and link and relations as pairs of relation word and registry id.
05Who owns which records
Who owns which records
Each of the six pillars of the programme owns its records and hands them on only through recorded handoffs, F01 to F14 between pillars and R1 to R4 around the ring; nothing crosses unrecorded 11. Nexus Universe owns the cycle mandate, mission admissions, gate decisions G0 to G7, after-action records and the renewal decision. Reports owns editions with their evidence cutoff, country and regional profiles, technology stream briefs and their correction history. Risk Academy owns pathways, cohorts, assessment evidence, completion records and credential issuance records 11.
The technical records sit with the systems that are their single authority. NXS-GRX (canonical data, provenance and risk) keeps source releases, ontology releases, fusion recipes, quality envelopes and correction lineage, and propagates a source correction to dependent cuts and products without rewriting old results 14. Ownership is what makes a correction possible: a reader who finds an error knows whose record it is.
| Pillar | Records it owns |
|---|---|
| Labs | Experiment register; prototype record; working papers 11 |
| Foundry | Projects and builds; observations and canonical data; simulation and benchmark runs; the National Portfolio record; evidence seals 11 |
| Nexus Universe | Cycle mandate; mission admission decisions; gate decisions G0 to G7; after-action records; renewal decision 11 |
| Nexus Standards | UNI identifiers; standards, clauses and profiles; change proposals; national adoption records; conformance evidence 11 |
| Reports | Editions and their evidence cutoff; country and regional profiles; technology stream briefs; correction history 11 |
| Risk Academy | Learning pathways and courses; cohorts and enrolments; assessment evidence; completion records; credential issuance records 11 |
06Sealing the evidence at stand-down
Sealing the evidence at stand-down
The moment that turns activity into archive is the end of Action Week. The proposed one-day stand-down stops new work, checkpoints authorized jobs, revokes temporary access, releases temporary capacity and seals transferable evidence with its provenance; its outputs are a stand-down receipt and an evidence manifest 8. Closeout then records the evidence seal, an exception register with accountable owners and completion records, and gate G5, evidence sealed and stand-down recorded, closes it 8.
The after-action review that follows is designed to keep what an event would forget: what worked, what failed and what was not tested, with dissent preserved 8. Failures, adverse findings and dissent are published, not dropped, and each result states its scenario assumptions and limits; simulated loss is not observed impact 1. The programme year still marks the one-day stand-down as proposed 8.
07Corrections create versions, never silent edits
Corrections create versions, never silent edits
Anyone can report that something is wrong, a factual error, a flawed method, a misleading claim or a conduct concern, and no route needs membership, an account or payment 15. The report receives a reference and the name of the next step; the responsible editor or source owner reviews the evidence, and a complaint about a decision is reviewed by someone not responsible for it 15. An accepted correction creates a new recorded version with its history; a rejected request receives a reasoned disposition 15.
Withdrawal follows the same rule. The model states that an identifier is never reused, that a withdrawn record keeps its record and that a replaced one names its successor 2. Rows that an owner has withdrawn from public pages are not listed in the Registry snapshot 16. GRF applies the same rule to Universe results: a correction creates a recorded new version and the earlier version is kept, and anyone can challenge a published claim through GRF corrections and concerns 1.
Fig. 04A correction is a new version, never a silent edit
Figure 4 in words
Five cards joined by arrows. Report: anyone names the page, passage and evidence, with no membership, account or payment. Acknowledge: a reference and the name of the next step, with no promised response time. Review: the responsible editor or source owner, with complaints about a decision going to someone not responsible for it. Decide, highlighted: an accepted correction creates a new recorded version and a rejection receives reasons. Propagate: dependent records are found and updated and the earlier version is kept. A note adds that NXS-GRX propagates source corrections without rewriting old results.
08A reference model for archives
A reference model for archives
The Consultative Committee for Space Data Systems published the third edition of its Reference Model for an Open Archival Information System, CCSDS 650.0-M-3, in December 2024 17. It describes an archive as hardware, software, information and policy-based processes operated by an organization that has accepted responsibility to preserve information for a designated community, and divides the work into six functional entities: ingest, archival storage, data management, administration, preservation planning and access 17. The programme cites it as a reference, not as a claim of conformance.
09Instruments behind the archive
Instruments behind the archive
The archive cites established instruments as references, not as claims of conformance, and the programme’s own standards are proposed for each country to adopt or not through its National Standards Council.
| Year | Instrument | What it contributes |
|---|---|---|
| 2013 | W3C PROV-O, the PROV Ontology | A standard vocabulary for lineage: entities, activities and agents 13 |
| 2017 | WHO Simulation Exercise Manual | Planning, conducting and evaluating exercises 6 |
| 2024 | CCSDS 650.0-M-3, OAIS reference model, third edition | Six functional entities of a preserving archive 17 |
| 2024 | W3C DCAT, Data Catalog Vocabulary version 3 | An RDF vocabulary for interoperability between data catalogues published on the Web 9 |
| Proposed | Nexus Standards NS-1, the UNI and the artifact catalog | One resolvable identifier for every object of the year 10 |
10What is changing
What is changing
- Preservation watch. The 2024 OAIS edition added a preservation watch function to preservation planning, a reminder that formats age faster than findings 17.
- Corrections as data. A correction lineage that propagates to dependent products, without rewriting old results, turns the history of errors into evidence in its own right 14.
11Three faces of institutional memory
Three faces of institutional memory
GCRI leads on science, methods and evidence: it publishes the record model, runs the technical office that captures evidence, and leads scientific and editorial review of results 2,7,1. GRF records the gate decisions of Nexus Universe with their reasons and authorises publication at G6, as the decision rights of the programme set out 1. GRA reads the sealed evidence for the questions competent financial institutions ask, through its Consortium finance interface, and keeps readiness work separate from any financing decision 18.
What this page does not claim: no Nexus Universe edition is on record and the programme is at service level R0. A record shows what was recorded and by whom; it is not certification, approval, a peer-review verdict beyond its review record, or a government endorsement. GCRI does not regulate or certify, GRF does not regulate, finance or procure, and GRA does not lend, underwrite, rate or invest. Naming a standard or agency is not a claim of conformance, partnership or endorsement.
Questions
Questions and answers
Where can I read the records of past Nexus Universe editions?
There are none yet. No edition is on record, and records are added only as each gate of an authorised edition produces them.
Is a participation record a credential?
No. A participation record is a consented record of a contribution or role within programme boundaries. It is not a licence, a qualification or an employment record; credentials are issued separately, by GCRI Canada as issuer of record, only where an assessment supports them.
How do I correct a record or a published finding?
Write through the corrections and concerns route, naming the page or publication, the passage and your evidence. No membership, account or payment is needed. The responsible editor or source owner reviews it, and an accepted correction becomes a new recorded version while the earlier one is kept.
Can a record be deleted?
The model states that a withdrawn record keeps its record, a replaced one names its successor and an identifier is never reused. Rows that an owner has withdrawn from public pages are not listed in the Registry snapshot.
Why publish the record model openly?
So that owners, auditors and reviewers can see how a record is structured and can question the model itself.
Terms
Glossary
- Evidence record
- A dated, attributed and versioned record of a dataset, model result or finding, with its evidence label and limits.
- Evidence label
- The source type of a claim, from Observed to Unknown; an estimate or a scenario is never an observation.
- Evidence manifest
- The frozen list of evidence produced at stand-down, sealed with its provenance at gate G5.
- UNI
- The identifier of the Nexus Standards under NS-1: allocated through a catalog, resolvable, never reused.
- OAIS
- The Reference Model for an Open Archival Information System, CCSDS 650.0-M-3.
- After-action review
- The review after Action Week of what worked, what failed and what was not tested, with dissent preserved.
Reuse and cite
Text CC BY 4.0. Cite the page with its date; data tables are linked under each figure.
Sources
References
18 sources, numbered in the order they are first cited
- The Global Risks Forum (2026-10). Nexus Universe: evidence and outcomes. globalriskforum.com. Accessed 2026-10-21.
- The Global Centre for Risk and Innovation (2026-10). Data and evidence record model. therisk.global. Accessed 2026-10-21.
- Science (American Association for the Advancement of Science) (2015-08-28). Open Science Collaboration, Estimating the reproducibility of psychological science, Science 349, aac4716 (Europe PMC record). www.ebi.ac.uk. Accessed 2026-10-21.
- The Global Centre for Risk and Innovation (2026-10). Programme status. therisk.global. Accessed 2026-10-21.
- The Global Centre for Risk and Innovation (2026-10). Public records and status. therisk.global. Accessed 2026-10-21.
- World Health Organization (2017-02-01). WHO Simulation Exercise Manual (WHO/WHE/CPI/2017.10). www.who.int. Accessed 2026-10-21.
- The Global Centre for Risk and Innovation (2026-10). Nexus Universe technical office. therisk.global. Accessed 2026-10-21.
- Nexus documentation (docs.therisk.global) (2026-10). The programme year. docs.therisk.global. Accessed 2026-10-21.
- World Wide Web Consortium (W3C) (2024-08-22). Data Catalog Vocabulary (DCAT) - Version 3, W3C Recommendation. www.w3.org. Accessed 2026-11-17.
- Nexus Standards (2026-10). NS-1: The UNI and the artifact catalog. nexustandards.com. Accessed 2026-10-21.
- Nexus documentation (docs.therisk.global) (2026-10). Identifiers and records. docs.therisk.global. Accessed 2026-10-21.
- The Global Centre for Risk and Innovation (2026-10). Provenance and attribution. therisk.global. Accessed 2026-10-21.
- World Wide Web Consortium (W3C) (2013-04-30). PROV-O: The PROV Ontology, W3C Recommendation. www.w3.org. Accessed 2026-10-21.
- Nexus documentation (docs.therisk.global) (2026-10). NXS-GRX: canonical data, provenance, risk and federation. docs.therisk.global. Accessed 2026-10-21.
- The Global Centre for Risk and Innovation (2026-10). Corrections and concerns. therisk.global. Accessed 2026-10-21.
- The Global Centre for Risk and Innovation (2026-10). Rights and visibility. therisk.global. Accessed 2026-10-21.
- Consultative Committee for Space Data Systems (CCSDS) (2024-12). CCSDS 650.0-M-3, Reference Model for an Open Archival Information System (OAIS), Magenta Book. public.ccsds.org. Accessed 2026-10-21.
- The Global Risks Alliance (2026-10). Consortium finance interface. globalriskalliance.com. Accessed 2026-10-21.
Record
Editorial record
Facts and programme states are given as of 21 October 2026. This page is reviewed at least every 180 days and whenever a programme state, a service level or a cited figure changes. It replaces an earlier version of the same post, which described records across platforms under names that are now retired and referred to maturity levels and sponsor records that are not part of the programme’s record model; the record model, fields and gates given here are those on record.
Published by the GCRI editorial desk under the scientific and editorial integrity policy. To report an error or request a correction, use the corrections and concerns route; every accepted correction is recorded as a new version, never a silent edit.
Cite this article
GCRI editorial desk (2026, June 8). Evidence records and archive: annual work as memory. The Global Centre for Risk and Innovation. https://therisk.global/evidence-records-and-archive-turning-annual-technical-work-into-institutional-memory/
@online{gcri2026evidencerecordsandarc,
author = {{GCRI editorial desk}},
title = {{Evidence records and archive: annual work as memory}},
publisher = {The Global Centre for Risk and Innovation},
year = {2026},
month = {6},
url = {https://therisk.global/evidence-records-and-archive-turning-annual-technical-work-into-institutional-memory/},
language = {en}
} TY - ELEC AU - GCRI editorial desk TI - Evidence records and archive: annual work as memory PB - The Global Centre for Risk and Innovation PY - 2026 DA - 2026/06/08 UR - https://therisk.global/evidence-records-and-archive-turning-annual-technical-work-into-institutional-memory/ LA - en ER -
Republish
Republish or translate this article free of charge, in print or online, under CC BY 4.0: keep the byline and The Global Centre for Risk and Innovation, link to the original and note any change. Figures, maps and twins made by the institutions carry the same licence; third-party data keeps its own credit line.
Attribution to paste
<p>Evidence records and archive: how annual technical work becomes institutional memory — GCRI editorial desk, The Global Centre for Risk and Innovation. First published 8 June 2026 at <a href="https://therisk.global/evidence-records-and-archive-turning-annual-technical-work-into-institutional-memory/">https://therisk.global/evidence-records-and-archive-turning-annual-technical-work-into-institutional-memory/</a>. Republished under CC BY 4.0 (https://creativecommons.org/licenses/by/4.0/).</p>