# Changes through your tools. Never around them.

> Approved changes arrive as GitHub pull requests or CMS drafts. Webtick never merges, never publishes and never asks you to migrate.

## One change, fully described.

A change proposal says what changes, where, why, the risk and the evidence. Approval is bound to that exact version: edit it, and it needs approval again.

## Delivered where it belongs.

- **Code, as a pull request**: JSON-LD, metadata, llms.txt and other code changes, on your repository through the Webtick GitHub App, limited to the paths you allow.
- **Content, as a draft**: Through your CMS's MCP server, using only the tools you enabled and mapped. Schema changes always need a person.

## No engineering ticket.

The marketer approves; a maintainer merges. Every step is in Activity.

## Limits that always hold

- Never merges your code: changes arrive as pull requests.
- Never publishes your content: changes arrive as CMS drafts.
- Never hands a credential to a model.
- Never touches your hosting or infrastructure.

## Related

- [Autonomy and control](https://webtick.app/product/autonomy): You set how much runs without you
- [Integrations](https://webtick.app/integrations): The tools Webtick works through
