Task Statuses

This page is the single authoritative reference for the task status lifecycle in Kabori.

Status Glossary

Status	Slug	Meaning
Refinement	refinement	Task is being clarified by AI/human before implementation.
Backlog	backlog	Refined and ready; not yet started.
In Progress	in-progress	Implementation is actively running; not yet merged.
Review	review	MR open; AI review and/or human review in progress.
On Staging	staging	Merged and deployed to the staging environment; live for internal validation but not yet in production.
Done	done	Deployed to production.
Closed	closed	Abandoned, superseded, or otherwise resolved without shipping.

Lifecycle Flow

refinement → backlog → in-progress → review → staging → done

Tasks can be moved to closed from any status (e.g. Backlog, In Progress, Review, On Staging).

Key Distinctions

staging vs done

staging (displayed as "On Staging") means the code is merged and running on the staging environment for internal validation. It is not yet in production. If you're asking "is this live for users?" for an On Staging task, the answer is no.

done means the code is deployed to production and available to end users.

This distinction matters for:

• Knowing what changes are queued for the next production release
• Scoping hotfixes to the correct branch
• Identifying rollback boundaries

closed vs done

closed means the task was abandoned, superseded, or resolved without being shipped to production. It is not the same as done.

Auto-transitions

Kabori automatically transitions task status in response to merge request events:

• MR merged → status moves from review to staging (top-level tasks) or done (subtasks).
• Production deploy → no automatic transition; done is set manually or via CI hooks configured for your project.