# Glossary

> The Dobby words you meet in the dashboard, the terminal and these docs, each with a link to the page that explains it.

The dashboard shows the same text behind its info icons.

## 5-hour window

Your plan also has a 5-hour limit. Dobby spreads the week across these windows so one busy window does not use up the week. [More](/docs/pacing.md#the-5-hour-window)

## Backlog

Tickets that are written but not queued. Nothing is built until you or the Engineering Manager queues one. [More](/docs/how-it-works.md#tickets)

## Billing

Plan mode runs on the part of your Claude plan you do not use. API key mode spends dollars, with a daily cap. [More](/docs/billing.md#which-one)

## Builder

The role that writes the code for a ticket, on its own branch, inside the sandbox. [More](/docs/roles.md#builder)

## Chief of Staff

The role that sends you a short brief every morning and evening. [More](/docs/roles.md#chief-of-staff)

## Classifier

What decides which safety category a change belongs to, such as payments or auth. The model is the default. [More](/docs/safety-categories.md#categories)

## Code Reviewer

The role that reviews every pull request Dobby opens and posts its findings on GitHub. [More](/docs/roles.md#code-reviewer)

## Done when

The line the Tester checks the finished work against. [More](/docs/how-it-works.md#tickets)

## Engineering Manager

The role that plans the work. It moves tickets from the backlog to the queue and writes new ones. [More](/docs/roles.md#engineering-manager)

## Goals

The larger outcomes your tickets belong to. They come from GitHub milestones or the Goals list in a project's dobby.md. [More](/docs/how-it-works.md#goals)

## Ideas

Suggestions from the Product Manager, the Engineering Manager and the Talent Scout. Turn one into a ticket or dismiss it. [More](/docs/roles.md#product-manager)

## Merging

The minimum every merge must meet: merge on its own, a strict review first, or you merge it yourself. [More](/docs/what-waits.md#the-floor-for-every-merge)

## Needs you

Things Dobby will not do alone: a merge you asked to approve, a deploy, or a question from a builder. [More](/docs/what-waits.md#needs-you)

## Paused

Stopped on purpose. A pause can cover everything, one part, one project or one ticket, and ends when you resume it. [More](/docs/pause-and-resume.md#pause-one-part)

## Product Manager

The role that ranks problems against your goals and writes idea cards and specs for large tickets. [More](/docs/roles.md#product-manager)

## Queue

Tickets marked ready, in the order builders will take them. Reorder it to change what gets built first. [More](/docs/how-it-works.md#tickets)

## Ready

Queued and waiting for a free builder. [More](/docs/how-it-works.md#tickets)

## Review cap

How much of the 5-hour window reviews may use. It can be higher than the builders' share, because reviews unblock merges. [More](/docs/config.md#reviewcap)

## Safety preset

How much Dobby may merge without you. Balanced, Strict or Autonomous. You can override single categories. [More](/docs/what-waits.md#safety-presets)

## Size

S, M or L, a rough measure of how big a ticket is. It sets how much of your week Dobby expects the ticket to use. [More](/docs/write-a-ticket.md#pick-a-size)

## Stop at

The share of your weekly plan Dobby may use. The rest of the week is yours. [More](/docs/pacing.md#the-weekly-cap)

## Supporting role

A smaller role that runs only when a ticket or a command needs it. [More](/docs/roles.md#supporting-roles)

## Talent Scout

A daily run that picks one role, looks for better skills for it and reviews the last 24 hours. Any change it makes arrives as a pull request. [More](/docs/roles.md#talent-scout)

## Tester

The role that checks a finished build against the ticket's done-when line. It can read files but not change them. [More](/docs/roles.md#tester)

## Ticket

A unit of work with a project, a title, a done-when line, a size and a priority. Everything Dobby builds starts as one. [More](/docs/how-it-works.md#tickets)