To stress-test it I pointed it at a dumb task: generate an entire novel. It wrote ~40K words across 11 chapters in about 10 minutes. The "author-bot" uses gollem's agent primitives — chained agents for chapter planning, continuity checking, iterative drafting. Basically an orchestration.ChainRun pipeline where each stage feeds into the next.
The novel ("The Year Unedited" — dystopian memory-editing premise) came out surprisingly coherent. Characters kept distinct voices across chapters, the plot threads mostly held together, and it didn't just wrap everything up neatly at the end. Not saying it's good literature, but it's a decent stress test for long-running agent orchestration.
I threw it on Amazon mostly as an experiment: https://a.co/d/037EOH88
The framework itself is the actual point of this post though. It does cost tracking, guardrails, middleware chains, streaming with Go 1.23+ iterators, background process management, graph workflows, eval framework, the works. Happy to dig into any of the architecture details.