What does action-space constraints mean in an ordinary business workflow?
An action space is the set of moves available to an agent in a task. A constraint removes some of those moves or makes them conditional. In a business, the constraint is a role permission or an approval rule, and the agent can be a person or software.
The term comes from reinforcement learning. In the Gymnasium library, a widely used toolkit for training agents, every environment declares an action_space that defines which actions are valid. Data companies now build business versions: Toloka describes environment mockups that replicate real tools' schemas, workflows and permission models. The research benchmark τ-bench gives agents a policy document for domains such as retail, and notes that some rules are enforced by the software while others depend on the agent applying them correctly. That second kind is where agents most often go wrong, which is why AI agents fail on tasks that look simple.
Payment software makes the constraint concrete. Stripe's documentation describes a tiered support setup in which tier 1 agents get a custom role with the refund permission removed, so they gather information while tier 2 takes actions that need more authority (custom roles are in private preview). Stripe's two-party approvals, in public preview, let an administrator require a second person to approve a refund, optionally above an amount, and Stripe ships default approval rules for refunds made by AI agent keys.
The permission map at one support desk (Illustrative)
The company is fictional: a 340-person subscription software firm. Its refund policy allows a full refund within 14 days of an annual renewal. Its support system and payment settings enforce this map:
| Action | Tier 1 agent | Tier 2 specialist | Billing lead |
|---|---|---|---|
| View account, invoices and plan history | Allowed | Allowed | Allowed |
| Propose a refund with reason code | Allowed | Allowed | Allowed |
| Apply an account credit up to $100 | Allowed | Allowed | Allowed |
| Issue a refund up to $500 | Blocked | Allowed | Allowed |
| Approve a refund above $500 | Blocked | Blocked | Allowed, and must not be the requester |
A customer renewed an annual plan for $1,150 nine days ago and asks for a refund. The tier 1 agent cannot issue it. The correct path is narrow:
| Step | Actor | Action | Record left |
|---|---|---|---|
| 1 | Tier 1 agent | Confirms renewal date and amount; checks the 14-day window | Ticket note with invoice reference |
| 2 | Tier 1 agent | Proposes a $1,150 refund, reason "within renewal window" | Refund proposal linked to the ticket |
| 3 | System | Routes to billing lead because the amount is above $500 | Approval request with timestamp |
| 4 | Billing lead | Approves | Approval record naming a different user than the requester |
| 5 | System | Issues refund; plan set to cancel | Refund ID and plan status change |
Two wrong paths are also informative. The agent could have offered a $100 credit to make the customer go away, which is inside its permissions but outside the policy. Or a tier 2 specialist could have split the refund into three payments under $500 to avoid the approval. Both leave records too, and a history that includes the corrections is more useful than one with only clean cases. This is also why synthetic data rarely replaces real records: invented tickets seldom contain the workarounds people actually try.
Which records show the constraint
Four kinds of record, each described at metadata level, make a constraint visible in a company's history:
- The rule. The role and permission configuration, or the approval rule with its amount threshold, and when it changed.
- The attempt. The ticket note or proposal where the agent reached the limit, with its reason code.
- The handoff. The approval request, its timestamp and the approver, who must differ from the requester.
- The outcome. The refund ID, credit or denial, and any later correction.
A company that can say which system holds each kind, and since when, has described its constraint without sharing any of it.
Does the company qualify, and what stays unknown?
Companies in the U.S., Canada and the EU qualify, as do companies in the UK, Australia, New Zealand, India, Singapore, South Africa, Latin America, the UAE and Saudi Arabia when at least 70% of the data is in English. The company also needs 50 or more full-time employees at peak (contractors excluded), documented operating history, rights to license the records, and an authorized contact.
Support records are often partly controlled by an outsourced support provider or limited by customer contracts, so the first rights question is who holds the tickets and the payment logs. Before you introduce anyone, confirm the owner is comfortable with the introduction; our guide on documenting client consent for a referral shows how. What remains unknown until SourceX reviews it: how many escalations carry complete role and approval records, how customer data will be handled, and whether any buyer wants this task type. Owners can start with questions to ask before licensing company data and whether a company can license its data to AI companies. More concepts sit in the data types hub, alongside customer support workflows.
Go deeper on action-space constraints
- Does action-space constraints data qualify?: a question page with what an introducer should ask a client.
- Which record gaps make action-space constraints hard to assess: a question page on the missing records that weaken a permission history.
- Action-space constraints review packet: a resource listing what belongs in an evidence packet for SourceX's review.
Next step
Refer a company. No cap on rewards. Default reward on a company's first qualifying transaction: the greater of $50,000 plus 5% and 15% of Actual Supplier Payout, with no cap; further qualifying transactions first agreed within 12 months of the first Closing pay 15%. Eligibility and payment conditions apply, including the USD 100,000 Minimum Transaction, and a signed Schedule A or addendum can differ. A lead, meeting or signature alone does not trigger payment.
If the support lead confirms role permissions enforced in software and logged approvals for escalated refunds, register as a partner, check the company against who qualifies, and read the terms before you introduce the decision-maker.