Core concepts
Runs, tickets & tasks
The core objects Premia works with.
Tickets
A ticket is the unit of work — usually a Linear issue (or a manual/CLI run). Its title and description are the task Premia plans against.
Runs
A run is one execution of a pipeline step. A ticket produces a tree of runs:
- A root run (the Planner) breaks the ticket into per-repo tasks.
- Each task becomes a child run that flows through the rest of the pipeline (Developer → Reviewer → QA → …) for that repo.
So a single ticket that touches three repos fans out into parallel work, then converges. The run view groups the root and its children together.
Your plan's concurrency limit counts top-level runs (tickets in flight), not the child fan-out — so one multi-repo ticket never counts against itself. See Billing.
Sub-tickets
When the Planner splits a ticket across repos, each repo's work shows up as a sub-ticket under the parent — each with its own PR and status.
What's next
- The pipeline — the default plan → dev → review → QA → merge flow.
- Status lifecycle — how a run moves from queued to merged.