Ayatori: An Experimental Agent Orchestration Engine in Clojure
serefayar
13 points
1 comment
March 30, 2026
Related Discussions
Found 5 related stories in 770.5ms across 14,015 title embeddings via pgvector HNSW
- I built ten custom subagents to tame a 500K-line Clojure codebase escherize · 43 pts · April 29, 2026 · 52% similar
- Agent-talk: Enabling coding agents to work together xhluca · 48 pts · July 16, 2026 · 51% similar
- Agentty – A drop-in alternative to claude-code, written in C++26. 11.0 MB binary tfeayush · 27 pts · July 15, 2026 · 50% similar
- Bringing Clojure programming to Enterprise (2021) smartmic · 190 pts · April 02, 2026 · 50% similar
- My thoughts after using Clojure for about a month speckx · 185 pts · June 02, 2026 · 50% 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.