> ## Documentation Index
> Fetch the complete documentation index at: https://docs.buildbetter.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Projects Overview

> Run your product roadmap from inside BuildBetter — every project grounded in real customer signals, ARR, and engineering activity

Projects is BuildBetter's roadmap hub. Every project is a tracked item that brings together the customer signals driving the work, the ARR on the line, the people and PRs delivering it, and a live status view — so you can answer five questions on one screen:

1. **What should we work on?** — Triage and the Decisions tab
2. **What are we currently working on?** — This week + Active
3. **Who is working on what?** — assignee avatars on every row
4. **Why are they working on it?** — signals, customers, and trend rollups
5. **What's the status / what's next?** — substatus chips, blockers, and next actions

## Where Projects Live

Projects start life as tracked items in [Triage](../Triage/overview). When you **promote** a triage item, it moves to `/projects` with `in_triage: false` and a status of `in_progress`. From that point on, the Projects Hub is its home.

<Info>
  Projects is gated by the `projects` feature flag. If you don't see `/projects` in the sidebar, contact your workspace admin to request access.
</Info>

## Core Concepts

| Concept            | What It Means                                                                                                                                           |
| ------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Project**        | A tracked item with `in_triage: false`. Has a title, type, priority, status, stage, optional area, and links to signals/calls/PRs/tickets.              |
| **Stage**          | Ordered lifecycle position: Triage → Scoping → In progress → In review → Ready to merge → Shipping → Released → Stable. Drives which rail cards appear. |
| **Status**         | Real-time substate (Drafting, In review, Ready to merge, Blocked, Shipping, Done). More granular than stage.                                            |
| **Priority**       | P0, P1, P2, P3 — urgency for sort and triage.                                                                                                           |
| **Area**           | Optional taxonomy path (e.g., `Features > Search > Filters`). Determines where the project shows up in Areas view.                                      |
| **Initiative**     | A user-created Projects V2 grouping (e.g., "Expansion", "Retention") that spans multiple projects.                                                      |
| **DRI / Assignee** | The owner. Avatars carry a small provenance badge — **L** for Linear-author match, **G** for GitHub PR author, **·** for manual.                        |
| **ARR rollup**     | Cumulative ARR from every distinct customer company linked to the project's signals.                                                                    |

## What's on the Pages

<CardGroup cols={2}>
  <Card title="List & Views" icon="grid" href="/pages/Projects/list-and-views">
    Mine / All / Areas views, list and kanban layouts, the AI Roadmap banner, and how taxonomy areas and initiatives organize work.
  </Card>

  <Card title="Project Detail" icon="layer-group" href="/pages/Projects/project-detail">
    The two-column detail page: timeline + signals on the left, rail cards (Status at a Glance, Rollup, Integration Issues, People & Signals, Post-Release Monitor, Close the Loop) on the right.
  </Card>

  <Card title="AI Features" icon="sparkles" href="/pages/Projects/ai-features">
    AI Roadmap clustering, Similar Projects detection, Suggested Signals, AI status suggestions, and the project rollup.
  </Card>

  <Card title="Workflows" icon="route" href="/pages/Projects/workflows">
    Create a project, update scope from a call, ship a status update, attach signals and calls, run close-the-loop after release.
  </Card>
</CardGroup>

## How Projects Connect to the Rest of BuildBetter

* **Triage** → promote a tracked item to make it a project
* **Signals** → drive priority via volume, ARR, and trend; attach to projects to record customer demand
* **Calls** → link a call and attach its signals in one move
* **Linear / Jira** → attach tickets via Integration Issues; assignees auto-populate from Linear author mappings
* **GitHub** → linked PRs feed the Status at a Glance card, trigger stage transitions, and roll up into project metrics
* **Knowledge** → close-the-loop drafts and project rollups can be exported to knowledge pages

<Tip>
  The list page subscribes to your org's tracked-item event stream and live-updates as PRs merge, statuses change, and signals attach. No manual refresh needed.
</Tip>