Creative Repository

A searchable store of produced assets, so creative is reused rather than regenerated.

Vertical: ATL · Status: ⬜ Planned Back to ATL · workflows index

---

Trigger

Write on every asset produced; read during creation and planning.

Flow

asset produced (script - blog - static - GIF - video)
        |
index: theme - product - market - language - performance
        |
searchable during creation
        |
reuse / variant / retire

Why it matters at page-4 volume

At 15 000 creatives, the expensive failure is not generation cost - it is producing something that already exists and having no way to know.

A repository is also the precondition for two other things on the roadmap: variant testing (which needs to know what shipped) and the Learning Agent (which needs to tie performance back to an asset).

Agents involved

Consumed by the Visual Agent and Creative Agent; written to by both.

Naturally part of the intelligence layer rather than a separate store.

Blocked on

An asset store. Drafts live per tenant today with nothing indexing across them.

Roadmap source

Deliverable ⑦ on page 5 — see roadmap_ref_extracted.md.