> 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-2/the-service-is-the-starting-point.md). # The service is the starting point Someone using a public service sees a short journey. They sign in, provide information, submit a request and receive a result. Behind that journey may sit several applications, databases, identity systems, certificate services, network routes and shared public capabilities. An interruption in any one of them can stop the public outcome. The useful question is therefore not simply, “Where should this application run?” It is: **what must work for a person to complete the service safely and receive a meaningful result?** That question changes how cloud is understood. A **virtual machine**, a software-defined computer running on shared physical equipment, can be running while the service cannot reach its identity provider. A database can be available while a certificate prevents a partner system from connecting. An application can restart while the information it needs has not been restored. Looking only at one component gives false reassurance. For the enrolment service, recovery means that learners can authenticate, submit a request, have it stored correctly and receive a result that staff can trust. Restarting a server may be part of recovery. It is not proof that recovery has succeeded. This service-first view also makes dependencies visible before an incident. A service may depend on a notification system, a shared data-exchange route, a payment capability or a public identity service. The organisation can then ask which of these dependencies are essential, who provides them, whether an alternative route exists and how the service behaves when one is unavailable. --- # 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-2/the-service-is-the-starting-point.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.