0082-laravel-state-machines

Complex Laravel state transitions are managed by defining states as classes using Spatie Model States, encapsulating rules inside dedicated transition handlers, and using model helper methods like `markAs*` and `canBe*` to trigger and guard changes.

Laravel model state transitions handle validation and side effects by encapsulating rules, timestamp updates, and domain event dispatching inside dedicated transition classes rather than scattering them across controllers or models.

An order lifecycle in Laravel is implemented by creating a state class hierarchy with explicit allowed transitions, such as pending to processing to completed, where each state change updates fields like `completed_at` and triggers domain events through transition handlers.

Spatie Model States builds type-safe workflows by defining states as classes and modeling allowed transitions explicitly with attributes, ensuring model status changes only through well-defined and validated paths.

Checking if a Laravel model state transition is allowed is done using `canBe*` model helper methods, which verify whether a transition is valid before you trigger the actual state change with the corresponding `markAs*` method.

Dedicated transition classes for Laravel model states should be used when status flows require explicit validation, timestamp updates, or domain event dispatching, ensuring transitions remain safe and consistent across complex workflows.