✨ [Feature Request / Suggestion]: Transforming EditingEngine => EditingTrack, CoreEditingAPI => EditingEngine, and implementing a dynamic editing track for each contentEngine, with ability to save to / pull from database.

Suggestion / Feature Request

Transforming EditingEngine => EditingTrack, CoreEditingAPI => EditingEngine, and implementing a dynamic editing track for each contentEngine, with ability to save to / pull from database.

Why would this be useful?

This will be useful to create more dynamic editing flows, and to be able to resume an automated editing process from memory. Also will help a lot in defining editing step inheritance between content engines.

Screenshots/Assets/Relevant links

No response