A numbered series on Africa's public institutions — what's broken, what
works, and what the evidence says. Each paper carries a stable WP number and is citable
from the Flux registry.
Most institutional software deployments in African field settings fail for a shared reason: they assume continuous connectivity that does not exist where they are meant to operate. This paper argues that offline-first architecture is not an optional feature but a prerequisite for data integrity — a system that loses or degrades data when the network drops produces worse operational intelligence than none. It frames connectivity assumptions as a requirements failure that precedes any line of code.
Conventional accounts attribute the underperformance of African public institutions to inadequate funding. This paper contends the deeper failure is the absence of tools built for their actual operating context: software has been imported rather than designed for local constraints. Resources are necessary but not sufficient; the relevant technology already exists; the unmet task is building it for here. The argument reframes institutional failure as a problem of design and translation rather than of budget.
