Skip to content

Build and deliver

An event model describes what a system does. This section is about what comes after: turning that description into software, and keeping track of how far along each part is.

The Progress board of Acme Commerce with one column per slice status and a card for every slice
The Progress board shows every slice of a project by status, so the whole team sees how far the build has come.

You choose how a slice becomes software, per application, in the application’s settings. Nothing about the model changes when you choose differently.

  • Keep the model as the deliverable. The model is complete and exact enough to hand to a team, to export, or to keep next to code that people write by hand. Studio writes no code.
  • Generate code from the model. Studio renders the code for commands, events, read models, rules and constraints from the model, the same way every time. You preview it, generate it, and review the result before it is merged. You can also let an AI agent add the parts that cannot be rendered.
  • Let a builder or a coding agent build it. A builder is a program that registers with your organization and builds slices on a machine you control, for a stack you choose. Developers can also connect their own coding agent to a board, so the agent models and builds alongside the team.

The first two are covered here. The third is described for developers in For developers; start with Builders.

  • To share the model without building anything, see Share and export.
  • To connect your own coding agent or builder, see For developers.
  • To set up the people, AI providers and integrations that building depends on, see Your organization.