Statuses and colors
Studio uses statuses to show where work stands, and colors to say what kind of thing something is. This page lists them all.
Slice statuses
Section titled “Slice statuses”Every slice has a status. Select Change status in the slice header, or open the slice’s menu and choose Set status, to change it. See Track progress.
| Status | What it means |
|---|---|
| Not started | Nobody has worked on the slice yet. |
| Draft | The slice is sketched on the board but not settled. |
| Analysis | The team is working out the details: fields, rules and examples. |
| Ready for implementation | The model is settled and the slice can be built. |
| In progress | The slice is being built. |
| Ready for review | The slice has been built and is waiting for someone to review it. |
| Done | The slice is built and accepted. |
| Blocked | The slice cannot be built yet. |
| Waiting for user interface | The slice is waiting for the builder of its user interface. |
A few things to know:
- Blocking a slice asks two questions. Why can it not be built? and Questions that need an answer, one per line. A slice with a block reason always shows as Blocked. The Progress board lists these questions.
- Studio sometimes manages the status for you. While a slice is assigned to the System member or to an AI agent, Studio moves it along and says so. While Studio generates a slice, its status cannot be changed until the generation has ended. When a generation moves a slice to In progress and then Ready for review, a failed run restores the previous status.
- Features have a simpler set. A feature can be raised to Draft, Analysis or Ready for implementation. The working statuses are set on each slice.
- Linked issues can follow along. When an application turns on Issue status sync, a slice that becomes done closes its linked issues, and the reverse. See Build and deliver.
The Progress board under Project options shows every slice by status, and you can filter it by event model, module or feature. See Build and deliver.
Sticky note colors
Section titled “Sticky note colors”A sticky note is yellow until you change its color. The colors have a shared meaning, so a board can be scanned at a glance. They are the same on every board and canvas.
| Color | Meaning |
|---|---|
| Yellow | A question. This is the default. |
| Pink | A risk. |
| Green | A decision. |
| Blue | An assumption. |
| Orange | Free to use as your team likes. |
| Purple | Free to use as your team likes. |
Element colors on the board
Section titled “Element colors on the board”The event model board uses color to tell its elements apart.
| Color | Element |
|---|---|
| Blue | Command |
| Orange | Event |
| Green | Read model |
| Yellow | Sticky note |
The sticky note colors above are a separate palette: a yellow sticky is yellow because it is a question, not because it is an element.
Build statuses
Section titled “Build statuses”When a builder builds a slice, the slice shows the status of its latest build. Open the build of a slice to see its progress, attempts, specification results and assumptions.
| Status | What it means |
|---|---|
| Building | A builder is working on the slice. |
| Built | The build finished. |
| Nothing to build | The slice needed no work. |
| Blocked | The build cannot go on. |
| Failed | The build did not succeed. |
| Builder stopped answering | The builder went quiet while it held the work. |
| Ran out of time | The build did not finish before its deadline. |
| Cancelled | The build was stopped. |
A build can also report assumptions to review: gaps the builder filled in. Accept one if the builder filled the gap the way it should be filled, or dismiss it, for example once the model says it. When the builder’s own results and the board’s run of the specifications differ, the build says that they disagree on a number of specifications.
Specification results
Section titled “Specification results”| Status | What it means |
|---|---|
| Not run | The specification has not been run. |
| Running… | A run is in progress. |
| Last run succeeded | The model behaves as the example says. |
| Last run failed | The model behaves differently. |
| Last run was inconclusive | The run could not reach a verdict. |
| Could not run | The run did not start. |
Issue statuses
Section titled “Issue statuses”Your own reports are listed under My issues, each with a State and its Last activity. A report you have just sent shows as Reported. See Get help.
Issues that are linked to a slice show their own state, Open, Closed or Unknown, taken from the tracker the issue lives in. See Link slices to issues.