> 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/why-governance.md). # why governance Natural-language access makes enterprise data easier to query, but fluency can hide four different failures: unauthorized access, ambiguous meaning, unsafe execution and unsupported conclusions. Valid SQL is therefore necessary but insufficient. A governed text-to-SQL path must decide what the requester may learn before exposing schema, use owned business definitions, constrain execution, and retain enough evidence to reconstruct material answers. Enterprise AI data access also needs an explicit non-answer path: clarification where meaning is incomplete and refusal where data, permission or an approved action is absent. The framework converts these concerns into 16 testable controls across eight domains. See [Governance Framework](/murray-love-code-docs/framework/readme.md). --- # 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/why-governance.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.