Negative demonstrations review packet: eight metadata documents for a duplicate-order failure class, in order

Short answer

A negative demonstrations review packet is eight short documents, prepared by the company in this order: a failure class summary, the task statement, a description of the failing action, the rule that makes it wrong, the fix history, an acceptance check written in advance, volume and span counts, and rights notes. Each describes records the company holds; none contains a transaction. The packet lets SourceX judge one class of failures before any agreement.

Visual briefFull-size diagram
Eight labelled documents drop one after another from a row above into an open review folder: failure class summary, task statement, failing action, rule and reason, fix history, acceptance check, volume and span, and rights notes; the folder closes with the label metadata only.
Illustrative packet for a fictional distributor's duplicate purchase orders. Each document describes records; none contains them.

The packet belongs to the guide to negative demonstrations in an ordinary workflow, which follows an integration that sent a supplier two purchase orders for one $18,400 requisition. Partners do not assemble or hold it. It is set out here so an introducer can tell an owner, honestly, what preparing for a review involves.

The eight documents, in order

The sequence runs from what kind of failure this is, through how it happens and why it is wrong, to how a case is judged and who may license the records.

#DocumentWhat it showsWho drafts it
1Failure class summaryThe kind of failure, systems involved, years coveredFinance operations manager
2Task statementThe job the process was meant to do, in one sentenceProcurement manager
3Failing actionThe exact step that goes wrong and the conditions it happens underIntegration owner
4Rule and reasonThe published rule or internal policy that makes the step wrongIntegration owner with IT
5Fix historyThe safer alternative, when it was introduced, and any later changesIT or integration vendor contact
6Acceptance checkThe fixed test each case must pass or failProcurement and finance together
7Volume and spanCounts per month, retention periods, migration datesERP administrator
8Rights and sensitivity notesContract limits and personal data presentLegal counsel or the CFO

What each document says, using the duplicate order

1. Failure class summary. Illustrative: "Duplicate purchase orders created when the procurement-to-ERP integration resent an order after a lost response; ERP and procurement tool; 2021 to present."

2. Task statement. Send one approved purchase order to the ERP and supplier exactly once, even when a response is lost.

3. Failing action. Sending the create request a second time after a lost response, without checking for an existing order or reusing a stable reference.

4. Rule and reason. Outside guidance does the work here. The HTTP standard (RFC 9110) says a request that is not idempotent should not be repeated automatically unless the client knows it is safe, and Stripe's API documentation says a server error leaves the outcome unknown, so the object should be checked first. The document names whichever rule the company's own tickets relied on, so a reviewer can label each case against it.

5. Fix history. The safer alternative: look up by external reference, or reuse the same request key, before sending again. NetSuite, for example, recommends external IDs with its upsert operation to prevent duplicate records. The document gives the date the change went live, because cases before and after it behave differently.

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

7. Volume and span. Canceled duplicates per month, months of retained integration logs, the date of the integration change, and any ERP migration dates. Estimates are fine if they are labeled as estimates.

8. Rights and sensitivity notes. Supplier names and prices, employee identifiers in tickets, and any limits in supplier or integration vendor contracts. These are questions for review, not legal conclusions.

The acceptance check, tested on two days (Illustrative)

Conditions 1 to 3 decide whether a case ended correctly. Condition 4 decides whether a case that failed them is usable as a labeled failure:

  1. Exactly one open purchase order exists per approved requisition line.
  2. Total committed equals the approved amount.
  3. The supplier received one order message.
  4. Any duplicate carries a cancellation reason and a linked ticket.

Applied to the fictional distributor's records on the day of the failure and on the day of the fix:

ConditionDay 1, before the changeDay 10, after the change
One open order per requisition lineFail: PO-55120 and PO-55121 both openPass: one open order
Committed equals approvedFail: $36,800 against $18,400 approvedPass: $18,400
One order message to supplierFail: two messages sentPass: one message
Duplicate has reason and ticketPass: cancellation reason and buyer's ticketNot applicable: no duplicate
ResultFails 1 to 3, passes 4: usable as a negative demonstrationPasses 1 to 3: usable as the paired correct example

The day 1 case is the valuable one, but only because condition 4 passes: the failure is explained. A duplicate with no reason or ticket would fail condition 4 too and teach nothing, since nobody could say which step was wrong. The check is what lets a buyer test each case instead of trusting the story around it. Real cases like this carry timing and system detail that is hard to invent, which is part of why synthetic data rarely replaces real data.

Preparing the packet without moving a single record

Every document above can be written from what staff already know or can count inside their own systems. The ERP administrator counts canceled duplicates; nobody exports them. The integration owner describes the retry logic; nobody forwards a log file. The procurement manager writes the task statement from the policy they already follow.

The same line holds for partners. Discovery stays at metadata level: what the records are, roughly how many, how far back, which systems, who owns them. If an owner offers to send a sample order or a screenshot of the ticket, decline and point them to SourceX's process. The procurement and vendor workflows page lists the surrounding record types an owner might mention.

What the packet leaves for review

Procurement, finance operations and IT usually share ownership of these records, and the CEO authorizes a licensing discussion. The company needs 50 or more 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.

The packet cannot settle how many cases pass the check, what de-identification supplier and employee details need, whether vendor contracts allow use, or whether any buyer wants this failure type. Owners often ask first whether a company can license its data to AI companies, and the reason buyers care about failures at all is set out in why AI agents fail. Before a packet is worth discussing, rate the company with the negative demonstrations qualification scorecard and describe weak spots with negative demonstrations evidence gaps.

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 procurement or integration owner believes the company could draft documents 3 to 7 for several years of reversals, register as a partner, confirm the basics on who qualifies, and read the terms before you introduce the CEO.

  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 put this packet together?

No. The company prepares it after a conversation with SourceX has begun, from what its own staff know and can count. It is described here so you know what the company's records must support later.

Why write the acceptance check before anyone looks at cases?

A check written after looking tends to fit whatever the records happen to show. Fixing it first means each case either passes or fails on stated terms, which is what lets a buyer trust the label instead of the narrative.

Can the packet cover more than one kind of failure?

It should cover one failure class at a time, such as duplicate orders after a timed-out create. A second class, such as reversed payments, gets its own packet with its own task statement and check.

Sources

  1. rfc-editor.org/rfc/rfc9110.html
  2. docs.stripe.com/api/idempotent_requests
  3. docs.oracle.com/en/cloud/saas/netsuite/ns-online-help/sectio…
  4. 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