# Concepts

Understand the setup, its files, and each separate permission.

Canonical page: https://bowerloom.ai/docs/concepts/

Version: 0.7.0-beta.1 · Release: v0.7-beta.

[Source repository](https://github.com/sageadvicellc/bowerloom) · [Current support and limits](https://bowerloom.ai/docs/status/)

Use these concepts to understand the specification for your existing workflow. They explain the roles, files, and approvals that you compare before integrating Bowerloom with the project. A plan describes proposed effects, and exact approval permits only the bound operation. Keep file readiness, runtime readiness, and execution authority separate.

| Question | Explanation |
| --- | --- |
| What does a team setup contain? | [Teams, agreements, and files](/docs/concepts/teams-and-files/) |
| What does approval permit? | [Plans and exact approval](/docs/permissions/) |
| What can the system trust? | [Trust and security boundaries](/docs/security/) |

A plan describes proposed effects. Exact approval permits the bound operation. The result records what happened, including uncertainty.

File readiness, runtime readiness, and execution authority are separate. [Status reference](/docs/reference/errors/) defines their fields.

For a concrete example, follow [Integrate your first team](/docs/learn/first-team/). For exact file names, read [Files and configuration](/docs/configuration/).