Branching

Branches let you explore alternative structured-state histories without losing the stable line of work.

main:      commit_1 -> commit_2
                         \
experiment:               commit_3 -> commit_4

Use branches when you want to compare product directions, prompt versions, document revisions, or extraction strategies before merging the useful state back.

Branches point at commits

In T3X, branches point at committed structured state. They are not separate copies of raw text; they are alternate histories of reviewed state transitions. Each transition still goes through YOps before it becomes a commit.