Core concepts

Repositories

A Dits repository combines a normal working directory with local metadata for staged state, immutable objects, manifests, commits, and refs.

Working tree

The files users and creative tools open. dits status compares this state with staged and committed state; dits add prepares selected content for a commit.

Repository metadata

Local .dits data records objects, manifests, indexes, commits, refs, configuration, locks, and related engine state. Treat it as durable repository data, but keep an independent backup while the alpha format and recovery behavior are evolving.

Local paths only

Local filesystem clone and object-transfer paths exist. Internet remotes, partial network clone, remote hydration, and hosted repositories are not functional product capabilities.

A remote-looking command is not a backup

Verify where data was written and restore it independently. Network push, pull, fetch, sync, network clone, and P2P do not transfer repository data.

Format maturity

Repository encodings need deterministic serialization, version markers, conformance fixtures, migration rules, and independent readers before they become a stable ecosystem contract.