Design archive — not shipped
This page describes a future or historical network, API, P2P, or deployment surface. The current product is a local alpha; there is no working network transfer, hosted server, public API/SDK, or deployable service.
Design Archive
Wire Protocol Design Boundary
A future repository protocol must preserve object integrity and atomic ref semantics before transport optimization matters.
Design, not a shipped service
The current product is a local alpha CLI and library. There is no hosted Dits service, complete repository remote, public API or SDK, managed webhook system, official server image, or supported production deployment. The items below are conditional design targets, not setup instructions or commitments.
Status
No stable Dits wire format, negotiation protocol, authenticated repository service, remote-ref transaction, or network clone exists. Push, pull, fetch, and sync return nonzero without changes. The in-process QUIC stream demo is an experiment, not a repository protocol.
Possible design targets
- Versioned capability negotiation and explicit repository-format compatibility.
- Verified object transfer followed by authenticated, atomic, compare-and-swap ref updates.
- Resumption, cancellation, backpressure, bounded resources, and deterministic failure recovery.
Prerequisites before implementation claims
- A frozen object/ref semantic model and independent compatibility fixtures.
- A reviewed authentication, authorization, confidentiality, and replay-threat design.
- Interoperability, fault-injection, corruption, rollback, and concurrent-update tests.
What can be evaluated today
- Evaluate local object storage and local-filesystem clone.
- Use dits gc --dry-run and dits fsck as local diagnostics, not protocol operations.
- Treat the embedded unauthenticated object server and QUIC demo as narrow experiments only.