Stories & progress

Plans are broken into stories — small, independently buildable and verifiable pieces of your app. Everything that tracks progress in the workspace is a view over the same stories, using one shared vocabulary, so two panels never describe the same story with different words.

​

The seven story states

Verified and built are both finished stories. The difference is what the checks showed. A built story carries a short note saying which it is: A story that closes as built is not a failed story. It is a story whose proof is incomplete, and the Proof tab shows which promises are still open. The other split that matters is the last two states. Both are “blocked” internally, but they ask opposite things of you: fixing means “we’re on it — ignore this”; needs you means “nothing moves until you look.” When in doubt, the platform errs toward asking you rather than silently parking a story.

​

The progress strip

A slim strip under the top bar tracks the build at whatever fidelity the data allows: per-state story counts and the current story once the plan exists, a simple completed/total bar before that, and a phase label during planning. It hides entirely when there’s nothing honest to show. When a story needs you, the strip says so and clicking it routes you straight to that story.

​

Kanban & Tasks

• Kanban is the macro view — all stories at a glance, in their states. Clicking a story zooms into…
• Tasks — the per-story ladder: the individual steps the agent worked through, and the story’s verification receipts.

​

When a story is genuinely stuck on you

A story that needs a person shows a card explaining exactly what’s needed — an answer, a credential, a judgment call. This is the one place the product uses the phrase “Needs your input”; it’s reserved for real handoffs, never used to dress up a platform fault (those say “Something went wrong” instead). Progress on promises — what was verified, what you confirmed, what couldn’t be checked — lives on the Proof tab.