One admin panel runs five different services

The admin dashboard manages audio mixing projects, music production sessions, session musician bookings, software builds, and accessibility audits from a single interface. Every project has the same shape — milestones, sessions, deliverables, comments, action items — regardless of whether the deliverable is a mastered track or a WCAG remediation report. The service type is a field on the project, not a separate system. That means the same admin workflow applies everywhere. I open the dashboard, see every active project across all five services, check which deliverables are pending, review which action items are overdue, and update session notes. One screen. One mental model. The alternative was five different tools — a DAW project tracker for audio, a Trello board for software, a spreadsheet for accessibility audits, a calendar app for musician bookings, a folder of production stems somewhere on a hard drive. Now it is all in the portal. The commit history shows each service type being added as a single enum value, not a new feature branch. That is the whole point of the architecture. A new service type is a database migration, not a rewrite.