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.
CLI Reference · Design
P2P commands
The parser exists for discovery, but every P2P operation fails before creating or changing local or network state.
Disabled in the alpha
dits p2p does not share, connect, mount, ping, cache, or transfer repository data. Every parsed operation exits nonzero before opening a repository, creating a target directory, changing a cache, or binding a socket.What is parsed
The provisional command family contains share, connect, status, list, cache, ping, and unmount. These names and flags are design scaffolding, not a compatibility promise.
$ dits p2p status
Error: P2P sharing is design scaffolding in this alpha and is disabled.
$ dits p2p connect ABC-123 ./peer-copy
Error: P2P sharing is design scaffolding in this alpha and is disabled.What does not exist
- No rendezvous, signaling, relay, or NAT-traversal service.
- No authenticated peer protocol or shipped P2P encryption scheme.
- No remote mount, cache, repository transfer, or ref transaction.
- No active share, peer-status, or connectivity result.
What must happen before this can ship
P2P needs a threat model, authenticated protocol, version negotiation, atomic repository and ref semantics, interruption recovery, and independent compatibility tests. Track those gates in the roadmap.
Need to copy a repository today
Use local-filesystem clone or an independently verified backup. Remote
push, pull, fetch, and sync also fail closed in this alpha.