I respect the honesty of admitting B.E.N.N.Y. is mostly if-else logic on top of an LLM layer, because that describes most of what ships as an "agent" right now. The line I would draw is autonomy over control flow: if the branching lives in your code rather than in the model's decisions, it is orchestration, which is often the safer choice anyway. Given your human-review step before a lead is submitted, do you actually want B.E.N.N.Y. choosing the next action on its own, or is the deterministic path exactly what a business-critical flow needs?
Hi Kartik! For B.E.N.N.Y. I would apply a deterministic approach in this case. I don't want it to make decisions to qualify leads on its own because the last thing I want are false positives, false negatives, etc. Even though I heavily emphasize the importance of human-in-the-loop (HITL) architecture, I am open to exploring more automation and agentic behavior of other aspects of B.E.N.N.Y., such as the timesheet monitoring feature I mentioned in the article, so that it can catch irregularities or anomalies that a human wouldn't normally catch before turning it over to them.
Kartik N V J K
AI Developer | Making AI reliable, trustworthy & accessible to everyone | Active community contributor
I respect the honesty of admitting B.E.N.N.Y. is mostly if-else logic on top of an LLM layer, because that describes most of what ships as an "agent" right now. The line I would draw is autonomy over control flow: if the branching lives in your code rather than in the model's decisions, it is orchestration, which is often the safer choice anyway. Given your human-review step before a lead is submitted, do you actually want B.E.N.N.Y. choosing the next action on its own, or is the deterministic path exactly what a business-critical flow needs?