# Research files vs referral notes: a workspace map | SourceX

Canonical: https://refer.sourcex.si/guides/how-to-separate-public-research-files-from-private-referral-notes
Last updated: 2026-11-05

Keep two stores and one rule about direction. The public research file holds only what anyone could cite, each item with its link and the date you read it, and it is built to be published. The private referral note holds what a CEO said for the purpose of an introduction and the dated status that followed, and it is never published. A public fact may be copied into a note with its source. Nothing from a note may travel back into research, a market map or a post. Anything that fits neither store goes on a quarantine shelf for counsel.

This map is for the general counsel liaison at a fund that publishes research, such as sector theses, market maps and posts about which businesses hold deep operating records, and also introduces companies to SourceX. Who inside the fund may read a referral note is an access question. This page answers a different one: where a fact may travel once it exists.

## Where a fact may travel, not only who may read it

NIST's security control catalog draws exactly this line. Control AC-4 in SP 800-53 Revision 5 reads: "Enforce approved authorizations for controlling the flow of information within the system and between interconnected systems based on [Assignment: organization-defined information flow control policies]." Its discussion explains that "Information flow control regulates where information can travel within a system and between systems (as opposed to who is allowed to access the information)." A fund is not a federal system, and the catalog is borrowed here only for the idea. A colleague with every right to read both stores can still carry a fact from one to the other, and that carrying is the leak.

The leak runs in both directions:

| Direction | What it looks like | Who is harmed |
|---|---|---|
| Note to research | A "strong archive" highlight on two companies in a public market map, because a partner mentioned them in the hallway | The company, whose talks with SourceX become guessable |
| Note to publication | A post that says the fund "has introduced several logistics firms to an AI data licensor" and names the sector, region and quarter | The company, and the fund's agreement with SourceX |
| Research to outreach | A public list of 40 companies turned into a mailing list for SourceX introductions | Every CEO who never asked to hear about it |
| Board knowledge to either | A systems fact from a board pack typed into the research file as "industry background" | The company that disclosed it in confidence |

SourceX's documents explain why the note side is sensitive. Section 1.6 of the sample Channel Partner Agreement lists "introduced contact identities, introduction records" among confidential information, and section 4.1 limits its use to evaluating, pursuing or performing "the referral relationship and Protected Opportunities." Section 4.5 adds: "Neither Party may publicly identify the other as a partner or disclose non-public deal details without written authorization, except as legally required." SourceX's process page says of a company's deal that "Neither side publicizes the deal." What these clauses require of your fund in a particular case is a question for your own counsel, or the company's.

## What each store holds, and what it must never hold

| | Public research file | Private referral note |
|---|---|---|
| Purpose | Analysis the fund may publish | One introduction the CEO agreed to |
| Every entry carries | The public source's link and the date read | The date and who said it |
| Allowed contents | Published filings, the company's own public statements, press, public datasets | The CEO's agreement and its date, the route of the introduction, what the CEO asked you to pass on, the stage SourceX shows you |
| Never | Any referral status; anything a CEO said for an introduction; board or information-rights material; SourceX's updates; a tag marking a company as introduced | Company files, exports, samples or logins; board material; estimates written as facts; drafts of anything meant for publication |
| Owner | The research lead | The person who holds the CEO relationship |
| Leaves the store by | Publication, after review | Nothing leaves except the introduction itself |

Two lines in SourceX's documents keep the note small. Section 4.6 of the sample agreement says a partner receives what it needs "to track its own referral and reward, using generic stages or reference codes." And SourceX's company process starts with "A few questions, no files", so nobody collects company data for SourceX: the company describes itself, and its CEO decides what it tells SourceX. Section 4.2 says the agreement "gives Partner no authority to share a supplier's inventory, records, raw data or personal information." A note that holds more than the introduction needs is a liability with no purpose; the [shadow data room guide](/guides/how-to-avoid-building-a-shadow-data-room-in-your-crm) shows how notes grow.

## The research-and-referral workspace map

Ten flows, each allowed, conditional or never. Examples are Illustrative.

| Flow | Rule | Condition | Example (Illustrative) |
|---|---|---|---|
| Public source to research file | Allowed | Link and date on every item | A company's own press release about a system migration |
| Public source to referral note | Allowed | Copied with its link and date, marked public | The same release, cited in the note as a reason the CEO was asked |
| CEO's words to referral note | Allowed | Only what the CEO said for the introduction | "We have dispatch records back to 2011; happy to talk" |
| Referral note to research file | Never | None | A "data-ready" flag added to a market map entry |
| Referral note to any publication | Never by default | The CEO's written consent to the exact words and SourceX's written authorization before it is named as your program | A recap post naming the companies introduced this year |
| Referral note to SourceX | Through the introduction only | The CEO agreed; the company describes itself | No files or records forwarded, ever |
| Research file to outreach | Not as a list | A public fact can prompt one question to one CEO, through whoever holds that relationship | A map entry suggests asking a founder you already know |
| Notes, counted, to published research | Only through a separate study | Published method, consent from each company and a disclosure review | A count of how many CEOs asked for a conversation |
| Board knowledge to either store | Never | It may prompt one question to that company's own CEO | A systems fact from a board pack |
| SourceX's status updates to anywhere else | Never | None | "In review" repeated in an LP letter |

