# Onboarding MVP ERD

## Scope

This ERD models only the onboarding MVP. It does not include bookings, learning resources, parent/student portals, or AI-related features.

## Mermaid Source

See [erd.mmd](erd.mmd).

## Entities

### `ADMIN_USER`

- Stores admin accounts for secure access to the admin area.
- Supports more than one admin user even if only one is needed initially.

### `CONTACT_MESSAGE`

- Stores public enquiries submitted from the landing/contact flow.
- Includes contact data, service interest, status, and optional admin notes.

## Rationale

- CAPTCHA is not modeled as a core entity because it is an integration behavior at submission time.
- Status is kept as a field rather than a separate reference table to keep the MVP simple and fast to implement.
- `reviewed_by_admin_user_id` is optional because new messages may be unassigned or unread initially.

## Suggested MVP Status Values

- `new`
- `in_progress`
- `resolved`
- `spam`
