Context engineering starts with the documents behind a business decision

Short answer

Context engineering is the work of choosing what an AI agent sees at each step: instructions, tool results, retrieved documents and prior history. For a business decision, the right context is the policy version in force that day, the evidence the person actually consulted and similar past decisions. Companies whose records link each decision to that policy and evidence hold a ready-made answer key for what good context looks like.

Visual briefFull-size diagram
A credit limit decision sits at the center, linked to policy v4.2 in force on the decision date, three evidence documents and the CFO approval; a newer policy v5.0 sits outside the bundle, marked as the wrong version.
Illustrative credit decision. The right context is the policy in force on the day, not today's policy.

How does context engineering use the documents behind a business decision?

It uses them to define which inputs a correct decision depended on, so an agent can be given those inputs and judged against the outcome. Anthropic describes context engineering as managing the whole context state an agent works with across many steps, and notes that a model's precision on retrieval and long-range reasoning can degrade as that context grows. More is not better. The task is selecting the few documents that matter.

Business decisions show why selection is hard. A credit approval, a refund exception or a change request was decided under a specific rule, using specific evidence, by someone with specific authority. Months later the rule has changed, the evidence sits in three systems and the approver has moved on. An agent handed today's policy and a pile of files will often make a confident, wrong decision.

A decision record that names its policy version and evidence answers three questions an agent builder needs: what should have been retrieved, what should have been ignored, and what the correct outcome was given those inputs.

A field map: one decision and its context bundle

Illustrative. A fictional 300-person industrial distributor raises a customer's credit limit. All details are invented.

FieldValue in the recordSystemRole in context
DecisionCredit limit raised from $60,000 to $120,000ERP customer masterThe outcome to predict or check
Decision date14 MarchERP change logSelects which policy applied
Policy in forceCredit policy v4.2, effective 1 FebruaryDocument managementThe rule the decision followed
Threshold that appliedLimits above $110,000 need CFO approval (v4.2, section 3)Policy textExplains the approval route
Evidence 124 months of payment history, average 31 days to payAR aging reportFact the policy tests
Evidence 2Two trade referencesCredit application fileFact the policy tests
Evidence 3Latest year-end financial statementsCredit application fileFact the policy tests
ApprovalCFO, 14 March, note: "strong payment record, reviewed statements"Approval workflowAuthority and reasoning
Later outcomeNo balance past 60 days in the following yearAR aging reportShows the decision held

Now the trap. The company issued credit policy v5.0 in August, lowering the CFO threshold to $75,000 and adding a credit insurance check. An agent given v5.0 to judge the March decision would flag a missing insurance check that was never required. The record is only useful because the decision date and the policy version are both kept, and the old version was not overwritten.

Context choiceWhat the agent concludesCorrect?
v4.2 plus the three evidence documentsApproval route and decision consistent with policyYes
v5.0 plus the same evidenceDecision missing a required insurance checkNo: wrong version
v4.2 with no evidenceCannot test whether the policy criteria were metIncomplete
Every credit file for the customer since 2015Slower, and older notes may misleadToo much context

Why do decision records matter to AI developers?

They turn "use the right documents" into something that can be checked. Evaluation vendors describe review loops in which a person compares a model's whole attempt, including the steps and tool calls, against a rubric; micro1, for example, describes its flow platform that way and says it builds realistic multi-step task environments. In a business setting, the decision record with its linked policy and evidence is close to that rubric already written: it says which inputs were relevant and what the outcome was.

The same structure appears across functions. The credit limit approval page covers the example above in more depth. Decision records and operational decision logs cover the general pattern, and standard operating procedures are the policy layer when they are versioned and dated. For a plain-language overview to share with a client, use the client explainer on licensing operational data.

Company qualification questions

Discovery stays at metadata level. You are checking whether the links exist and who owns them, never the content.

AskStrong answerWhy it matters
Are policies versioned with effective dates, and are old versions kept?Yes, in a document system with historyLets the right version be matched to each decision
Does each approval record the policy or threshold it relied on?Often, through a workflow field or noteThe link between rule and decision
Is supporting evidence attached to the decision record?Attached or linked by IDLets the evidence set be rebuilt
How many years of decisions exist, and in which systems?Five or more years, named toolsDepth
Who can authorize a licensing discussion?The CEO, usually the owner in an owner-run companyThe sponsor to introduce

The introduced company needs 50+ full-time employees at peak (contractors excluded), a 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.

What stays unknown until SourceX reviews it: SourceX's current data needs for this record type, whether customer or employee data in the files can be redacted adequately, the rights review result, and any offer.

Limits and unanswered questions

This page does not claim that any AI developer has licensed decision records for context engineering, or publish figures on their value; SourceX has not released such data. The sources cited describe context engineering and evaluation practice in general terms.

Use type also matters. A company may be comfortable licensing records for model training or evaluation but not for live retrieval inside a deployed product, or the reverse; the training vs retrieval license comparison explains the difference. Policies themselves can carry third-party content, such as an insurer's underwriting guide, that the company cannot license.

Company compensation and referral rewards are separate. The company is paid under its own agreement with SourceX. The partner's reward is calculated on what SourceX actually pays the company, is funded separately and never reduces that payment. Illustrative only: a $400,000 payout would mean a $70,000 reward. See how rewards work.

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 keeps dated policy versions and links its approvals to them, register as a partner, check the company against who qualifies and read the program terms before you introduce its decision-maker. More agent data topics are in the guides hub.

  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

Is context engineering the same as retrieval-augmented generation?

Retrieval is one part of it. Context engineering covers everything placed in front of the model for a step: instructions, tool results, retrieved documents and earlier messages. Decision records help with the whole selection, not only the search.

Would a company license its policies, or its decisions?

Usually the linked set: decisions with the policy version and evidence each one relied on. Policies alone are generic. Whether the license covers training, evaluation or retrieval use is set in the agreement; see the training vs retrieval license comparison.

What if the company never versioned its policies?

It is weaker but not hopeless. Dated policy files in a document system, change logs or board minutes can sometimes reconstruct which version applied. SourceX reviews that during its assessment; the partner does not need to.

Sources

  1. anthropic.com/engineering/effective-context-engineering-fo…
  2. micro1.ai/blog/introducing-flow
  3. 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