Skip to content

Glossary

The durable state an application needs to open coherently: SQLite databases, settings, attachments, generated assets, imports, and related app-owned files.

A tracked non-SQLite file entry in a Graft tree. Text files can be inline. Binary files and configured resource paths use external payload storage.

An immutable repository object that points to a tree and records one app-state version.

File bytes stored by content hash outside normal commit/tree objects. Used for binary files and configured external paths.

The optional SQLite virtual file system registered by the Graft extension. It writes live database pages directly to a Graft Volume. It is a data-plane mode, not the repository command API; the default worktree uses ordinary SQLite files.

The staging area between the worktree and the next commit. During conflicts, the index can also hold base, ours, and theirs stages.

The content class of a tracked path: sqlite_database, text_file, or binary_file.

Writing a tracked SQLite snapshot back to a normal SQLite database file in the worktree.

A named storage backend for repository objects, refs, SQLite storage, and external payloads. Examples include fs://, s3_compatible://, and https:// (or the explicit graft+https:// compatibility form).

A worktree plus .graft/ metadata. The repository stores refs, objects, index state, local SQLite storage, config, and payload cache.

An immutable SQLite database state that can be referenced by a repository object.

The representation strategy for a path: sqlite_snapshot, inline, or external.

The app data directory containing materialized SQLite files and app-owned files that Graft tracks.