# Changing data mandate network signals: a cadence | SourceX

Canonical: https://refer.sourcex.si/guides/a-platform-team-s-early-warning-system-for-changing-data-needs
Last updated: 2026-11-05

Data needs change in layers, and an early-warning system should weigh each layer by its distance from a SourceX decision. SourceX's own program pages, the terms version and the who-qualifies criteria, are authoritative and cheap to check weekly. Your introductions' outcomes are direct but sparse, so review them monthly. AI research and regulation move first but say nothing about any program, so read them quarterly as hypotheses. Change founder outreach only on the first two layers, and never infer who is buying from news.

This is for a VC platform strategist who wants to notice when the companies worth introducing are shifting, before founders hear stale criteria from the fund. Everything said here about the program reflects SourceX's terms (Version 2026-10-22.2, since replaced by version 2026-11-04) and who-qualifies page as they stood on 26 October 2026. The cadence, its triggers and the illustrative signals are this page's method.

## Four distances between a signal and a SourceX decision

A signal is useful in proportion to how close it sits to the decision it is meant to anticipate. The closest is SourceX's own published text. Its screening page says each program is judged on its own criteria rather than against one universal minimum, and that a company outside one program's criteria may suit a different program later; the page carries its own update date, 26 October 2026 when this was written. The terms keep a running record: section 11 lists each change since version 2026-10-12, version 2026-10-22.2 redefined Actual Supplier Payout, and the current version, 2026-11-04, set today's reward structure; the October change also redefined Actual Supplier Payout in the words of the agreement's Schedule A.

One step out are the outcomes of your own introductions: duplicates, declines and the reason where one is given, and what introduced CEOs tell you. Two steps out is AI research and developer documentation. Anthropic's engineering post on agent evaluation, dated 26 November 2025 on its index, treats a task as one test with specified inputs and success criteria, and advises running several trials because model outputs vary. Three steps out is regulation. The EU AI Act's Article 10(3) says "Training, validation and testing data sets shall be relevant, sufficiently representative, and to the best extent possible, free of errors and complete in view of the intended purpose", and EUR-Lex's consolidated text dated 27 July 2026 carries an amended Article 10.

Every signal then has to be translated into a company question a relationship owner could put to a CEO, such as "does the company keep a record of whether each job's outcome was checked, or only of the conversation about it?" A signal that cannot become such a question is commentary. Funding rounds, press about AI companies' data deals and conference claims sit outside the layers altogether: they establish no supplier eligibility and imply no buyer relationship.

| Distance | Layer | Example | What it can tell you | What it cannot |
|---|---|---|---|---|
| 0 | SourceX's program text | Terms version history; the who-qualifies criteria and update date | What the program says today | Why it changed, or what comes next |
| 1 | Outcomes of your introductions | A duplicate decision; two declines for the same reason | How the criteria are being applied to your companies | Anything about companies you did not introduce |
| 2 | AI research and developer documentation | Anthropic's guidance on evaluation tasks and trials | What some developers say they measure | Whether any program wants a given company's records |
| 3 | Regulation | EU AI Act Article 10 data-quality criteria for high-risk AI systems | Obligations some AI providers face | Demand, price or any program's criteria |
| Outside | Noise | Funding rounds, deal rumors, conference claims | Nothing about mandates | Anything you should act on |

## The mandate signal review cadence

Each layer gets a cadence matched to how often it changes and how much it can be trusted. Anthropic's advice to run several trials because outputs vary applies here by analogy: one decline is one trial. That is why the monthly trigger needs a reason to appear twice before anyone changes a sentence in outreach, and why a quarterly reading produces hypotheses rather than instructions.

When a program change does land, re-screen only the rows it touches, using the [criteria change impact register](/guides/how-to-revisit-a-network-map-when-buyer-criteria-change), and recall old wording with the [versioned criteria distribution process](/guides/the-risk-of-using-old-mandate-criteria-in-founder-outreach). The cadence below decides when you look; those two pages decide what you do once you have seen something.

