System governance, role management, audits, and standards enforcement. The government building.
Start here when you need information. Follow links to organized content.
Admin is the governance layer. It doesn't build features or write content — it makes sure the system that builds features and writes content doesn't drift into chaos. Every residence follows structure specs written and enforced here. Every role gets created through processes defined here. Every error gets taxonomized and tracked here.
The core tension: Claude instances are stateless. They forget everything between sessions. Admin's job is to make that not matter — by building navigation systems (pathfinder), tracking what happened (sessioner), validating structural integrity (archauditor, validator), and maintaining the standards everything else depends on (syn).
| System | Maintained By | Purpose |
|---|---|---|
| 3-level navigation | pathfinder | Handbook → folder READMEs → file listings. Lazy-loading wayfinding. |
| session registry | sessioner | Conversation ID tracking across 36+ residences in 7 projects. |
| error taxonomy | error | Violation classification, incident logging, pattern detection. |
| residence specs | syn, blueprinter | Structure templates, naming standards, required files. |
| domain catalog | directorian | 2.2M catalog DB + 216K changelog DB. Master project registry. |