Interoperable State Infrastructure
Federated systems with defined interfaces, not one giant government database.
Interoperable state infrastructure
The digital layer this architecture depends on is not one giant government database, and it is not a single central computer coordinating society. It is closer to an operating system: common infrastructure that separate systems build on top of, communicating through defined, access-controlled interfaces.
Illustrative systems that would need to interoperate, without merging into one store, include: identity, payments, taxation, product information, business registration, public expenditure, infrastructure state, and environmental data. Each can remain a separate system of record, built and operated by the institution best placed to run it, exposing only the specific, purpose-limited interfaces other systems legitimately need.
This distinction matters architecturally, not just rhetorically: a federated design with defined interfaces can support the same policy functions (adaptive taxation, outcome-tracked spending, product verification) as a single monolithic store, while bounding what any one breach, misuse or scope-creep episode can expose. See Privacy for the constraint this operates under, and Digital State Architecture in Design Decisions for why this candidate rejects both departmental silos (which cannot support the measurement this system needs) and a single centralised database (which concentrates risk unnecessarily).