| Cadence | Time box | What you check | Trigger | What you do | Owner |
|---|---|---|---|---|---|
| Weekly | 10 minutes | The terms version string and the who-qualifies update date, against saved copies | Either one changed | Read the changed section within two business days; hold outgoing criteria sentences until they match | Platform analyst |
| Monthly | 45 minutes | Your introductions' outcomes: duplicates, declines with any reason given, CEO feedback | The same unexpected reason twice in a month, or a reason the published criteria do not explain | Ask SourceX through the partner channel before changing outreach; tag the affected rows | Platform lead |
| Quarterly | 90 minutes | Three to five primary research or regulatory documents | None automatic | Write each as one hypothesis and one CEO question; add them to a pilot backlog, never to outreach | Platform strategist |
| On a program change | Within 10 business days | Rows on your map that the change touches | Any change to criteria text | Re-screen only those rows; leave the rest alone | Platform analyst |
| Yearly | 2 hours | Which signal sources preceded real changes | A source that preceded nothing all year | Demote or drop it | Platform strategist |

## One quarter of signals, sorted

Four rows below are Illustrative and marked so; the other four are real, dated documents cited on this page. The sorting shows the habit the cadence builds: most signals end in a log entry, a few in a question, and only the closest ones change what the fund tells founders.

| Date | Signal | Distance | Decision |
|---|---|---|---|
| 22 Oct 2026 | Terms version 2026-10-22.2, since replaced by version 2026-11-04 redefines Actual Supplier Payout | 0 | Re-read section 4 and update the reward sentence in founder templates |
| 26 Oct 2026 | The who-qualifies page shows a new update date | 0 | Compare with the saved copy; re-screen only if a criterion's wording changed |
| September, Illustrative | Two declines in one sector citing client-owned records | 1 | Ask SourceX whether anything changed; sharpen the "who created the records" question for that sector |
| September, Illustrative | A portfolio CEO says an AI company approached her for data | Outside | Log it confidentially; it implies nothing about SourceX's programs or about buyers |
| 26 Nov 2025 | Anthropic's guidance on evaluation tasks, success criteria and trials | 2 | Hypothesis: records that capture a checked outcome may matter more; one CEO question; no outreach change |
| 27 Jul 2026 | Consolidated AI Act text with an amended Article 10 | 3 | Watch item; it governs high-risk AI systems, and no program change follows from it |
| August, Illustrative | A portfolio company announces a Series B | Outside | No action; funding never establishes eligibility |
| October, Illustrative | A conference speaker says developers pay more for one record type | Outside | Ask for a primary source; log it as unconfirmed until one appears |

## Relationship and ownership evidence no signal replaces

A signal can point at a kind of record. It never points at a company's eligibility. When a hypothesis survives and a company seems to match it, the company still faces the same tests as any other: a headcount that peaked at 50 or more full-time employees (contractors do not count), years of records of its own making, the rights to license them, and an eligible location. 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.

Who decides stays fixed too. Opening a licensing discussion and signing for the company both rest with the CEO, so a signal-driven idea goes first to the relationship owner who can put it to that CEO. Every question stays at metadata level, with no files, samples or logins, and whether a company's records match current demand is checked in SourceX's review, not by your signal log. Funding plays no part in SourceX's screening, which is why a funding alert belongs in the noise row; the [event suitability test for funding announcements](/guides/why-funding-announcements-should-not-trigger-automatic-outreach) turns such alerts into review tasks instead of emails.

## A two-quarter test of whether the system warns early

The cadence is itself a thesis: that some signals arrive before program changes and can be read in time. Test it for two quarters before trusting it. Log every signal with its date and distance, then, for each program change you see, look back for earlier signals that pointed the same way. Pair it with a narrow introduction pilot: write one CEO question from each quarterly hypothesis, ask it of up to ten watch-list companies through their relationship owners, and count how many describe the records the hypothesis expects.

