Build in Nexus Foundry
The Nexus Foundry systems that serve Nexus Agency, what an authorized project can do with them, and how access is requested.
- Publisher
- The Global Centre for Risk and Innovation
- Field
- Governance and institutions, Development finance
- Status
- Established
- Service level
- R0: information and enquiries
Pipeline
Build in Nexus Foundry · Workspace WS-92
Stages
- Ingest3 sources
- Validateschema · licence
- Transformversioned
- ModelSystems…
- Testheld-out
- Releasewith limits
Artefacts
| Request register | v5.6 | Open | OFFICIAL |
| Expert roster | v3.1 | Open | OFFICIAL |
| Declarations of interest | v2.8 | Open | OFFICIAL |
| Assignment reports | v4.3 | Open | REPORTED |
Compute quota
share used vs alert level
Nexus Agency · PipelinePipeline, in outline: domain structure with placeholder names and illustrative values, not a record.
The short answer.
Building in Nexus Foundry is how authorized Nexus Agency projects use the shared technical systems that serve governance and institutions: Hub, Rails and Nexus. Access requires an accountable project owner, data terms and a review plan, and allocations open only when their terms and review capacity exist. Foundry work produces designs and analyses with their limits, not operational services.
Scoping to review.
Fig.A programme from scoping to the owner's decision. Design, not a record.
Jurisdictions in the Zambezi Basin.
The jurisdictions that hold authority over this question: countries, their first-level divisions and capitals, shown for the Zambezi Basin as an example geography for this subject.
Foundry systems for this field.
- 01
- 02
Rails
- 03
Nexus
The Foundry systems technical assistance work draws on.
How a project gets access.
- 01
Enquiry
Describe the project and its owner to contact@therisk.global.
- 02
Authorization
Access requires an authorized project with an accountable owner, data terms and a review plan.
- 03
Allocation
Compute and data allocations open when their terms and review capacity exist.
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.
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.
| Term | Definition |
|---|---|
| Digital twin | A computational representation of a physical system that is updated with data from it and used to explore its behaviour. |
| 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. |
| Least privilege | Granting each user or process only the access needed for its current task. |
| Workflow orchestration | Automated management of the order, execution and recovery of computational tasks. |
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.
Where this page leads across the Consortium.
Questions and answers.
Is Foundry access free?
Around Nexus Agency.
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.