PRODUCT
Branches.
Safe experimentation.
History built in.
Everything you do in the EMS is a resource event. Every change — big or small — is stored as an event that can be undone, redone, or replayed.
Branches build on this foundation. A Branch is a set of resource events applied on top of main. This makes Branches both familiar to developers and more powerful than traditional draft/publish systems.
How Branches work.
→
Branch from main: create a new branch to work on changes without affecting live.
→
Branch from another branch: try out alternatives in parallel.
→
Branch from a specific resource event: rewind to a moment in history and continue from there.
When a branch is applied to main, all other branches automatically inherit those resource events — like an “auto-rebase” in Git. This keeps everything consistent without manual conflict resolution.
Exploring changes.
Because branches are built from resource events, you can review changes in detail.
→
Use a progress bar to move back and forth in time.
→
See exactly which changes have been made, and in what order.
→
Visually inspect how the system evolves across the life of the branch.
Parallel work.
Branches let teams explore different directions safely.
→
Designers can prototype multiple layout options.
→
Engineers can test workflows or schema changes.
→
Managers can compare branches and decide which version to apply.