# RC-013 ## Wedding Event Management Foundation You are implementing Release Candidate RC-013 for the INVEETAIRE platform. IMPORTANT This is NOT feature development. This is NOT Theme development. This is NOT QR enhancement only. This patch establishes the Wedding Event Management foundation. The application has already completed: ✓ RC-011 Couple Experience ✓ RC-012 Guest Management Do NOT modify authentication. Do NOT redesign architecture. Do NOT modify Theme Engine. Reuse existing modules whenever possible. --- Objective Implement the Wedding Event Management layer. The platform must support multiple wedding events within a single workspace. For Pilot Wedding v1, the supported events are: • Holy Matrimony • Tea Pai • Reception These are fixed events for the pilot implementation. Future dynamic events are NOT part of this RC. --- Guest Event Access Every guest can be invited to one or more events. For Pilot v1 implement: Holy Matrimony Tea Pai Reception Each guest stores access for each event. Example Guest A Holy ✔ Tea Pai ✔ Reception ✘ Guest B Holy ✘ Tea Pai ✘ Reception ✔ Do NOT implement dynamic event builder. --- Guest Workspace Inside Guest Management create tabs: Holy Matrimony Tea Pai Reception Each tab only displays guests invited to that event. Guest statistics become event-aware. Reuse existing Guest List. Do NOT duplicate pages. --- Guest Form When creating or editing a guest, display Event Access. Checkboxes: ☑ Holy Matrimony ☑ Tea Pai ☑ Reception These determine invitation visibility and Wedding Day access. --- Invitation Rendering Reuse the existing Theme Engine. When rendering a guest invitation, only display sections for events the guest is invited to. Example Holy ✔ Tea Pai ✘ Reception ✔ Invitation displays: Cover Holy Matrimony Reception Gallery RSVP Tea Pai section must not be rendered. Do NOT redesign the invitation. Only control visibility. --- Wedding Day Navigation Replace the disabled placeholder. Sidebar Wedding Day Holy Matrimony Tea Pai Reception Each event opens its own operation workspace. --- Guest Check-in Rename "QR Scanner" concept. The page becomes Guest Check-in Support TWO methods. 1. Scan QR 2. Search Guest Search supports: Guest Name Phone Number Guest Code Reuse existing guest lookup logic where possible. --- Check-in Flow Guest found ↓ Display Guest Summary Name Category Pax Allowed Events Current Event ↓ Allowed Show Check-In button. ↓ Already Checked-In Display status. ↓ Not Invited Display warning. Buttons Reject Manual Override --- Manual Override Override must require: Reason VIP Family Request Organizer Approval Extra Pax Other Optional Notes Operator Timestamp Store audit trail. Do NOT silently override. --- Attendance Attendance becomes event-specific. Each Wedding Day page displays: Expected Guests Checked-In Pending Manual Overrides Rejected Reuse dashboard calculations where possible. --- Dashboard Dashboard summary becomes event-aware. Display: Holy Matrimony Tea Pai Reception Each with: Expected Checked-In Pending --- Constraints Do NOT Implement Broadcast Implement Wishes Center Implement Dynamic Events Modify Theme Engine Modify Authentication Modify Database unrelated to Event Access Duplicate SQL Rewrite Guest module Rewrite Invitation module --- Verification Verify Guest Event Access Guest Tabs Invitation visibility Wedding Day navigation Guest Check-in QR lookup Search lookup Override flow Attendance Dashboard Responsive Accessibility BASE_PATH compatibility localhost/inveetaire compatibility Production compatibility PHP syntax --- Acceptance Criteria PASS only if Multi Event foundation implemented. Guest Event Access works. Invitation visibility respects Event Access. Wedding Day navigation implemented. Guest Check-in supports QR and Search. Manual Override available. Dashboard becomes event-aware. Business logic preserved. Theme Engine unchanged. PHP syntax passes. --- Output Provide: 1. Files created. 2. Files modified. 3. Wedding Event architecture. 4. Guest Event Access implementation. 5. Invitation visibility implementation. 6. Wedding Day workflow. 7. Manual Override workflow. 8. Verification results. 9. Acceptance checklist. 10. PHP syntax results. Stop after implementation. Wait for Human Approval.