Glossary

A plain-English dictionary of the words you'll see across Operum. No jargon, no assumptions — just what each term means and why it matters.

Core Concepts

The seven ideas that everything else builds on.

TermWhat it means
AgentA specialized AI teammate that handles one kind of work — planning, coding, testing, and so on. Your Operum team is a group of these agents working together.
PM (Project Manager)The lead agent and the one you talk to. It takes your requests, breaks them into work, and coordinates the other agents.
PipelineThe step-by-step path every task follows from idea to finished — like an assembly line (design → build → test → review → done).
IssueA single piece of work: a feature to build, a bug to fix, or a task to do. Everything starts as an issue.
Pull Request (PR)A finished change waiting for approval before it becomes part of the live product — a "ready for sign-off" package.
MergeApproving a Pull Request so its change goes live in the product.
LabelA tag on an issue that shows its current stage (e.g. "ready for dev", "in testing") and which agent owns it.

More Terms

Other words that come up as you work with your team.

TermWhat it means
BacklogThe list of work that's been captured but not started yet.
Turbo ModeWhen on, agents proactively push work forward without waiting for you to prompt each step.
Auto-MergeWhen on, approved-and-tested changes merge automatically — no manual sign-off needed.
QA (Quality Assurance)The testing stage where a QA agent checks a change works before it can ship.
Branch / WorktreeA private workspace where an agent makes changes without affecting the live product or other agents.
Knowledge BaseThe team's shared memory: project facts, decisions, and context that all agents can read.
FounderYou — the human owner who sets direction and approves key decisions.
HandoffWhen one agent finishes its part and passes the work to the next agent in the pipeline.

Where to next?