This scorecard belongs to starting-state fidelity, which rebuilds a glove order at 10:42, after 150 of 200 cartons had shipped. Here the task is deciding whether a particular company is worth introducing for this kind of record.
Scoring rules
Count strong answers out of nine. Write down borderline answers; they become the open items you state when introducing. Three criteria are gates, and a weak answer on any of them means pause.
| Strong answers | Zone | Reading |
|---|---|---|
| 7 to 9 | Strong | Starting states can likely be rebuilt for many change requests; introduce |
| 4 to 6 | Borderline | Some requests can be rebuilt, others only show endings; introduce with gaps named |
| 0 to 3 | Weak | Records show final states only; wait |
Why the timing criteria weigh so much: AI agent training starts every task from a defined state. Gymnasium's reset() puts an environment into its initial state before the first step, and τ-bench grades an agent by comparing a database's final state with an annotated goal. Both need the start pinned down. For a business record, that means knowing what had shipped at the exact moment the request came in, because systems such as Shopify let merchants edit unfulfilled items but not fulfilled ones.
Nine criteria for order-change histories
The general screen is in the company qualification checklist. This version is specific to rebuilding a starting state.
| Criterion | Strong | Borderline | Weak | Who answers |
|---|---|---|---|---|
| Company size (gate) | Well over 50 full-time employees at peak | Near 50 | Under 50 full-time, or mostly contractors | CEO or HR |
| Operating history | Several years on one order and warehouse system | Years split by a replacement | Recently formed | COO |
| Rights (gate) | Company owns order, warehouse and carrier logs | A 3PL holds shipment events under an unreviewed contract | A parent or customer controls the records | CFO or counsel |
| Event timestamps | Picks and shipments logged with a time | Time on shipments only | Date only, from packing slips | Warehouse manager |
| Kept old values | Order line edits logged with before and after values | Edits logged without old values | Current values only | ERP administrator |
| Request capture | Change requests attached to the order with a received time | In a shared inbox, searchable by order number | Phone calls and personal inboxes | Customer service lead |
| Return linkage | Returns reference the original order line | Linkable by customer and date | Not linked | Returns or finance lead |
| Migration continuity | Timestamps and edit history carried through system changes | Partial history migrated | History cut at migration | IT lead |
| Authorized contact (gate) | Named executive over the records | Senior contact, authority unconfirmed | Nobody identified | CEO |
Kept old values depend partly on configuration. Microsoft Learn describes Business Central's change log as recording the user, time, and old and new values, but only for the tables and fields a company chooses to log and activates. "Our ERP has a change log" is a borderline answer until someone confirms it covers order lines.
Outside the U.S., Canada and the EU, English share becomes a gate too. 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.
Strong, borderline and weak: three fictional distributors
| Criterion | 520-person janitorial supplies distributor | 160-person auto parts distributor | 70-person packaging distributor, Mexico |
|---|---|---|---|
| Company size | Strong | Strong | Strong |
| Operating history | Strong | Strong | Borderline |
| Rights | Strong | Borderline | Borderline |
| Event timestamps | Strong | Strong | Weak |
| Kept old values | Strong | Weak | Weak |
| Request capture | Borderline | Borderline | Weak |
| Return linkage | Borderline | Strong | Weak |
| Migration continuity | Strong | Weak | Borderline |
| Authorized contact | Strong | Strong | Strong |
| Strong answers | 7 of 9, strong | 5 of 9, borderline | 2 of 9, weak |
The janitorial supplies distributor logs picks and shipments with times and keeps order-line edit history in its ERP. Change requests live in a shared inbox searchable by order number, which is workable but not ideal.
The auto parts distributor has excellent warehouse timestamps, but its order system shows only current quantities and a 3PL handles one region. Its history was cut when it moved ERPs two years ago.
The packaging distributor works largely in Spanish, so the 70% English rule is unlikely to be met, and its shipments carry dates only.
The five questions behind the scores
These come straight from the order desk and warehouse. Ask the operations lead.
| # | Question | Criterion it moves | A strong answer sounds like |
|---|---|---|---|
| 1 | Which customer requests most often arrive after work has started? | Request capture | A named, frequent case with a rough yearly count |
| 2 | Are picks and shipments logged with a time, not just a date? | Event timestamps | "Yes, from the warehouse system" |
| 3 | When someone edits an order, is the old value kept? | Kept old values | A change log or audit trail on order lines |
| 4 | Where does the change request itself get recorded? | Request capture | Attached to the order with a received time |
| 5 | Who owns the order and warehouse records, and who can authorize a licensing discussion? | Rights and contact gates | A named COO or VP operations, with the CEO signing off |
Clear yes answers to questions 2 and 3 plus a named executive make the company worth introducing. If question 2 gets "date only," same-day tasks cannot be rebuilt and the opportunity is narrower than it sounds. The logistics workflow example pack shows the wider set of logistics records buyers look at.
Limits of the score
The score reflects what the operations lead says. It cannot measure what share of change requests can be matched to a precise moment, how customer names and site addresses would be handled, whether a 3PL contract permits use, or whether a buyer wants this task. SourceX settles those in its review. The starting-state fidelity evidence gaps analysis explains how to word borderline rows, and the starting-state fidelity review packet lists what the company prepares later. For why field-level detail matters to buyers, see metadata and AI training data value; the introducer's wider role is in the business introducer guide, and the category sits under inventory and fulfillment.
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 distributor reaches the strong or borderline zone with all three gates passed, register as a partner, check it against who qualifies and read the terms before introducing the COO or CEO.