Context
CorvEd intentionally uses WhatsApp as the MVP communication layer, but the platform remains the system of record. docs/ARCHITECTURE.md future-proofing and advisor_update.md both call out a missing message/notification log, which matters once reminders, no-shows, renewals, and disputes need traceability.
Acceptance criteria
- Define the MVP data model for manual message events: recipient, related entity, template/type, sent_at, actor/admin, and optional notes without storing full sensitive message text unless explicitly approved.
- Add migration, RLS, generated DB types, and minimal admin UI or action hooks if included in MVP 0.2.
- Connect high-value events first: payment confirmation, tutor assignment, one-hour reminder, no-show notice, reschedule confirmation, renewal reminder.
- Keep WhatsApp API automation out of scope unless a separate future issue promotes it.
- Update OPS/docs with how admins record sent messages.
References
docs/ARCHITECTURE.md future-proofing notes: WhatsApp automationdocs/OPS.md WhatsApp templates and data hygiene rulesadvisor_update.md Data model gaps: No message/notification log
Context
CorvEd intentionally uses WhatsApp as the MVP communication layer, but the platform remains the system of record.
docs/ARCHITECTURE.mdfuture-proofing andadvisor_update.mdboth call out a missing message/notification log, which matters once reminders, no-shows, renewals, and disputes need traceability.Acceptance criteria
References
docs/ARCHITECTURE.mdfuture-proofing notes: WhatsApp automationdocs/OPS.mdWhatsApp templates and data hygiene rulesadvisor_update.mdData model gaps: No message/notification log