Glossary

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

Backlog

Tickets that are written but not queued. Nothing is built until you or the Engineering Manager queues one. More

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

Builder

The role that writes the code for a ticket, on its own branch, inside the sandbox. More

Chief of Staff

The role that sends you a short brief every morning and evening. More

Classifier

What decides which safety category a change belongs to, such as payments or auth. The model is the default. More

Code Reviewer

The role that reviews every pull request Dobby opens and posts its findings on GitHub. More

Done when

The line the Tester checks the finished work against. More

Engineering Manager

The role that plans the work. It moves tickets from the backlog to the queue and writes new ones. More

Goals

The larger outcomes your tickets belong to. They come from GitHub milestones or the Goals list in a project's dobby.md. More

Ideas

Suggestions from the Product Manager, the Engineering Manager and the Talent Scout. Turn one into a ticket or dismiss it. More

Merging

The minimum every merge must meet: merge on its own, a strict review first, or you merge it yourself. More

Needs you

Things Dobby will not do alone: a merge you asked to approve, a deploy, or a question from a builder. More

Paused

Stopped on purpose. A pause can cover everything, one part, one project or one ticket, and ends when you resume it. More

Product Manager

The role that ranks problems against your goals and writes idea cards and specs for large tickets. More

Queue

Tickets marked ready, in the order builders will take them. Reorder it to change what gets built first. More

Ready

Queued and waiting for a free builder. More

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

Safety preset

How much Dobby may merge without you. Balanced, Strict or Autonomous. You can override single categories. More

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

Stop at

The share of your weekly plan Dobby may use. The rest of the week is yours. More

Supporting role

A smaller role that runs only when a ticket or a command needs it. More

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

Tester

The role that checks a finished build against the ticket's done-when line. It can read files but not change them. More

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