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

# Concepts

> The mental model behind no-tickets — phases, push origins, entitlements, roles, epics.

no-tickets describes work in three nouns — **epics**, **features**, and
**fixes** — and one verb: **push**. Everything else in the product (the
dashboard board, the activity feed, billing, agent assignment) is a view onto
those four primitives.

This section is the canonical definition for each term. If a word appears in
the dashboard, the CLI, an error message, or a marketing page, its meaning is
fixed here.

## Pages

* **[Phases](/concepts/phases)** — the five-state machine work moves through:
  ideation → development → testing → review → done.
* **[Push origins](/concepts/push-origins)** — what changed in a project and
  where the change came from (CLI, CI, MCP, dashboard).
* **[Entitlements](/concepts/entitlements)** — what your plan unlocks and how
  feature gating works.
* **[Roles](/concepts/roles)** — humans, agents, and what each can do.
* **[Epics](/concepts/epics)** — grouping work across multiple features and
  fixes.

## How these fit together

```
Epic ────────► Feature ─────► Tasks ──► Pushes ──► Activity feed
   │              │                                       ▲
   │              └─► Fix ───► Tasks ────────────────────┘
   └─► Phase (rolled up from features)
```

A push is the unit of change; an epic is the unit of intent; phases tell you
where the intent is in its lifecycle. Roles and entitlements answer "who can
do this?" and "is it included in your plan?"