I've been experimenting with an orchestration-first approach instead of relying on a single model to handle an entire workflow.
The project started as a way to explore a real customer scenario, and along the way it evolved into a long-form publishing workflow involving multiple specialized agents, MCP/A2A services, evaluation loops, and supporting infrastructure.
By the end, the system had processed 26 billion tokens and grown to include 25 agents and tools, 30 agent skills, 27 packaged skills, 22 projects, 12 MCP/A2A-native services, 8 full-stack services (API + UI + MCP + A2A), 318 PRs, and 423 commits.
My goal as CTO was to go deep into a real customer scenario myself before asking my engineering organization to build in this new way.
The project is here: https://theisaiahchronicles.com
Would love to hear how others are approaching orchestration and multi-agent systems.
Comments URL: [https://news.ycombinator.com/item?id=49009663](https://news.ycombinator.com/item?id=49009663)
Points: 1