Skip to content

Glossary

Words in the examples come from the Acme Commerce sample project. The ideas behind most of these terms are explained in Event modeling.

Whoever does the work in a row of the board: a person using screens (UI Actor), the system acting on its own (System Actor) or an AI conversation (Chat Actor). See Screens and personas.

An AI teammate in your organization. Studio has a fixed roster: Atlas models, Merlin writes code, Quill writes documentation, Sherlock reviews, Echo carries the conversation, Hunch suggests what to model next, and Iris designs screens. A maintainer gives each agent a provider and a model. See Work with AI.

One system that a team builds, inside a project. An online shop is one application. Acme Commerce has five: Acme Catalog, Acme Shop, Acme Sales, Acme Purchasing and Acme Warehouse. See Modules and features.

A slice where the system reacts to a fact and acts on it, with no person involved. For example, EmptyBasketAfterCheckout empties the basket once an order is placed. See Automations and translations.

A ready-made starting point for an application’s screens, with templates you can use and a preview you can run with its own sample data. See Design screens.

A free-form board in a domain for the early, messy thinking: events written as facts, sticky notes, regions and chat bubbles. Events can be moved from it onto an event model. See Discover your domain.

Software that turns modeled slices into code, on any machine that can reach Studio. A builder registers itself and builds nothing until a maintainer approves it. See Build and deliver.

Something a person or the system asks for. A command is an intent and can be refused. Commands are blue on the board. See Commands, events and read models.

A typed value the business talks about, such as a quantity, an order number or an email address. A concept can carry rules that hold everywhere it is used, and can be marked as personal information. See Discover your domain.

A rule about what must never happen twice, such as two customer accounts with the same email address. See Commands, events and read models.

A diagram of an application’s domains and how they relate through the events they publish and consume.

One area of the business inside an application, such as Storefront or Warehouse. A domain owns the event models, brainstorming boards, personas, concepts, constraints and other canvases that describe that area. See Modules and features.

A fact that happened, written in the past tense and never taken back. Events are orange on the board. See Commands, events and read models.

The board that describes one domain as a timeline, read left to right. See Event modeling in Studio.

One kind of thing a domain keeps a history of, such as a basket or an order. An event source says what identifies each one and which streams it has.

A group of related behavior inside a module. The Shop module has the features Browse, Basket, Checkout and My orders. Features can nest. See Modules and features.

A problem or gap that Studio points out on a board, such as a slice with no specification or a field that nothing fills. Each finding says why it matters and suggests a fix.

A named starting situation that several specifications can share, either events that already happened or the state a read model is in. See Specifications and Play.

The three parts of a specification: what was already true, what happens, and what should be the result. See Specifications and Play.

How an application’s modeled behavior becomes code. The four modes are Screenplay only (the model is the deliverable), Static code, Static code + AI and AI only. See Build and deliver.

The trail of where a value comes from. Select an element and ask Where does this value come from? to follow it back through read models, events and commands.

An organization role. Maintainers invite and remove people, assign seats, set up AI and integrations, and can see and change every project. See Your organization.

The Model Context Protocol, a standard way for an AI agent to work with a tool. Studio offers an MCP connection so that agents can read and change your organization’s models. See For developers.

A screen written as an HTML and CSS page and attached to a screen. See Design screens.

A whole area of the business on a board. Modules hold features. See Modules and features.

Your company or team in Studio. It holds the people, the AI setup, the integrations and the billing, and its projects never mix with another organization’s. See Your organization.

A description of one kind of person in a domain: who they are, what they want and which roles they hold. Personas can be given to actors, used in specifications and used in a preview. See Screens and personas.

Runs an event model as if it were the finished application, in a sandbox. See Specifications and Play and Play an event model.

A named rule that says who may do what. It admits some callers and turns the rest away. Policies belong to the whole application. See Screens and personas.

Draws a screen with sample data, optionally as a particular persona, without running the whole model. See Design screens.

The top level of the work, typically one per team. Everything a team builds is inside a project. See Modules and features.

The recipe that builds a read model from events. When this event happens, change that value. See Commands, events and read models.

A way to capture an existing system, with a separate tool, so that Studio can help you work out a model of it. It records only names of tables, columns and endpoints, never the data. This feature is in beta. See Discover your domain.

An event that an application publishes as a contract for the rest of the company. See Automations and translations.

How a screen asks a read model a question, such as the basket with this id. See Commands, events and read models.

What someone looks at afterwards, built from events. Read models are green on the board. See Commands, events and read models.

A named kind of access defined in an application, such as Shopper or SalesManager. Personas hold roles, and policies and specifications use them. Do not confuse it with an organization role, which is either Maintainer or Member.

What a person sees and clicks, attached to a slice. See Screens and personas and Design screens.

The text format in which Studio can export and import an event model, in files that end in .play. See Share and export.

A license for one person to use Studio. A person needs an assigned seat to sign in and work. Maintainers assign and free seats. See Your organization.

What an application starts with: named collections of starting events. Play and Preview use it as sample data.

A screen drawn with a pen, boxes and labels, attached to a screen. See Design screens.

One behavior of the system, drawn as one column on the board. The four types are State Change, State View, Automation and Translator. See Slices.

A concrete example of a slice’s behavior, written as Given, When, Then. See Specifications and Play and Check a slice with specifications.

A slice where a person asks for something and facts are recorded. See Slices.

The stages that something goes through, such as placed, paid, packed and shipped, and the events that move it along. It follows a read model and never decides on its own.

A slice where a person looks at something built from earlier facts. See Slices.

A note on a board. Its color says what kind of note it is: yellow for a question, pink for a risk, green for a decision, blue for an assumption. See Statuses and colors.

A named path through the board, such as a user journey, that you can step through and play. See The event model board.

A separate line of history within an event source. Every event source starts with one called Default.

A slice, feature or module that Studio proposes for a feature. You preview it on the board and accept or dismiss it. See Work with AI.

A frame for screens. A template chosen on a module or feature applies to the screens inside it, unless a screen chooses another. See Design screens.

A slice that carries facts across the border between two areas, either bringing an outside fact in or publishing one of your own. Studio’s slice type is called Translator. See Automations and translations.

How an application looks and what its screens are built from: component libraries, styling and blueprints. Changes are a draft until you review and apply them. See Design screens.

What happens step by step once something starts a run, with triggers, waits and approvals.