branches

branches isolate each attempt

A branch begins from a pinned basis and gives an authorized participant somewhere real to work without changing accepted managed state. Several branches, including branches created from other branches, can diverge while everyone else continues from the parent.

how composite branching isolates an attempt

“Composite” means the design coordinates versioned knowledge, files, and relevant execution context from one starting point. “Copy-on-write” means the branch shares unchanged structure with its parent and records only what diverges. This design can isolate an attempt without duplicating every unchanged item.

branches and backups serve different purposes

A backup supports recovery. A branch supports active work and has its own identity and provenance. Its provenance records who created it, which basis it used, what ran, and what changed. A successful branch can become a proposal.

parallel attempts share one accepted record

• Successful attempt. Turn the diff into a proposal and ask for review.
• Failed or unwanted attempt. Discard the branch. The parent remains unchanged.

when the parent has moved

Conflict handling compares the proposal's pinned basis with the current parent and reveals competing changes before they combine. The reviewer decides whether to resolve the conflict, revise the proposal, or discard the attempt.

Architecture connection. Kabel synchronizes state, and Yggdrasil coordinates the composite fork. See the branching architecture.