Ask a team where a campaign variant came from and watch what happens: someone opens three folders, checks two Slack threads, and offers a confident answer that a colleague contradicts. The pixels exist; the relationships do not. Lineage is the missing structure — the explicit graph of parents, variants, and derivatives that makes every asset traceable.
The three relationship types
- Parentage: the source asset (and version) this asset derived from.
- Variants: sibling branches serving different audiences, formats, or markets.
- Derivatives: downstream transformations — crops, adaptations, localizations, sequels.
Every asset except true originals has a parent. Every delivered asset may grow derivatives. Recording both directions means you can walk up to the approved source or down to everything affected by a change.
What lineage unlocks
Lineage in practice: a campaign family
- Hero v6 approved with full production record — the canonical source.
- Twelve audience variants branch with parent links to hero v6.
- Channel adaptations (vertical, square, OOH) derive from their variants, linked in turn.
- A legal note on one reference image propagates: lineage shows every affected derivative in one query.
- Next quarter’s campaign starts from hero v6’s record — reuse with full context.
Lineage discipline
Rules that keep the graph true
| Rule | Practice | Violation symptom |
|---|---|---|
| Link at creation | Parent recorded before branching | Orphan folders nobody trusts |
| Version the link | Parent version, not just asset | Traced to the wrong state |
| Retire explicitly | Superseded links marked | Zombie variants resurrected |
| Review the graph | Lineage check at delivery gate | Delivered files with unknown parents |
Implementation checklist
Lineage checklist
- Require a parent link on every branched variant.
- Record parent versions, not just parent assets.
- Make lineage navigable both directions in your tooling.
- Gate delivery on lineage completeness.
- Run rights-propagation drills: pick a source, list affected derivatives.
What to measure in a paid pilot
Trace time from derivative to canonical source, orphan-asset share, and rights-query response time. Use the Campaign variant control page as a pilot surface.
Start with the workflow assessment to find where your team loses context today, read the Production Memory guide, and browse the use-case library for related workflows.
Key takeaways
- Lineage = parent links + variant branches + derivative chains, navigable both directions.
- Link at creation: every branch records its parent before work starts.
- Lineage powers approvals (what authorized this?), rights (what sources flow in?), and reuse (what descends from this win?).
- A lineage graph is the most quotable artifact a creative team can publish internally.