Action-space constraints review packet: eight metadata items a support team assembles before review

Short answer

An action-space constraints review packet has eight metadata items, assembled in this order: the task specification, a dated role and permission map, policy text with version dates, a note on how each limit is enforced, the action log field list, the acceptance check, volume and span, and rights and sensitivity notes. Together they tell a reviewer what the task was, what each role could do, and how to test that the limits held, without any customer record leaving the company.

Visual briefFull-size diagram
An open box-file fills as eight labelled sheets drop in from above in order: task spec, permission map, policy versions, enforcement note, log fields, acceptance check, volume and span, and rights notes, grouped as rules, records, test and scope, ending at 8 of 8.
The eight items in the order a support team would assemble them. Each describes records or configuration; none contains customer data.

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 contents list: what a support team would be asked to put together once a licensing discussion starts, who prepares each item and which system it comes from.

Contents list, in assembly order

OrderItemWhat it showsWho prepares itComes from
1Task specificationThe job, in the company's wordsHead of customer operationsSupport playbook
2Role and permission mapWhich role may take which action, with effective datesHelpdesk administratorHelpdesk and billing role settings
3Policy text and versionsThe refund rule and each earlier versionSupport operations with financePolicy library or knowledge base
4Enforcement noteWhich limits software blocks and which rely on trainingHelpdesk administratorAdmin configuration
5Action log field listThe fields recorded when someone proposes, approves or issuesBilling administratorHelpdesk and billing logs
6Acceptance checkThe test a case must passSupport operations, refined with SourceXWritten for the packet
7Volume and spanCounts per year, years of history, migration datesSupport analyticsHelpdesk reporting
8Rights and sensitivity notesWhat limits reuse and what needs redactionCounselCustomer and vendor contracts

The order matters. Items 1 to 4 define the rules; item 5 says where behavior under those rules was recorded; item 6 joins them into a test. Items 7 and 8 size the archive and set its limits. The graphic on this page drops the eight items into a box-file in the same sequence.

What goes into each item

1. Task specification. Two or three sentences. An Illustrative version: "Resolve a refund request on an annual plan according to the refund policy in force. Tier 1 may propose; only roles with refund permission may issue; amounts above the approval limit need a second approver."

2. Role and permission map. A table of roles against restricted actions (refunds, credits, cancellations, price overrides), with the amount limit and the date each setting took effect. This is the core of the packet; a current-only map loses the history a reviewer needs.

3. Policy text and versions. The written rule (for example, a full refund within 14 days of renewal) and every earlier version with dates. Paraphrase is fine; customer-facing wording is helpful where it differs.

4. Enforcement note. For each limit, whether the software blocks the action or staff are trusted to follow it. Research benchmarks draw the same line: τ-bench notes that some policy rules are enforced by the system and others depend on the agent applying them. Payment tools can provide 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.

5. Action log field list. User, role, action type, amount, reason code, approver, timestamps and linked ticket ID. Note which fields exist in which years.

6. Acceptance check. Written out in the next section.

7. Volume and span. Refund requests and escalations per year, years of history, and the date of any helpdesk or billing migration.

8. Rights and sensitivity notes. Customer names and payment details, employee identifiers, and any customer or outsourcing contract terms that limit reuse. Counsel lists categories, not individual tickets.

The acceptance check, written out (Illustrative)

The acceptance check turns a pile of tickets into something gradable. It checks the path, not just the amount. An Illustrative check passes a case only if all four hold:

  1. The refund was issued by a role permitted to issue that amount on that date.
  2. Any refund above $500 carries an approval by a user other than the requester.
  3. The refund falls within the policy window in force on the request date.
  4. No single request was split into several smaller refunds to stay under the limit.

Three short cases show how it reads:

CasePath takenResult
A $1,150 renewal refund on day 9Tier 1 proposes, billing lead approves, system issuesPass
A $1,150 renewal refund on day 9Tier 2 issues three refunds under $500Fail on test 4
A $300 refund on day 20Tier 2 issues it inside its limitFail on test 3, outside the window

The second case ends with the right amount in the customer's account and still fails. That is why the check exists: a refund of the right size issued by the wrong path is exactly the behavior a constrained agent must learn to avoid.

An Illustrative dated permission map entry

Illustrative and fictional. A 340-person subscription software firm writes item 2 like this. Dates replace adjectives.

ActionRole allowedLimitEffective fromPrevious setting
Apply account creditTier 1, tier 2, billing leadUp to $1002022-01-10Tier 2 and above only
Issue refundTier 2, billing leadUp to $5002024-03-01Up to $250
Approve refund above limitBilling lead, not the requesterAbove $5002024-03-01Above $250
Cancel annual planTier 2, billing leadNo amount limit2021-06-01Billing lead only

The previous-setting column is what makes older escalations interpretable. Without it, a 2023 approval for a $400 refund looks unnecessary, when under the old $250 limit it was required. Where a date is not known, write "not recorded" rather than guessing; the evidence gap analysis explains how to describe that.

What the packet leaves open

The packet describes the archive; it does not show that the archive qualifies or is wanted. Data companies build business environments around permission models (Toloka's agent environments page, checked October 18, 2026, describes mockups that replicate real tool schemas, workflows and permission models), which shows interest in the category, not demand for any company's tickets. Nothing here claims that SourceX has already licensed this kind of record.

The company itself must have 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.

Open until SourceX reviews it: how many cases pass the acceptance check on sampling, the rights review result, redaction effort, buyer interest and any offer. Owners weighing the wider question can read whether a company can license its data to AI companies. To judge first whether an introduction is worthwhile, use the qualification scorecard. Related record families include customer support workflows and root cause analysis records.

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 client's support lead could fill in a dated permission map like the one above, register as a partner, check who qualifies, and read the program terms before you introduce the decision-maker.

  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

Who in the company usually leads the packet?

The head of customer operations or support, because most items describe the helpdesk and its roles. Billing or finance supplies the payment-side fields, and counsel writes the rights notes.

Can the permission map be a screenshot of the admin settings?

It is better written as a table of roles, actions and limits with effective dates. A screenshot shows only today's settings and may expose user names; the packet needs the history of the rules, not the current screen.

Does the partner see the finished packet?

No. The packet is prepared by the company for SourceX's review under their agreement. The partner's role ends with a metadata-level introduction.

Sources

  1. docs.stripe.com/get-started/account/teams/custom-roles
  2. docs.stripe.com/account/approvals
  3. toloka.ai/virtual-environments-rl-gyms
  4. arxiv.org/abs/2406.12045
  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