Approvals and the needs-you lane

Which transitions stop and ask you, what each button does, and how to answer from the CLI.

Torta starts nothing you have not approved. An agent that cannot finish stops and asks.

What lands in the lane

A status marked userFacing carries a prompt, the question the board shows. The default workflow has five:

Status	The question you are asked
`SPEC`	This is one slice of the plan. Approve it, or send it back for more detail?
`REVIEW`	Approve this before it gets built?
`BLOCKED`	This work stopped on something it cannot get past. Look at what blocked it?
`NOT_FEASIBLE`	This cannot be built the way it was described. Drop it, or describe it differently?
`FOR_DEPLOY`	This is ready to go live. Ship it?

Your first ticket arrives as REVIEW.

The three decisions

approve makes the transition the session stopped to ask about. From REVIEW that is APPROVED.
reject sends it back for changes. From REVIEW that is REDO, back to its author.
interrupt stops the running session instead of ruling on the ticket.

Each row on the board names where approve and reject would send it.

REDO and RE_SPEC both increment redo_count, and the third one halts the ticket and notifies you.

Where a pending decision lives

Open decisions are files under .torta/pending/, one JSON file per question. The board lists them, sweeping stale entries as it reads. Each row carries the ticket, the question, the note from the status, and the last few budget_breach or lease_reclaim events for it.

While a ticket is a question for you, the engine holds it back.

Answering from the terminal

torta pending
torta approve <ticket> --reason "looks right"
torta reject <ticket> --reason "needs the empty state"
torta reject <ticket> --interrupt

torta pending prints the decisions waiting on you. Both commands take an optional directory before the ticket.

Approving with no engine

Approving moves the ticket. It starts nothing unless an engine is running. torta board gives you the board alone; torta start brings both.