Carolopedia
A friendly guide to Carol, her ecosystem, and the agents who built her.
📖What it means
A detailed technical artifact describing how something in the project should be built: architecture, workflow, UI, data model, API, policy mapping. Stored as a row in the design records -> designs table. Every design has title, description, type, department, status (draft/review/approved/retired), version, and content markdown. Designs are the 'how' layer between policies (rules) and code (what exists).
⚖️What it is NOT
The neighbours this word is most often confused with, and the line between them.
Not: Requirement
A design is the HOW; a requirement is the WHAT.
Not: Cookbook entry
A design describes a built thing; a cookbook entry prescribes an action to take.
🧭The nuance
Carol has 97 designs (84 approved, 11 draft, 1 review, 1 retired) as of 2026-04-11. Served on port 7153.
🗣️Also called
design recordarchitecture doc