Route consequential work through explicit review

When Kole proposes a configured consequential action in Quantum Lab, the notebook pauses execution and presents the proposal for review. The person reviewing can inspect what the agent wants to do, check or edit the arguments, and decide whether to approve or reject the action before it runs.

This keeps the human in the loop for operations that change data, structure, or stored queries -- the kind of work where reviewing the target and intent matters before committing to it.

What triggers approval

Approval is triggered when Kole proposes an action using a tool that has been configured as consequential. Read-only discovery tools -- inspecting schemas, listing tables, browsing metadata -- run without pausing because they do not change anything. Only tools that write, mutate, or create are configured to require explicit review.

The distinction is deliberate: the agent can gather context freely, but it cannot act on that context without a person confirming the proposed operation. Not every action in a notebook requires approval -- manual blocks you write and run yourself proceed normally. The gate applies to configured agent-proposed consequential actions specifically.

How review works

When a consequential action is proposed, Quantum Lab shows an approval card with the action name, the arguments Kole intends to use, and the source context. The reviewer can read the proposed operation, edit the arguments to narrow scope or correct intent, and then approve or reject.

Rejecting an action lets you include feedback so the agent understands what to change. Approving with edited arguments lets you refine the proposal without starting over. The goal is that the person reviewing has enough information to make a judgment about whether this specific operation should proceed with these specific arguments.

After the decision

An approved action proceeds with the final arguments (original or edited). A rejected action does not execute; the agent receives the rejection and any feedback provided. The notebook continues from there -- the reviewer's decision is the gate, and no configured consequential action bypasses it.