G09 · PAGE · projectsGCRI dossier · service level R0
GCRINexus FoundryEstablished
Nexus Foundry · Projects

Projects and workspaces

In Nexus Foundry, all work happens inside a project: a bounded workspace with a scope, an accountable owner, data terms and a review plan. This page, published by The Global Centre for Risk and Innovation (GCRI), explains how projects and workspaces are scoped and authorized. It describes the model only; it never displays project data, participants or privileged information. The current service level is R0: information and enquiries.

01In brief

The short answer.

A Nexus Foundry project is the bounded workspace in which all Foundry work happens, with a scope, an accountable owner, data terms and a review plan. The page explains how projects and workspaces are scoped and authorized; it never shows project data, participants or privileged information.

02Geography

Digital demand and connectivity in Poland.

Urban demand centres and the hubs that anchor digital and data infrastructure, shown for Poland 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
03Scope

A project is defined before it is opened.

  • the question or mission and the institution that owns it;
  • the accountable owner and the people and agents who may act;
  • the data the project may use, with the owner's terms for each source;
  • the systems it may reach and the deployment profile it runs on;
  • the openness profile, from open through consortium-shared and confidential to restricted;
  • the review plan, the outputs expected and the closeout point.
04Authorization

Authenticated is not authorized.

Signing in proves who you are. It does not decide what you may do. In the design of the Nexus Sovereignty Framework, each request is evaluated against the project's policy and the caller's identity, mandate and purpose, and requests without an explicit decision fail closed.

Identity

Who is asking

A verified identity, with any delegation recorded.

Mandate

On whose authority

The role and mandate under which the person or agent acts in this project.

Purpose

For what

The purpose and data class, checked against the owner's terms.

05Workspaces

Shared rooms, separate permissions.

Projects are designed to share a common set of rooms, such as Station, Mission, Maps, Data, Builder, Reports and Knowledge, so that work looks the same across systems. What a person sees in each room depends on the project's permissions, not on the room.

An application for a project is not acceptance, and a payment is never access to restricted data.

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
Least privilegeGranting each user or process only the access needed for its current task.
Data sharing agreementA document setting out the purpose, legal basis, data, safeguards and responsibilities for sharing data between parties.
Trusted research environmentA secure computing environment where approved researchers analyse sensitive data without removing it.
07Start

How a project is proposed.

Projects open when their terms and review capacity exist. Institutions can describe a candidate project to contact@therisk.global. Platforms across the network describe the builds they need on their own Foundry pages, for example Build in Nexus Foundry for Nexus Labs.

08Questions

Questions and answers.

Can I see other institutions' projects?
No. Project information is shown only to people the project authorizes. Published outputs appear through Nexus Registry and Nexus Reports.
Who can be a project owner?
An institution with a mandate for the work, represented by an accountable person named in the project record.
Does the openness profile affect results?
No. The profile governs who can see the work, never whether its results are valid.
What happens when a project closes?
Access is closed, outputs and records are retained as the terms require, and data is returned or deleted as its owner decided.
Can a project span several countries?
Yes, where each data owner agrees. Federation creates no right to move data: where data cannot move, the analysis can run where the data is held.
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?