Shared base services do not only bundle development — they become infrastructure for many procedures. The more central the form, the more important the return path.
A shared base, many procedures — and the consequence that must return to the base.
At first, the Germany Stack sounds like technology: components, interfaces, standards, identity, data exchange, communication, payment, reusable building blocks. In political language it appears as an answer to a familiar problem. Too many digital public services have been developed separately; too often states, municipalities and specialist administrations had to build similar things several times; too rarely did procedures fit together across levels.
The promise is strong. A state that starts over digitally everywhere loses time, money and trust. Shared base services can simplify procedures, bundle development and help citizens, businesses and administration avoid failure at the seams of federal fragmentation. The Germany Stack is not meant merely to make administration more digital. It seeks to unify its digital foundation.
That is precisely where its political meaning lies. The state is not simply building tools. It is building platform forms. What used to sit inside individual procedures, forms or specialist applications moves into shared components. Identity, data retrieval, communication and delivery are no longer just auxiliary functions of a particular procedure. They become infrastructure for many procedures. Here the question of Accountable Power begins.
A platform acts differently from a single procedure. Its error does not stay local. Its assumptions repeat themselves. Its standards travel into many areas of administration. What appears there as a technical base can alter practical standing: those who cannot identify themselves fail to reach several services; those who are wrongly carried in a shared data logic take the error into several procedures; those who receive no intelligible response to a platform problem are not merely searching for a specific authority, but for the site of the form.
The state is not simply building tools. It is building platform forms.
For that reason, the Germany Stack needs sites of response. Not only at the margin, once support requests appear. Sites of response have to be built into the architecture. Who is responsible when a base service generates a consequence? Where does it become visible which component was involved? Which body can distinguish whether the problem lies in the specialist procedure, the interface, the register, the identity service or the platform logic? Who has responsive capacity when the task is not merely to repair one case, but to change a shared form?
A central access point without a clear return path remains incomplete. Citizens and businesses then experience a modern surface, but not a modern answer. They see the entrance, not the chain of forms behind it. They know that the state acts digitally, but do not reach the place where this action was built.
This is not an argument against the platformization of the state. On the contrary: shared digital foundations can strengthen answerability when they make patterns visible, clarify responsibilities and keep errors from hiding inside isolated specialist solutions. A stack can improve consequence-responsiveness because it bundles consequences instead of distributing them across many bespoke systems. But it must be more than a technical portfolio. It needs its own answerability architecture.
The decisive test is therefore not only whether the Germany Stack makes public services faster and more uniform. One must also ask whether its components remain reachable for their consequences. Where identity, data flow, delivery and communication become shared operative forms, decentralized support is not enough. The answer must be able to reach the platform form.
A state as platform needs more than standards. It needs sites of response that reach all the way to those standards.