Creative history and lineage

Nothing gets overwritten

Nothing you make here gets quietly replaced. The grid is your project's full creative history, and every render persists as a stored artifact. When you regenerate, you do not overwrite the earlier version. You add a new tile beside it, so the take from last week is still one click away.

Work that is still running shows up too. In-flight renders appear as placeholder tiles merged right into the grid, so you can watch a batch of twenty fill in as each one lands instead of refreshing to check whether it finished.

Hiding is not deleting

When you remove a creative from the canvas, it is a soft hide, not a hard delete. The tile leaves your view, but the underlying record and its lineage stay intact underneath. Any Improvise or rerun trail that points at it still resolves, so tidying your view never snaps a chain you built earlier.

There is no hard delete button in the workspace. If you genuinely need a creative gone for good, that goes through support, not a control in the grid. This is deliberate, and it is the reason a cleanup never costs you a creative you later wish you had kept.

Why lineage matters

Think of it like the version history in a document editor. Every save is still there, and the current draft always knows where it came from. Because lineage survives, a version two or version three creative always traces back to its parent, which is exactly what keeps Improvise and rerun predictable over time. The history is a record you can trust, not a view that loses the originals the moment you look away.