P7Y

Action Gate tutorial

Learn how to review Action Gate results.

This service is in development. Live exercises below use your account and the deployed development contracts. Independent engine qualification is unfinished.

  1. Review and accept a policy interpretation, then acknowledge the exact typed binding. A new policy starts in shadow mode.
  2. Submit the exact proposed tool call and the required context. Arguments are data; they do not create new permissions.
  3. A shadow decision is always no; its diagnostic never authorizes execution. Activation needs a registered qualification for the serving release, so the exercise expects a refusal.

Try a live exercise

Shadow by default: decisions are no until a policy is activated on a registered qualification for the serving release. This workspace never executes a tool.

Checking account…

Read an example

Written by hand to illustrate the result, not a live or measured output.

Within the approved policy

You send

Policy v4
Support agents may issue refunds of up to $100 to the original payment method. (approved)
Call
issue_refund(amount: 80, currency: "USD", method: "original")

You get

Decision
yes — within the $100 limit, to the original payment method (v4 §1)
Outside it

You send

Policy v4
Support agents may issue refunds of up to $100 to the original payment method. (approved)
Call
issue_refund(amount: 80, currency: "USD", method: "store_credit")

You get

Decision
no — refunds must go to the original payment method (v4 §1)
Not covered, so no

You send

Policy v4
Support agents may issue refunds of up to $100 to the original payment method. (approved)
Call
issue_refund(amount: 95, currency: "EUR", method: "original")

You get

Decision
no — the limit is stated in USD; the approved policy does not cover currency conversion

Check your understanding

What did the caller supply? Which parts of the result follow from that input? Where does the example leave a question open?