Context engineering review packet: eight metadata-only documents to assemble, in order, and who prepares each

Short answer

A context engineering review packet is eight short documents, assembled in order: a cover sheet, the task statement, an inventory of required and excluded context, a register of policy versions with effective dates, an authority summary, an outcome and dispute summary, the acceptance check, and rights notes. Every document describes records the company holds; none contains them. The introducer helps only with the cover sheet. The company's operations, finance, IT and legal staff prepare the rest once a review starts.

Visual briefFull-size diagram
Eight labelled sheets slide down into a review folder one after another, from the cover sheet through the task statement, context inventory, version register, authority summary, outcome summary and acceptance check to the rights notes, each tab naming who prepares it.
Illustrative assembly order for a fictional service credit review. Every sheet describes records; none contains them.

This contents list supports the guide to context engineering in a real workflow, and uses the same fictional service credit case: a managed IT provider deciding whether an outage earns a contractual credit under the schedule version in force on the incident date.

The packet in assembly order

Order matters because each document depends on the one before it. The task statement defines what context is needed, the inventory names it, and the version register shows whether it survived.

#DocumentWhat it showsWho prepares itLength
1Cover sheetCompany size, systems, years covered, authorized contactIntroducer with the ownerOne page
2Task statementThe decision being tested, in one or two sentencesService delivery leadA paragraph
3Context inventoryDocuments a correct decision needs, and those it must ignoreService delivery lead with legalOne table
4Version registerEach policy revision with effective dates and where it is storedDocument control or ITOne table
5Authority summaryWho could approve what, and the limits in force by yearFinanceHalf a page
6Outcome and dispute summaryCounts of decisions, credits, disputes and reversals per yearBilling or accounts receivableOne table
7Acceptance checkThe test that proves an answer right, written before outcomes are readService directorA paragraph
8Rights and sensitivity notesCustomer data, contract terms limiting reuse, who must consentLegalHalf a page

What each document must say, and must not

1. Cover sheet. Peak full-time headcount (contractors excluded), the ticketing, billing and document systems in use with their years, the date of any migration, and the name of the person who can authorize a licensing discussion. No customer names.

2. Task statement. For the service credit case: "Decide whether a customer is owed an SLA credit and how much, citing the governing schedule." Keep it to one decision. A packet that tries to cover every ticket type is impossible to check.

3. Context inventory. Two lists. Required: the incident ticket, the credit request, the contract clause naming the governing version, the schedule version in force, the monthly fee and the approver authority table. Excluded: later schedule revisions, other customers' credit decisions and draft schedules never adopted. Anthropic frames good context engineering as finding the smallest set of high-signal information that makes the desired outcome most likely; the excluded list is where a packet shows it understands that.

4. Version register. One row per revision: revision number, effective from, effective to, storage location, and whether the file still exists. Microsoft notes that a SharePoint library saves only up to a set number of versions and deletes the oldest when the limit is reached, so the "still exists" column is not a formality.

5. Authority summary. The approval limits by role and year, for example a service director's goodwill limit. It describes the table; it does not attach approvals.

6. Outcome and dispute summary. Counts only: credit requests per year, approved, declined, disputed, reversed, and which system holds the dispute.

7. Acceptance check. Written before anyone looks at outcomes, so the test cannot be tuned to the answers. For this case: the cited schedule version equals the version in force on the date the contract names; the computed credit matches that version's formula; any goodwill credit is labeled separately and sits within the approver's limit.

8. Rights and sensitivity notes. Whether customer contracts restrict reuse of their records, what personal data appears in tickets, and whether a parent company must approve.

A filled-in task sheet for the service credit case (Illustrative)

Documents 2, 3, 6 and 7 are often combined into one task sheet. Here is the fictional provider's version, with counts the operations lead estimated in conversation.

FieldEntry
TaskDecide SLA credit eligibility and amount, citing the governing schedule
Required contextIncident ticket, credit request, clause 9.2, schedule version in force, monthly fee, authority table
Excluded contextLater schedule revisions, other customers' decisions, unadopted drafts
Allowed actionsApprove contractual credit, decline, refer to service director, approve goodwill within limit
Acceptance checkCited version matches incident date per clause 9.2; credit matches that version's formula; goodwill labeled and within limit
Volume and spanAbout 300 credit requests a year, six years of history, ticketing migration in 2021
Known gapsSchedule edited in place before 2023; disputes held in email

The known-gaps row matters. Our evidence gap analysis for context engineering shows how to word those gaps so the review starts from an accurate picture.

How a reviewer uses the packet

The packet lets a reviewer decide whether past decisions can be turned into tasks with a checkable answer. micro1, a data company, describes on its blog (checked October 18, 2026) a review tool in which a reviewer inspects a model's full attempt, including tool calls and output, against the task's rubric. A packet whose acceptance check is concrete enough to grade that way is far easier to assess than one that says "correct decisions were made".

The reviewer reads the packet in order and stops at the first document that fails. If the version register shows most revisions lost, the acceptance check cannot be applied to those years, and the reviewer narrows the scope rather than rejecting the company. If the rights notes show a parent company controls the records, nothing else matters until that is settled.

What stays out until an agreement is signed

  • Records themselves. No tickets, schedules, contracts or billing extracts. The packet describes them.
  • Customer identities. Counts and categories only.
  • Recreated notes. Writing reasons into old tickets now would corrupt the evidence. Describe the gap instead.
  • Value estimates. Nobody in the packet guesses what the records are worth.

Owners preparing for the discussion can start with questions to ask before licensing company data. Contract-heavy review work is illustrated in the MCP M&A contract review example, and engineering sign-off trails in engineering QA and QC process data. For the first conversation with the owner, use the context engineering discovery questions.

The company still has to meet the basics: 50+ full-time employees at peak (contractors excluded), documented operating history, rights to license the 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. Whether any buyer wants the task, what de-identification is needed and what the company would be offered stay unknown until SourceX reviews the packet. Other record families are listed under data types.

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 owner can fill in the cover sheet and names a service lead who could prepare the rest, register as a partner, confirm who qualifies and read the terms before you make the introduction.

  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 introducer build the packet?

Only the cover sheet, and only from what the owner says in conversation. The company's own staff prepare the rest, and only once a review is under way with SourceX.

Why list context that should be excluded?

Because the task tests whether a system picks the right version, not whether it can read every version. Later revisions and drafts that were never adopted are the wrong answers a reviewer wants to see rejected.

Can a sample ticket go in the packet to show what the records look like?

Not before an agreement. The packet describes records by type, count, span and system. Samples move only under SourceX's agreement with the company.

Sources

  1. micro1.ai/blog/introducing-flow
  2. anthropic.com/engineering/effective-context-engineering-fo…
  3. support.microsoft.com/en-us/sharepoint/lists/documents-and-library…
  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