Top 10 Important Files (Junior Edition)
These are the 10 files/documents that are most important for you to master first.
1) docs/overview.md
Why it's important: system summary, so the main compass before reading the details.
2) docs/architecture.md
Why it's important: help understand module boundaries and the impact of changes across components.
3) docs/role-access-matrix.md
Why it's important: prevents permission bugs (the most frequent source of incidents).
4) docs/state-machine.md
Why it matters: wrong business status = chaotic data + problematic approval.
5) docs/api-reference.md
Why it's important: API contracts serve as a reference for client/server integration and debugging.
6) docs/request-response-catalog.md
Why it's important: speeds up payload traces during bug investigations.
7) docs/database-viewer.md
Why it matters: fast map of table relationships before query execution.
8) docs/database-design-full.md
Why it matters: in-depth details for data changes/migrations.
9) docs/deployment-runbook.md
Why it matters: secure deployment standards, including verification steps.
10) docs/troubleshooting.md
Why it's important: decision tree during incidents, saves triage time.
Bonus (must be opened when data changes)
docs/change-data-playbook.mddocs/common-maintenance-tasks.md
Note: the most critical source code file path requires verification against the application repo (
adi-jaya-master) because the structure can change between versions.