Do not start with the agent.
Start with the consequence. The same agent may be harmless in one scope and unacceptable in another.
SIO22 · Refused Workflow Challenge
Define the consequence
before you connect the system.
Turn the generic ActionGate ceremony into the exact workflow your organization currently refuses to automate. Nothing you enter here becomes authority, policy, a connector, or an execution instruction.
AUTHENTICATED · YESNETWORK PERSISTENCE · NONEMACHINE AUTHORITY · NONE
CHALLENGE MANIFESTchallenge_—
DEFINITION STATEREADY_FOR_SHADOW_SETUP
NEXT AUTHORITY EFFECTNONE
01–07 / Define the refused workflow
Make every consequential assumption explicit.
Customer-entered text stays in this browser session. SIO22 performs no network persistence and creates no customer-system connection.
The refused workflow is the wedge.
Start with the action the organization will not delegate today.
Do not assume the authority source.
A directory role, API token, subscription, or system access may identify capability without proving permission for this action.
Precommit the proof.
Define success and prohibited collateral before future execution so evidence cannot be retrofitted around a preferred outcome.
machine_authority=NONE · permit=NONE · credential=NONE · customer_connection=NONE · execution=NONE