# INVEETAIRE — Architecture Planning (Event Session)

Before writing any code, I want you to fully understand this new business requirement and perform a complete impact analysis.

Do NOT implement anything yet.

====================================================
CURRENT SYSTEM
====================================================

INVEETAIRE currently supports exactly three wedding events:

1. Holy Matrimony
2. Tea Pai
3. Reception

Guests can be invited to one or more of these events.

Attendance, RSVP, QR Scanner, Dashboard, Analytics and Invitation Renderer are already working.

====================================================
NEW BUSINESS REQUIREMENT
====================================================

Currently each Event only has one schedule.

However, this is no longer sufficient.

Example:

Holy Matrimony may have two invitation sessions.

Session 1
10:00 WIB

Session 2
11:00 WIB

Guest A receives 10:00.

Guest B receives 11:00.

However...

Both guests are still attending the SAME Holy Matrimony event.

Therefore Attendance must still record only:

✓ Holy Matrimony

NOT

✓ Holy 10
✓ Holy 11

The same concept should also be applicable in the future for Tea Pai and Reception if they ever need multiple sessions.

The system will ALWAYS have ONLY THREE EVENTS:

- Holy Matrimony
- Tea Pai
- Reception

Do NOT introduce additional event types.

====================================================
IMPORTANT BUSINESS RULES
====================================================

Attendance remains based on Event.

RSVP remains based on Event.

QR Check-in remains based on Event.

Dashboard remains based on Event.

Analytics remains based on Event.

Session is ONLY used for:

- guest invitation schedule
- invitation display
- guest assignment

====================================================
ADMIN REQUIREMENT
====================================================

Inside Guest Management,

when assigning a guest to an Event,

Admin should also be able to choose which Session that guest belongs to.

Example:

Holy Matrimony

▼ 10:00 WIB

▼ 11:00 WIB

Tea Pai

▼ Default

Reception

▼ Default

The selected Session determines the schedule shown on the invitation.

====================================================
YOUR TASK
====================================================

Do NOT modify the code yet.

First study the entire project architecture.

Then provide:

1. Your understanding of the requirement.

2. Proposed architecture.

3. Database impact.

4. Model impact.

5. Controller impact.

6. Guest Management impact.

7. Invitation Renderer impact.

8. Attendance impact.

9. RSVP impact.

10. QR Scanner impact.

11. Dashboard impact.

12. Backward compatibility analysis.

13. Risks.

14. Recommended implementation phases.

Do NOT start coding.

I want to review and approve the architecture before implementation.