This is part 6 of the Agent production system series. Previous: Claim safety. Later: GitHub tokens and the last click. Words I use below Agent. A program that writes and lands code for you, in a chat session. Automate. Let the agent do the step without you. Work path. The steps from idea to shipped. I also call this the funnel. The middle is plans, code, and tests. The edges are the start and the finish — where someone can get hurt. ...
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. ...