> ## Documentation Index
> Fetch the complete documentation index at: https://docs.revolte.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Human-in-the-loop model

> Where people decide, what runs on its own and where approvals are enforced.

Revolte runs on its own between fixed checkpoints. You define the work, approve the plan and review the result. Between those points the agent understands the codebase, plans, writes and tests code and opens the pull request, even while you work on something else.

## The three checkpoints

| Checkpoint | Who | What happens |
| :- | :- | :- |
| Define intent | You | You bring a feature to build, a bug to fix or a ticket to execute. |
| Approve the plan | You | You review the proposed approach, the affected files and the validation steps before any code is written. |
| Review and merge | You | You inspect the changes in the pull request and decide whether to merge. |

## What runs without you

* Reading and understanding your codebase
* Building the plan
* Writing and testing code in an isolated [sandbox](https://docs.revolte.ai/get-started/sandboxes.md)
* Opening the pull request
* Running your build and deployment pipeline

A workflow can continue while your team is offline and pauses only where a person has to decide. When you respond, it resumes.

## Oversight at every stage

Every session keeps its plan, reasoning, generated code, execution history, approvals, pull requests and deployments. You can inspect, pause, resume or step in at any stage. See [Review the execution plan](https://docs.revolte.ai/workflows/review-execution-plan.md) and [Review code changes](https://docs.revolte.ai/workflows/review-ai-changes.md).

## Where you set the controls

* **Execution mode.** Choose how much Revolte does before it asks you. See [Interactive Chat](https://docs.revolte.ai/get-started/ai-chat.md).
* **Branch-to-environment mapping.** Decide which branches deploy where. See [Configure app and branch settings](https://docs.revolte.ai/yaml/repo-preferences/app-branch-settings.md).
* **Manual approval gates.** Require a person to approve before a deployment to a sensitive environment. See [Pipeline execution flow](https://docs.revolte.ai/deployments/pipeline.md).
* **Quality gates.** Run code review, code quality and tests before every build. See [Configure pre-build workflows](https://docs.revolte.ai/yaml/repo-preferences/prebuild-workflow.md).

## What always needs a person

Two things always involve a person, whatever the execution mode: you approve the plan before Revolte writes code, and you review the code and merge it. Pipelines can also require a manual approval gate before a deployment reaches a sensitive environment such as Production. See [Pipelines and approvals](https://docs.revolte.ai/deployments/pipeline.md).


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.