A creative studio run as a system of AI agents
As a non-programmer, can I run a whole creative studio as a coordinated system of AI agents — a main orchestrator that routes work to specialized sub-agents, each scoped to its own domain — instead of leaning on one general-purpose assistant?
The leverage isn't a clever prompt; it's architecture. Giving each agent a narrow scope, plus shared infrastructure — a glossary of agreed terms, a security policy, persistent memory — makes the whole thing behave like a team with institutional knowledge rather than a chatbot that forgets. Directing it well is a design and systems skill, not a coding one. That's the differentiator I didn't expect to have.
This isn't 'parked' so much as 'always running' — it's the operating system behind everything else in this log. It evolves continuously: each new project tends to become a new agent with its own scope and rules.
What it is
Most of my work now flows through a multi-agent system: a main agent that coordinates, and a set of specialized sub-agents — research, web coding, store operations, crowdfunding, game prototyping, and client-facing marketing — each scoped to its own folder with its own instructions. The main agent doesn't do the specialized work itself; it routes tasks and merges the results.
Why architecture, not prompting
Anyone can ask an AI a good question. The real gain came from treating it like building a studio:
- Narrow scopes. Each agent only knows and touches its own domain, so it stays sharp and doesn't trip over unrelated context.
- Shared infrastructure. A common glossary (so terms mean the same thing everywhere), a security policy (what may be installed or sent out), and persistent memory (so knowledge survives between sessions).
- A single human director. Me — supplying scope and judgment, not code.
Why it's the rare part
I'm a designer, not an engineer. The interesting claim isn't "I used AI" — it's that I built and run the system that builds the things. This very site, the Escalation Protocol web presence, and the game prototype were all produced by directing this system. The skill is orchestration.
Where it stands
It's live and it's the backbone. It grows by accretion: a new kind of work shows up, it becomes a new agent, and the institutional knowledge compounds. The other entries in this log are, in a sense, its output.