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

# Understand Lleverage

- [Lleverage overview](https://docs.lleverage.ai/understand-lleverage/readme.md): Understand what Lleverage does, where it sits in your operation, and how it carries recurring work across the systems your company already uses.
- [People, Agents and Workflows](https://docs.lleverage.ai/understand-lleverage/readme/humans-agent-and-workflows.md): Understand how people, the Agent and Workflows divide the execution of a real operational process in Lleverage.
- [Automation levels](https://docs.lleverage.ai/understand-lleverage/readme/from-manual-to-autonomous.md): A practical way to think about increasing automation without assuming every process should become fully autonomous.
- [Requests and exceptions](https://docs.lleverage.ai/understand-lleverage/readme/requests-exceptions-and-human-attention.md): Understand what Requests are, what operators can expect, and why their exact setup differs by organisation and workflow.
- [Process discovery](https://docs.lleverage.ai/understand-lleverage/readme/understanding-before-automating.md)
- [Agent context](https://docs.lleverage.ai/understand-lleverage/readme/how-lleverage-gets-its-context.md): Understand the different layers of instructions, context and system authority that shape Agent work.
- [Projects and solutions](https://docs.lleverage.ai/understand-lleverage/readme/projects-and-solutions.md): Understand a Project as the maintained working environment around an Agent, and how that differs from channel routing and the customer-facing Solution.
- [Operational metrics](https://docs.lleverage.ai/understand-lleverage/readme/measuring-improvement.md)
- [Documentation by role](https://docs.lleverage.ai/understand-lleverage/readme/start-here-by-responsibility.md): Find the part of the documentation that matches what you are trying to do in Lleverage.
- [Operational examples](https://docs.lleverage.ai/understand-lleverage/operational-examples.md): Representative examples of recurring operational work in the language used by the companies Lleverage is built for.
- [Key terms](https://docs.lleverage.ai/understand-lleverage/key-terms.md): The main Lleverage terms, explained in the context of real operational work.


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.lleverage.ai/understand-lleverage.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.