Ayatori: An Experimental Agent Orchestration Engine in Clojure
serefayar
13 points
1 comment
March 30, 2026
Related Discussions
Found 5 related stories in 51.5ms across 3,471 title embeddings via pgvector HNSW
- Bringing Clojure programming to Enterprise (2021) smartmic · 190 pts · April 02, 2026 · 50% similar
- Show HN: Orloj – agent infrastructure as code (YAML and GitOps) An0n_Jon · 19 pts · March 26, 2026 · 49% similar
- JSSE: A JavaScript Engine Built by an Agent tilt · 26 pts · March 31, 2026 · 49% similar
- Datomic at Clojure/Conj 2025 tosh · 15 pts · March 30, 2026 · 49% similar
- Agent-to-agent pair programming axldelafosse · 34 pts · March 27, 2026 · 48% similar
Discussion Highlights (1 comments)
geokon
The caps/deps node/network looks very similar to Pathom Resolvers. Those also allow for parallel execution. I think it will be a huge project to recreate all the features (and robustness) that they have there. So far I've found their engine is quit sophisticated and robust. You can have very complex declarative models (it's a very weird inside-out way to write code, but the net result is very composable) Just my unsolicited advice, but I'd try to build your system on top of their engine if you can. It's quite extensible. For instance they don't have "capabilities" but I think it'd be very easy to add that as a resolver key that's passed around.