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
Webhook and Event Design Boundary
Reliability and security requirements for a future event-delivery service.
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 has no hosted webhook service, event subscription API, delivery worker, signing secret, retry queue, or repository event stream. No current push, lock, or hosted user event can trigger an external webhook.
Possible design targets
- Versioned event envelopes with stable identifiers, timestamps, and documented ordering limits.
- Authenticated registration and signed deliveries with replay protection.
- At-least-once retry semantics, idempotency guidance, dead-letter handling, and delivery observability.
Prerequisites before implementation claims
- A hosted service and canonical server-side repository event model.
- Tenant authorization, secret rotation, abuse controls, retention policy, and incident procedures.
- End-to-end tests covering duplicates, delay, reordering, endpoint failure, and key rotation.
What can be evaluated today
- Use local Dits hooks only for the hook names and behavior documented by the current CLI.
- Use your automation platform's native filesystem or process triggers for local experiments.
- Do not expose a receiver based on the removed speculative payload examples.