Platform Ecosystem — Engineering Plan
Global Risk · Food Security · Natural Resource Management
07

Cross-Platform Shared Infrastructure

Global Risk, Food Security, and NRM are three organizational and funding domains — three PDDs, three sponsor relationships, three sets of named hubs — sitting on top of what should be one shared system: one data layer, one capability layer, one set of MCP-wrapped tools. “Global Risk Platform” describes who scoped and funded a capability, not a separate system a user has to go find it in.

Five sharing points, built once

Shared signalGlobal RiskFood SecurityNRM
Deforestation / land-disturbance alerts
GFW GLAD-L/S2, RADD, DIST-ALERT
—EUDR compliance moduleProtect Nature module
Climate & hazard data
Drought indices, precipitation, temperature
Hazard modelsClimate-adjusted calendars, yield forecasts—
Land cover & changeExposure layer (assets + nature)Field/crop-type layer (cropland baseline)Platform backbone by definition
GEOGloWS streamflow/dischargeFlood hazard moduleIrrigation-water-availabilityWater-resource / wetland monitoring
NASA Harvest methodology—In-season yield estimation (primary)Cropland classification (adjacent)

Every future build decision defaults to “build this once, in the shared system, tagged with which domain scoped it” — not “build this for platform X, then figure out sharing later.”

Common audience model

The Global Risk PDD's five user groups are adopted as the confirmed, shared audience model for all three platforms, rather than each platform inventing its own list:

Governments

National and subnational.

Development partners

World Bank, FAO, WFP, UNDP, ADPC, RECOFTC.

NGOs / civil society

Private sector

Commodities, insurance.

SERVIR hubs

As internal users.

Hub footprint — a real mismatch, flagged not hidden

PlatformLead hubCo-lead / named hubsWhere real use cases exist today
Global RiskEast Asia and the PacificCo-lead: West Africa; supporting: South Asia, Mesoamerica, Tropical South AmericaAir quality (SEA), flood (GEOGloWS regions)
Food SecurityNot explicitly namedSouth Asia, Tropical South America, Mesoamerica ("Associated Hubs")East & Southern Africa (9 cases), Tropical South America (6) — not the named associated hubs
NRM / LCEMSouth Asia (explicit)East Asia & Pacific, SIG-NALTropical South America (renamed from Amazonia in 2025 — §09), East Asia & Pacific — not the starting hub
Worth flagging to platform owners directly. NRM's Protect Nature demand is documented in hubs that aren't its starting hub, and Food Security's most-developed hubs aren't the ones named as its primary associated hubs. Sequencing capacity-building investment should follow where real use cases already exist, not just where a platform is nominally starting.

Resolved (Decision #11): the Service Inventory's CATIE-led "Central America" hub and the PDDs' "Mesoamerica" hub are the same hub under two names — treat "Central America" as informal shorthand going forward.

← Previous06 · Natural Resource Management Platform — Engineering Detail Next →08 · Decisions Status Board & Phased Roadmap