Press Ctrl/Cmd + P to print
or save as PDF

Article 10. Programs, Tracks, Regionalization & Collaboration

(Swiss Verein; Zug register; principal base Geneva. This Article operationalizes GRF’s purpose through three Programs—DRR, DRF, DRI—delivered via five cross-cutting Tracks, executed in 90-day Regional Sprints, and coordinated with Nexus Entities under the Earth Cooperation Treaty (ECT). It specifies how, when, and where delivery occurs; the assurance, tooling, and transparency obligations; and the engagement rules for cross-entity collaboration. Cross-refs: Arts. 2 (Seat), 3 (Independence), 4 (Membership), 5 (Defs/Precedence), 6 (Governing Bodies), 7 (Representation), 8 (Elections), 9 (Authorities), 11 (ECT), 12 (CB Clearance), 13 (Finance), 14–15 (Data/Privacy/Security), 16 (Ethics & Safeguarding), 18 (Disputes); Annexes P (Program Charter), Q (Sprint Charter), R (Convening Protocol), S (KPI Catalogue), T (Data/Model Governance), U (ECT Operating Protocol), V (Readiness Levels). EN controls; FR/DE companions provided where operationally required.)


10.0 Purpose, Design Principles & Delivery Discipline

10.0.1 Purpose

Establish a single, enforceable operating system that converts risk evidence into policies, finance, and action—measured against Sendai-aligned outcomes and implemented at country, city, and sector levels.

10.0.2 Design Principles

(a) Independence by design (Art. 3): no donor-conditioned metrics or pay; co-branding controls.
(b) Time-boxed execution: 90-day sprints with auditable outputs.
(c) Assurance first: QA/QC, model governance, provenance logs, and public scorecards.
(d) All-of-society: state-level members, institutions, and individuals participate under common safeguards.
(e) Inter-nexus interoperability: common data/contract standards and shared registers via the ECT.


10.1 Programs — DRR, DRF, DRI (Sendai-Aligned KPIs)

10.1.1 Program Scope & Objectives

(a) Disaster Risk Reduction (DRR): Reduce mortality, morbidity, displacement, and infrastructure downtime; expand multi-hazard early warning.
(b) Disaster Risk Finance (DRF): Pre-arrange, rules-based finance that pays out rapidly on transparent triggers and resilient rails.
(c) Disaster Risk Intelligence (DRI): Deliver decision-grade analytics, forecasts, and scenarios with quantified uncertainty and limits.

10.1.2 KPI Framework & Cadence (Annex S)

