Glossary

The cryptographic hash function Dits uses for current content identifiers. A digest detects changed bytes but is not an author signature.

The raw content of a file stored in the repository. In Dits, blobs are chunked and deduplicated.

An independent line of development. Branches allow you to work on features without affecting the main codebase.

A portion of file content created by the chunking algorithm and stored locally by its BLAKE3 identifier.

Creating a repository copy. Dits currently supports clone from another local filesystem path only; network clone fails.

A snapshot of your repository at a point in time. Each commit has a unique identifier and records changes made since the last commit.

Identifying content by its cryptographic hash rather than its location. This enables deduplication - identical content is stored only once.

A chunking algorithm that determines chunk boundaries based on file content rather than fixed sizes. This improves deduplication when files are modified.

The process of eliminating duplicate copies of data. In Dits, identical chunks are stored only once, saving storage space.

The default chunking algorithm in Dits. It's a fast, efficient content-defined chunking implementation optimized for large files.

A roadmap remote operation. The current command returns a nonzero error without changing objects, refs, or the working tree.

Filesystem in Userspace. Dits has an experimental, local-only mount path behind the optional fuser Cargo feature.

A fixed-size identifier computed from content. Dits uses BLAKE3 for its content-addressed objects and chunks.

A reference to the currently checked-out commit. Usually points to the tip of the current branch.

A local script associated with a supported Dits workflow event, such as a commit step.

Materializing file bytes from objects already available to a local repository. Remote on-demand hydration is not implemented.

Also called the staging area. A snapshot of files you've marked to include in the next commit.

A local advisory record of editing intent. Current locks are not synchronized, remote leases, authorization, or enforcement against other tools.

Combining changes from different branches into a single branch. Dits supports various merge strategies.

An experimental local FUSE view, available only in source builds that enable the fuser feature. It does not fetch from a remote.

A conventional remote configuration name. Local clone records its source path as origin, but remote transfer remains disabled.

Planned direct repository exchange between peers. Current P2P code is nonfunctional scaffolding and transfers no repository data.

A low-resolution or placeholder version of a large file. Used for preview while keeping full-quality originals available.

A roadmap remote operation. The current command returns a nonzero error without changing objects, refs, or the working tree.

A roadmap remote operation. The current command returns a nonzero error and uploads no repository data.

Replaying commits from one branch onto another. Creates a linear history by avoiding merge commits.

Short for reference. A pointer to a commit, typically a branch name or tag.

A named URL stored in local configuration. Saving one does not enable repository exchange in the current alpha.

A directory containing your project files and the complete history of changes, stored in the .dits directory.

Selecting local paths for the working tree. It is not network partial clone or remote on-demand hydration.

Marking changes to include in the next commit. Done with 'dits add'.

Temporarily storing uncommitted changes so you can work on something else, then restore them later.

A lifecycle label used by local freeze/thaw experiments. Automatic cloud-tier movement is not a current capability.

A named reference to a specific commit, typically used to mark release versions.

An object representing a directory. Trees contain references to blobs (files) and other trees (subdirectories).

The experimental local FUSE mount path. It is feature-gated and does not provide remote hydration.

A future repository-exchange contract. No complete Dits client/server wire protocol is implemented today.

The directory containing your actual project files. Changes here are tracked by Dits.