Evaluate Dits locally

1. Install the published package

npm install -g @byronwade/dits
dits --version

On a packaged target, Node.js 16 or later is required by the launcher. There is no published shell installer, Homebrew tap, or crates.io package.

2. Create a disposable workspace

mkdir dits-evaluation
cd dits-evaluation

printf 'first version
' > notes.txt
mkdir assets
printf 'generated fixture
' > assets/example.bin

dits init
dits status

3. Record the first snapshot

dits add .
dits commit -m "First exact snapshot"
dits log
dits status

4. Make and inspect a controlled change

printf 'second version
' >> notes.txt
dits status
dits diff
dits add notes.txt
dits commit -m "Update notes"
dits log

5. Verify a restore

Record a standard operating-system hash before changing or removing a test file, check out the desired committed state, and compare the result. The exact checkout syntax can vary by the revision you are evaluating; confirm it in the generated CLI reference.

# Record expected hashes for the disposable fixture.
shasum -a 256 notes.txt assets/example.bin

# Inspect repository integrity and command help.
dits fsck
dits checkout --help

What not to try as a working workflow

Network push, pull, fetch, sync, and network clone are not implemented. The four remote commands return a nonzero error for both local-path and Internet remotes without changing objects, refs, or the working tree. P2P transfers no repository data. FACR, photo-edit, proxy, and VFS paths are experimental and should be evaluated separately from the exact local-history core.

Continue with core concepts, the status and roadmap, and the evaluation trade-offs.