Approval boundaries

Purpose

Automated outbound acts on real people, using the user's domain, accounts and reputation. This skill defines the boundary between what an agent may do on its own and what requires the user to say yes — once, explicitly, for a specific action. It exists as one skill rather than a paragraph repeated in every workflow, because a rule that lives in eleven places drifts in eleven directions.

When to use / when NOT to use

• Use before performing any operation whose effect is act, before any bulk write, when resuming interrupted work, and when setting up an agent to run unattended.
• Use when you are unsure whether an earlier approval still covers what you are about to do. The answer is usually no; this skill says when.
• Do NOT use it to look up provider mechanics — scoped credentials and their enforcement belong to the adapter pack.
• Do NOT treat it as optional because the user seems in a hurry. Speed is not consent.