Versioning works like git

Choice:

• Main is the approved design; nobody edits it directly. An edit goes to your private draft; Review saves the draft as a new branch or into an open one.
• Verify compares a branch with the captured site or a URL and returns a match score. Merge puts a branch on main; only Can merge does it.
• Every merge to main syncs every open branch and draft. A conflict never stops a sync; it is marked and settled before that branch merges.
• A product starts at v0.0.1 when first captured, imported or created; every merge bumps patch, minor or major.
• A branch is viewed like main, through Journey, Pages, Components and Styles, with Complete · Delta beside the picker. The bar holds conflicts, Verify and Merge; commits are the History tab.
• Every editor address names its ref after the product, main too: /<company>/<product>/<ref>/journey, /pages/<id>, /components/<id>, /styles/<group>/<id>, /analysis, /review.

Why: a branch is looked at the same way as main; fewer screens, one way of looking.

Rejected: a separate branch page and Branches list · a CRDT (it merges silently; Babul must show conflicts).