dbarchitect
🏛️ dbarchitect
Decide where each fact lives, what is derived from it, and what each reader may assume about freshness and consistency — before anyone models tables. dbdesign designs the schema of one relational store; this skill decides how many stores there are, what kind, which one is authoritative for what, and how the others are kept in step. Theory: theory.md §5 (isolation anomalies) and §6 (system of record vs derived data; the four meanings of "consistency").
It decides and stops. No DDL, no infrastructure code, no provisioning, no configuration change, no connection to a live system unless the user says so (and then read-only). Each relational system of record goes to dbdesign; migrating an existing estate goes to dbpropose.
Reference docs in this folder: