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
Peer-to-Peer Design Boundary
Direct repository exchange remains a design question, not a usable sharing workflow.
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
The dits p2p parser is discoverable so users receive an explicit diagnostic, but every P2P operation returns a nonzero error before validating paths, creating directories, opening a repository, changing cache state, binding a socket, or mounting anything. There is no rendezvous, discovery, NAT traversal, relay, peer authentication, or repository transfer.
Possible design targets
- Peer identity and authorization tied to an explicit repository capability model.
- Verified object negotiation followed by atomic ref updates and deterministic conflict handling.
- A transport strategy that documents direct, relay, privacy, metadata, and availability trade-offs.
Prerequisites before implementation claims
- A complete remote CAS/ref protocol and stable compatibility contract.
- A reviewed threat model covering join-code entropy, replay, impersonation, relay trust, and denial of service.
- Interoperability and fault tests across disconnects, address changes, partial data, and concurrent ref updates.
What can be evaluated today
- Use dits p2p --help only to inspect the disabled command surface.
- Use local-filesystem clone for a current repository-copy workflow.
- Use independently managed transfer and backup tools when data must cross machines.