An engineer reviewing a deployment authorization screen showing Approve & Merge to Production and Reject Deployment options, awaiting human review

Human approval: the merge button still matters

This is part 2 of the Agent production system series. Previous: Eval gates are not optional theater. Constellation node: Human approval. Words I use below Agent โ€” a program that writes code or words for you, and can use tools, in a chat or a job queue Pull request (PR) โ€” a proposed change to a code repository; someone (or something) asks to land a diff, and reviewers say yes or no Merge โ€” accepting that pull request into the main line of code, so the change becomes part of what ships Force-push โ€” overwriting history on a branch; useful in cleanup, dangerous when it erases work other people (or agents) already built on Irreversible action โ€” something hard or expensive to undo (delete data, rotate a secret into the void, change production infrastructure, send a public message you cannot unsend) Approval identity โ€” a separate login or app credential whose only job is to approve and merge a reviewed pull request (not the same credential the agent uses to write code day to day) Decision brief โ€” a short package an agent hands a human: what it wants to do, why the gate fired, what it already checked, and what it needs you to decide โ€” not a guilt trip and not a demand Action class โ€” a bucket of similar actions that share one autonomy rule; routine merges after checks can be auto, irreversible carve-outs always pause Those eight words are the toolkit. Now the point. ...

July 31, 2026 ยท Dave Voyles