> For the complete documentation index, see [llms.txt](https://docs.e6data.com/query-engine/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.e6data.com/query-engine/reference/platform-reference.md).

# Platform reference

- [Version upgrades](https://docs.e6data.com/query-engine/reference/platform-reference/version-upgrades.md): How to upgrade Platform Components and the Metadata Service for your workspace, and what to expect.
- [Release notes format](https://docs.e6data.com/query-engine/reference/platform-reference/release-notes-format.md): What each section of an e6data release note covers, so you can scan releases efficiently.
- [Permissions matrix](https://docs.e6data.com/query-engine/reference/platform-reference/permissions-matrix.md): The complete set of Control Plane named permissions, grouped by resource family, as a lookup table.
- [Resource naming conventions](https://docs.e6data.com/query-engine/reference/platform-reference/resource-naming-conventions.md): Naming rules for e6data workspaces, clusters, and catalogs - allowed characters, length limits, and how names are normalized.


---

# 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://docs.e6data.com/query-engine/reference/platform-reference.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.