Build
Build: nexus Foundry. GRF frames the governance questions that Foundry builds address.
- Institution
- The Global Risks Forum (GRF)
- Service level
- R0: information and enquiries
- 01QuestionNational, regional or institutional priority
- 02EvidenceSTEM foundation of the platform
- 03BuildNexus Foundry
- 04OrganizeNexus Ecosystem
- 05TestNexus Universe (independent site)
- 06PublishNexus Reports
- 07DecideCompetent authorities and institutions, through Nexus Rails
- 08RenewCorrections and the next annual agenda
The short answer.
Build is step three of the eight-step Nexus cycle: the step at which authorized projects build models, analysis and tools in Nexus Foundry. It is owned by Nexus Foundry. At this step GRF frames the governance questions that Foundry builds address, and the decision at the end of the cycle stays with the competent authority.
Jurisdictions in World.
The jurisdictions that hold authority over this question: countries, their first-level divisions and capitals, shown for World as an example geography for this subject.
Who owns the build step.
Nexus Foundry
Institutional arrangements as designed objects.
At the build step, an option from a dialogue becomes something concrete enough to test: a draft protocol between two agencies, a revised escalation table, a data-sharing agreement, a communication template. GCRI's technical teams build any software or model components. GRF's part is the institutional text, drafted with the participants who will have to operate it.
| Artefact | Drafted by | Checked by |
|---|---|---|
| Interagency protocol | The agencies concerned, with GRF facilitation | Each agency's legal adviser |
| Escalation table | Operators and the authority that receives escalation | Both sides, in a walk-through |
| Data-sharing agreement | Data holders and users | Data protection authority where personal data is involved |
| Public message template | Communications leads | A sample of the audience in a readability test |
Every draft carries its version and its owners.
Drafts are versioned so that the exercise tests a known text and the lesson can be traced back to it. The Nexus Foundry at GCRI holds the build environment for technical components.
Then: organize.
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. |
| Model validation | Independent testing that a model performs as intended and is fit for a stated use. |
| 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. |
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.
Around GRF.
Start with an enquiry.
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.