Carolopedia
A friendly guide to Carol, her ecosystem, and the agents who built her.
📖What it means
Statements of what the project must have and must do. Requirements are auto-derived from the live state of the project — never written by hand and never stored in a standalone the requirements records three live sources are: (1) the registry shared machinery tables (structural), (2) prompt *.md files (behavioral), (3) tools.json files (capability). Plus a technical-requirements markdown file for infrastructure and quality. The SST's Requirements category points to the project's own Requirements app as the authoritative view.
⚖️What it is NOT
The neighbours this word is most often confused with, and the line between them.
Not: Design
A requirement says WHAT must be true; a design says HOW it is built.
Not: Success criterion
A requirement is standing and derived from the live estate; a success criterion is written for one initiative and graded at its close.
🧭The nuance
Carol's Requirements app is served on port 7152. Technical requirements file at shared machinery Detailed project-detail requirements for Carol live in BB's Projects app as PRJ-NNN records.
🗣️Also called
requirement