Codex Git is the local Git workspace presented for the Current Project. Its language keeps Repository-wide facts separate from the state and actions of each registered Worktree.
Current Project: The local macOS project currently selected as the source of the Git workspace. It may or may not belong to a Repository. Avoid: Active project, open folder
Repository: One Git repository, including its shared objects, references, configuration, and registered Worktrees. Avoid: Repo, project, folder
Worktree: One registered checkout of a Repository with its own Working Tree, Index, and HEAD. Avoid: Workspace, checkout, task
Main Worktree: The primary Worktree of a Repository. It is a Git role, not a claim about its Branch name or how the Worktree is used. Avoid: Main Branch, root Worktree
Linked Worktree: Any registered Worktree that is not the Main Worktree. Avoid: Secondary Repository, child Worktree
Available Worktree: A registered Worktree whose Working Tree can currently be inspected and used for the capabilities allowed by its Git state. Avoid: Healthy Worktree, active task
Unavailable Worktree: A registered Worktree that cannot currently be inspected or acted on, while its registration remains relevant for diagnosis. Avoid: Deleted Worktree, invalid Worktree
Worktree Generation: One continuous identity lifetime of a registered Worktree. Removing, moving, or recreating a Worktree begins a different generation even if a path is reused. Avoid: Worktree version, refresh generation
Provenance: Optional evidence about who or what created or owns a Worktree. Provenance never determines whether a Worktree belongs to the Repository or which Git capabilities it has. Avoid: Worktree type, Git source
Codex Task Worktree: A Worktree whose association with a Codex task is proven by stable Codex-owned metadata. Avoid: Codex-looking Worktree, task Branch
Scheduled Worktree: A Worktree whose scheduled lifecycle is proven by stable Codex-owned metadata. Avoid: Automation Branch, scheduled-looking Worktree
Permanent Worktree: A Worktree whose permanent lifecycle is proven by stable Codex-owned metadata. Avoid: Long-lived Worktree, manually named Worktree
External Worktree: A Worktree whose non-Codex origin is proven by stable Codex-owned metadata. Avoid: Manual Worktree, unknown Worktree
Unclassified Worktree: A Worktree for which provenance evidence is absent, unstable, or conflicting. Avoid: External Worktree, other Worktree
Working Tree: The checked-out files of one Worktree. Avoid: Workspace files, local files
Index: The staged snapshot belonging to one Worktree and proposed for its next Commit. Avoid: Staging area, staged files
HEAD: The current Commit position of one Worktree, either attached to a Local Branch or detached. Avoid: Current Branch, latest Commit
Local Branch: A named local reference to a Commit. Avoid: Branch when local or remote-tracking kind matters
Remote-tracking Branch: A locally cached reference representing the last fetched state of a Branch in a Remote. Avoid: Remote Branch, live Branch
Upstream: The configured Remote-tracking Branch against which a Local Branch is compared and to which its ordinary Pull and Push are directed. Avoid: Remote, origin, destination Branch
Unpublished Branch: A Local Branch without an Upstream that is eligible to be published to a confirmed same-name Branch on a selected Remote. Avoid: New Branch, local-only Branch
Detached HEAD: A Worktree state in which HEAD identifies a Commit without being attached to a Local Branch. Avoid: No Branch, anonymous Branch
Initial Repository State: A Repository state before the first Commit exists. Avoid: Empty Branch, broken HEAD
Clean Worktree: A Worktree with no Conflict and no difference among HEAD, Index, and Working Tree, including no Untracked File. Avoid: Safe Worktree, unchanged Repository
In-progress Git Operation: A Git-managed Repository state indicating an unfinished operation whose completion or recovery is outside the MVP. Avoid: Busy Worktree, lock
Branch Occupancy: The association between a Local Branch and the registered Worktree in which it is currently checked out. Avoid: Branch lock, Branch owner
Changed File: One path-and-baseline observation in a Worktree. The same path may be represented by more than one Changed File when it differs across multiple baselines. Avoid: Dirty file, modified path
Conflict: A Changed File whose Index has unresolved entries. Avoid: Merge error, unstaged change
Staged Change: A Changed File representing a difference from HEAD to Index. Avoid: Staged File
Change: A Changed File representing a difference from Index to Working Tree. Avoid: Unstaged File, modification
Untracked File: A Working Tree path that is not represented in the Index. Avoid: New Change, unstaged file
Diff Baseline: The exact pair of Git states compared for one Changed File review. Avoid: File version, diff type
Commit Draft: The unsubmitted Commit message associated with one Repository and Worktree. Avoid: Commit, message template
Local Mutation: An operation that may change one Worktree's Index, HEAD, or Working Tree without contacting a Remote. Avoid: Local command, file operation
Branch Switch: A Repository-coordinated operation that changes the Branch or detached position of one Worktree. Avoid: Checkout, Branch change
Remote Operation: An operation that communicates with a configured Remote and may change shared references or transfer Git objects. Avoid: Network command, sync
Refresh: A local observation that produces current Repository and Worktree state without contacting a Remote. Avoid: Fetch, reload
Reconciliation: A fresh observation after an attempted mutation that establishes what Git state actually resulted. Avoid: Refresh when outcome recovery is meant, rollback
Succeeded: An operation outcome in which the requested effect is verified in reconciled state. Avoid: Completed
Rejected: An operation outcome in which a current precondition prevents execution and no requested mutation begins. Avoid: Failed, invalid
Failed Known: An operation outcome in which execution does not achieve the requested effect and reconciled state is known. Avoid: Error, rejected
Partial Success: An operation outcome in which independently reportable requested effects have a mixture of verified success and failure. Avoid: Failed, mostly succeeded
Unknown Outcome: An operation outcome in which interruption, timeout, or ambiguous process state prevents the product from proving whether the requested effect occurred. Avoid: Failed, cancelled
Busy: A Rejected outcome indicating that a conflicting operation lane is already in use and the new mutation was not queued. Avoid: Pending, waiting