What does it mean that status types track lifecycle?

Objects often move through defined states — tracking these states enables workflow.

Example: A blog post moves through draft, in review, published, and archived. An e-commerce order moves through placed, confirmed, shipped, delivered, and possibly returned. A job application moves through applied, phone screen, interview, offer, accepted. None of these objects change identity — they change status. The status type tells you where the object sits in its lifecycle and, critically, what operations are valid next.

Try this: Pick one recurring process in your life — a project, a piece of writing, a personal goal, a purchase. Map the lifecycle states it actually passes through from beginning to end. Write each state as a node. Draw arrows between them showing which transitions are allowed. Then ask: are there states missing? Are there transitions you've been making that skip necessary intermediate steps? Name the lifecycle explicitly and keep the diagram.