Documentation

OWNERS

docs/OWNERS.md

Feature & Runbook Owners

Single source of truth for who maintains each feature and the runbooks that support them. Keep this file updated whenever ownership, escalation paths, or primary verification contacts change.

AreaOwnerTeam / RolePrimary ContactBackup
AuthenticationPriya ShahIdentity & AccessSlack #oncall-auth, auth@petunia.incRiley Chen
Billing & SubscriptionsJordan LeeBilling EngineeringSlack #billing-ops, billing@petunia.incLina Alvarez
Encryption & SecretsSasha KimSecurity EngineeringSlack #security, security@petunia.incPriya Shah
Error TrackingMorgan PatelObservabilitySlack #observability, obs@petunia.incTheo Ramos
OnboardingCasey NguyenGrowth EngineeringSlack #growth-onboarding, onboarding@petunia.incJordan Lee
Platform Admin / TrialsLina AlvarezPlatform OperationsSlack #platform-admin, platform@petunia.incCasey Nguyen
Real-Time WebSocketTheo RamosRealtime InfrastructureSlack #realtime, realtime@petunia.incMorgan Patel
Unified InboxRiley ChenMessaging PlatformSlack #messaging-inbox, inbox@petunia.incSasha Kim
User ManagementJamie OrtizAccess ControlSlack #access-control, iam@petunia.incPriya Shah
Platform Integrations RunbookRiley ChenMessaging PlatformSlack #integrations, integrations@petunia.incJamie Ortiz
WebSocket Operations RunbookTheo RamosRealtime InfrastructureSlack #realtime, realtime@petunia.incMorgan Patel

How to use this map

  • Reference owners directly in feature docs (Owner: [Name](../OWNERS.md#feature-name)) to avoid drift.
  • Keep contact routes actionable for on-call (Slack channel + email alias).
  • Update backup owners when rotations change so verification and incident response have a clear path.