Data lineage vs data provenance: what's the difference in AI data licensing?

What is the difference between data lineage and data provenance?

Data lineage answers how data got to where it is and what happened to it along the way. Data provenance answers where it originally came from, who created it and whether it may be used. Lineage is a map of movement and transformation; provenance is a record of origin and authority.

The verdict depends on who is asking. Data engineers and analytics teams live in lineage, using it to trace a wrong number back to a broken join or to see what a schema change will break. Counsel, diligence teams and AI data buyers start with provenance, because no amount of tidy transformation fixes records a company had no right to license. An AI licensing deal needs both, in a fixed order: provenance before anything is promised, lineage when the data is prepared for delivery.

The words overlap in practice. Some data catalogs label everything lineage, and some research traditions treat lineage as one part of a broader provenance record. The split used on this page follows the two questions a buyer's diligence team has to answer.

Data lineage vs data provenance side by side

An AI licensing example: one ticket archive, two records

Illustrative: a fictional managed IT services firm with 180 full-time employees wants to license nine years of helpdesk tickets.

Its provenance record answers the origin and authority questions:

• Sources: the firm's current helpdesk, plus a predecessor ticketing tool that was exported before it was switched off.
• Creators: technicians on staff wrote the diagnosis and resolution notes; client employees wrote many of the original requests.
• Rights basis: staff-written notes are the firm's work product; text supplied by clients, and anything copied from client environments, depends on each master services agreement.
• Restrictions: two client contracts forbid reuse of client data, so those clients' tickets are excluded.
• Prior licenses: the tickets have never been licensed for AI training.

Its lineage record answers what happened between the source systems and the delivered files:

1. Export both systems through their standard export functions.
2. Merge the two exports and remove duplicate tickets created during the migration.
3. Drop every ticket belonging to the two excluded clients.
4. Apply the agreed redaction rules to names, email addresses, IP addresses and credentials.
5. Strip attachments the license does not cover.
6. Join each ticket to its time entries so effort and outcome sit together.
7. Package and checksum the files, then deliver once the agreement is executed and the firm authorizes release.

If a buyer later asks why the delivered set holds fewer tickets than the raw export, lineage answers. If the buyer asks whether the firm could license a particular client's tickets at all, only provenance can.

When does provenance win?

Provenance comes first whenever the question is whether something can be licensed. Rights are decided at the source, not in the pipeline.

Ownership shows why. Copyright Office guidance explains that material employees prepare within the scope of their jobs is generally a work made for hire, so the employer is the author and owner, while content from outside contractors may not belong to the company unless it falls in a listed category under a signed work-made-for-hire agreement or the rights were assigned in writing (Copyright Office Circular 30). Ownership can also be divided: the Copyright Act lets any exclusive right be transferred and owned separately (17 U.S.C. § 201), which is how a company can grant an AI-training license while keeping ownership and its other rights.

Provenance signals a partner can listen for without seeing any records:

• Most records were created by the company's own employees in the company's own systems.
• The company can name the systems it has used and roughly since when, including retired ones.
• Client and vendor contracts do not obviously forbid reuse of the material.
• Nothing has already been licensed to someone else for AI training.
• Someone at the company can run exports and own the inventory.

This is general information, not legal, tax or financial advice. Ownership questions belong with the company's own counsel.

When does lineage win?

Lineage takes over once rights are settled and the work turns to preparing data. It matters most when:

• Proving agreed redaction ran: lineage shows the step, the rule set used and how many fields it changed.
• Explaining counts: it accounts for every record removed between export and delivery.
• Reproducing a delivery: the same steps can be rerun on the same scope if files are lost or a correction is needed.
• Withdrawing a source: if a client later has to be excluded, lineage shows every output that client's records fed.
• Answering curation questions: filtering, deduplication and joins are lineage events, the same steps described in what is data curation for AI.

How can partners use the two terms with a company?

Use the origin-and-path test, two questions that mirror what a buyer will ask:

1. Origin: who created these records, in which systems, and is anything stopping you from licensing them?
2. Path: if you exported them, could your team show every step between the system and the delivered file?

A weak answer to the first question is a reason to pause. A weak answer to the second is normal at the start, because that trail can be built during preparation.

A way to frame it for an owner:

Partners stay out of the records entirely: no exports, no file reviews, no descriptions of confidential content.

How does SourceX fit?

SourceX's process starts with rights. Qualification looks at company size, operating history, data breadth and rights; the company then completes a data inventory of its systems, years of history and export options; redaction and de-identification requirements are agreed before preparation begins; and data moves only after an executed agreement and the company's authorization, which is where lineage records come in. Each stage is set out in how it works. The company keeps ownership and licenses its records rather than selling them, as explained in licensing vs selling data.

For deeper reading, what is data provenance covers origin records in detail, and what is rights-cleared data covers the rights side.

Companies that fit are US businesses with 50+ full-time employees at peak (contractors excluded), several years of documented operations, rights to license their records and an authorized sponsor such as the owner, CEO, CFO or another authorized representative. Partners earn 25% of the eligible platform fees SourceX actually collects from the referred company's licensing deals, capped at $100,000 per referred company, and rewards become payable only after the buyer pays and SourceX receives its fee. Leads and meetings do not count toward payment on their own, and the partner's share is never deducted from what the company receives.

Next step

Ask the origin question about one company in your network this week. If the answer is clean, check it with the company fit checker, then register as a partner and make the introduction. Owners can also apply directly at sourcex.si/apply with your referral link.