**The quarantine shelf.** Some items fit neither store: a fact a founder said on a podcast that also appears in the board deck, a public article that seems to echo an introduction, a list a colleague built from mixed sources. Park them, unused, and let counsel decide. An item stays on the shelf until someone can show its public source.

**Setting it up.** Two locations with different owners. The research store has no field for referral status, so nobody can fill one in. The note store has no export into research tools. Shared tags such as "AI data candidate" in a CRM visible to both teams come out, because a tag is a fact travelling.

**Method note.** The map was built for this page from SourceX's terms (Version 2026-10-22.2, since replaced by version 2026-11-04), sections 1.6, 4.1, 4.2, 4.5 and 4.6 of the sample Channel Partner Agreement, SourceX's process and screening pages, and control AC-4 of NIST SP 800-53 Revision 5, all read on 2026-10-28. The ten flows and the quarantine shelf are this page's own design. Nothing here measures how often such leaks happen; no such data exists.

## If your research wants to use the fund's own referral experience

Run it as a separate study, never as a reading of the notes. Publish this design before contacting anyone.

- **Sampling frame.** Every company whose CEO the fund asked about a SourceX conversation during a stated period, including those who declined, did not reply, did not fit, withdrew or were declined.
- **Consent.** Written consent from each company for research use, separate from the introduction and asked only after the CEO's decision about the introduction, so it cannot sway it. Withdrawal is honored until publication.
- **Variables.** Only the CEO's answers to the study's own questionnaire, never fields copied from referral notes.
- **Analysis.** Counts with stated denominators, small cells suppressed, missing answers reported as missing. Descriptive only: a study like this cannot show that research caused introductions, or the reverse.
- **Results.** None exist, and none are published here.

The [twelve-gate anonymization and consent review](/guides/how-to-publish-network-research-without-exposing-companies) is the release test for anything such a study produces. For turning public research into questions rather than lists, see the [research-to-question guide](/guides/how-to-use-public-ai-research-to-ask-better-referral-questions).

## Escalation, withdrawal and publication, kept apart

**Escalation.** A note holder sees a research draft about to single out a company they introduced. They ask for a hold without explaining why, and counsel decides. The researcher learns that a hold exists, not what is behind it.

**Withdrawal.** A CEO withdraws from the introduction. The note shrinks to dates and the withdrawal itself. Public research built from public sources can stand, but rerun the coincidence check: does any entry now read as a pointer to that company's talks?

**Publication.** Three permissions, never bundled: the CEO's written consent for the company's facts, SourceX's written authorization before it is named as your program, and your counsel's review of anything learned in confidence. An introduction yes is none of them. The [decision register](/guides/the-professional-referral-audit-trail-without-excess-client-detail) shows how to record each without copying company facts.

## One market map, two introductions (Illustrative)

Illustrative. A generic fund and invented companies.

A research associate drafts a public map of 40 regional logistics companies with long operating histories, built from public filings, company sites and trade press. Two of the 40 had CEOs introduced to SourceX last quarter. The draft marks exactly those two as "notably data-rich", because a partner mentioned them at lunch.

Applying the map: the highlight is a note-to-research flow, so it comes out. The map keeps both companies only because public criteria, applied to all 40, put them there. The coincidence check asks whether any column now separates the two introduced companies from the rest; none does. The draft names no licensing partner. A week later a colleague asks to email all 40 CEOs about SourceX. The answer is no: each relationship owner may ask one CEO they already know, one at a time.

## Where the workspace map can be wrong

- **People remember.** Separate stores do not separate memories. In a five-person fund the analyst and the relationship owner may be one person, and the only control is the habit of citing a public source for every research fact.
- **Selection leaks.** A list can reveal by what it includes, even with every entry sourced. The coincidence check is a judgment, not a test.
- **Public sources change.** Pages move or vanish; a dated citation is the only proof a fact was public when used.
- **Tools copy.** CRMs, shared drives and AI note-takers mirror content across stores. Check where each tool writes.
- **It is not legal advice.** What your confidentiality duties require, under SourceX's agreement or the company's, is for your counsel or the company's.

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

Set up the two stores before the next introduction, then [register as a partner](/register) and sign the Channel Partner Agreement, let [who qualifies](/who-qualifies) describe fit in SourceX's words, and keep the [program terms](/terms) as the reference for what credit rests on: dated records, not research files.

Keeping research and referral notes apart is referral housekeeping. Judging SourceX as a possible investment is a separate exercise, and the [SourceX investor overview](https://sourcex.si/investors) is where to ask for its materials.

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://sourcex.si/documents/partner/SourceX_Channel_Partner_Agreement_Sample.pdf
- https://sourcex.si/how-it-works
- https://refer.sourcex.si/who-qualifies
- https://csrc.nist.gov/CSRC/media/Projects/risk-management/800-53%20Downloads/800-53r5/SP_800-53_v5_1-derived-OSCAL.pdf
- https://sourcex.si/investors
