Context engineering evidence gaps: a gap analysis of what a review expects and what decision archives hold

Short answer

Six items decide whether a context engineering decision can be checked: a linked trigger, the dated policy version, the clause or rule cited, the approver and their limit, the fee or amount at the time, and the final outcome including disputes. Most companies keep the first and fifth well. The dated policy version, the cited rule and the linked dispute are the usual gaps, and each one turns a checkable decision into an anecdote. Name them plainly when you introduce the company.

Visual briefFull-size diagram
Six horizontal bars compare expected and available evidence per 10 fictional service credit decisions; incident links and fee records are nearly complete, while dated policy versions, cited clauses and linked disputes show large outlined missing segments.
Illustrative estimate for a fictional managed IT provider. The outlined segments are the gaps to name in an introduction.

This gap analysis belongs to the guide on context engineering in a real workflow, which walks through one service credit and the three dates on its ticket. Here the job is different: comparing what a review would expect against what a typical decision archive holds, and turning the difference into honest sentences for an introduction.

The six items a context review looks for

A context review asks one question of each past decision: could someone rebuild exactly what the decider saw, and nothing more? Anthropic describes context engineering as curating the best set of information during a model's work, covering instructions, tools, external data and history. A training or evaluation task built from a company decision needs the historical version of that set, so the reviewer looks for these items in the record.

#Expected evidenceWhy the review needs it
1Trigger linked to the decision (incident, request, order)Fixes the facts and the date the rule keys on
2Policy or schedule version with its effective datesShows which rule was in force, not which one is current
3The clause or rule the decider citedSeparates the governing document from the merely relevant ones
4Approver identity and authority limitShows whether a discretionary step was allowed
5Amount or fee in force at the timeLets a reviewer recompute the result
6Final outcome, including any dispute or reversalConfirms the decision stood, or shows it did not

A reviewer using a tool such as micro1's flow, which micro1's blog (checked October 18, 2026) says compares a model run's steps, tool calls and output with a task rubric, needs items 2, 3 and 6 to write that rubric at all. Without them there is no answer key.

Expected, typically held, usually missing

Most archives were built to run the business, not to explain decisions later. The table sets the expectation against what operations leads commonly describe, and the shape of the gap.

Evidence itemWhat companies typically holdWhat is usually missingShape of the gap
Linked triggerIncident and request in one ticketing tool, related by a linkLinks for requests that arrived by emailOlder years, email-only channels
Dated policy versionThe current schedule, perhaps a few prior versionsThe revision a past decision depended onPolicies edited in place, or version limits reached
Cited clauseAn outcome status: approved, declinedA note naming the document or clause relied onFree-text notes, or none
Approver and limitWho closed the ticketAn approval field and the limit table in force thenGoodwill gestures with no approver
Amount at the timeBilling history with monthly feesRarely missingSmall
Outcome and disputesThe credit note or declined statusDisputes and reversals linked back to the decisionDisputes handled in email or a separate system

The version gap is the one introducers most often miss. Microsoft's documentation explains that SharePoint libraries keep a version history from which earlier versions can be viewed and restored, but also that a library saves only up to a set number of versions and deletes the oldest when the limit is reached. A busy policy library edited dozens of times may have lost the revision a two-year-old decision used. Ask whether policies are published as separate dated documents or edited in place, and whether anyone changed the version limit.

The service credit archive, gap by gap (Illustrative)

A fictional 260-person managed IT provider grants or declines service credits after outages. Its service delivery lead was asked, for every 10 credit decisions in a recent year, roughly how many carry each item. Nobody opened a ticket; these are the lead's estimates.

Evidence itemExpected per 10 decisionsAvailable per 10Missing per 10Cause the lead gave
Linked trigger1091Some requests still arrive by email
Dated policy version1046Schedule edited in place until a policy library was set up
Cited clause1037Directors write "declined" without a reason
Approver and limit1064Goodwill credits skip the approval field
Amount at the time10100Billing history is complete
Outcome and disputes1037Disputes live in the account manager's email

Read across the rows and the picture is specific. Nearly every decision can be placed in time and priced. Fewer than half can be tied to the rule version that governed them, and only about three in ten record why the director decided as they did. That does not make the archive worthless; it means the reconstructable share is smaller than the ticket count suggests, and that the years after the policy library was set up are likely stronger than the years before.

How to describe each gap in an introduction

An honest introduction names the gap, its scope and its cause. It does not guess at value. These sentences work as templates.

  • Dated policy version. "Policies were edited in place until 2023; versions with effective dates exist only from then."
  • Cited clause. "Decision notes name the governing clause in some cases, mostly for declined requests; approvals often carry no reason."
  • Approver and limit. "Contractual credits record the approver; goodwill credits do not, and the authority table for earlier years was not kept."
  • Outcome and disputes. "Disputes are handled by account managers in email and are not linked to the original ticket."

Each sentence tells SourceX where to look and what to expect, which is more useful than a confident claim that "all the history is there". For the related check on access and sign-off before a call, see how to identify missing permissions before a discovery call.

Gaps that narrow a review, and gaps that stop it

Most context gaps narrow the usable share of decisions. A few stop the conversation until they are resolved, and none of them are about the records' content.

GapEffectWhat the introducer does
Missing versions, missing notes, unlinked disputesNarrows the reconstructable shareDescribe scope and years
Approver not recorded for one decision typeNarrows that decision typeName the type
Company under 50 full-time employees at peak (contractors excluded)Stops the introductionDo not introduce
Customer contracts or a parent company control the recordsStops until rights are clearAsk who can authorize a licensing discussion
No authorized contactStops until one is namedFind the CEO, or the owner in an owner-run company

The company also needs documented operating history and rights to license the records. 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: the exact reconstructable share, whether any buyer wants this decision type, the de-identification needed for customer names and fees, and any offer. When the company prepares for that review, the context engineering review packet lists what to assemble, and the discovery questions for context engineering cover the first call. Engineering teams with similar decision trails are covered in assessing issue histories and review decisions, and finance-side context in the MCP CFO dashboard example. Other record families sit 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 you can describe a client's context gaps in a few honest sentences and the gates above are clear, register as a partner, check who qualifies and read the terms before you introduce the decision-maker.

  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 one missing item rule a company out?

No. A gap lowers the share of past decisions that can be rebuilt with the context that was actually used. Only SourceX's review can measure that share, so describe the gap and let the review size it.

Should the company fix its gaps before I introduce it?

No. Gaps in historical records usually cannot be fixed after the fact, and recreating notes would damage the evidence. What helps is an accurate description of which years and systems are affected.

Can I check the gaps myself by looking at a few tickets?

No. Ask the operations or service lead whether each item exists and roughly how often. Partners stay at metadata level and never open client records.

Sources

  1. anthropic.com/engineering/effective-context-engineering-fo…
  2. support.microsoft.com/en-us/sharepoint/lists/documents-and-library…
  3. support.microsoft.com/en-us/office/view-the-version-history-of-an-…
  4. micro1.ai/blog/introducing-flow
  5. 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