docs
Contents
Concepts

Change proposals and execution

A change is approved by its exact version, then delivered as a pull request or a CMS draft.

A change proposal describes one change: what, where, why, risk and the evidence behind it. It moves through draft, awaiting approval, approved or rejected, superseded (a newer revision replaced it) and executed.

Approval is bound to a hash of the exact proposal. If anything changes after approval, the approval no longer applies and the new revision needs its own.

Execution

  • Code changes: Webtick opens a pull request on the linked repository through its GitHub App, limited to the allowed paths. It never merges.
  • Content changes: Webtick saves a draft through your CMS's MCP server, using only the tools you enabled and mapped. It never publishes.
  • CMS schema changes always need a person and are reported as a manual schema change.

Execution states include queued, preparing, pull request open, CMS updated pending publish, merged or closed, verified and failed. Every step is in Activity.

Next: Autonomy levels