Verifiable rewards review packet: the metadata-only contents list, in order, with who prepares each document

Short answer

A verifiable rewards review packet holds eight metadata-only documents, assembled in this order: a cover note naming the authorized contact, a system inventory, a workflow description, a field map, a rule version log, a written acceptance check, a linkage and volume summary, and rights notes. Together they let a reviewer judge whether a workflow's results could be scored by rule, without seeing a single record. The company prepares them; the introducer only shares this list.

Visual briefFull-size diagram
A folder assembling itself as eight labeled documents stack into it in order: cover note, system inventory, workflow description, field map, rule version log, acceptance check, linkage and volume summary, and rights notes.
The packet holds descriptions of records, not records. Order matters: each document builds on the one before.

This contents list is part of the reinforcement learning with verifiable rewards guide. For a workflow that would fill it well, see the worked freight dispute example.

Why the packet is built around the acceptance check

A verifiable reward exists only when a rule can confirm a result is correct; the Tulu 3 paper describes RLVR as rewarding a model only when a verification function says so. DeepSeek-R1 makes the requirement concrete with rule-based accuracy rewards: answers must arrive in a specified format so a rule can verify them, and code is checked by running test cases. A review packet is the business equivalent of that specification. Every document either describes the task and its inputs, the rule, or the evidence of the outcome. Anything else is noise.

The contents list, in order

OrderDocumentWhat it showsWho prepares it
1Cover noteCompany, workflow in scope, authorized contact, dateOwner or COO
2System inventoryWhich systems hold the workflow, since when, and any migrationsIT lead
3Workflow descriptionSteps from request to outcome, in plain language, with rolesProcess owner
4Field mapField names per step and the keys that link steps, no valuesIT lead with process owner
5Rule version logPolicies, limits or agreements that govern the result, with effective datesController, compliance or contracts lead
6Acceptance checkThe written conditions that make a result correct, as yes-or-no testsProcess owner with controller
7Linkage and volume summaryYears covered, items per year as a range, share of items with each link intactIT lead
8Rights notesContracts or terms that may limit reuse, and counsel's initial viewCompany counsel

What each document needs, and what it leaves out

1. Cover note. One page. It names who can authorize a licensing discussion and confirms that no records are attached. Leave out financial expectations.

2. System inventory. A table of systems with start year, version changes and where archives live. Leave out credentials, hostnames and screenshots.

3. Workflow description. Five to ten numbered steps. Leave out names of employees or customers; use roles.

4. Field map. Field names, types and which field links to the next step, for example "credit memo reference on the adjustment line". Leave out any example values; a field map with real values is a record.

5. Rule version log. Each policy or agreement that the check compares against, with the date range it applied and where earlier versions are stored. Leave out the documents themselves unless SourceX later requests them under agreement.

6. Acceptance check. The conditions written as tests. For a bank reconciliation adjustment, for instance: the adjustment amount equals the unreconciled difference on the bank statement; the account matches the reconciliation policy; the approver differs from the preparer; and the item does not reappear on the next reconciliation. A loose check such as "status equals reconciled" is the business version of a gameable grader; tighten it before the packet goes out.

7. Linkage and volume summary. Ranges, not exact counts: "about 2,000 to 3,000 adjustments a year since 2016; supporting statements attached to roughly nine in ten." Leave out row-level samples.

8. Rights notes. Which contracts or regulations might limit reuse, in counsel's words. Leave out legal conclusions from the introducer.

An illustrative packet at a glance

Illustrative and fictional. A 480-person property management group prepares a packet for monthly bank reconciliation adjustments across its operating accounts.

DocumentExample content, metadata only
Cover noteCEO is the authorized contact; workflow is bank reconciliation adjustments, 2016 to present
System inventoryAccounting system since 2016; reconciliation tool added 2019; earlier years in archived database
Field mapAdjustment line carries statement ID and reconciliation period
Rule version logReconciliation policy versions 2016, 2019 and 2023 with effective dates
Acceptance checkFour yes-or-no tests as above
Linkage and volumeAbout 2,000 to 3,000 adjustments a year; approver named on all items since 2019
Rights notesBank statements contain tenant names; counsel flags de-identification

The gaps this packet reveals, such as approver names only from 2019, are exactly what the evidence gaps analysis teaches you to describe plainly. For how contract and reporting workflows are packaged differently, see the M&A contract review example; tool-use training data and why finance data is valuable give background.

Who does what between introduction and review

The partner's job ends at the introduction: confirming the company plausibly meets the baseline and describing the workflow at metadata level. The baseline is 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.

After that, the company prepares the packet and works with SourceX directly. SourceX licenses approved business data directly from companies for AI training and evaluation and manages agreement, rights review, data preparation, delivery and payout. What stays unknown until SourceX reviews it: rights, scope, de-identification, and whether any buyer wants the record type. A complete packet does not guarantee acceptance or any offer.

Sign the Channel Partner Agreement before submitting, and disclose your referral interest to the owner. The reward is paid separately by SourceX; how referral rewards are calculated walks through the arithmetic. 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.

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 an owner reads this list and believes the company could fill it, register as a partner, confirm the company on who qualifies and read the program terms before you introduce them.

  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

Does the partner assemble the packet?

No. The company prepares it, usually after it has been introduced and is talking to SourceX directly. A partner may share this contents list so the owner knows what to expect, but never collects or forwards the documents.

How long does a packet usually take to prepare?

It depends on how well the company documents its systems. SourceX has not published typical preparation times, so do not promise a timeline to the owner.

Can a sample record be included to make the field map concrete?

Not in the packet described here. It is metadata only. If SourceX and the company later agree to review samples, that happens under their own agreement and controls, not through the partner.

Sources

  1. arxiv.org/abs/2501.12948
  2. arxiv.org/abs/2411.15124
  3. refer.sourcex.si/terms
  4. refer.sourcex.si/rewards

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