Slices
A slice is exactly one behavior of the system, drawn as one column on the board. Everything needed for that behavior sits in the column: the screen, the command, the event, the read model and the examples that prove it works.
Slicing the model this way has a practical payoff. A slice is small enough for one person to understand, to discuss with the business, to give to a builder or an AI agent, and to check on its own. You can move a slice, copy it, mark it done or block it without touching the rest.
Studio offers four kinds of slice. When you add a slice, Studio asks you to choose a vertical slice type.
| Kind in Studio | What it does | Acme Commerce example |
|---|---|---|
| State Change | A person asks for something, and facts are recorded. | AddToBasket |
| State View | A person looks at something built from earlier facts. | BasketView |
| Automation | The system reacts to a fact and acts on it. | EmptyBasketAfterCheckout |
| Translator | Facts cross the border between two areas. | ListProduct, PublishOrder |
State change: someone asks, something happens
Section titled “State change: someone asks, something happens”Studio describes a state change as UI drives a command that produces events. This is the most familiar slice: the shopper presses Add to basket, the shop checks the request and records what happened.
The command is where the rules live. AddToBasket reads what the shop knows about the product and refuses it when it is out of stock. A state change slice is also where you ask what a command must know, what it may refuse and which facts it leaves behind. Read more in Commands, events and read models.
State view: someone looks at something
Section titled “State view: someone looks at something”A state view is described as UI reads a projection built from events. It changes nothing. It turns the facts that already happened into something a person can read.
BasketView builds the basket from every line that was added, changed or removed, and the Basket screen shows it. A view can only show what earlier slices record. Studio helps you keep that honest: if you drag a view to the left of the events it depends on, the board refuses the drop and says that those events are not produced before this position.
Automation: the system reacts
Section titled “Automation: the system reacts”An automation is the system reacts to events and issues commands. No person is involved, so there is no screen: it watches for a fact and acts.
When checkout completes, EmptyBasketAfterCheckout empties the basket. An automation can start from an event, from a timer, or from a custom description of when it should run. Read more in Automations and translations.
Translation: facts cross a border
Section titled “Translation: facts cross a border”Studio calls this slice type Translator: it translates external events into internal commands, and the same idea works the other way round. It is how one area of the business tells another what happened, without either reaching into the other.
ListProduct hears that the Catalog published a product and records it in the shop’s own words. PublishOrder does the reverse: it turns the shop’s private fact that checkout completed into a public OrderPlaced for the rest of the company.
A slice grows through its life
Section titled “A slice grows through its life”A slice has a status, from Not started through Draft, Analysis and Ready for implementation to In progress, Ready for review and Done, with Blocked and Waiting for user interface for the times it cannot move. The status is how a team sees progress across a whole model. The full list and what each means is in Statuses and colors.