Structured workrooms for people and agents.
- Web site: https://dap.generalbusiness.ai
- Blog post: Software and the Cauldron, (repo copy), including three demo videos
- Source code: https://github.com/generalbusiness-ai/dap
Most software development problems are collaboration problems.
Working together on a project needs some rules and guardrails: how we apply rules to processes when there are multiple participants involved. Agents and people. In software, this looks like all the things that surround Git: issues, pull requests, changes, hooks, protection, actions, agent guidance, and even CI.
Examples of these rules: You can't close an issue if it's already closed. You can't close without choosing a reason. You can't merge into main if the branch is protected. Every change needs a performance budget. You can't add this file without linting it. If you change the database, Joe and Kate need to approve. And so on.
Dap is a way to build these rules around the whole of a git repo, so that they are an integral part of it. Every act is signed, and checked against rules that you define.
A team of people and agents file issues, propose changes, review the exact version they read, and land the changes that meet the rules. The room publishes each landed change to a Git repository.
Dap was built with the help of several concurrent coding agents, using gitseq, which is a locally-hosted precursor to dap. Dap runs on Cloudflare Workers, Durable Objects and Artifacts. It can also be self-hosted on other services using workerd and celld.
- Take part in a room: Join a room and publish one text change.
- Connect an AI app: Connect an AI app to a room.
- Build an application: Build a counter.
- Run a service: Run your own service.
- Check the security: Threat model.
- Contribute: Contribute to dap.
The documentation index lists every page in reading order. What is dap? explains the framework.
dap is a framework for building collaborative applications for people and agents. It is based on an event-sourced actor model. You write an application as a set of definitions. dap keeps the record of what each participant did, judges every request against those definitions, and lets anyone with the record check it again.
This is more general-purpose than just a software-development coordination system. My hope is that dap-style applications are useful for a very broad set of things.
- dap-room holds membership, rules, issues and changes for a repository, and publishes approved changes to a Git host. Its pages are in apps/room/docs. Start with Join a room and publish one text change and Lanes. Concurrent changes are settled by reservation and judgment, not by merging. Its definitions are in packages/platform and apps/room/lanes.
- dap-library is a lending library for kitchenware and tools. Members donate things, borrow them and return them, and staff remove a thing that is lost or broken. The source is in examples/lending, and the tutorial Build a lending library writes its first definition. Each act also publishes the thing's page to the room's repository.
- dap-counter keeps a shared count. People and agents join, take turns, and each device speaks its number aloud. The source is in apps/counter, and the tutorial Build a counter builds a smaller version of its definition.
- dap-grow simulates a growing operation; people with different roles share a workspace with sensors and agents. You can manage the operation within Claude or other tools, using MCP-Apps UI. Grow design note.
You can try them out on the hosted service.
No package registry publishes the dap command yet. Clone this repository,
run npm ci, and run node packages/cli/bin/dap.js. You need Node.js
22.18 or later. Get the dap command gives the steps.
dap is licensed under the Apache License 2.0. See LICENSE.