The everyday question.
A working draft can be complete enough to share internally and still need another set of eyes. Without an explicit signal, the next step is often hidden in a message or a person’s memory. This scenario makes that signal part of the record.
The smallest useful rule.
Collect the working title and review flag, then route the draft to an editor when another look is needed. A cleared draft moves to the ready branch.
When needsReview is true, the record follows Editorial review. When it is false, the record follows Ready to share. The rule does not judge writing quality; it makes the existing review decision visible.
What the local test tells you.
The output names the record, the selected branch, and the reason. You can change the inputs and run the test again to see the opposite outcome. No actual team, document, notification, or external queue is involved.
A pattern to take away.
Keep a decision close to the information it describes. A small flag can be more useful than a complicated process when its meaning is shared and the route remains visible.
Try this scenarioOriginal fictional example. No commissioned client, testimonial, or measured business outcome is implied.