The brief says twelve more like the approved one — new audiences, formats, markets. Three weeks later there are four hundred files, two competing source candidates, and a delivery that mixes them. Variant chaos is the most visible production-memory failure because clients see it directly. The fix is branching discipline borrowed from software, adapted for creative work.
The branching model
- Lock the canonical source: approved version with full production record.
- Branch each variant with an explicit parent link to the source version.
- Attach delivery specs per variant: dimensions, duration, channel, market, legal notes.
- Give each variant its own approval lifecycle — approval never inherits silently.
- Gate delivery on spec fit plus lineage completeness.
Rules that prevent chaos
Apply the lineage model in the AI asset lineage guide to the Campaign variant control workflow: the same graph and rules, applied to campaign variants.
Variant hygiene table
Variant states and their meaning
| State | Meaning | Allowed next step |
|---|---|---|
| Branched | Parent linked, work started | Production |
| In review | Candidate with recipe attached | Revise or approve |
| Approved | Signed off for its spec | Deliver |
| Delivered | Shipped with lineage | Measure and reuse |
| Superseded | Replaced, retained | Reference only |
Implementation checklist
Variant-management checklist
- Lock canonical sources before branching begins.
- Require parent links and specs on every branch.
- Run separate approval lifecycles per variant.
- Gate every delivery on spec plus lineage.
- Retire superseded variants explicitly; never delete silently.
What to measure in a paid pilot
Source-trace time per derivative, wrong-version deliveries, and spec-rejection rate at delivery. The variant-control use case is a purpose-built 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
- One canonical source; every variant branches with a parent link and spec.
- Approval state inherits nothing automatically — each variant earns its own status.
- Delivery gates check spec fit and lineage before files ship.
- Variant count is a vanity metric; traceability is the operating metric.