> 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/framework/readme.md).

# README

The canonical control set contains 16 records. Every record defines a requirement, a falsifiable test, a pass condition and expected evidence. Use the domain pages for implementation guidance and the [canonical JSON](https://github.com/murraylovecode/enterprise-data-agent-governance/blob/main/data/controls.json) for automation.

| Domain               | Core decision                                   |
| -------------------- | ----------------------------------------------- |
| Identity             | Is the requester known?                         |
| Authorization        | What may that identity discover and execute?    |
| Semantic grounding   | Which owned definition governs the term?        |
| Query safety         | Can execution stay inside approved boundaries?  |
| Verification         | What supports the result?                       |
| Refusal              | When must the agent decline?                    |
| Lineage              | Can the answer be reconstructed?                |
| Audit and operations | Can drift, incidents and revocation be managed? |


---

# 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/framework/readme.md?ask=<question>&goal=<endgoal>
```

`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.