Architecture Reference
This section holds durable architecture notes, migration policy, and database ownership decisions.
Pages
- Dependency Resolution
- Database Flow
- UI vs Domain Modules
- Database Module Migration Structure
- Database Migration Authoring Workflow
- Existing Migration Classification
- Database Migration Safety Policy
How to use this section
- Put stable system rules here.
- Prefer forward-looking, repo-owned guidance over client lore.
- Link operational procedures from here only when architecture depends on them.
Repo source
docs/architecture/README.mdThis page is rendered directly from the root docs folder. Edit the markdown there, not inside the app.
PreviousProjects ModuleThe Projects module extends the platform with work-management data and project access rules. It depends on CRM because projects are attached to organizations, and it inherits the Admin and RBAC layer through that dependency chain.NextDependency ResolutionBrightWeb resolves module order from the registry, not from ad hoc assumptions. The current chain is linear: **Core** first, then **Admin**, then **CRM**, then **Projects**.