Comprehensive Operational Manual & Technical Specification for Sovereign Cabinet Ministers, Institutional Investors, Multilateral Country Directors, Logistics Operators, and Field Economists.
The Strategic Systems Intelligence (SSIP) is an independent analysis platform. It is not an organ of the Republic of South Sudan, holds no official mandate and issues no official publication.
What is operational today: a corpus of dated, source-attributed records, each carrying an explicit evidence state; retrieval, filtering, sorting, comparison and CSV/JSON export over that corpus; an evidence ledger with declared gaps, contradictions and published corrections; and, for organisations with a contracted plan, the institutional API (Section 8). No language model runs anywhere in SSIP: nothing on this site is summarised, phrased or decided by one. SSIP is built with the help of an AI coding tool; that tool is not part of the product.
PLANNED — not connected: satellite radar observation, riverine telemetry, community 2G/USSD field reporting and automated multilateral synchronisation. These are described throughout this manual as the design SSIP is built around. Each is labelled where it appears. None is receiving data.
The platform features 4 Tailored Decision Perspectives accessible via the top status bar. When toggled, every visual dashboard, alert threshold, and tabular view dynamically adapts to the user's strategic focus:
The platform is organized into specialized intelligence hubs accessible via the secondary navigation bar or Universal Search:
| Module Name | Strategic Function | Primary Beneficiary |
|---|---|---|
| Decision Command Landing | National overview computed from held records — OPERATIONAL | Cabinet, Ministers, Country Directors |
| Decentralized Edge Mesh (*884#) | Offline 2G/USSD gateway, LoRa relay — PLANNED, NO GATEWAY PROVISIONED | Field Enumerators, Remote Communities, Trade Traders |
| Macroeconomic Stress Lab | Scenario model over stated assumptions — SIMULATED | Ministry of Finance, Central Bank, IFI analysts (intended audience — not users) |
| Multilateral Integration Hub | World Bank / IMF / FAO / HDX connector design — NOT CONNECTED | Development Partners, UN Agencies, Embassy Missions |
| Juba Market Basket Pilot | 12-commodity price index across 3 Juba bazaars — REFERENCE CORPUS | Commercial Banks, Retail Importers, Policy Planners |
| 13 State & Area Profiles | Profiles for all 10 states and 3 administrative areas — OPERATIONAL | State Governors, Local Administrators, Investors |
SSIP holds records for every jurisdiction below. Coverage means held records with dates and sources — not active telemetry, which SSIP does not receive from anywhere:
PLANNED — NO GATEWAY PROVISIONED. The short code *884# is not
registered with any South Sudanese mobile network operator, no USSD gateway is connected, and no LoRa relay is deployed.
Dialling these codes today reaches nothing. They are specified below so the design can be reviewed and costed:
SIMULATED. The Macroeconomic Stress Lab runs policy shock experiments over stated assumptions. Users adjust sliders for oil production quotas (bpd), pipeline transit tariffs and FX auction volumes to see modelled impacts on inflation, reserves and food basket costs. Output is model behaviour under those assumptions — it is not an observation of South Sudan and must not be cited as one. The “decision room” the design describes would send scenario parameters to a language model; SSIP has no language-model runtime, so nothing is generated on any deployment. Since 2.8.8 the Lab / Preview screens are not included in the production web root at all: their addresses state that, and the screens exist only in a separate review build.
NOT CONNECTED. The Institutional Integration Hub is a connector catalogue, not a running integration. SSIP has never contacted the World Bank Open Data API, the IMF Article IV series, FAO/WFP VAM or the UN-OCHA Humanitarian Data Exchange; it holds no credentials for any of them and has no agreement with any of them.
No synchronisation has run, so the snapshot register and the reconciliation log are empty. An empty reconciliation log means
SSIP has compared nothing — it does not mean the sources agree. The endpoints that would write to those stores return
501 and write nothing.
Production SSIP is two things: this static web root (every dataset is compiled into the application, and
/api/* on the web host answers a genuine 404) and the institutional backend, a separate service
that serves the staff portal and the API at /api/v1.
/api/v1 requires a signed-in
session or a bearer token issued at sign-in, the permissions of the account's role, and an organisation whose contracted plan
includes the module and api:access; otherwise it answers 401 or 403 not_entitled. The only
anonymous paths are GET /api/v1/health (an uptime check) and GET /api/v1/evidence-states (the state
definitions). API keys are issued only by SSIP staff to a contracted organisation and are rate-limited to the contract. Request
access through Request access; the reference is the backend package's
docs/API.md.
An earlier edition of this manual documented a demonstration API (/api/health, /api/intelligence/*,
/api/ask/synthesize) and said that “requests are unauthenticated”. Those paths belong to a local
preview server used only for development and the test suites; it has refused to run as a service since 2.8.6, is deployed
nowhere, and since 2.8.8 contains no model client — its former summarisation endpoint answers 503 and
generates nothing. Nothing in production SSIP is reachable without controlled access, and nothing in it calls a language model.
*884# mesh and a river-gauge survey tasking. SSIP can execute neither: it operates no USSD gateway and dispatches no aircraft. In a real event, act through the responsible authority.Executive user manual • Version 4.3.0 (release 2.9.2) • SSIP is not an organ of the Republic of South Sudan and issues no official directive