# Long-horizon task data review packet contents | SourceX

Canonical: https://refer.sourcex.si/resources/long-horizon-task-data-review-packet
Last updated: 2026-11-04

A long-horizon task data review packet is eight metadata-only documents that describe how one type of multi-step case is recorded, so SourceX can judge whether whole cases survive across systems. In order: a cover sheet, the task specification, a step inventory, a join-key map, an outcome check, a break register, a volume and migration sheet, and rights notes. The join-key map and break register carry most of the weight, because long cases fail at the joins, not for lack of volume.

This packet is part of the guide to [long-horizon task data in an ordinary workflow](/guides/concept-long-horizon-task-data), which explains the idea through a parts order. To show that the packet works for any case type, this page fills it in for a different one: supplier warranty recovery on failed equipment, at a fictional cold-storage operator. The company's own team assembles a packet like this. Partners never assemble or handle packets; SourceX reviews records under its own agreement with the company.

## Packet contents, from cover sheet to rights notes

| # | Document | What it shows | Who prepares it |
|---|---|---|---|
| 1 | Cover sheet | Headcount, systems, years of history, named owner and contact | Owner or CFO, with the introducer helping only on these metadata fields |
| 2 | Task specification | The end-to-end job a case represents, in plain words | Engineering or asset manager |
| 3 | Step inventory | Every step in the case type, and the system or inbox that holds it | Asset manager with the warranty administrator and accounts payable |
| 4 | Join-key map | The reference that links each step to the one before, and whether it is stored or typed | Systems administrator for the maintenance platform and ERP |
| 5 | Outcome check | The test a closed case must pass, which only the full chain can satisfy | Controller, reviewed by SourceX |
| 6 | Break register | Known places where chains split into separate records | Asset manager and systems administrator |
| 7 | Volume and migration sheet | Cases per year, years retained per system, cutover dates | Finance systems lead |
| 8 | Rights and sensitivity notes | Supplier terms, personal data, contract limits | Counsel or CFO |

Taken in order, the eight answer seven questions a reviewer brings: what the job is, where each part sits, what ties the parts together, how a correct ending looks, where ties fail, how much history exists, and whether it may be licensed.

## The worked case behind this packet (Illustrative)

A fictional 600-person cold-storage operator loses a refrigeration compressor on a loading dock 14 months after installation. The unit carries an 18-month, parts-only supplier warranty. Every figure is invented.

| Day | Event | Where it is recorded |
|---|---|---|
| 0 | Technician logs the failure against the asset ID | Maintenance platform work order |
| 1 | Replacement compressor ordered, $9,400 | ERP purchase order |
| 2 | Warranty eligibility checked: install date and serial number | Asset register |
| 4 to 6 | Replacement received, invoiced and matched | ERP receipt, invoice, match |
| 5 | Claim filed for $12,000: $9,400 parts and $2,600 labor | Supplier warranty portal |
| 9 | Supplier issues a return authorization with a 30-day deadline | Portal message, email |
| 20 | Failed unit shipped back | Carrier tracking, shipping log |
| 47 | Teardown verdict: defect confirmed, parts covered, labor excluded | Supplier email with attached report |
| 58 | Credit memo for $9,400 posted against the supplier account | ERP accounts payable |

The packet never contains this table's records. It describes how cases like this one are stored across the operator's history.

## Documents 2 and 3: the task and the step inventory

**Document 2, task specification.** A single testable instruction, for example: "Recover the supplier's share of a failed in-warranty asset. Confirm coverage from the asset register, file within the warranty window, return the failed part before the authorization expires, and book whatever the supplier declines." Each clause depends on a step days or weeks away, which is what makes the task long-horizon.

**Document 3, step inventory.** Each step, with where it lives: the failure in the maintenance platform; install dates and serials in the asset register; the replacement purchase in the ERP; the claim, return authorization and teardown verdict in the supplier's portal or in email; shipping in a carrier account or a dock log; the credit memo in accounts payable. Mark every step that lives outside a company system, such as a supplier portal account tied to one engineer's login, because those disappear first when people leave.

## Document 4: the join-key map

Expect the first draft of this map to have gaps. Against each step it records the identifier that ties the step to the case, and whether software stores it or a person keys it in.

