> For the complete documentation index, see [llms.txt](https://murray-love-code.gitbook.io/murray-love-code-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://murray-love-code.gitbook.io/murray-love-code-docs/use-cases/data-operations.md). # data operations Data leaders should own definitions, grain, joins, calendars, currency rules and quality status. Operations leaders should own runtime budgets, dependency monitoring, evidence retention, incident response and revocation. For customer concentration, for example, a percentage may be permitted while customer names remain restricted. The answer must still identify which certified revenue definition and reporting period it uses. --- # 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 dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://murray-love-code.gitbook.io/murray-love-code-docs/use-cases/data-operations.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. 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.