Collection branching leverages content-addressed storage to make copies nearly free. When a collection is branched, only the membership list is copied — the actual image files, stored by content hash, are shared between the original and the branch. Changes to one branch (adding, removing, or reordering assets) do not affect the other.
Practical applications include client review workflows (branch a collection, remove work-in-progress items, share the branch), version snapshots (freeze a collection at a point in time for archival), and collaborative editing (each team member branches a shared collection and curates independently before merging selections).
Related Guides
Related Terms
See AI Asset Management in Action
Numonic automatically captures provenance, preserves metadata, and makes every AI-generated asset searchable and reproducible.