> For the complete documentation index, see [llms.txt](https://experience-digital-transform.gitbook.io/experience-digital-transformation/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://experience-digital-transform.gitbook.io/experience-digital-transformation/cloud-for-dpi/chapter-1/shared-public-building-blocks-raise-the-stakes.md). # Shared public building blocks raise the stakes Some capabilities are used by many services rather than one. Digital public infrastructure (DPI) refers here to shared components such as identity, payment, data exchange, notification, and records services that other public and private services can use. A shared component or building block can prevent every programme from rebuilding the same basic functionality. It also means that a poor operating decision can affect many services at once. If a shared identity service is unavailable, a permit portal, a benefit application, and an internal case system may all lose a route for users or staff. If a notification component is misconfigured, several services can send incorrect messages. The institution therefore needs to know who operates the component, what failure is tolerable, how it is recovered, who can approve changes, and whether dependent services have a degraded route. DPI is useful only when the shared capability is governed and operated as carefully as the services that depend on it. ![Diagram showing public services and DPI building blocks: government services, citizen services, digital channels, data assets, identity profiles, business processes, policy and rules, APIs and services, and ecosystem partners, supported by shared capabilities: compute, data, network, identity, integration, security, observability, recovery, and operations. Operating-home options are owned or colocated infrastructure, managed hosting, rented infrastructure, cloud platform, and SaaS.](https://1406653965-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FkZFMZ3jCMUwHtTN0sL4J%2Fuploads%2Fgit-blob-a18d0f5aeac8acc423f2c723a1ec1571cbef6762%2Ffinal.png?alt=media) This does not require every service to sit on one platform. Shared capability can reduce repeated work where the public purpose, legal basis, access rules, and operating arrangements support reuse. It can also create concentration risk if one component becomes a single, poorly understood point of failure. The arrangement must be judged against the effect on real services, not against the appeal of centralization. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://experience-digital-transform.gitbook.io/experience-digital-transformation/cloud-for-dpi/chapter-1/shared-public-building-blocks-raise-the-stakes.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.