Skip to main content
Work on a project is grouped into numbered rounds. Your first build is Round 1; when that’s landed and you come back for the next batch of changes, you start Round 2. The round chip in the top bar appears once a project has more than one round.

​
Starting a new round

The Start Round N sheet asks one thing — what to call it — and tells you the truth about where you’re starting from:
  • Carried over lists what the previous round left unfinished, keeping its two kinds strictly apart: promises “we couldn’t check yet — our limitation, not your app” versus promises “that didn’t work”. You should never have to guess which is which.
  • If stories are still open in the current round, the sheet says so — “they carry forward — nothing gets stranded.”
  • The sheet deliberately shows no time estimate. There’s no honest data behind “roughly 30 minutes”, so it isn’t said.
  • The server can refuse to start a round (for example, mid-build) — and when it does, you see its actual reason, not a dead button.
Everything you ask for next gets built in the new round, and you can keep adding to it until it starts building.

​
Reading a finished round

Pick an earlier round from the round chip to read its history. History is a reading mode, not a separate screen — same panes, same tabs — with a banner that states exactly what is and isn’t scoped:
Reading Round 1 — 12 stories. Nothing here can be changed. The board shows this round. The conversation and the preview always show your app as it is now.
That second sentence is deliberate: the Kanban board really is filtered to the round you’re reading, but the conversation is one continuous thread per project, and a running app can’t be time-traveled. The banner says so rather than letting you assume more. Back to now returns you to the live round.