About DASP
DASP grew out of a practical integration problem: the actor keeps working, but its client disconnects. The next connection needs a reliable account of what happened.
Mike Hostetler extracted the session contract from work on Jido and its agent tooling. Publishing it gives other builders something concrete to inspect, test, and challenge.
A common boundary
The goal is a shared contract between an actor host and its clients. Commands, saved outcomes, and recovery should have the same meaning across languages.
Jido and the BEAM informed the work. DASP does not require either. The Elixir client uses Jido Signal; the protocol and TypeScript client remain independent of that library.
Open for review
DASP is a working draft. The next useful evidence is an implementation that can survive the failure cases in the contract.
If you are building a similar system, bring a concrete example: a command, a failed connection, or a recovery rule that does not fit. Share feedback or review status and open decisions.
The DASP-Protocol organization maintains the project. Maintainers review changes to the core, profiles, bindings, and clients. The project license is still being selected.