# G014.3 — Guest Identity & Invitation URL Integrity

You are acting as the Principal Software Architect and QA Lead for INVEETAIRE.

This is the final architecture validation sprint before RC-1.

Do NOT redesign routing.

The routing architecture has already been accepted in G014.2.

Canonical routes are FINAL:

Public Invitation

/{workspace_slug}/i/{guest_token}

Live Preview

/{workspace_slug}/livepreview

Builder Preview

/app/couple/invitation/preview

Do not propose any alternative routing.

---

# Objective

Verify that Guest Identity is implemented consistently throughout the entire application.

A Guest must have one canonical identifier.

That identifier must remain consistent across every module.

---

# Part 1 — Guest Identity Audit

Audit the Guest model.

Verify there is exactly one canonical guest identifier.

Review:

- database
- models
- services
- controllers
- views

Ensure no duplicate identifiers exist.

Examples:

guest_id

guest_token

uuid

invitation_code

id

Determine which identifier is canonical.

Recommend consolidation only if inconsistencies exist.

---

# Part 2 — Invitation URL Integrity

Verify that every invitation URL is generated using:

https://domain/{workspace_slug}/i/{guest_token}

Audit every module that generates guest links.

Examples:

Guest Management

Messaging

QR

Dashboard

Invitation

Exports

Bulk Import

Verify all use the canonical route.

---

# Part 3 — Couple Experience

Audit Guest Management.

Verify Couples can easily access:

Guest Name

Guest Token / Guest ID

Invitation URL

Copy Guest ID

Copy Invitation URL

Open Invitation

Recommend UI improvements only if essential.

---

# Part 4 — End-to-End Guest Journey

Verify the complete lifecycle:

Guest Created

↓

Guest Token Generated

↓

Guest Listed

↓

Invitation URL Generated

↓

Guest Opens Invitation

↓

RSVP

↓

Guest Book

↓

QR

↓

Attendance

↓

Analytics

↓

Reports

Identify any broken links in the chain.

---

# Part 5 — URL Stability

Verify behavior when:

Guest name changes

Phone changes

Category changes

Workspace slug changes (before Publish)

Invitation Published

Ensure guest_token remains stable.

Verify URL regeneration behaves correctly.

---

# Part 6 — Table & UI Audit

Review every guest-related table.

Verify Guest ID is visible where operationally useful.

Examples:

Guest List

Attendance

Messaging

QR

Reports

Invitation History

Recommend where Guest ID should be displayed.

Avoid exposing unnecessary internal database IDs.

---

# Part 7 — QR Audit

Verify QR generation uses the canonical Guest Token.

Verify QR validation resolves the same Guest.

Ensure there is no secondary identifier.

---

# Part 8 — Final Consistency Review

Verify every module uses the same canonical Guest Identity.

There should be exactly one source of truth.

No duplicated guest identifiers.

No inconsistent URL generation.

No routing inconsistencies.

---

# Deliverables

Provide:

1. Guest Identity Architecture

2. Invitation URL Audit

3. Guest Table Audit

4. Dashboard Improvement Recommendations

5. QR Consistency Audit

6. End-to-End Guest Journey Audit

7. Required Fixes

8. Final RC-1 Readiness Verdict

If implementation changes are required, keep them minimal.

Do not redesign routing.

Do not redesign Live Preview.

Focus only on Guest Identity consistency, Invitation URL integrity, and operational usability.