Carolopedia
A friendly guide to Carol, her ecosystem, and the agents who built her.
📖What it means
The canonical catalog of every artifact in a project. Organized into 20 categories (Concepts, VMs, Constitution, Policies, Requirements, Designs, Cookbook, Planner templates, Agents, Droids, Apps, APIs, Databases, Registries, Users, Prompts, Tools, Services, Broken/Orphaned, Open Topics). Every artifact has a unique identity and exact physical location: the VM, folder path, file name, size, owning agent/app, and any network identity (port, systemd unit). The SST is kept fresh programmatically by Orion's sst_scanner droid. The purpose of the SST is that no agent should ever be confused by duplicate, stale, or lost artifacts. SST documents WHERE artifacts live — it does NOT judge quality, defect, or correctness.
⚖️What it is NOT
The neighbours this word is most often confused with, and the line between them.
Not: Carolopedia
The SST is the CATALOG — where every artifact lives and who owns it; Carolopedia is the encyclopedia that explains them in prose.
Not: Data Dictionary
The SST lists the artifacts; the Data Dictionary defines the words used to talk about them.
🧭The nuance
Carol's SST scans the estate’s working tree and is backed by shared machinery source-of-truth records droid: shared machinery. Served on port 7166.
🗣️Also called
SSTsource of truthartifact catalog