Workflows & states

The state machines are code-defined on the control plane, one per workflow id, and a ticket's workflow field selects one. This page is the tables; the narrative is on The ticket lifecycle.

Claimable marks the states a conductor may dispatch. Every non-terminal ticket state is claimable; done and cancelled are terminal and have no outgoing transition.

gaia_feature

State	Claimable
qualification	yes
spec	yes
coding	yes
review	yes
done	— terminal
cancelled	— terminal

Transition	From	To
qualify	qualification	spec
requalify	spec, coding	qualification
to_coding	spec, review	coding
to_review	coding	review
finish	review	done
cancel	qualification, spec, coding, review	cancelled

gaia_bug

State	Claimable
qualification	yes
diagnose	yes
coding	yes
review	yes
done	— terminal
cancelled	— terminal

Transition	From	To
qualify	qualification	diagnose
requalify	diagnose, coding	qualification
to_coding	diagnose, review	coding
to_review	coding	review
finish	review, coding	done
cancel	qualification, diagnose, coding, review	cancelled

Review is optional: finish may leave coding directly.

gaia_chore

State	Claimable
qualification	yes
spec	yes
coding	yes
review	yes
done	— terminal
cancelled	— terminal

Transition	From	To
qualify	qualification	spec
requalify	spec, coding	qualification
to_coding	spec, review	coding
to_review	coding	review
finish	review, coding	done
cancel	qualification, spec, coding, review	cancelled

Review is optional, as for a bug.

gaia_deployment

State	Claimable
pre_deployment	yes
post_deployment	yes
done	— terminal
cancelled	— terminal

Transition	From	To
deploy	pre_deployment	post_deployment
finish	post_deployment	done
cancel	pre_deployment, post_deployment	cancelled

A deployment ticket carries the release batch — the tickets it delivers — in referenced_tickets.

gaia_verification

State	Claimable
verifying	yes
summary	yes
done	— terminal
cancelled	— terminal

Transition	From	To
to_summary	verifying	summary
finish	summary	done
cancel	verifying, summary	cancelled

gaia_run

The run's own workflow. No run state is claimable — runs are not dispatched, they are the dispatch.

State	Meaning
claimed	the lease is granted; the agent has not started
running	the agent session is up
done	the ticket's state write retired the run
expired	a claimed run whose lease lapsed before the agent started
failed	dispatch or setup threw; the cause is in the run's error_log

Transition	From	To
start	claimed	running
finish	claimed, running	done
expire	claimed	expired
fail	claimed, running	failed

done, expired and failed are terminal. A running run is never expired automatically: its lease says nothing about liveness once the agent has started. expired and failed runs do not count toward a conductor's capacity and do not block re-claiming the ticket.

Next

• The ticket lifecycle — the diagrams and who acts in each state
• Run a ticket: from claim to done — the run workflow in practice
• The normative spec — the contract these tables implement