Concept ownership boundary for this component group.
These are requirement-level concepts, not table names, column names, or implementation directives. The boundary lets later database agents know which persistent concepts this group owns, which concepts it may reference, and which nearby concepts belong elsewhere.
Prisma schema filename. Convention: schema-{number}-{domain}.prisma where
number indicates dependency order.
Component group kind.
"authorization": Auth tables (users, sessions, password resets).
Processed by Authorization Agent."domain": Business tables (products, orders). Processed by Component
Agent.NamespacenamespaceBusiness domain namespace for Prisma directive.
Use a snake_case component namespace such as "systematic", "actors", "sales", "orders", or "articles". This namespace describes component ownership and is not automatically a table-name prefix.
Final rationale cementing the component's structure.
Review considerations: relationships with other domains, grouping validation.
Initial thoughts on why these tables belong together.
Database component skeleton generated during the DATABASE_GROUP phase.
Field order is deliberate: reasoning fields (thinking → review → rationale) come BEFORE technical fields (boundary → namespace → filename → kind) to ensure the AI reasons through purpose before committing to technical details.
Author
Samchon