Write in advance what would change the cadence. If no research or regulatory signal preceded any program change across both quarters, cut the quarterly reading to twice a year. If your monthly outcomes caught a shift before the program page showed it, give that layer more time. If the ten-company pilot finds the expected records at two companies or fewer, retire the hypothesis rather than stretching it. Testing a whole category narrative, rather than one hypothesis, is covered in [the referral experiment behind a category-creation story](/guides/the-referral-experiment-behind-a-category-creation-story).

| Measure | How to compute it | What would change the cadence |
|---|---|---|
| Lead time | Days between the earliest pointing signal and the program change | No lead from distances 2 and 3 in two quarters: read them twice a year |
| False alarms | Hypotheses written that no change or pilot supported | More than three of four unsupported: tighten what enters the backlog |
| Outcome warnings | Program changes first visible in your monthly outcomes | One or more: lengthen the monthly review |
| Pilot match | Watch-list companies, of up to ten, describing the expected records | Two or fewer: retire the hypothesis |
| Time spent | Hours a quarter across all cadences | Over eight: drop the least useful source |

## Where an early-warning system fails

**Method note.** The layers and cadence rank signals by their distance from a SourceX decision, using SourceX's terms and screening page, Anthropic's evaluation guidance and the EUR-Lex consolidated AI Act text, all read on 26 October 2026. They measure when a signal appeared and whether it preceded a change. They do not measure demand for any company's records, prices, payouts or SourceX's pipeline, none of which is public; SourceX shares company and commercial metrics with investors directly. The quarter of signals is a teaching example, not a forecast.

- **Overreaction.** A single vivid paper can pull a whole map toward one record type. The two-occurrence rule and the hypothesis backlog exist to slow that down.
- **Sparse outcomes.** A fund with a handful of introductions a quarter will rarely see the same reason twice; its monthly layer may stay quiet even when something has changed.
- **Unshared reasons.** SourceX may not give a reason for every outcome, so a quiet monthly review is not evidence that nothing moved.
- **Regulatory scope.** Article 10 of the AI Act concerns high-risk AI systems; reading it as a statement about all AI data demand stretches it past what it says.
- **Programs change by design.** Criteria follow each program and can move quickly, while signed agreements are never silently replaced and keep their own rates and exceptions, so what governs an introduction already made can differ from today's page.
- **Confirmation bias.** A team that wrote a thesis will read signals as supporting it. Record the signals that point the other way with the same care.
- **Synthetic substitutes.** If synthetic data replaces real records in a domain, research signals pointing at that domain would mislead; treat any such finding as a reason to retire a hypothesis.

## 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.

When the weekly check shows your criteria sentences match SourceX's current pages and a company's CEO wants the conversation, [register for a partner link](/register) and sign before submitting, screen the company against [who qualifies](/who-qualifies), and keep the [program terms](/terms) version you read on file. The portfolio-side overview is for [venture platform teams](/for/venture-platform-teams), the record-event memo is the [quarterly brief on network signals](/guides/a-quarterly-brief-on-network-signals-worth-following), and more essays are in the [guides hub](/guides).

Watching the program for changes is referral work; judging SourceX as a possible investment is a separate task, and investor materials, including the company and commercial metrics SourceX shares with investors directly, can be requested through the [SourceX investor overview](https://sourcex.si/investors).

This article is for information only and is not an offer to sell or a solicitation of an offer to buy securities. Any offering by SourceX is made only to verified accredited investors through its offering documents.

## Sources

- https://refer.sourcex.si/terms
- https://refer.sourcex.si/who-qualifies
- https://www.anthropic.com/engineering/demystifying-evals-for-ai-agents
- https://eur-lex.europa.eu/legal-content/EN/TXT/HTML/?uri=CELEX%3A02024R1689-20260727
- https://sourcex.si/investors
