I have a similar need for a PoC that I'm developing these days, see https://github.com/mariofusco/quarkus-drools-llm/tree/main?tab=readme-ov-file#the-airline-chatbot-example

There I implemented the state machine with a rule engine and more in general it would be great to have a pluggable mechanism to allow using different options. If it's ok for you I could give a try to what you're proposing here (and maybe contribute with some changes with another pull request) and validate it with my use case.

@mariofusco sounds great, I would definitiely love to see how this looks like with drools! Having a pluggable mechanism is a good idea. But first we need to see whether giving AiService N states is easier/clearer/more_flexible than having N AiServices (one per state) and allow the user to route and manage that himself using whatever he wants. WDYT?

For now I'm not sure to be honest. The N AiServices (1 per state) approach actually works and indeed is the one I used for my PoC, but simply because it is the only option I had. Then I googled to check if langchain4j already had something to cover this requirement out-of-the-box and bumped into this pull request. For now I want to give it a try and see how it comes along and then we can further continue this discussion. Usually I don't know what I'm doing or about to do before I start writing down some code :)

I am following this :)
Any feedback on the idea is much appreciated.