| Step | Key it carries | Stored in a field or typed |
|---|---|---|
| Work order | Asset ID | Field |
| Eligibility check | Asset ID, serial number | Field in the register |
| Replacement PO and receipt | Work order number | Field |
| Invoice and match | PO number | Field |
| Warranty claim | Serial number; work order number | Field in the portal; typed in a note |
| Return authorization | Claim number | Typed in email |
| Shipment of the failed unit | Return authorization number | Typed on the label |
| Teardown verdict | Claim number | In an attached report |
| Credit memo | Claim number | Often typed, sometimes missing |

The replacement purchase is the strong segment. Microsoft's documentation describes three-way matching as comparing invoiced quantity with the product receipt quantity and treating a difference as a matching error, so the software itself polices that join. The fragile segment is everything the supplier controls: claim, authorization, verdict and credit, where a missing claim number on the credit memo leaves $9,400 that nobody can tie back to the failed compressor.

## Document 5: an outcome check only the whole chain can pass

Write the check before anyone counts cases, and phrase it so a reviewer has to walk every join. For the Illustrative compressor:

1. The credit memo equals the parts value the supplier approved, $9,400, and cites the claim number.
2. The declined $2,600 of labor is booked as maintenance expense, not left sitting as a receivable.
3. The failed unit shipped on day 20, inside the 30-day window that opened on day 9.
4. The claim was filed inside the 18-month warranty measured from the install date in the asset register, not from the invoice date.

Booking the whole $12,000 as recoverable on day 5 fails, even if the books are tidied after day 58, because it ignored the verdict that only arrived on day 47. A check like this cannot be passed from any single record. That is also why evaluation tools judge whole attempts: micro1 says its flow product lets reviewers inspect an agent's steps, tool calls and outputs and score the attempt as a whole or criterion by criterion, which only works when the record holds the full case.

## Documents 6 to 8: breaks, volume and rights

**Document 6, break register.** Where chains tend to split, and in which years. Typical entries for warranty recovery: claims filed from a personal portal login with no copy in company systems; return labels printed without the authorization number; teardown reports kept only as email attachments; credits netted against the next invoice with no claim reference. Every break turns one two-month case into scattered fragments. Listing them builds credibility.

**Document 7, volume and migration sheet.** Approximate warranty claims per year, years retained in each place (maintenance platform, asset register, ERP, supplier portal, email), and every cutover. Supplier portals and mailboxes may keep far less history than the ledger, which narrows the window in which whole cases still exist.

**Document 8, rights and sensitivity notes.** Warranty and supply agreements can restrict how supplier documents, prices and failure reports are reused; work orders name technicians. Counsel or the CFO records these as open questions. The company itself must qualify: 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 effort goes into joins because a long case is only useful when it can be checked end to end. METR measures agent capability by the length of task, in human expert time, that agents finish half the time, and reports that length doubling roughly every seven months; as evaluated tasks get longer, so do the cases needed to test them. Background reading: [long-horizon tasks and project records](/guides/long-horizon-tasks-ai-agents), [agentic AI in the enterprise](/guides/agentic-ai-enterprise-2026) and [agent trajectory data](/questions/agent-trajectory-data). The packet leaves open how many cases pass the check, what supplier agreements permit, what de-identification is needed, and whether any buyer wants this case type. Before starting a packet, test fit with the [long-horizon task data scorecard](/questions/does-long-horizon-task-data-data-qualify). Advisors covering several companies can add it to a [portfolio introduction plan](/guides/a-practical-introduction-plan-for-advisors-supporting-a-portfolio-review); related records are covered in [procurement and vendor workflows](/data-types/procurement-and-vendor-workflows).

## 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 a client's systems administrator could draft the join-key map above with most keys stored in fields, [register as a partner](/register), check [who qualifies](/who-qualifies), and read the [terms](/terms) before introducing the CEO or owner.

## Sources

- https://www.micro1.ai/blog/introducing-flow
- https://learn.microsoft.com/en-us/dynamics365/finance/accounts-payable/three-way-matching-policies
- https://arxiv.org/abs/2503.14499
- https://refer.sourcex.si/terms
