(Swiss Verein; Zug register; principal base Geneva. This Bylaw establishes the GRF program system (DRR/DRF/DRI), the Sendai-aligned KPI regime, quarterly public scorecards, regional 90-day sprints, and the lifecycle controls for track artifacts (T+72h filings, provenance, QA sign-off). It binds Executive Management (EM), Regional/Thematic Chairs, and program delivery to the Central Bureau (CB) clearance and Council System of Record (CSR). Cross-refs: Arts. 1 (Purpose), 3 (Independence), 4 (Membership), 5 (Defs/Precedence; EN controls; FR/DE companions), 6 (Organs), 7 (Representation), 8 (Appointments & Elections), 9 (Authorities/DoA; CB), 10 (Programs/Tracks/Regionalization), 11 (ECT), 13 (CSR/Gazette/Records), 14–16 (Finance; Data/Privacy/Security; Ethics), 17 (Protocol), 18–21; Bylaws 1–5. Annexes: F (DoA), G (Signatory), T (Data/Model Governance), W (Records), X (Gazette), Z (Continuity/RAP). EN controls.)
6.0 Construction, Scope & Roles
6.0.1 Scope & Hierarchy
This Bylaw operationalizes Article 10 (Programs, Tracks & Regionalization). If conflict arises, Art. 5.2 (Precedence) governs; Board-reserved matters under Art. 9.1 prevail over this Bylaw and any playbooks.
6.0.2 Program Pillars
GRF programs are organized under three overarching pillars:
(a) DRR – Disaster Risk Reduction (risk understanding, prevention, preparedness, early action);
(b) DRF – Disaster Risk Finance (risk transfer, contingent finance, payout rails);
(c) DRI – Disaster Risk Intelligence (analytics, foresight, benchmarking, decision support).
Each pillar is delivered through Tracks (Research, Innovation, Policy, Capital, Foresight) per Art. 10.
6.0.3 RACI for Delivery & Assurance
Responsible (R): Regional/Thematic Chairs for sprint execution; Program Directors (DRR/DRF/DRI) for method pipeline.
Accountable (A): ED/CEO for KPI attainment and Operating Plan delivery.
Consulted (C): Leadership Council (policy); Board Committees (ARC/FIC/TDC/ECC).
Informed (I): Board of Trustees (quarterly).
CB (Privy Council): non-executive—issues Clearances, maintains Registers, publishes Gazette, and may halt non-cleared acts (Arts. 9.3, 12).
6.0.4 Nexus Platform Interfaces (operational)
Programs run on the Nexus stack: NXSCore (HPC/GPU), NXSQue (orchestration), NXSGRIx (standardization/benchmarks), NXS-EOP (AI/ML & simulation), NXS-EWS (early warning), NXS-AAP (anticipatory actions), NXS-DSS (dashboards), NXS-NSF (financial rails). Platform use must respect Art. 15 and Annex T.
6.1 KPI Governance — Sendai-Aligned Indicators & Public Scorecards
6.1.1 Principles & Classes of Indicators
(a) Public-benefit materiality. KPIs must reflect real-world risk reduction, coverage and decision quality, not vanity metrics.
(b) Alignment. KPIs are Sendai-aligned and mapped to DRR/DRF/DRI outcomes.
(c) Classes. Each pillar maintains: Inputs, Outputs, Outcomes, Impact; Leading (predictive) and Lagging (realized) indicators.
(d) Baselines/targets. Every KPI has a documented baseline (t₀), target (t₁…tn), owner, method spec, update cadence, and uncertainty bounds.
(e) Disaggregation. Where relevant: region, hazard, income group, gender/age/disability, rural/urban.
(f) Data quality tiers. DQ0–DQ3 (annexed): DQ3 = independent, triangulated, reproducible; DQ0 = indicative only (must be labeled).
(g) Independence wall. KPIs cannot be donor-conditioned; any susceptibility triggers an Independence Impact Assessment (IIA) (Annex J) and CB review.
6.1.2 Minimum KPI Families (illustrative definitions)
DRR
- Early-warning lead time (hours): median lead time delivered to at-risk populations by hazard HHH. Source: NXS-EWS logs; DQ2–3.
- Reach (% at-risk reached): proportion of at-risk population receiving actionable alerts (by channel), with verification rate.
- Loss avoidance (CHF): modeled avoided losses vs. counterfactual (method: PML/AAAL change; uncertainty bands required).
- Resilience standard uptake (% assets/jurisdictions): share meeting defined resilience criteria (critical infrastructure, health, education).
DRF
- Protection-gap index (%): insured/financed losses ÷ modeled losses for event classes; reported by region/income.
- Time-to-payout (days): median days from trigger to beneficiary receipt, by instrument (parametric/indemnity/sovereign CRF).
- Capital leverage (×): CHF mobilized via GRF-facilitated structures ÷ CHF of platform/operating cost.
- Beneficiary coverage (people/assets): active coverage counts with equity lens; include % lowest income quintile.
DRI
- Forecast skill (Brier/CRPS): hazard nowcast/forecast skill with calibration plots.
- Bias & calibration error: pre/post-correction bias; reliability diagrams; fairness diagnostics where person-level data exists.
- Decision uptake (% citing): decisions citing DRI artifacts (CRE/URI evidence in CSR).
- Data completeness & freshness (%): coverage by hazard/exposure; median latency (days).
Method specs, equations and QA criteria are maintained in Annex T and published in the KPI Catalogue (CSR).
6.1.3 KPI Lifecycle Controls
(a) Specification file. Each KPI has a versioned spec (owner, formula, data sources, QA tests, caveats).
(b) Method change control. Changes logged in Method Change Log, validated by Model Risk & Validation CoE, CB-cleared if Material; restatement policy in §6.5.2.
(c) Assumptions & limitations. Public scorecards must carry plain-English caveats; quantitative uncertainty is mandatory for modeled KPIs.
(d) Reproducibility. Computation notebooks (or equivalent pipelines) are hashed and archived in CSR; open-source where feasible.
6.1.4 Quarterly Scorecards (Public)
(a) Cadence. Quarterly, within 30 days of quarter end (Q1–Q4).
(b) Form. Public HTML/PDF + machine-readable annex; EN controls; FR/DE companions as feasible.
(c) Content. KPI table (baseline/target/actual/Δ), uncertainty, narrative drivers, variance flags (R/A/G), corrective actions, and CB Clearance ID.
(d) Compute freeze. Data “freeze date” is disclosed; late data appear as Q-1 restatements per §6.5.2.
(e) Filing & transparency. Filed in CSR; Gazette summary within 10 Business Days (lawful redactions).
(f) Independent assurance. ARC may commission limited assurance on selected KPIs; opinion excerpt is gazetted.
6.2 Regional 90-Day Sprints — Publication & Close-Out
6.2.1 Sprint Charter & Stage-Gates
Before kick-off, a Sprint Charter is filed in CSR with: scope, users, KPI set, milestones, resources, risks, DPIA/TIA (if any), and publication plan.
Gates: Initiate → Scope → Build/Test → Operate/Publish → Close-Out. Evidence at each gate is mandatory.
6.2.2 Required Publications & Timelines
(a) T+72h after each sprint session:
• Session Note (scene-setter; decisions; vote tallies if any);
• Action Log (owner, due date, dependencies, CB conditions).
(b) D+30: Baseline Pack (starting KPI values; sources; QA summary).
(c) D+60: Midpoint Update (variance analysis; risks; remediation steps).
(d) D+90 (Close-Out): Sprint Outcome Pack (KPI deltas; artifacts; uptake; lessons; next-cycle asks).
All filings carry classification (Art. 13.2) and are cross-referenced to the KPI Catalogue.
6.2.3 Variance Management & Escalation
(a) Red variance. If a KPI crosses Red thresholds (Standing Orders), the owner files a Remediation Plan within 15 Business Days.
(b) Escalation ladder. Owner → Program Director → ED/CEO; CB may halt Material Actions lacking required Clearance.
(c) Board call-in. The Board may call-in any sprint under Art. 9.1(j).
6.2.4 Resourcing & Procurement
Sprint resources (data, vendors, venues) follow Annex F (DoA), Annex AB (open-contracting), and CB Clearance for Material Actions (DRF rails; exclusive licenses; cross-border data).
6.2.5 Inter-Nexus Work (ECT)
Where sprints implicate ECT collaboration (Art. 11), Joint Clearances and mirrored Register entries are required. Independence rules and non-exclusivity safeguards apply.
6.2.6 RAP Compatibility
During RAP (Art. 19), timelines may compress; deviations are marked with RAP IDs and post-ratified.
6.3 Track Artifacts — T+72h Filings, Provenance & QA Sign-off
6.3.1 Mandatory Artifact Set (per Track/Session)
- Session Note (T+72h) with decisions and vote tallies (where applicable).
- Action Log (T+72h) with owners, deadlines, dependencies, CB conditions.
- Publication Pack for any public-facing output, comprising:
• abstract & intended use;
• Data Card(s) (sources, licenses, lineage, limitations);
• Model Card(s) (training/validation; calibration; fairness; failure modes);
• QA/validation evidence;
• license terms (open/FRAND/restricted) compliant with Annex T;
• Clearance ID;
• classification and provenance hashes;
• stable URI/CRE reference. - Implementation Note (if deployed): deployment design, monitoring hooks, rollback plan, and service levels.
6.3.2 Provenance, Versioning & Immutability
(a) Every artifact carries a content hash, version ID, and CRE link.
(b) Revisions create new versions; prior hashes remain accessible in CSR.
(c) Public artifacts display a provenance banner (version/date/hash/maintainer).
6.3.3 QA Sign-off Chain (minimum)
Data/Model: Chief Data Steward (CDS) signs Data/Model Cards and QA/QC; CISO (security) and DPO (privacy) sign where applicable; CB Pre-Clearance for public release, cross-border transfers, safety-critical/high-stakes analytics. Authorization within DoA by ED/CEO or delegate.
6.3.4 Access, Licensing & Privacy
(a) Licensing per Annex T; third-party terms must be honored; no donor-conditioned editorial control (Art. 3).
(b) Classification per Art. 13.2 (Public / Member / Internal / Restricted / Secret).
(c) Personal data minimized; DPIA/TIA and ROPA updated pre-release (Art. 15.4).
6.3.5 Retention & Legal Holds
Artifacts are retained per Annex W (≥10 years for material publications). Legal Holds (Art. 13.4) override destruction.
6.4 Methods Governance, Restatements & Deprecation
6.4.1 Method Change Control
Any change to KPI definitions, computation methods or material data sources must be:
(i) logged in the Method Change Log; (ii) reviewed by Model Risk & Validation CoE; (iii) CB-cleared if Material; (iv) disclosed in the next scorecard with impact analysis.
6.4.2 Restatement Policy
(a) Minor restatements (≤1% Delta or DQ tier uplift) are footnoted in the next scorecard.
(b) Major restatements (>1% Delta or method change) require a Restatement Note (cause, magnitude, comparatives) and Gazette summary.
(c) Historical series remain accessible with clear version labels.
6.4.3 Deprecation & Replacement
Deprecated KPIs/artifacts require a sunset plan and replacement mapping; back-series restated or bridged. All versions remain in CSR with provenance.
6.5 Scorecard Mechanics, Weights & Remedies
6.5.1 Aggregation & Weights
(a) Pillar-level scores may aggregate project KPIs using published weights (stakeholder-approved), documented in the KPI Catalogue.
(b) No aggregation may mask Red on any safety-critical KPI; “safety-critical trumps composite.”
6.5.2 RAG Thresholds & Triggers
(a) Green: ≥ target or within tolerance; Amber: within alert band; Red: beyond alert band. Thresholds published in Standing Orders.
(b) Triggers: Red → Remediation Plan (§6.2.3) within 15 Business Days; two consecutive Reds → Board/Committee review.
6.5.3 Independent Review & Challenge
(a) ARC may commission independent review of KPI computations and controls; TDC reviews model governance posture.
(b) Chairs and members may file a Challenge Note with evidence; CB logs and routes to the appropriate committee; outcome gazetted in summary.
6.6 Transparency, Publication & Communications
6.6.1 CSR & Gazette
Scorecards, Sprint Packs, and Publication Packs are filed in the CSR and summarized in the Council Gazette within required timelines (lawful redactions; Art. 13.3).
6.6.2 Public Dashboards & Member Views
EM may publish public dashboards (privacy-safe) alongside member-level views with additional detail consistent with classification rules.
6.6.3 Plain-Language Summaries
Each public artifact must include a plain-language summary (aim, method, limitations, do-not-use cases).
6.7 Exceptions, RAP Interface & Enforcement
6.7.1 Exceptions & Waivers
Temporary deviations from this Bylaw require: Board resolution (scope & duration), CB Clearance, and Gazette notice (lawful redactions).
6.7.2 RAP (Art. 19)
During RAP, the Chair and CGS may authorize compressed cycles and RAP-Clearances with post-event ratification; all RAP decisions carry RAP IDs.
6.7.3 Non-Conformance & Sanctions
Failure to file required artifacts, falsification, or execution without required CB Clearance is a material breach:
(a) CB may halt publication/execution;
(b) ED/CEO files a Cure Plan within 10 Business Days;
(c) Persistent breaches escalate to the Board and may trigger disciplinary action (Art. 16) and contract remediation/clawback.
6.8 Quick-Reference Calendars
6.8.1 Quarterly Scorecard
- Q Close: Day 0
- Compute Freeze: Day +7
- Internal Review (ARC/TDC/ECC as needed): by Day +20
- CB Clearance & CSR Filing: by Day +25
- Public Release & Gazette Summary: by Day +30
6.8.2 Sprint Artifacts
- Session Note & Action Log: T+72h
- Baseline Pack: D+30
- Midpoint Update: D+60
- Outcome Pack: D+90
6.9 Glossary (this Bylaw)
DQ: Data Quality tier (DQ0–DQ3). Freeze date: date at which inputs are locked for a scorecard. KPI Catalogue: CSR index of KPI specs. Method Change Log: CSR record of definition/algorithm/source changes. Publication Pack: complete, sign-off’d bundle for any public output. RAP: Rapid Activation Protocol. URI/CRE: stable link/Council Register Extract.