Module and dependency map of the current system
This is a team plan, best installed into a shared workspace so everyone with a role in it can see and own their tasks. Before anyone argues about services, someone needs to draw what actually exists: the modules, the database tables each one touches and the calls between them.
First tasks
- Run a dependency graph tool over the main codebase and save the output
- List which modules read and write each database table
- Highlight tables written by more than one module
- Write a one-page summary naming the tangled core and the clean regions