Team ownership¶
Who owns which part of the platform, and who to ask when something breaks. Ownership means: first responder for incidents, default reviewer for PRs touching the area, and the decision-maker for its roadmap.
CONFIRM — this whole page
The structure below is a scaffold. Fill in real team names, members, and Slack channels, then delete the CONFIRM admonitions. Keep it short — link to an org chart rather than duplicating it.
Areas¶
| Area | Code | Owning team | Slack | Primary contact |
|---|---|---|---|---|
| Members app | apps/perci-platform-members |
CONFIRM | #CONFIRM |
CONFIRM |
| Clinicians app | apps/perci-platform-clinicians |
CONFIRM | #CONFIRM |
CONFIRM |
| Backend functions | apps/perci-platform-backend/functions |
CONFIRM | #CONFIRM |
CONFIRM |
| Web professionals | apps/perci-platform-backend/web-professionals |
CONFIRM | #CONFIRM |
CONFIRM |
| Medplum bots / FHIR | apps/perci-platform-backend/medplum |
CONFIRM | #CONFIRM |
CONFIRM |
| Shared Flutter packages | packages/ |
CONFIRM | #CONFIRM |
CONFIRM |
| Infrastructure / CI | infrastructure/, .github/ |
CONFIRM | #CONFIRM |
CONFIRM |
Codify it
Consider adding a CODEOWNERS file (.github/CODEOWNERS) so GitHub auto-requests the
owning team on PRs that touch their area. That keeps this table and review routing in
sync. If you add one, link it here.
Escalation¶
CONFIRM — on-call / escalation
Document how to reach the owner urgently (on-call rota, incident channel, who to page out of hours). Link to the incident/RCA process if one exists.
Cross-cutting decisions¶
CONFIRM — decision forum
Where do architecture decisions that span teams get made (e.g. a weekly tech sync, an RFC process)? Name it and link to where decisions are recorded.