What does state repair mean in an ordinary business workflow?
State repair is the work of returning a system to the state it should be in after an error moved it somewhere else. The unit of evidence is three snapshots and the actions between them: intended, broken, restored.
Subscription software makes the idea concrete. A customer's plan decides which features they can use. Stripe's documentation calls these entitlements and sends an event whenever a customer's active entitlements change, so the company can switch features on or off. When someone changes the plan by mistake, features disappear for a paying customer, and someone has to put the account back.
The same pattern appears far outside billing: a purchase order released against the wrong supplier, a warehouse location overwritten during a cycle count, a user's access removed by a bulk script. In each case the repair is not "undo everything". It is restoring the specific fields the error touched, while keeping the legitimate changes made around it.
AI developers are interested in this kind of record because an agent working in business software will eventually make or meet a bad change, and it needs examples of how a careful person restores the right state without causing new damage. Our explainer on why AI agents fail covers the failure side. A record of a real repair also captures details that are hard to invent, which is why synthetic data rarely replaces real data for this work.
The plan change that broke an account (Illustrative)
This case is fictional. A 180-person B2B software company sells a Business plan with six features and per-seat pricing. A customer on the monthly Business plan with 40 seats asks to move to annual billing.
| Moment | State of the account | Action and record |
|---|---|---|
| Intended state | Business plan, 40 seats, six features, annual billing from today | Signed order form in the CRM |
| Day 1, 09:00 | Starter annual price applied by mistake; quantity falls to 1 seat; single sign-on and audit export disappear | Subscription update event and entitlement summary event, each with previous values |
| Day 1, 10:30 | Customer's admin reports that single sign-on has stopped working | Support ticket |
| Day 1, 13:00 | Billing specialist restores the Business annual price with quantity 40 and reviews the proration the wrong change created | Second subscription update; ticket note listing old and new values |
| Day 1, 13:05 | Six features active again | New entitlement summary event |
| Day 2 | Finance compares active features and invoice preview with the order form; both match | Ticket closed with reason "plan change error" and the check recorded |
One detail in the middle row is a documented trap. Stripe's guide to upgrades and downgrades says that updating a subscription's price reverts the quantity to the default of 1 unless the request includes the existing quantity, and that prorations are created by default. A fictional rep who forgot the quantity would produce exactly this broken state. The repair therefore had two parts, price and quantity, plus a decision about the proration that a careless fix might have left on the next invoice.
Which fields turn a repair into usable workflow evidence?
A repair is only legible when each of the three states can be reconstructed from fields the company already keeps. In the illustrative case, those fields sit in three systems.
| Field | Where it lives in the example | What it shows |
|---|---|---|
| Contracted plan, seats and term | Order form in the CRM | The intended state the repair aims for |
| Previous and new values on the subscription | Billing event history | Exactly what the error changed |
| Active features before and after | Entitlement summary events or the company's own entitlements table | The customer-facing effect of the error and the fix |
| Customer report and timestamps | Support ticket | When the error was noticed and by whom |
| Corrective actions with old and new values | Ticket notes and the second subscription update | The repair steps, in order |
| Acceptance check and close reason | Ticket close fields | That someone confirmed the restored state matched the contract |
The link between them matters as much as the fields. A ticket that names the subscription, and a subscription event that can be matched to the ticket by time and account, let a reviewer follow the chain without guessing.
How can a repair go wrong, and what would the record show?
Repairs fail in recognizable ways, and the records reveal them only if the after-state was checked.
- Partial repair. The price is restored but the quantity is not, so features return while billing stays wrong. The invoice preview on day 2 is what catches it.
- Collateral damage. The fix reverses a legitimate change made the same morning, such as two seats the customer added. Only a field-level comparison with the order form shows this.
- Unverified close. The ticket closes when the customer stops complaining, with no recorded check. The record shows actions but not an outcome.
- Undocumented manual work. Someone edits the account directly and writes "fixed" in the ticket. The steps cannot be reconstructed.
None of these make a record worthless, but they change what it can teach. A careful review separates repairs with a recorded acceptance check from those without one.
Does the company qualify, and what stays unknown?
The company needs 50 or more full-time employees at peak (contractors excluded), documented operating history, rights to license its records, 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.
The records are usually owned by the company, held in vendor systems (billing, CRM, support) and governed by the head of finance operations or the COO; the CEO is the person who can authorize a licensing discussion. Unknown until SourceX reviews it: how many repairs pass the acceptance check, how customer data is de-identified, whether the billing or support vendor's terms limit use, and whether any buyer wants this task type. Partners never request exports or screenshots; discovery stays at the level of which systems, how many years and who owns them. The owner can prepare with questions to ask before licensing company data. Related concepts are in the data types hub.
Go deeper on state repair
- Questions an introducer should ask about state repair: a short question set for checking whether a company's repair records could qualify.
- Record gaps that make state repair hard to assess: a guide to the missing links and retention limits that weaken repair evidence.
- State repair review packet: a ready-to-use list of what belongs in an evidence packet for SourceX 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 billing lead confirms that order forms, plan-change events and ticket notes can be tied together for repaired accounts, register as a partner, confirm the company against who qualifies, and read the terms before you introduce the CFO or COO.