Start building

Start at the boundary you own: the client that requests work, or the host that runs it.

DASP has experimental Elixir and TypeScript clients. You can run their recorded examples today. A production binding and persistent example host are still to be built.

Connect a client

Use a language client to construct requests, check replies, and apply saved updates. Supply your transport, profile validation, and storage.

Choose Elixir or TypeScript. Each page includes a recorded example, setup, and API details.

Expose an actor

Implement a host around your actor runtime. The host owns admission, saved outcomes, and recovery. Its storage must preserve those decisions before it reports success.

Define a profile and binding so both sides agree on commands and delivery.

Inspect the contract first

Follow a command to see complete messages and recovery. Then use the specification for requirements and conformance coverage for the evidence behind each check.