> For the complete documentation index, see [llms.txt](https://docs.kula.digital/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.kula.digital/get-started.md).

# Get started

- [Set up & get your first answer](https://docs.kula.digital/get-started/start.md): The full setup, start to finish — no technical help needed. About 15 minutes to your first real answer.
- [Run your first diagnostic](https://docs.kula.digital/get-started/first-diagnostic.md): Let the AI work up your whole studio in order — what's true first, what to do about it second.
- [What you can ask](https://docs.kula.digital/get-started/ask.md): A library of plain-English questions grouped by the problem you're trying to solve — with what to expect back.
- [Is my data safe?](https://docs.kula.digital/get-started/trust.md): The short, plain-English version of how we protect your studio's data — and where to read the detail.
- [Your weekly rhythm](https://docs.kula.digital/get-started/your-rhythm.md): A simple habit that keeps Kula Intelligence useful long after setup — what to check, what to ask, and where things live.


---

# 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.kula.digital/get-started.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.