---
title: "Workflow States"
description: "Lifecycle stages for artifacts with entry/exit criteria and validation"
---

# Workflow States

Workflow states define where an artifact is in its lifecycle. Each transition can enforce rules (required links/fields), trigger automation, and capture audit data.

## Overview

- **States** are per artifact type (e.g., Draft, In Progress, Ready, Done, Archived).
- **Transitions** have guards (e.g., tests linked) and effects (e.g., notify owners).
- **Audit** records actor, time, previous state, new state, and why.

## Designing states

- Keep the state set small and meaningful.
- Define entry criteria (what must be true to enter) and exit criteria (what must be true to leave).
- Use transitions to enforce traceability (e.g., code must link to requirements/tests before Done).
- Allow reversible transitions for rework but audit them.

## Example criteria

- **Draft → In Progress**: has owner, description filled.
- **In Progress → Ready**: linked tests + code, review complete.
- **Ready → Done**: deployment verified, monitors in place.

## Tips

- Encode checks in automation; avoid manual checklists.
- Emit events on state changes for dashboards and alerts.
- Block state advancement if required links/fields are missing.

## Related

- [Workflows](./02-workflows/)
- [Relationships](./04-relationships/)
- [Traceability](./01-traceability/)
