Module forks 

Provider-neutral workspace forks (roadmap phase 81).

A fork is a writable workspace copy or session derived from a source workspace — backing a thread, subagent lane, task branch, or experiment. Providers implement concrete storage/compute behavior (Git worktrees, Rift copy-on-write snapshots, remote sandboxes); core code only sees these types. Forks are not inference providers and are not GitHub repository forks.

Structs

ForkCapabilities

ForkOwnership

Durable ownership, independent of a worktree’s path or branch naming. Git forks with None are external, unmanaged checkouts. Other providers may omit ownership when they do not support this contract.

ForkPolicy

Source-state policy applied before fork creation.

ForkProvenance

Provider-recorded provenance. All fields optional so local and remote providers can populate what they actually know; never secret-bearing.

ForkProviderDescriptor

ForkRequest

RemoveForkPolicy

Removal is destructive and always path-confirmed: the caller must name the exact fork workspace being removed.

RemoveForkResult

WorkspaceFork

Enums

AgentWorkspaceIsolation

Opt-in filesystem isolation for a collaboration agent, separate from conversation-history forking. Worktrees start from committed HEAD.

ForkCleanupPolicy

ForkReason

Why a fork is being created; recorded for provenance/audit only.

ForkStatus

Traits

ForkProvider

Provider contract for workspace forks. Registered through the extension registry (ProvidedService::ForkProvider); providers declare their capabilities and must not assume ambient authority beyond them.

Type Aliases

ForkId

Provider-scoped fork identifier. Stable and resolvable by the provider alone (e.g. the absolute worktree path for git-worktree).

ForkProviderId