A project in the web app

Every project in the web app has four tabs: Overview, Spec, Plan and Validate. They follow the work. You write what to build on Spec, order it on Plan, and check what agents built on Validate. Overview tells you where the project stands.

The four tabs

Tab	What it's for
Overview	Progress, your connections, and what your agents remember.
Spec	The vision, the story map, the data model and design. See The Spec tab.
Plan	The build order, its phases, and build runs. See The Plan tab.
Validate	What agents built and what needs you, release by release, up to Go live. See The Validate tab.

On a new project, Plan and Validate are locked until the five vision questions are answered and the story map exists. A locked tab shows a lock and, when you tap it, what it's waiting for.

The Validate tab carries a count when stories need you.

Every story opens on the same story page, with its own tabs: Spec, Plan, Tests and Review. See The story page.

Phone and desktop

The phone and the desktop show the same project, the same stories and the same words. What changes is where things sit.

	Desktop	Phone
Tabs	In the header, across the top.	In a bar at the bottom of the screen. The bar shrinks to the current tab's name as you scroll; tap it to bring the tabs back.
Filters	In a strip under the header.	Behind one filter pill at the top right.
Story cards	Show their status as a pill.	Show their status as the card's colour and a small word. See Story cards.
A story	Opens in a panel beside the map.	Opens full screen.
The assistant	A column at the side, or a thread under the page.	A circle beside the tab bar. As you scroll it grows into a field: "Ask about this spec…".

The Overview

Overview opens with the project's name and three cards.

• Progress: a line saying where the project is, then three numbers: In the spec, To build and Built. Each opens its tab. Under them, a chart shows how many stories sat in each status over time.
• Connections: one row for your agent and one for the repository, with its GitHub App. A row turns amber or grey only when something needs you, such as an agent that hasn't synced for a while. Use Connect an agent or Reconnect to fix it. See Connecting your agent.
• Agent memory: the latest Decisions logged on the project, and the Examples agents should follow, each with a link to the full list.

Until the map has stories, Overview also shows the interview card, which takes you to the vision questions. On desktop, the activity log opens from the Progress card.

Project settings

Whoever administers the project sees Project settings at the bottom of Overview. It holds the things you set once:

• Story keys: the prefix of every story's key, such as PB in PB-42. Changing it renames every key at once. The old keys keep working.
• Test reporting: whether CI is reporting test results, the prompt that sets it up, and the CI keys, which you can revoke.
• Ownership: moving a personal project into a workspace. This can't be undone, so it lives here and not on Overview. A workspace project says it belongs to its workspace.

Notifications

The bell collects what happened while you were away: stories completed, criteria failing, a regression, a blocker raised, a release ready, criteria with no tests, and a new build run waiting for your approval. Each one links to the story or run it's about.