controlled_action
Evaluate an action against runtime gate policies, execute if allowed, or initiate human approval workflow with optional spending limits.
Instructions
Run the high-level AVP controlled-action flow.
Returns `ControlledActionOutcome.to_dict()` as a JSON string. Possible
statuses are `executed`, `approval_required`, and `blocked`. Human approval
is never auto-approved; after approval, call `execute_after_approval`.Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| action | Yes | Action name to evaluate and execute only if Runtime Gate allows it | |
| resource | Yes | Target resource identifier bound into the Runtime Gate decision | |
| environment | Yes | Execution environment. Examples: development, staging, production | |
| delegation_receipt | Yes | DelegationReceipt JSON object string issued by the workflow owner/principal | |
| params | No | Optional execution params as a JSON object string. Default: {} | {} |
| amount | No | Optional monetary amount for spend-sensitive actions. Omit when not applicable | |
| currency | No | Optional ISO currency code for spend-sensitive actions. Example: USD | |
| approval_expires_in_seconds | No | Approval TTL in seconds when Runtime Gate returns WAITING_FOR_HUMAN_APPROVAL |
Output Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| result | Yes |