Skip to main content
Dits LogoDits
Local alpha

Exact history first. Explainable media next.

Dits separates the storage foundation that works locally from the semantic and collaboration layers that still need proof.

Current local path

From a working file to a verifiable snapshot

  1. Step 1
    Chunk large content
    FastCDC chooses variable-size boundaries from the content, so a local insertion usually disturbs nearby chunks rather than every later offset.
  2. Step 2
    Address exact bytes
    BLAKE3 identifiers name stored content. Reads can verify that an object still matches the identity recorded by its manifest.
  3. Step 3
    Commit a project state
    Manifests and history connect paths to exact content while Git-shaped commands expose commits, branches, tags, diffs, merges, and checkout.
  4. Step 4
    Reconstruct and verify
    Checkout reassembles ordered chunks into exact local files. Verification and recovery behavior are being hardened before the format is frozen.
Experimental
Represent the pipeline, not only its exports
FACR, photo edit logs, dependency records, project structure, and renditions explore a graph that links immutable sources to explicit decisions and derived outputs.

This model must preserve the difference between an exact source, a deterministic rendition, and an approximate or perceptual representation. It is not yet a stable cross-tool format.

Roadmap
Exchange verified objects safely
A future remote protocol will negotiate missing objects, verify every import, resume interruption, update refs atomically, and enforce identity and authorization.

HTTP comes first. Bundles, QUIC, or peer transports are optional later only if they preserve the same semantics and pass one conformance suite. No network transfer ships today.

Important boundary

Chunk reuse is not the same as understanding an edit

A full media re-encode can alter nearly every byte even when the visible change is small. Generic chunking cannot reconstruct artistic intent. Dits must capture explicit edit decisions or imported timeline data where possible and retain final bytes when exact archival recovery requires them.

The durable rule

Never confuse a proxy, decoded frame, or perceptual match with the exact archival source.

Inspect the design and its open questions

Architecture guideRoadmap and gates