Skip to content

Reusable episode assets (logos, guest photos, b-roll, sponsor marks) have no home with lifecycle and approval state #1038

Description

@seekmistar01

Problem

The canvas can reuse a show template and a returning guest profile, but there is no single place to reuse the smaller visual assets an episode depends on — show logos, guest headshots, lower-third art, b-roll, screenshots, sponsor marks, and title/thumbnail backgrounds.

Today these assets are effectively re-introduced (and re-approved) per episode, which causes real reuse mistakes:

  • A sponsor mark that was rejected as unreadable on one episode can quietly be picked again on the next.
  • A guest headshot flagged as the wrong speaker has no home that holds the warning across episodes.
  • Archiving an old season's title background does not stop it from being suggested for new placements, yet creators still expect to find it on the episodes that already used it.

Why it matters

Reuse only saves time if the creator can trust what they are reusing. Without a library that separates availability (is this offered for new placements?) from trust (has it been approved?), the "make it reusable" flow leans on memory and re-checks the same assets every episode.

Proposed screen

An Episode asset library in the "Make it reusable" flow that:

  • Lists reusable assets with a clear lifecycle status (suggested / in use / archived) and an approval flag (approved / review / rejected).
  • Treats a status change as never resolving an approval concern: an in-use asset with an unresolved flag stays on already-exported episodes but is held back from new placements until resolved.
  • Keeps archived assets findable where they are already used while removing them from new suggestions.
  • Routes each approval concern to the workflow that owns it (guest profile reuse, contextual b-roll, thumbnail & cover frame, show template adaptation) instead of asking the creator to fix it inline.
  • Offers filters for available for new use, in use, needs a decision, and archived.

This sits naturally after runtime shaping in the reuse flow and hands off to the watch-through preview like the other reuse steps.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Fields

    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions