📖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.

📖Easily confused with

[{"term": "Carolopedia", "distinction": "The SST is the CATALOG \u2014 where every artifact lives and who owns it; Carolopedia is the encyclopedia that explains them in prose."}, {"term": "Data Dictionary", "distinction": "The SST lists the artifacts; the Data Dictionary defines the words used to talk about them."}]

📖Also called

- SST
- source of truth
- artifact catalog

📖Filed under

Category: records.

Service: Governance.