Platform Ecosystem — Engineering Plan
Global Risk · Food Security · Natural Resource Management
The building plan for one shared system — Global Risk, Food Security, and Natural Resource Management — with the full capability register behind it: 259 repositories, 123 hub services, 34 NASA assets, and 36 documented use cases.
“Connecting space to village.”
Every platform section follows the same shape: the build matrix on three clocks, an interaction diagram, the companion exposure layers, the build seams, then documented use cases.
This plan turns the Master Architecture (v1.7) and SIG-NAL's GeoAI Strategy into a single build order: one shared data-and-capability layer, one gateway, and three platform domains that pull from it rather than duplicate it. Globa…
02Two internal documents independently describe the same mechanism — the SERVIR Global Platform Technical Integration Guide and SIG-NAL's GeoAI Strategy — which means GeoAI capabilities don't need their own integration architecture.…
03Every engineering decision in §04–08 traces back to one of six design principles and six strategic pillars set out in SIG-NAL's cross-platform GeoAI Strategy. They're restated here as the checklist each platform section is built a…
04RiskMap. Twelve perils under one MVP scope (Decision #1, resolved), each of which has to be answered on three different clocks : what is happening now, what the annualized baseline risk is, and how that baseline shifts under clima…
05GeoAI AgriNexus (Google.org-funded). Climate-driver-led, not commodity-led — but the build list is commodity-shaped, because what has to be constructed is a crop-type layer, a yield method and a calendar per commodity. Same three-…
06Land Cover and Environmental Monitoring (LCEM). Five PDD components — Land Cover & Change, Carbon Estimation, Ecosystem Intelligence, NbS Monitoring, Decision Support — which resolve, in build terms, into twelve monitoring themes …
07Global 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 capabi…
0822 tracked decisions as of Master Architecture v1.7. All 14 original items have a direction; 8 more surfaced when the three standalone platform documents were folded in. 18 of 22 still have real, unstarted next actions — none of t…
09Every service this ecosystem has completed, started or retired — 123 across the six hubs , each with the user institution named where a source names one, and each with a status. This is the asset base the three build matrices sit …
10SERVIR is one programme inside a much larger NASA applied-science estate, and most of that estate is open, free and already operational. This section inventories what the other programmes provide that these three platforms would o…
11Terminology tie-breakers and the source record — kept together so a reader checking a fact knows exactly where it came from.…