This contents list belongs to the guide on tool-call provenance in a business workflow. That guide shows one traced status change; the packet is how a company proves its systems can produce thousands of them. Partners never assemble it. It is described here so an introducer knows what the company will be asked for later, under SourceX's agreement with the company, and can ask the right metadata questions up front.
Why the order matters
Each document depends on the one before it. A field dictionary means nothing until the reviewer knows which system it describes; a rule catalog cannot be read without knowing which audit field names the rule; an acceptance check cannot be written until the outcome linkage is known. Assembling in sequence also stops early: if the field dictionary shows no actor field on automated changes, the later documents can wait.
The sequence borrows its logic from W3C's provenance model, which separates the thing being changed, the change itself and whoever answers for it. Documents 1 to 5 pin down how the change and the responsible party are logged; document 6 follows the changed record forward to its consequences; documents 7 and 8 settle whether the archive may be licensed and what a correct case looks like.
Packet contents, in order
| Order | Document | What it shows | Who prepares it |
|---|---|---|---|
| 1 | System inventory | Each system involved (help desk, billing, CRM), its vendor, the years in use and any migrations | IT |
| 2 | Audit field dictionary | The fields each audit event carries: actor type, actor name, rule ID, revision, old and new value, timestamp | Support operations with the platform admin |
| 3 | Rule catalog and revision history summary | Each automated rule that changes status, when it was created, how often it was edited, and whether past versions survive | Support operations |
| 4 | Integration and credential map | Which integrations write into the system, through which API user, and whether any login is shared | IT |
| 5 | Retention statement | How many years of audit history exist, what is archived versus deleted, and any scheduled platform change | IT with legal |
| 6 | Outcome linkage note | Which key ties a ticket to its reopen, refund, dispute or next invoice, and where the link breaks | Finance with support operations |
| 7 | Rights and contract summary | Who owns the records, what customer and vendor terms say about reuse, and who can authorize licensing | Legal, signed off by the CEO |
| 8 | Task specification and acceptance check | One routine automated task written as a testable case, with the conditions a correct run must meet | Support operations, drafted with SourceX |
Document 2 is where a packet tends to succeed or stall. On some help desks it is short work: Zendesk's API documentation, for example, says each ticket audit carries a via object, and an individual event carries its own via when it differs from the audit's, as when a trigger makes a status change. A platform admin can describe those fields from the documentation and the configuration screen, without exporting a single ticket.
Document 8 in practice: one testable task
Document 8 turns the archive into something a reviewer can test. It is written before anyone looks at outcomes, so the standard cannot drift to fit the data.
Task specification (Illustrative). A fictional subscription company handles cancellation requests in its help desk. When a customer asks to cancel and the CRM integration has written the contract end date onto the request, the approved automation sets the request to Pending and schedules the plan to stop in the subscription system on that end date. Nobody stops a plan before the end date is confirmed, and nothing stops early.
Records the task depends on:
- The request's complete event history, every change rather than only the latest state.
- The automation's definition as of the version that fired, plus the dates each version was live.
- The CRM write that supplied the end date, with its source system and time.
- The scheduled stop in the subscription system, so the date can be compared independently.
- The follow-up window: reactivations, win-back requests from the same account, and card chargebacks within 60 days.
Acceptance check. A case passes only if all four hold: the named automation, not a person, scheduled the stop; the automation version that fired was the one approved on that date; the CRM end date was on the request before the stop was scheduled; and the account neither filed a chargeback nor complained of an early cutoff.
Four cancellations, scored against the check (Illustrative)
Every timestamp and version number below is invented to show how each document earns its place.
| Case | What the records say | Verdict | Document that settles it |
|---|---|---|---|
| A | CRM wrote end date 09:40; automation v12 scheduled the stop for that date 09:41; no complaint | Pass | 2, 3 and 6 read together |
| B | An agent stopped the plan by hand at 08:15, before the CRM had confirmed any end date | Fail: acted before its input existed | 2 names a person as actor |
| C | Automation fired, but it was v11, which stopped plans the same day; v11 had been retired | Fail: superseded logic ran | 3 gives the version dates |
| D | v12, right order, right date; the account later filed a chargeback for the final month | Fail on follow-up | 6 ties the chargeback to the request |
Case B is the one to remember. The plan would have ended anyway and the customer may never have noticed, so a check that looked only at outcomes would wave it through. Only the sequence of input and action, kept in the event fields, shows the step jumped ahead. Agent-evaluation vendors sell this kind of diagnosis: Appen, for one, advertises expert reference runs and failure analysis, both of which need to know which step broke. Treat that as a sign of market interest, not proof anyone wants a particular archive.
There is a reason documents 2 to 4 carry so much weight. When an AI agent invokes a tool under the Model Context Protocol, the call is valid only with an exactly listed name and schema-conforming arguments. A business automation's identity, version and input field play the same part, so a packet that cannot describe them cannot describe the call either.
What the partner does and does not touch
The partner's job ends at a qualified introduction. Before introducing, the partner can confirm that documents 1, 2 and 7 could be written, by asking the support or IT lead what systems exist, whether automated changes name their rule, and who could authorize licensing. The qualification scorecard turns those answers into a fit score, and the evidence gap analysis shows how to describe what is missing.
The partner never requests or forwards exports, screenshots, sample tickets or rule definitions. Partners sign the Channel Partner Agreement before submitting introductions. The company needs 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.
For the difference between tracing transformations and tracing origin, see data lineage vs data provenance. For how buyers judge what a packet describes, see how AI labs and data users evaluate datasets and why buyers want licensed data. Related record families are under tool-use training data.
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 company's support and IT leads say they could write the first two documents from what they already know, register as a partner, check who qualifies, and read the terms before you introduce the CEO, who would sign off document 7.