I am shipping Inky today. It is a storytelling application built on a multi-agent architecture. This is not a wrapper around a single prompt; it is a system designed to handle narrative consistency, character state, and world-building across long-form sessions.
When you are building an ai story app, the challenge isn't getting the LLM to write. The challenge is getting the LLM to remember that the protagonist lost their sword three chapters ago. Most people try to solve this with a larger context window. I learned the hard way that context is a blunt instrument. You need a system.
The Architecture of a Narrative Engine
Inky runs within my studio's monorepo. I treat AI as the operating layer, not just a feature. The architecture relies on what I call agentic engineering—a series of specialized agents that handle specific domains of the story.
Instead of one massive call to Claude or Gemini, the system breaks the request down:
- The Archivist: Manages the long-term memory and state. It queries a vector database for relevant lore and character facts.
- The Architect: Outlines the structural beats of the scene based on the user's input and the current narrative arc.
- The Author: Generates the prose, constrained by the Architect's structure and the Archivist's facts.
- The Critic: Reviews the output for hallucinations or contradictions before it ever reaches the user.
This modularity allows me to swap models based on the task. I use Claude 3.5 Sonnet for the Author agent because of its nuance in prose, while Gemini 1.5 Pro handles the Archivist role due to its massive context handling during the initial ingestion of world bibles.
Why a Monorepo Matters for Solo Operators
I run a multi-product studio. I do not have a team of engineers. I have a system of agents and a single codebase that houses every product I ship. Building an ai story app inside this monorepo means Inky shares the same authentication, billing, and deployment logic as my other tools.
This reduces the surface area of what I have to manage. When I update the VERA orchestration layer—the custom agent system I built—every product in the studio gets smarter. I am not building one-off apps; I am building an integrated ecosystem.
