Every Workflow Needs a Terminal State That Humans Can Read

Workflows should end in states that tell a human what happened and what, if anything, is still owed, because ended and finished are not the same thing.

A workflow that simply stops leaves a question behind. A workflow that ends in a named terminal state leaves an answer, even when the answer is that a human owes it attention.

What a terminal state should say

• Whether the intended effect happened, partially happened, or did not.
• What cleanup or follow-up remains, with an owner.
• Which evidence to consult if the outcome is disputed.

Use the architecture guide, blackboard schema, and examples to give every workflow an ending a human can act on.