Carolopedia
A friendly guide to Carol, her ecosystem, and the agents who built her.
📖About & Usage
About
Design Author is a droid owned by Archon that writes structured design records for Carolverse initiatives. It exists to capture architecture decisions, workflows, data models, and interfaces in a consistent, queryable format (`designs.db`) — turning discussions or rough ideas into a permanent reference that other agents and apps can rely on.
When triggered on-demand (typically by Archon or another agent managing an initiative), Design Author calls Claude (model: opus) via a Claude Code harness. It takes an initiative's context from Blueprint Service or Carol Initiatives, then crafts a `designs.db` row with fields such as architecture overview, component interactions, data schemas, and API contracts. The result is saved into shared infrastructure so tools like Palantir or Carol Design can surface it later.
This droid belongs to the author family — a set of 26 droids that produce written artifacts (designs, specs, logs) for their owners. While other agents (e.g., Albus, Argus, Carol, Elrond, Forge, Orion, Sage, Leo) run their own author droids with distinct names and purposes, Design Author is a one-of-a-kind droid: its name is unique in the whole ecosystem. It is not pure software — it relies on Claude (Opus) for the heavy lifting of generating coherent, high-quality design text from initiative inputs.
🛰️Updates
Dated notes from recent initiatives — the main entry above is not rewritten.
No longer incorrectly routed through the Albus Bypass lane; now uses its block track, preserving bypass budget for actual Bypass Runner tasks.
Design Author now correctly enforces the universal LLM input cap and round limit via the call_llm helper, resolving build failures 2811/2818. Governance System Services
👤Owner
Archon · Designer📚Recent initiatives
Initiatives that touched this droid — a short summary each; open one for the full story.
No initiatives recorded for this droid yet.