# Choose where Taiga waits for a decision

Taiga Learning · Worksheet
https://taiga.training/en/lessons/taiga-autonomy/

Use fictional or approved information. Do not put secrets in this worksheet.

## Learning objectives
- Distinguish automatic build from autonomous merge.
- Explain merge ceilings, product defaults, and initiative overrides.
- Check branch rules and deployment consequences before enabling automation.

## Exercise
The fictional equipment service needs human review of plans and pull requests. Its main branch deploys to staging. Write the build setting, required branch rules, merge setting, and separate production approval needed for this arrangement.

## Your response
- Scenario and scope:
- Assumptions and open questions:
- Proposed answer or decision, with reasons:

## Verify your response
| Claim or criterion | Evidence or test | Result or gap | Owner |
| --- | --- | --- | --- |
| | | | |
| | | | |
| | | | |

## Next action
- Action, owner, and date:
- When will you review this response?

## Principle to retain
Autonomy settings control when work proceeds. Repository rules, permissions, and deployment controls must enforce the boundaries you require.

## Sources
- [Taiga docs: Initiatives](https://docs.tai.ga/deliver/initiatives/)
- [Taiga docs: Autonomous merge](https://docs.tai.ga/deliver/auto-merge/)
- [Taiga docs: Integrations and environments](https://docs.tai.ga/administration/integrations-and-environments/)

This worksheet supports learning. Completing it does not itself authorize a production change.