> 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/administer-and-govern/rollout-and-operations.md).

# Rollout and operations

Introduce and operate Lleverage changes without confusing testing, publishing and live operational responsibility.

Moving from a working build to a dependable operational capability requires more than publishing a Workflow.

This section covers the practices around introducing change, observing live behaviour and deciding who acts when something needs attention.

The exact rollout process is organisation-specific, but three boundaries should stay clear:

* **build and test** — prove the implementation with realistic inputs;
* **publish and operate** — make a reviewed version the live path;
* **observe and improve** — use real execution evidence and operator feedback to decide what changes next.

Lleverage provides the runtime and product controls. Your organisation defines the release authority, review cadence and support ownership around them.


---

# 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.lleverage.ai/administer-and-govern/rollout-and-operations.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.