G09 · EVIDENCE · publicationsGCRI dossier · service level R0
GCRINexus FoundryEstablished
Research and publications

Public outputs

Citable outputs of Nexus Foundry: capability catalogue; installation guidance; public technical examples.

Publisher
The Global Centre for Risk and Innovation
Field
Data and compute, Methods and modelling
Canvas · draft to published versionDesign, not a record
Public outputs: systematic evidence synthesisA question is framed with its owner and a protocol registered; records are searched, screened and checked for eligibility by two reviewers; data are extracted, synthesised and graded for certainty before a brief is written. Design of the process, not a record of a run.

Fig.How a finding is reviewed before it is published. Design, not a record.

01In brief

The short answer.

Nexus Foundry publications are the platform's reviewed, citable outputs, such as capability catalogue, installation guidance and public technical examples. Each carries its authors, date, method, evidence labels and editorial status, and a correction creates a new version with its history. Contributions to series such as Foundry Build and Readiness also appear in Nexus Reports.

02Geography

Digital demand and connectivity in Canada.

Urban demand centres and the hubs that anchor digital and data infrastructure, shown for Canada as an example geography for this subject.

Urban demand centres and the hubs that anchor digital and data infrastructure.Indicator derived from Natural Earth at map scale; a screening view, not an assessment.
GCRI · Nexus Foundry · fieldDESIGN FIGURE
03What is published

Every output shows its status.

  • Each publication carries its authors, date, method, evidence labels and editorial status.
  • Corrections create a new version with its history.
  • Series contributions also appear in Nexus Reports; see Publish in Nexus Reports.
04Output types

What Foundry publications look like.

Foundry publications are written for technical reviewers and project owners: system descriptions, build notes and security summaries at a public-safe level. A reader looks for the architectural responsibility of each system and for evidence of what has been tested. They connect to the project workstations and agents and automation topics and to computing methods.

  • Build and readiness notes.
  • System descriptions for each of the twenty systems.
  • Security and assurance summaries at public-safe level.
05Series

Report series this field contributes to.

06Key terms

Terms used on this page.

Each term as this page uses it. Where a standard-setting body defines the term, the wording follows that body.

TermDefinition
Version of recordThe fixed version of a work that a publisher formally declares published; later changes appear as dated corrections or new versions, never as silent edits, in the sense NISO's journal article versions recommendation uses.
Peer reviewEvaluation of a work by independent experts in the field before publication.
CorrectionA published notice that amends an error in a work whose main findings stand.
Evidence labelA tag on an assertion naming the kind of evidence behind it, such as observed, officially reported or modelled.
07Sources

Where this page's references lead.

The bodies and documents this page is read against. Status and editions change; each link goes to the issuing body.

08Questions

Questions and answers.

How do I cite a publication?
Each publication shows its citation and permanent address.
Nexus Foundry

Bring your expertise to this field.

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.

Have questions?