When the screen changes,
your plan can change too.

Use positive evidence

“Ready,” “Processing,” and “Complete” should each have their own reliable references. Missing “Processing” does not prove “Complete.” A state group remains unknown when several states match or evidence has not persisted.

Give uncertainty a path

Every condition needs an intentional response to failure and uncertainty. Retry within a time limit, verify a recovery screen, or stop for review. Do not create an unbounded retry loop.

Separate recovery from repetition

A partially delivered click may already have changed the application. Re-observe before deciding to continue; repeating that action blindly can create duplicates. The current engine does not automatically replay uncertain delivered input.

Keep it understandable

Name steps for their purpose, use small reference regions, and verify the result of each action. Start with a short graph, then expand only when its behavior is clear.