Hosts and supporters
Hosts and supporters make Nexus Universe possible: a host provides a venue or operational support for an edition, and a supporter funds a defined public-good capability. The Global Risks Forum (GRF) sets the conditions under which both take part, because the programme is only credible if no one can buy its agenda, its admissions or its findings. Hosting is not ownership, and sponsorship is not authority. No host is confirmed for any edition, and no edition is on record yet; a proposal is never presented as a confirmed host, sponsor or event.
- 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.
Hosts and supporters of Nexus Universe make the programme possible: a host provides a venue or operational support for an edition, and a supporter funds a defined public-good capability. GRF sets the conditions so that no one can buy the agenda, admissions or findings, and no host is confirmed yet.
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.
What hosts and supporters do.
Venue and operational support
A host provides a site and support for an edition. A hosting agreement is designed to give it a readiness decision, a responsibility schedule and a closeout record.
Defined public-good capability
A supporter funds a defined capability under a contribution agreement, which is designed to include a use-of-resources report.
Forms of support and the risk each carries.
| Form | Risk to independence | Control |
|---|---|---|
| Venue or in-kind support | Host expects visibility over content | Host has no role in scenario or record |
| Funding for a capability | Funder expects the capability to favour its interests | Capability defined before funding, public description |
| Secondment of staff | Seconded staff carry employer priorities | Declared, and excluded from evaluating their employer |
| Data contribution | Data shapes the scenario | Provenance and licence recorded; scenario reviewed by others |
What is published about support.
Supporters and the capability they fund are listed in the edition record, with the form of support and any conditions. Anonymous support is not accepted. The same rules apply as under sponsorship and independence.
What a host must show before an edition is confirmed.
- 01
Authority
The host has authority to commit the site and the support it offers, evidenced in writing.
- 02
Readiness
Site safety, access, accessibility, connectivity and capacity for the admitted missions, assessed before the build month.
- 03
Responsibility schedule
Who does what during the build, the action week and the stand-down, with accountable operators named.
- 04
Closeout
An approved closeout plan, retention decisions and a closeout record.
- 05
Disclosure
Consent to be named, and a declaration of interests that could bear on the programme.
No event is presented as confirmed before the host's authority and readiness are evidenced.
Safeguards designed into every agreement.
- No support buys an appointment, a finding, consent or a procurement advantage.
- Sponsors cannot approve publications, change evidence or choose participants.
- Funding grants no ownership of the programme, its records or its results.
- Neither hosting nor sponsorship secures a computing allocation or mission admission.
- A host or sponsor is named only with its written permission and a current record.
- Conflicts are declared, and anyone may raise a concern about capture through institutional independence.
How to propose hosting or support.
Hosting and support proposals can go to partnerships@globalriskforum.com. The acknowledgement gives a reference and names the next step. GRF's general policies are on hosts and programme supporters and sponsorship policies, and the programme's own website is universe.nexus. The Global Risks Alliance (GRA) sets out comparable rules on conflicts, sponsors and neutrality. The overview of the programme is on the Nexus Universe gateway.
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 |
|---|---|
| Host | An institution that provides a venue, logistics or support for a programme session; hosting confers no authority over the programme's agenda, findings or records. |
| Sponsorship | Support given for a programme under published terms; sponsors receive acknowledgement only and no influence over content, findings, speakers or participation decisions. |
| Sponsor neutrality | The principle that a campaign's funder does not control its findings, claims or editorial decisions. |
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.
Questions and answers.
Who is hosting the next Nexus Universe?
Can a host shape the agenda?
What does a supporter receive?
Is there a fee schedule for hosting or sponsorship?
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.