# BETA-001
## End-to-End Wedding Acceptance Simulation

You are executing the first Beta Acceptance Test for the INVEETAIRE platform.

This is NOT feature development.

This is NOT architecture refactoring.

Authentication, Portal Separation, Workspace Session, and Workspace Users have already been stabilized.

Assume BETA HOTFIX-001 has been completed successfully.

Focus ONLY on validating the complete wedding workflow.

If defects are found:

Fix ONLY defects that prevent completion of the business flow.

Do NOT redesign architecture.

Do NOT introduce new features.

---

Current Status

✅ Sprint 0
✅ Sprint 1
✅ Sprint 2
✅ Sprint 3

✅ Pilot-001
✅ Pilot-002
✅ Pilot-003
✅ Pilot-004
✅ Pilot-005
✅ Pilot-006
✅ Pilot-007

✅ Alpha Patch-001
✅ Alpha Patch-002

✅ DEV PATCH-001
✅ DEV PATCH-002

✅ Alpha Stabilization-001
✅ Alpha Stabilization-002
✅ Alpha Stabilization-003
✅ Alpha Stabilization-004

✅ Beta Hotfix-001

Repository Status

BETA READY

Development Environment

http://localhost/inveetaire/

Use this environment for all verification.

---

Test Accounts

Platform

/admin

Username:
admin

Password:
admin

Workspace

/couple

Username:
test

Password:
test

(Optional compatibility)

Username:
crew

Password:
admin

---

Objective

Validate that a complete wedding can be operated without touching the database manually.

The platform should behave exactly as a real customer would use it.

---

Acceptance Flow

STEP 1

Login as Test Couple.

Verify:

Dashboard loads.

Workspace session exists.

Correct workspace displayed.

---

STEP 2

Complete Invitation Configuration.

Verify:

Bride name

Groom name

Love story

Wedding date

Holy Matrimony

Reception

Venue

Hero section

Cover image

Publish invitation

Preview

---

STEP 3

Guest Import

Import realistic guest data.

Include:

Single guests

Families

VIP

Friends

Different pax values

Holy-only guests

Reception-only guests

Dual-event guests

Verify:

Statistics

Duplicates

Validation

Stored data

---

STEP 4

Guest Identity

Verify:

guest_code

guest_slug

Invitation URL

QR Code

No internal IDs exposed.

---

STEP 5

Messaging

Generate invitation message.

Verify placeholder replacement.

Verify:

Holy only

Reception only

Dual events

WhatsApp Deep Link

Copy Message

Copy Invitation Link

---

STEP 6

Public Invitation

Open invitation as guest.

Verify:

Responsive layout

Guest personalization

Correct event visibility

RSVP

Wish

QR rendering

---

STEP 7

Guest Interaction

Submit RSVP.

Submit Wish.

Verify persistence.

Verify duplicate handling.

Verify dashboard updates.

---

STEP 8

Operation

Login using operational account.

Open Operation module.

Open Check-In.

Scan guest QR.

Verify:

Correct guest

Correct event

Attendance recorded

Duplicate scan blocked

Attendance statistics updated

---

STEP 9

Dashboard

Verify:

Guest Attendance

Pax Attendance

RSVP Summary

Wish Summary

Operational metrics

Progress widgets

Charts

No broken UI.

---

Bug Handling

If defects are found:

Fix ONLY defects that block the acceptance flow.

Keep fixes isolated.

No architectural redesign.

No feature additions.

---

Constraints

Do NOT:

Refactor authentication

Refactor routing

Refactor workspace architecture

Modify database schema

Implement payment

Implement WhatsApp API

Implement Email

Implement SMS

Implement Printer integration

Implement Analytics

---

Verification

Verify every completed step.

Verify PHP syntax.

Verify tenant isolation.

Verify responsive layout.

Verify localhost/inveetaire compatibility.

---

Acceptance Criteria

PASS only if:

Complete wedding workflow succeeds.

Invitation configured.

Guests imported.

Identity generated.

Messaging generated.

Invitation accessible.

RSVP works.

Wish works.

QR Check-In works.

Dashboard updates correctly.

No critical blocking defects remain.

PHP syntax passes.

---

Output

Provide:

1. Simulation summary.

2. Workflow executed.

3. Blocking bugs discovered.

4. Blocking bugs fixed.

5. Remaining non-blocking issues.

6. Verification results.

7. Acceptance checklist.

8. PHP syntax results.

Stop after the simulation.

Wait for Human Approval.