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, discover capabilities, and apply saved updates. Supply authenticated setup, profile validation, and durable storage. The Elixir client includes a WebSocket implementation. The TypeScript client uses an application transport.

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.

If the binding selects capability discovery, expose the actor's exact profile, bounded summary pages, selected details, and exact schema resources before normal profile confirmation. Review the discovery flow.

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.