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
Public SDK Design Boundary
Conditional goals for future client libraries, not installable package documentation.
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
Dits publishes no supported JavaScript, TypeScript, Python, Go, or Rust SDK. Names, package-install commands, generated clients, compatibility promises, and code examples from earlier drafts did not correspond to released artifacts.
Possible design targets
- Small clients generated from one versioned API or protocol contract.
- Consistent error, retry, cancellation, streaming, and authentication semantics across languages.
- Published support matrices, signed artifacts, examples, and conformance tests for each release.
Prerequisites before implementation claims
- An implemented and stable API or remote protocol to wrap.
- Package ownership, release automation, vulnerability response, and deprecation policy.
- Cross-language fixtures proving byte identity and repository transaction behavior.
What can be evaluated today
- Inspect the local Rust workspace as implementation source, not as a stable third-party SDK contract.
- Invoke documented local CLI commands from controlled tooling when their human-readable output is sufficient.
- Pin the exact alpha commit and verify behavior before depending on internal modules.