Application overview, onboarding guide, and architecture diagrams
The Prisma schema has 148 models across 24 bounded contexts, too many to diagram exhaustively. This shows the core aggregate every other module attaches to: Person → Worker → Employment → Assignment, with Assignment placing a worker into a Position and Grade.
Worker is the central hub: leave requests, time entries, payslips, benefit enrollments, performance reviews, documents, assets, and dozens of other domain models all hold a foreign key back to a Worker (occasionally an Employment or Assignment) rather than to Person directly — this is what lets one Person have multiple Worker records (e.g. re-hire history, or a concurrent employee + contractor engagement) without losing referential integrity.
The schema is heavily relational: 148 models with explicit @relation foreign keys are the norm, not the exception — nested/denormalized JSON fields are essentially unused in the schema.