Action-space constraints evidence gaps: where refund permission histories break, and how to describe it

Short answer

Four gaps make action-space constraints hard to assess: missing context on the request, missing evidence of who acted and in what role, limits that changed without a dated record, and outcomes stored in another system with no link back. In a refund case they decide whether anyone can confirm that the person who issued a refund was allowed to. None of them rules a company out; each narrows how much of the history can be used, which SourceX measures in its review.

Visual briefFull-size diagram
Five paired horizontal bars compare expected and available evidence in a fictional broadband provider's refund escalations: request context 65%, issuer role 50%, separate approver 70%, threshold version 40% and linked outcome 55%, with each missing segment outlined in orange.
Illustrative gap analysis for a fictional 280-person business broadband provider. Percentages are invented for this page.

This page is part of the guide to action-space constraints at a support desk, where a tier 1 agent may propose a refund but cannot issue one. Its job is a gap analysis: set what a review would expect beside what support desks usually keep, then show how to describe the difference honestly.

What a review of a permission history expects

An action space is the set of moves available in a task; in reinforcement learning libraries such as Gymnasium, every environment declares which actions are valid. A business history is useful when it shows the same thing for people: what each role could do, what they tried, and whether the limit held. For a refund, a reviewer looks for six pieces of evidence.

Expected evidenceWhy the review needs it
Request context on the ticketShows the policy test (for example, the 14-day renewal window) could be applied
Role of the person who issued the refundShows the action was within that role's permissions
Approver distinct from the requesterShows a required second approval actually happened
Limit in force on the dateShows whether an escalation was required at that amount
Linked outcomeShows whether the refund stood, was reversed or became a dispute
Enforcement typeShows whether software blocked the action or staff were trusted

The last row echoes research practice. τ-bench notes that some policy rules are enforced by the software while others depend on the agent applying them, and the two need different evidence. Payment tools can supply the first kind: Stripe documents roles with refund permission removed (custom roles are in private preview) and two-party approvals, in public preview, that hold a refund until a different team member approves it.

The four gaps in a refund history

Each gap below is shown in the main guide's refund case, with what support desks usually keep and what that loses.

GapHow it shows upWhat desks usually keepWhat a reviewer loses
Missing contextTier 1 note says "refund requested" with no invoice or renewal dateThe ticket text and statusProof that the 14-day window was checked
Missing permissionsRefund recorded against a shared login, or with no roleThe account name on the payment recordAny way to verify the role limit held
Unclear versionsApproval threshold moved from $250 to $500 in March with no recordThe current setting onlyWhether pre-March escalations were required
Unproven outcomeRefund issued, then a chargeback filed in a separate dispute toolThe refund IDWhether the fix stood or was reversed

Shared logins and undated threshold changes are the two to ask about first. Both are common at growing support desks, especially on night or weekend shifts, and both decide whether the constraint can be reconstructed at all.

One broadband provider's refund history, measured (Illustrative)

Illustrative and fictional. A 280-person business broadband provider has handled about 5,200 refund and credit escalations since 2020 in one helpdesk, with refunds issued in a separate billing tool. An introducer asks the head of customer operations how often each piece of evidence is present, and records the answers as rough shares.

EvidenceExpectedAvailable (owner's rough share)The gap in one line
Request contextEvery escalation65%Invoice references became a required field in 2022
Issuer roleEvery refund50%The weekend team shared one billing login until 2023
Separate approverEvery refund above the limit70%Approvals logged in billing; a few by email
Threshold versionEvery escalation40%The 2021 limit change was made but never dated
Linked outcomeEvery refund55%Chargebacks live in the payment processor without a ticket ID

Read across, the usable core is clear: escalations from 2023 onward, after the shared login ended and once invoice references were required. Earlier years are thinner but not worthless; they may still show proposals and approvals, just not who issued each refund. The graphic on this page plots the same five shares against what a review would expect.

Wording each gap for the introduction

Rounded-up descriptions create problems at review. Plain ones save time.

Instead ofSay
"Every refund is approved properly.""Refunds above the limit carry a logged approval in most cases; some approvals went by email."
"We know who did everything.""Issuer roles are reliable from 2023; before that the weekend team shared a login."
"Limits have always been the same.""The approval limit changed in 2021; the exact date is not recorded."
"We track outcomes.""Refund IDs are kept; chargebacks sit in the payment processor without a ticket link."

Two habits help. Give years, not adjectives, and say who gave each answer so the review knows whom to ask. Gaps found and explained by the company read better than gaps discovered later. Records of why limits changed, where they exist, are a record type of their own; see architecture decision records and root cause analysis records for neighboring families.

What gaps do not change, and what stays unknown

Gaps do not change ownership or the company test. Support records usually belong to customer operations, with finance owning refunds and IT administering the tools; authority to discuss licensing sits with the CEO. The company needs 50+ full-time employees at peak (contractors excluded), documented operating history, rights to license and an authorized contact. 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.

Unknown until SourceX reviews it: the real share of usable escalations, how customer and payment data will be handled, whether an outsourced provider's contract affects rights, and whether any buyer wants this task type. Interest across the industry is real, as why AI companies pay for data explains, but it does not mean every support archive qualifies. To decide whether the client is worth introducing, use the qualification scorecard; for what the company assembles later, see the review packet contents list.

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 you can state a client's permission-history gaps in the plain terms above and name the records owner, register as a partner, check who qualifies, and read the program terms before you make the introduction.

  1. Step 1Share your linkSend your personal link to a company you know.
  2. Step 2Company appliesThe company applies itself at /apply.
  3. Step 3Company signs and is paidThe company signs, delivers its data and is paid by SourceX under its agreement.
  4. Step 4You get your rewardthe greater of $50,000 plus 5% and 15% of the actual supplier payout, with no cap. A reward becomes payable after SourceX has paid the referred company under its signed agreement and the payout conditions in the program terms are met, including finance approval and your tax and payment details.

Common questions

Why do shared logins matter so much?

Because the constraint is about who was allowed to act. If several people used one account, the record shows that the account issued a refund but not which role did, and the limit cannot be checked for those cases.

Is a threshold change a problem or an opportunity?

Either, depending on whether it was dated. A dated change makes the history richer, because the same request was handled under two rules. An undated change makes escalations before it look unnecessary when they were required.

Should the introducer estimate the percentages in the worked example for a real client?

Rough shares from the owner's own answers are fine and help the review. They are recorded as the owner's estimate, never checked by the partner against tickets or exports.

Sources

  1. docs.stripe.com/account/approvals
  2. docs.stripe.com/get-started/account/teams/custom-roles
  3. arxiv.org/abs/2406.12045
  4. gymnasium.farama.org/api/env
  5. refer.sourcex.si/terms

Free resources

Know a company with valuable proprietary data?

Become a referral partner, get your link and introduce the company’s CEO (in an owner-run company, usually the owner). Referral partners can join from most countries. We can't work with partners in countries or regions under U.S. sanctions or on U.S. restricted-party lists. The companies you introduce should be based in the U.S., Canada and the EU, or in the UK, Australia, New Zealand, India, Singapore, South Africa, Latin America, the UAE and Saudi Arabia with at least 70% of their data in English.

Refer a company →

I own a business

Explore licensing your company's data directly to SourceX for AI training and evaluation. Start a short assessment; no uploads needed.

Start an assessment