Comment by zkmon
6 days ago
I think you missed the whole point. Processor does not have routing logic. It's only job is to parse the request (form, text, image etc) and categorize it enough so that the workflow can do the routing for next actions. Routing is done by traditional predetermined logic, using rules. The discussion here is about whether it helps to define that routing logic at runtime (on-the-fly), instead of having it coded in predetermined logic. My view is, it doesn't help.
AI-based tools are mostly about replacing the processor with something smarter, not the router.
Of course, sometimes it can be an advantage to not have to explicitly write the router, but the big benefit is the better processor for request->categorization, which with AI can even include clarification steps.
I edited my comment to add more of what the agent would be doing. Not sure if this reached you, but if you read the edited one, how would traditional workflow engine solve the particular problem with a free form raw content that could be anything, and requires using various tools to solve the problem?
IME traditional rules based systems don't try to solve free form problems. So they stop at the point the inputs can't be handled (any further) whereas LLM could continue, albeit without any guarantee the result is accurate. It could completely hallucinate a fictional solution, which I've seen too often to trust them.