Appearance
Glossary
| Term | Definition | More |
|---|---|---|
| Worktree | A working directory linked to a Git repo's branch. daft places one worktree per branch on disk. | Worktrees |
| Layout | The geometry of where worktrees go on disk relative to the repo (sibling, contained, nested, custom). | Layouts |
| Adopt | Convert a traditional Git repo (single working tree) into the daft worktree layout. | Adopting existing repos |
| Hook | A unit of automation that fires on a code-evolution boundary (worktree create, commit, merge, etc.). | Hooks |
| Job | A unit of work inside a hook. One hook can fire multiple jobs in parallel or sequenced. | Job orchestration |
| Recipe | A documented pattern in docs/recipes/ for solving a specific lifecycle problem. Distinct from a daft.yml job entry, which some ecosystems (e.g., just) call a "recipe" in their own config sense. | Recipes |
| Trust | A confirmation that a daft.yml is authorized to run on this machine. Trust is invalidated when the file changes. | Trust & security |
| Visitor configuration | A daft.yml whose git tracking status is "untracked". Daft treats untracked daft files (daft.yml, daft.local.yml) as personal artifacts: it copies them into new worktrees on branch-out and consolidates genuine refinements back on daft merge or worktree removal, guided by seed provenance. Run daft install to bootstrap a visitor configuration. | FAQ |
| Seed | The content daft last wrote into a worktree's untracked daft file, recorded at branch-out, install, or consolidation. A copy byte-identical to its seed is pristine (deleting it loses nothing); an edited copy is refined and is never silently lost or silently merged — daft prompts, refuses, or (when forced) stashes it under .daft/discarded/. | FAQ |
| Multi-remote | A worktree layout that organizes worktrees by their remote (e.g., separate folders for origin and upstream). | Multi-remote |
| Shortcut | A short symlink alias for a longer command (e.g., gwtco for git worktree-checkout). | Shortcuts |
| Boundaries thesis | The framing that daft hooks are gates at each code-evolution stage — a local parallel to GitHub Actions. | Hooks |
| Adoption arc | The three stages of worktree adoption depth: code isolation → environment isolation → automation. | Worktrees |