Looks interesting. Quick question - one of the biggest challenges with agentic systems in non-deterministic behaviour. Does this framework do anything to address this? Does it help test and validate agent behaviour?
This is where the governance layer of Orloj fits in. You create policies and attach them to agents/tools which are all governed at runtime. These policies could be token guardrails, tool authority, etc. You can then check all of the traces of a task to have an audit trail for debugging (cli or UI). There are also human in the loop approval features that can be applied to make sure things are working correctly before proceeding on tasks.
It depends on what you're trying to build to be honest. For simple tasks Orloj can be a little overkill but it really starts shining when you are trying to setup large task flows that need many agents/tools/policies. Working with Terraform/Kubernettes for years gave a lot of the inspiration for the gitops side of things which we think fits naturally with how agent systems work.
Yes! We visited The Prague Orloj 2 years ago and it's amazing engineering. That's why we named it after it, for how it's coordinating and orchestrating so many complex mechanisms.
(for anyone wondering it's pronounced Or-Loy)
You should check out the Olomouc orloj [1]. Equally technically interesting as the Prague one, but with the added "benefit" of having been adjusted for political correctness under the Communist regime.
Didn't realize the Czechs had so many...The story about the clockmaker on the Prague one was interesting. The king trying to blind him so he could never make another for anyone else...
8 comments:
Looks interesting. Quick question - one of the biggest challenges with agentic systems in non-deterministic behaviour. Does this framework do anything to address this? Does it help test and validate agent behaviour?
This is where the governance layer of Orloj fits in. You create policies and attach them to agents/tools which are all governed at runtime. These policies could be token guardrails, tool authority, etc. You can then check all of the traces of a task to have an audit trail for debugging (cli or UI). There are also human in the loop approval features that can be applied to make sure things are working correctly before proceeding on tasks.
Feels like I would be taking on a lot of debt and maintainability I may not need
It depends on what you're trying to build to be honest. For simple tasks Orloj can be a little overkill but it really starts shining when you are trying to setup large task flows that need many agents/tools/policies. Working with Terraform/Kubernettes for years gave a lot of the inspiration for the gitops side of things which we think fits naturally with how agent systems work.
Orloj, btw, is Czech for "Astronomical Clock".
https://en.wikipedia.org/wiki/Prague_astronomical_clock
And it comes from mutated Latin word "Horologium".
Yes! We visited The Prague Orloj 2 years ago and it's amazing engineering. That's why we named it after it, for how it's coordinating and orchestrating so many complex mechanisms. (for anyone wondering it's pronounced Or-Loy)
You should check out the Olomouc orloj [1]. Equally technically interesting as the Prague one, but with the added "benefit" of having been adjusted for political correctness under the Communist regime.
[1] https://en.wikipedia.org/wiki/Olomouc_astronomical_clock
Didn't realize the Czechs had so many...The story about the clockmaker on the Prague one was interesting. The king trying to blind him so he could never make another for anyone else...