Skip to main content
Dits LogoDits
Documentation
Project

Status and roadmap

The current product boundary and the evidence gates Dits must pass before formats, media semantics, or collaboration can be called stable.

Current local paths
Available to evaluate
  • Local repository initialization, add, commit, history, branch, merge, tag, diff, and checkout workflows
  • FastCDC chunking and BLAKE3-addressed local object storage
  • Hybrid handling for text and large binary assets
  • Byte-exact local reconstruction and integrity-oriented reads
  • MP4 structure-aware code plus experimental FACR, photo, proxy, and VFS paths
Limitations
Do not infer beyond this boundary
  • Alpha software: evaluate on disposable or independently backed-up projects
  • Network push, pull, fetch, sync, and network clone do not transfer repository data
  • P2P, QUIC transport, a hosted service, public SDKs, and NLE plug-ins are not shipped
  • FACR, photo edit logs, proxies, VFS, and broad media compatibility remain experimental

Dependency-ordered milestones

Dates are intentionally absent. Each milestone advances when its exit evidence exists, not when a calendar says it should.

1. Credibility and data safety
Now
Crash-safe writes, recovery, compatibility fixtures, and truthful docs.
2. Stable format and scale
Next
Versioned deterministic objects, bounded-memory ingest, packs, indexes, and trees.
3. Semantic media
Research
Source, edit, dependency, timeline, and rendition records proven on real workflows.
4. Verified collaboration
Later
A transport-independent remote CAS protocol with atomic refs and recovery tests.

Gate 1: credibility and data safety

Crash-safe writes, deterministic reads, corruption recovery, a real-media fixture corpus, and documentation checks. This is the active priority.

Gate 2: stable format and scale

Versioned canonical objects and manifests, bounded-memory ingest, packs, indexes, tree objects, garbage collection, and representative end-to-end benchmarks.

Gate 3: semantic media

Explicit source, edit, dependency, timeline, and rendition records that survive at least one real game/virtual-production workflow and one post-production workflow.

Gate 4: verified collaboration

A transport-independent protocol with have/want negotiation, resumable verified import, compare-and-swap refs, identity, scoped authorization, expiring lock leases, version negotiation, and failure injection.

Not near-term priorities

  • A generic AI creative assistant.
  • Real-time multi-user editing before safe asynchronous collaboration.
  • P2P or QUIC before one protocol works over HTTP.
  • Broad SDKs over an unstable object model.
  • Kubernetes or enterprise scale claims before a deployable service exists.
  • Petabyte, savings, or cost claims without public workload evidence.