Terms are defined here once and linked from everywhere else.
Acceptance criteria
The checkable statements in a specification that decide whether work succeeded. Verification tests against them.
Advisory gate
A quality gate whose failure is recorded as a finding but does not stop the task. Contrast with a blocking gate.
Agent
A specialised worker that performs one stage of a task. Each agent has a fixed role and a restricted set of tools. See Agent roles.
Agent-hour
A unit of metered execution time. Counts while an agent is actively working a task, not while the task waits in the queue.
Agent slot
The unit of parallelism. One slot runs one task at a time. See Capacity and agent slots.
AI profile
A named model configuration assigned to an agent, trading cost, speed, capability and constraints such as data residency. See AI profiles.
Blocking gate
A quality gate whose failure stops the task until it passes or is overridden.
BYOK
"Bring your own key" — supplying your own model provider credentials so usage is billed by your provider at your rates rather than through Coroid.
Check
A single verification performed against a change. Checks are grouped into policies and run as gates.
Discovery
Something Coroid found in your codebase while analysing it, which may become suggested work.
Finding
An issue recorded against a change — by a reviewer agent, a scanner, or an advisory gate. Findings are either fixed as rework or attached to the pull request.
Hook
An organization-level automation that reacts to a platform event. See Hooks.
Intake
The stage where a request becomes trackable work, whether typed in directly or imported from an issue tracker.
Lane
The branch a plan's tasks integrate into. Tasks target the lane rather than your base branch, and the assembled result is promoted as a single pull request. See Tasks, plans, sprints and lanes.
MCP
Model Context Protocol. Coroid both connects to external MCP servers and can be used as one. See the Integrations overview.
Plan
An ordered set of tasks grouped into phases, approved before code is written.
Policy
A named, versioned set of quality gates attached to projects.
Project
One repository plus its configuration, context and settings. The container work runs in.
Promotion
Opening the pull request that takes a lane's integrated work to your base branch, once it qualifies.
Provider key
A credential for a model provider that you supply. Encrypted at rest, never returned by the API, never included in settings exports.
Quality gate
A check work must pass before progressing. See Quality gates.
Review evidence
Artifacts attached to a pull request as proof of verification — preview deployments, scan results, coverage reports, test runs. See Review evidence.
Review rule
An organization-defined instruction that shapes what the reviewer agent looks for.
Rework
Sending a task back to the developer agent with findings, keeping its context, rather than starting over.
Sentinel
Autonomous monitors that watch for conditions and can open remediation work. See Sentinel.
Service account
A non-human identity for programmatic access, with its own scoped credentials.
Specification
The statement of scope, exclusions and acceptance criteria produced before work is built.
Sprint
A time-boxed container for work, with its own metrics and timeline.
Task
One unit of work that ends in one pull request. The unit that actually executes.
Work qualification
The determination that a piece of work meets the bar to move forward.
Workspace
The isolated, disposable environment where an agent clones your repository and works. One per task.