# INVEETAIRE — Event Sessions (Phase 3 Architecture & UI Design)

Phase 1 and Phase 2 have been completed and approved.

Do NOT implement any code yet.

This phase is focused entirely on architecture, workflow, and UI/UX design.

====================================================
OBJECTIVE
====================================================

Design the complete Event Session Management experience for Couples.

This feature allows Couples to configure invitation sessions for each of the three wedding events.

The system still supports ONLY:

- Holy Matrimony
- Tea Pai
- Reception

No additional event types should ever be introduced.

====================================================
CURRENT ARCHITECTURE
====================================================

Phase 1

✓ Event Session database
✓ Default Session
✓ Guest Session relationship

Phase 2

✓ Guest Session Assignment
✓ Invitation Renderer
✓ Backward compatibility

Phase 3

Design the Couple Admin interface.

====================================================
GOAL
====================================================

The Couple should be able to manage Sessions for each Event in a clean and intuitive way.

The UI must remain simple for users with only one session, while still supporting multiple sessions when needed.

Avoid over-engineering.

====================================================
PLEASE DESIGN

Think as both:

- Product Designer
- UX Designer
- Senior Software Architect

====================================================
DESIGN THE FOLLOWING

1.

Overall navigation flow.

Where should Session Management live?

Example:

Invitation

↓

Events

↓

Holy Matrimony

↓

Sessions

Or another approach if you think it is better.

Explain your reasoning.

----------------------------------------------------

2.

Session Management page layout.

Design the complete page.

Include:

- Header
- Event selector (if needed)
- Session list
- Session cards/table
- Actions

Provide an ASCII wireframe.

----------------------------------------------------

3.

Create Session workflow.

How does a Couple add a new Session?

Fields?

Validation?

Buttons?

User flow?

----------------------------------------------------

4.

Edit Session workflow.

What can be edited?

What cannot?

Validation?

----------------------------------------------------

5.

Delete Session workflow.

Business rules.

Prevent deleting:

- the only remaining Session
- Sessions currently assigned to Guests

Suggest the best UX.

----------------------------------------------------

6.

Default Session behavior.

Can the Default Session change?

Should it be automatic?

Manual?

Explain your recommendation.

----------------------------------------------------

7.

Sorting.

If there are multiple Sessions,

how should they be ordered?

By:

- Start Time
- Manual Drag & Drop
- Sort Order

Recommend the best approach.

----------------------------------------------------

8.

Validation Rules.

Consider:

- overlapping time
- duplicate names
- invalid time
- minimum one session
- default session uniqueness

Add any validation you believe is necessary.

----------------------------------------------------

9.

Guest Impact.

If a Session is edited,

what happens to assigned Guests?

If deleted,

what happens?

Recommend the safest behavior.

----------------------------------------------------

10.

Future Scalability.

Without changing today's requirements,

does this architecture already support:

- multiple Reception sessions
- multiple Tea Pai sessions

Explain why.

====================================================
OUTPUT FORMAT
====================================================

Generate:

1. Functional specification

2. UX specification

3. Business rules

4. ASCII wireframes

5. Recommended workflow

6. Validation checklist

7. Edge cases

8. Risks

9. Final recommendation

====================================================
IMPORTANT

Do NOT write code.

Do NOT modify files.

Do NOT generate SQL.

This phase is architecture and UI review only.

After I approve the design, we will proceed to implementation in the next phase.