liveBook · Manning

Approval decision

As explained in Vibe Engineering

Action approval is a human authorization step that must be granted before an automated system performs a requested operation.

An approval decision is a human authorization step before an automated system performs a requested operation. For AI coding agents, it keeps reading, writing, searching, and execution under explicit human control. section 5.2.1

Use approval decisions to structure agent activity:

  • Review the agent’s proposed plan before execution begins. section 5.2.1
  • Grant or deny each requested operation, such as reading files, searching the codebase, editing code, or executing actions. section 5.2.1
  • Constrain authority through modes: Architect can propose designs, Code can edit within boundaries, and Ask can answer questions. section 5.2.1

Payment validation migration

An agent proposes migrating payment validation, requests permission to read PaymentService.py, then asks separately to search for currency validation and read currency.py. The operator approves or denies each step. section 5.2.1

How Vibe Engineering covers it

How deep it goes
Explains approval through an agent loop, permission prompts, planning, and constrained modes, but stops short of implementation details.
Examples
Uses file-read, code-search, and payment-validation migration prompts with Allow and Deny choices.
What you can do after
Operate AI coding agents by reviewing plans and approving or denying individual actions within constrained modes.
How it connects
Connects approval decisions to AI coding agents, the Plan-Act-Observe loop, Plan Mode, and role-based access control.

Also explained in

Compare how 3 books explain approval decision →

Related concepts

This explainer was generated by Manning's knowledge graph from the text of Vibe Engineering. The section links point to the parts of the book it draws on.