Data Model And API

The mobile and admin apps are separate codebases, but they rely on a shared set of business entities.

Core entities

• events
• insights
• advocates

Shared expectations

• event metadata must be stable enough for mobile capture context
• insight fields should remain consistent across capture, analysis, and reporting
• changes to enums or required fields need coordination across both repos

Coordination guidance

• document schema changes in this docs repo
• update code-local docs in the affected repo
• call out migrations and backward compatibility risks explicitly

API ownership

The admin/backend side is the operational source for management and reporting endpoints.

The mobile app should preserve its offline-first write model even when backend/API behavior evolves.