Concepts
The terms Blume uses and how they relate: deliveries, phases, plans and tasks, agents, tests and evidence, revisions, reviews, projects, applications and requests.
Blume has a small vocabulary. Each term below names something you can open in the app.
→
Delivery
One outcome and everything needed to trust it: the plan, the tasks, the agents, the evidence and your decisions. “Customers can check out with a saved address” is a delivery. A branch, a pull request or a chat is not.
Read more: Deliveries
Phase
Where a delivery’s work is right now: Start, Plan, Build, Test, Review, Release or Done. Review has two steps, the outcome review and the merge review.
Read more: Phases
Plan and tasks
The plan is the delivery’s spec: the outcome, the acceptance checks that prove it, the approach, the decisions and the tasks. The agent writes it as one Markdown file in your repository. Tasks are its checklist, grouped by phase.
Read more: Plan and tasks, Acceptance criteria
Agent
One conversation in a coding harness, such as a Claude Code session or a Codex chat, connected to Blume through the plugin. An agent can work on several deliveries, and a delivery can have several agents.
Read more: Agents
Test and evidence
A test is a check that the outcome holds. Evidence is the record of a check or an observation: a test result, a screenshot, a link, a summary of the change. Every piece of evidence names the revision it was gathered at.
Revision
One version of the code that was sent for review, pinned to a commit. Revisions are numbered R1, R2 and so on. New code under review makes a new revision, and the earlier one is marked Superseded.
Read more: Pull requests and revisions
Review
A decision only a person makes. There are four kinds: the plan review (“Should the agent build this plan?”), the outcome review (“Does this revision do what was agreed?”), the merge review (“Is this code ready to merge?”) and the release review (“Ship this to the environment?”). An approval belongs to the exact thing it approved.
Read more: Reviews
Project
A group of repositories and folders that belong together, with their applications and deliveries. An agent’s conversation belongs to the project its folder is part of.
Read more: Projects
Application and environment
An application is something that runs for users, such as a website or an API. Its environments are its release steps, for example Canary, then Production.
Read more: Applications and environments, Release
Question and request
A request is anything an agent asks of you. A question asks for an answer. A review request asks for one of the four approvals. Requests wait under Waiting on you on the delivery and in the Requests page.
Read more: Questions and requests