Skip to main content

Status & lifecycle reference

Starfire uses explicit lifecycle states so users, developers, and operators can distinguish work that is waiting, active, complete, failed, or intentionally stopped.

Generic run states

Exact backend enum names can differ by subsystem. The UI should present the same lifecycle meaning even where implementation-specific names vary.

FORGE build stages

Knowledge source states

Incident states

Account states

Starfire administration supports the idea of multiple account conditions rather than only active/banned.
Do not infer a user’s intent or wrongdoing from a state label. Account states describe platform access, not a judgment about the person.