(a) Core indicators mapped to Sendai A–G with normalization (population, GDP, exposure) and minimum disaggregation (sex/age/disability, sub-national).
(b) Update cadence: quarterly for active portfolios; 72-hour rapid updates during RAP (Art. 9.1.9).
(c) Illustrative set:

  • A Mortality: A1 deaths/100k (all hazards); A2 heat-attributable deaths/100k.
  • B Affected: B1 affected/100k; B2 displacement-days/1k.
  • C Economic: C1 loss %GDP (PPP-adj.); C2 insured/uninsured ratio.
  • D Infrastructure: D1 critical facility downtime (hours/100k); D2 continuity-plan coverage (%).
  • E Strategies: E1 DRR strategies meeting GRF criteria (% national/local); E2 annual stress-tests (#, quality).
  • F Cooperation: F1 pre-arranged finance per capita; F2 technical-assistance days.
  • G Warning/Info: G1 EWS population coverage (%); G2 alert-to-action conversion (%); G3 lead-time gain.
  • U Quality/Uncertainty: U1 dataset QA/QC pass rate; U2 model calibration score; U3 posterior predictive checks.

10.1.3 Methods & Tooling

(a) Tri-Source Data Stack: EO & in-situ; administrative/regulatory; alternative/OSINT.
(b) Nexus Platforms: NXSCore (HPC/GPU), NXSQue (orchestration/audit), NXSGRIx (standardization/benchmarking), NXS-EOP (AI/ML/simulation), NXS-EWS (alerts), NXS-AAP (anticipatory smart triggers), NXS-DSS (dashboards), NXS-NSF (financial rails).
(c) Assurance: Data QA/QC Cards and Model Cards per Annex T; red-team cadence; provenance hashes filed in the Council Register.

10.1.4 Program Governance & Gates

(a) RACI: LC R for policy/strategy; Board A; CB/Chairs C; Members I. Delivery: Chairs R; CB A for compliance & continuity (Art. 6).
(b) Lifecycle: Discover → Define → Deliver → Scale with entry/exit criteria (Annex P).
(c) Materiality: stage transitions that trigger Material Actions require CB Clearance (Arts. 9.2.3, 12).


10.2 Delivery Tracks — Research, Innovation, Policy, Capital, Foresight

10.2.1 Common Rules (All Tracks)

(a) Track Charter per Annex P (scope, KPIs, dependencies); annual refresh.
(b) Leadership: Track Lead (SLB/RSB/EM designee) vetted under Art. 8.4; CB-Cleared if Material.
(c) Cadence: ≥ 1 deliverable per 90-day cycle; monthly progress note to Secretariat.
(d) Quality: peer review or external panel for high-stakes outputs; IP/license posture recorded.
(e) Openness: default open data/code where lawful; exceptions CB-Cleared.

10.2.2 Research Track (Evidence & Standards)

Outputs: benchmark studies; validation datasets; methods compendia; QA/QC Cards; Model Cards. Acceptance: reproducibility, uncertainty disclosure, ethics/safeguarding sign-off.

10.2.3 Innovation Track (Prototypes & Pilots)

Outputs: TRL-scored prototypes; pilots; interoperability specs. Acceptance: user testing in ≥ 2 regions; perf/security tests; DPIA where personal data used.

10.2.4 Policy Track (Rules & Playbooks)

Outputs: draft laws/ordinances; sectoral SOPs; audit/disclosure templates; Independence Impact Assessments (IIA). Acceptance: legal review; consultation record; implementability score.

10.2.5 Capital Track (Finance, Risk Transfer & Execution)

Outputs: term sheets; trigger definitions; payout/verification protocols; portfolio dashboards. Guardrails: no investment advice; no success-fees; KYC/AML & sanctions screens; CB-Cleared independence walls. Acceptance: independent actuarial/structural review; annual payout rehearsal.

10.2.6 Foresight Track (Scenarios & Stress-Tests)

Outputs: scenario books; stress-test matrices; decision thresholds; value-of-information analysis. Acceptance: documented assumptions; sensitivity analysis; red-team challenge.


10.3 Regionalization — 90-Day Sprints (How, When, Where)

10.3.1 Sprint Calendar & Windows

(a) Cadence: Four 90-day sprints per region per year; RAP sprints during crises.
(b) When: Secretariat publishes a rolling 4-quarter calendar each December; mid-year updates gazetted.
(c) Where: Primary in-person nodes hosted by Regional Stewardship Boards (RSBs); hybrid default; Geneva hub support available for cross-regional work.

10.3.2 Sprint Mechanics (How)

(a) Kick-Off (Week 1): file Sprint Charter (Annex Q) with objectives, KPIs, partners, dependencies, budgets, risks, and CB Clearance needs.
(b) Mid-Cycle Review (Week 6): traffic-light dashboard; course-correct or escalate.
(c) Close (≤10 Business Days post-cycle): Sprint Note + Action Log + evidence pack (datasets, code stubs, methods, contracts of record) filed in Council Register.

10.3.3 Minimum Outputs (per Sprint)

One Research, Innovation, Policy, Capital, and Foresight deliverable (may be light-weight but complete); public Sprint Note summarizing results, uncertainties, and next-sprint carry-overs.

10.3.4 Roles & Responsibilities

(a) Regional Chairs (RSBs): own delivery; maintain KPI scorecards; R for Programs.
(b) SLB/Thematic Chairs: co-lead domain tasks; method fidelity.
(c) NWGs/NACs/Host Institutions/Host Corporations/C-Cells: localize standards; training/drills; monitoring; feed NXSGRIx.

10.3.5 Data, Ethics & Security

(a) DPIA/PIA for personal/sensitive data; safeguarding-compliant fieldwork; security classification (Art. 15).
(b) Cross-border transfers and sensitive-country work require CB Clearance; provenance logs maintained.

10.3.6 Performance & Remedies

(a) Two amber cycles → remedial plan; red → Board notification and optional call-in (Art. 9.6).
(b) Persistent non-performance may trigger re-scoping or suspension of a sprint/track with Gazette notice.


10.4 Convenings — Global Assembly; Geneva Dialogue; Regional Summits; Sectoral Capital Tracks

10.4.1 Common Rules (How, When, Where)

(a) Protocol: Annex R governs format, quorum, security, press, and records.
(b) Where:
Global Assembly (GA): hybrid; principal venue Geneva or another CB-cleared hub;
Geneva Dialogue: Geneva, hosted at principal base or partner venue;
Regional Summits: within RSB jurisdictions;
Sectoral Capital Tracks: rotating hubs aligned with sector stakeholders.
(c) When:
GA: Q4 annually;
Geneva Dialogue: annually in July within the Geneva window adopted by the Board;
Regional Summits: semi-annual;
Capital Tracks: quarterly or ad-hoc with RAP activation.
(d) How: accreditation via Secretariat; PII handled per Art. 14; security posture filed with CB; minutes + Decision & Action Log lodged in Council Register; material items gazetted.

10.4.2 Global Assembly (GA)

Function: supreme decision-making body (Art. 6). Outputs: resolutions; board elections; dues schedules; KPI State of Programs.

10.4.3 Geneva Dialogue

Function: high-discipline technical/strategic dialogue to align Programs & Tracks; publish model governance baselines and capital execution protocols; finalize 12-month public workplan.

10.4.4 Regional Summits

Function: ratify regional backlogs; adopt sprint portfolios; validate KPI baselines; approve risk-appropriate procurement pipelines (CB-Cleared where Material).

10.4.5 Sectoral Capital Tracks

Function: link user demand signals with NXS-NSF rails; produce term sheets, triggers, payout rehearsals; ensure beneficiary safeguards; no solicitations, no success fees.

10.4.6 Sponsorships & Funding

Permitted only if unrestricted and CB-Cleared; logos in neutral galleries; no editorial influence, no vendor exclusivity, no pay-to-speak.


10.5 Nexus Entity Engagement & Systemic Collaboration (ECT)

10.5.1 Who May Engage

GCRI, GRA, NSF, NE Labs and acceding Nexus Entities under the ECT. Engagement respects Art. 3 (independence) and Annex U (ECT Operating Protocol).

10.5.2 How Engagement Occurs (Pipeline & Documents)

(a) Initiation (T-60 to T-45 days before a sprint or convening): Exchange of Intent Note (scope, roles, data/contract needs).
(b) Assessment (T-45 to T-30): Independence Impact Assessment (IIA) and, if needed, DPIA/PIA; CB issues Pre-Clearance conditions.
(c) Contracting (T-30 to T-15): Model Inter-Nexus Schedule (Annex U) signed (IP, licensing, data flows, security, publication rights).
(d) Access (T-15 to T-5): Identity provisioning, environment hardening, and dataset staging via NXSQue; signatory and audit trails set.
(e) Delivery (0 to +90): joint sprint execution; shared evidence packs; cross-entity red-team where high-stakes.
(f) Close (+10 Business Days): joint Result Note with provenance hashes; filing in both Council Registers; public summary in both Gazettes.

10.5.3 When & Where

(a) Geneva Dialogue is the default venue to finalize annual cross-nexus workplans.
(b) Regional joint sprints rotate across RSB hubs, prioritizing host readiness and legal adequacy.
(c) Virtual collaboration via Nexus Platforms is default; in-person only where value outweighs travel cost and carbon (per policy).

10.5.4 What Is Shared

(a) Data/Models: only per Annex T and Schedule U; minimal necessary; with purpose limitation and retention controls.
(b) IP: work-product assigned to GRF or jointly licensed under open/reciprocal terms; core marks remain non-assignable; any exclusivity requires Board approval and CB Clearance.
(c) Registers: both CBs lodge parallel entries (Clearances, contracts of record, hashes).

10.5.5 Safeguards & Conflicts

(a) Walls: donor/procurement walls and recusal mechanics apply across entities (Arts. 8.4, 8.5.9).
(b) No dual-office conflicts: governing-board ↔ executive-board rules per Art. 8.5.9; ECT waivers only with robust walls, public interest, and CB-Cleared protocols.
(c) Sanctions/KYC/AML: cross-screens run pre-access (Annex M); sensitive-country work requires explicit CB opinion.


10.6 Readiness Levels, Quality Gates & Acceptance

10.6.1 Readiness Levels (Annex V)

(a) TRL (technology), PRL (policy), CRL (capital), DRL (deployment/ops).
(b) Gate criteria: defined per level; Clearance IDs referenced on acceptance forms.

10.6.2 Acceptance Tests & Evidence

(a) Research: reproducibility pack + uncertainty statement.
(b) Innovation: field test logs in ≥2 regions + security/performance tests.
(c) Policy: legal review + implementability and cost-of-compliance.
(d) Capital: independent actuarial/structural review + payout rehearsal.
(e) Foresight: sensitivity and value-of-information analysis + red-team memo.


10.7 Publication, Transparency & Open Access

10.7.1 Registers & Gazette

(a) Program charters, sprint calendars, convening minutes, KPI updates, and ECT schedules are filed in the Council Register with provenance hashes.
(b) Material decisions and outcomes are summarized in the Council Gazette within 10 Business Days (lawful redactions).

10.7.2 Open Materials & Embargoes

(a) Default open datasets and methods where lawful; embargoes permitted only with CB-Cleared necessity and expiry.


10.8 Funding, Neutrality & Procurement

10.8.1 Permitted Sources

Membership/platform revenues; exceptions to no-grants stance require ≥2/3 LC vote and CB opinion (Art. 9.1.2).

10.8.2 Procurement

Competitive sourcing, transparent scoring, and independence walls; donor-conditioned vendor selection is prohibited; related-party transactions require CB Clearance.


10.9 Compliance, Remedies & Updates

10.9.1 Compliance

All Programs, Tracks, Sprints, Convenings, and ECT engagements must comply with Arts. 3, 12–16, Annexes P–U, and applicable host law.

10.9.2 Remedies

(a) Call-in (Art. 9.6) for integrity breaches or systemic underperformance.
(b) Suspend or re-scope sprints/tracks; void actions executed without required clearance (Art. 7.11).
(c) Gazette notices and corrective action plans are mandatory.

10.9.3 Updates

Annexes P–V may be updated by Board resolution (majority unless otherwise specified). KPI definition changes require CB opinion and Gazette notice.


10.10 Transitional & Housekeeping

10.10.1 Initial Schedule

Within 30 days of adopting this Article, Secretariat publishes: (i) Annual Sprint Calendar, (ii) Geneva Dialogue week dates, (iii) Regional Summit windows, (iv) initial Sectoral Capital Track lineup.

10.10.2 Legacy Alignment

Legacy projects migrate to Annex P/Q templates at next milestone; data/model artifacts receive retroactive QA/QC and Model Cards within 90 days.