Asset Lifecycle Management

Assets have a lifecycle: generated, reviewed, approved, deployed, active, deprecated, archived. Managing the lifecycle prevents three common failures: deploying unapproved assets, using deprecated assets in new materials, and losing track of where assets are deployed.

The lifecycle states. Generated: the asset exists but has not been reviewed. No deployment allowed. Reviewed: the critic has scored the asset. If it passes all three quality dimensions, it moves to Approved. If not, it moves to Rejected with specific revision instructions. Approved: the asset has passed quality review and is available for deployment. Active: the asset is deployed in one or more locations (tracked in the deployed_to metadata). Deprecated: the style version has been superseded — the asset is still live but flagged for replacement. Archived: the asset has been replaced everywhere and moved to cold storage.

The transition from Active to Deprecated triggers automatically when a new style version is published. Every active asset with the old style version is flagged. The replacement queue generates new assets from the same prompts using the new style version. Deployed locations are updated as replacements are approved. This is the style evolution pipeline — and at scale, it must be automated.

1. Generate and Review Asset enters the pipeline, passes through the generation template, and goes to the critic for quality scoring. Pass → Approved. Fail → Rejected with revision instructions.
2. Deploy and Track Approved assets deploy to their target locations. The deployed_to metadata updates with every deployment. Active assets are production assets — they are visible to the audience.
3. Deprecate and Replace When the style version changes, active assets on the old version become Deprecated. The replacement queue generates updated versions. As replacements deploy, old assets move to Archived.