The agent proposes; the alias disposes

The agent works all week: builds, fixes, snapshots its results as candidate-tuesday, candidate-thursday. It can create snapshots freely. What it never touches is the alias named approved.

That pointer belongs to a human. A reviewer restores a candidate, clicks through the running result, and if it holds, moves approved onto it: one PUT to the alias endpoint. The nightly ship job evaluates nothing; it deploys whatever approved points at, and only that.

The governance isn't a prompt asking the agent to be careful, and it isn't a review process bolted on after. It's a division of the API surface: the agent proposes states, the human moves the pointer, the pipeline follows the pointer.

The agent proposes; the alias disposes.