Start small enough to understand every step.

Pick a repeatable request

Choose work that arrives often and follows a recognizable path. A request for account information is easier to bound than an instruction to improve operations. Write one sentence describing the input and another describing the finished result.

Keep the first version supervised

Let the agent prepare an action while a person performs the final review. Save examples where the reviewer changes the recommendation. These examples show which rules are ambiguous and which source documents need attention.

Expand after learning

Add another branch only after the first route is understandable. A small workflow with reliable ownership is a stronger foundation than a large diagram that nobody can explain. In the Weavaryn concept, every route has an owner and a review boundary.