G09 · PAGE · aapGCRI dossier · service level R0
GCRINexus FoundryEstablished
Nexus Foundry · AAP

AAP

AAP supports anticipatory action: evaluating triggers, preparing pre-agreed actions and readiness, and handing activation to the institutions that hold the funds and mandates. It releases nothing automatically.

Publisher
The Global Centre for Risk and Innovation
Field
Data and compute, Methods and modelling
Canvas · the Nexus cycleDesign, not a record
The Nexus cycle on Nexus FoundryA question from a programme becomes evidence, a governed build, an organized community, a controlled test, a reviewed publication and a decision taken by the competent authority. Design of the cycle, not a record of a run.

Fig.The Nexus cycle, from question to renewal. Design, not a record of a run.

01In brief

The short answer.

Anticipatory Action Platform is the Nexus Foundry system for evidence-triggered playbooks, trigger evaluation, readiness and action records. It serves 4 platforms, among them Food Nexus as well as Disaster Resilience and Recovery, and its stated limit is that it releases no funds and dispatches no one automatically. Access is through an authorized project with an accountable owner, data terms and a review plan.

02Geography

Digital demand and connectivity in the contiguous United States.

Urban demand centres and the hubs that anchor digital and data infrastructure, shown for the contiguous United States 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
04The problem it addresses

Acting before a disaster needs agreement before the forecast.

Anticipatory action links a forecast threshold to pre-arranged actions and finance. Its quality depends on trigger skill (how often it fires correctly), the cost of false alarms and misses, and the readiness of the actions it triggers.

  • Trigger skill evaluated on historical forecasts.
  • Action plans with owners and lead times.
  • Handoff to the funding institution's activation process.
05Reference practice

The standards a design like this is read against.

ReferenceRelevance
Anticipation Hub resourcesPractice in forecast-based action
Sendai Framework priority fourPreparedness for effective response
IEC 31010Event-tree and decision analysis for triggers
06Neighbouring systems

What it exchanges with the other systems.

  • Receives forecasts and verification from EWS.
  • Records handoffs in Rails.
07Access

Authorized projects only.

Access requires an authorized project with an accountable owner, data terms and a review plan. Enquiries go to contact@therisk.global.

08Key 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
Anticipatory actionPre-agreed action and finance released on a forecast or early warning trigger, before a hazard's peak impact.
TriggerA pre-agreed forecast or observed threshold that releases planned action or finance when it is crossed.
Early action protocolA pre-approved plan setting triggers, actions and budgets for acting ahead of a hazard.
09Sources

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.

10Questions

Questions and answers.

Is the system available now?
Allocations open when their terms and review capacity exist; the current service level is R0, information and enquiries.
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?