A modern programming language that makes developers happier.

kotlinlang

Question about the design of Koog: what is the reason the restorable state machine / graph system is tied into the rest of the AI stuff?  From a distance, it looks like the graph stuff is actually fairly unrelated to the AI portion and could be separated out into a different library for cleanliness.

To be clear, I understand why Koog would USE the graph system.  I just don't understand why the graph system isn't a separate library.

Because it was developed for Koog specifically, and is tailored for AI workflows design.

Once it becomes a separate library:
• it would be an extra step to update a separate library it if Koog needs something new. Hence, we’ll be less productive 
• we’ll get some issues and requests unrelated to AI =&gt; the team would loose focus 
• I don’t see too many usages for the pure graph library apart from AI, workflow automations (that are nowadays also connected to AI), and probably some computer science. Did I miss something?

Fair enough - even if it could be separated out, it probably wouldn't really be used for anything besides this.  For me it just was an extra obstacle to reading the docs and working with the code because it felt like a lot of concepts were introduced at once.