> For the complete documentation index, see [llms.txt](https://sfdigitalservices.gitbook.io/data-systems-guide/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://sfdigitalservices.gitbook.io/data-systems-guide/purpose-and-scope.md). # Purpose and Scope Most City technology standards focus on cybersecurity, compliance, or procurement requirements. While these are critical, they do not ensure that the underlying data systems are modern, usable, or effective for the staff who rely on them. The purpose of this guide is to define the baseline capabilities that make a data system reliable, easy to use, and adaptable for the City’s operational and analytical needs. These requirements are intended to: * Improve interoperability and reduce silos between departments * Enable automation and reduce repetitive manual work * Support collaborative development and transparency * Allow for faster, more secure delivery of new services and enhancements * Ensure scalability and sustainability by leveraging modern architectures ### When to apply this guide This guide should be incorporated when **procuring, developing or significantly upgrading** data systems. --- # 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://sfdigitalservices.gitbook.io/data-systems-guide/purpose-and-scope.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.