Annual programme cycle
Nexus Consortiums work on an annual rhythm: one year of work, one month to build, one week to test and one day to stand down. Monthly working-group delivery and quarterly evidence in each country build towards an annual integration in Nexus Universe and the annual flagship report. The Global Centre for Risk and Innovation (GCRI) supports the cycle with evidence, methods and its technical office; The Global Risks Forum (GRF) governs the annual programme. This page explains each stage, its gates and what continues afterwards. Return to GCRI programmes.
- Institution
- The Global Centre for Risk and Innovation (GCRI)
- 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.
The annual programme cycle is the rhythm of Nexus Consortiums: one year of work, one month to build, one week to test and one day to stand down. Monthly working-group delivery and quarterly country evidence build toward integration in Nexus Universe and the annual flagship report, through eight gates from authorization to renewal.
Scoping to review.
Fig.A programme from scoping to the owner's decision. Design, not a record.
Systemic exposure in East Asia.
Where people and networks concentrate, the exposure through which shocks travel between systems, shown for East Asia as an example geography for this subject.
Five stages, each with an entry and an exit.
| Stage | Work | Exit |
|---|---|---|
| One year: prepare | National demand, research, monthly working-group delivery, quarterly evidence, technology and resource qualification. | An approved mission portfolio, qualified inputs and an achievable build plan. |
| One month: build | Assemble the Core, bind authorized resources, integrate software and data, test security and interoperability, rehearse. | A Core Build Report, measured readiness, known defects and go or no-go decisions. |
| One week: act and test | Controlled exercises, scenario work, benchmarks, independent observation and leadership deliberation. | Run, decision and observation records, limitations and improvement items. |
| One day: stand down (proposed) | Stop new work, checkpoint jobs, revoke temporary access and seal transferable evidence. | A stand-down receipt and a preserved evidence manifest. |
| Following period: review and renew | Validate archives, complete review, publish approved results and close corrective actions. | Reviewed publications, closed corrections and the next mandate. |
The one-day stand-down is a proposed stage. It becomes a commitment only when the annual programme records it, and scientific review, financial reconciliation and corrections continue afterwards.
Eight gates, from authorization to renewal.
- G0 annual programme authorized; G1 missions admitted; G2 data and resources qualified; G3 build accepted for exercise
- G4 controlled live operation authorized; G5 evidence sealed and stand-down recorded; G6 publication authorized; G7 renewal reviewed
Monthly work, quarterly evidence.
Working groups
National Working Groups deliver bounded, supervised work each month. See Working groups.
Country editions
Q1 state and agenda, Q2 evidence and build, Q3 stress test and readiness, Q4 annual synthesis. See Reports gateway.
Integration
Selected missions are tested in Nexus Universe. See Nexus Universe technical office.
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 |
|---|---|
| Nexus cycle | The eight-step loop by which work moves in every Nexus field: question, evidence, build, organize, test, publish, decide and renew, each step with a named owner. |
| Stage gate | A review point at which a project must show set evidence before moving to the next phase. |
| After-action review | A structured discussion after an activity of what was planned, what happened, why, and what to change. |
| Lessons identified | Findings from a review that have been recorded but not yet acted on, as distinct from lessons implemented. |
No edition is scheduled on this page.
No annual edition, date or host is shown here until an edition record exists. The current service level is R0: information and enquiries. The governance of the cycle is set out by GRF on Annual operating cycle, and the independent programme website is Nexus Universe.
Questions and answers.
Is everything deleted after the one-day stand-down?
When is the next edition?
Does every country take part every year?
Around GCRI.
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.