> 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/governing-principle.md).

# governing principle

For a material answer, an organization should be able to reconstruct:

1. who or what asked;
2. what that identity was permitted to know;
3. which versioned business definitions applied;
4. what query ran and within which limits;
5. what sources and data state supported the result;
6. what verification occurred; and
7. why the system answered, requested clarification or refused.

This reconstructability standard connects access control, semantic meaning and operational evidence. A feature can support a control, but the deploying organization still owns configuration, approval, testing, retention and risk acceptance.


---

# 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/governing-principle.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.