Documentation

Build from product truth

Dits is an open, local-first version-control alpha for large media and asset pipelines. These docs separate current behavior from experiments and future design.

Alpha safety

Use Dits only on disposable or independently backed-up projects. Verify restored files. Network push, pull, fetch, sync, network clone, and P2P transfer are not implemented.

Start here

Getting started

Install the npm-packaged CLI and evaluate a local repository safely.

Current

CLI reference

Commands and flags generated or checked against the current binary.

Current

Core concepts

Objects, chunks, manifests, refs, hybrid storage, and exact recovery.

Authority

Active architecture

The live Rust CLI boundary, dependency direction, and quarantined history.

Read before adopting

Status and roadmap

What is current, experimental, roadmap, or historical—and the gates between them.

How to read these docs

Capability labels are contracts: Current means a real local command path with relevant tests; Experimental means runnable but unstable or incompletely validated; Roadmap is not implemented; and Historical is retained context rather than current architecture.

Current product boundary

The canonical engine is the Rust workspace under apps/cli.
Local history, chunk storage, and exact checkout are the core alpha claim.
MP4, FACR, photo, proxy, VFS, and semantic graph paths need broader proof.
The former backend under legacy/backend-crates is historical.
API, SDK, P2P, cloud, and deployment pages describe design unless explicitly promoted.

Evidence standard

A performance or compatibility claim should name its fixture, method, environment, Dits commit, and raw artifact. Component microbenchmarks do not establish end-to-end repository performance.