# RC-1 — Independent Release Readiness Audit You are acting as an Independent Release Auditor. You are NOT the original architect. You are NOT the implementation engineer. You are the final reviewer before Version 1.0 is released to real wedding customers. Assume that tomorrow morning a real Couple will use INVEETAIRE for their wedding. Hundreds of guests may access the invitation simultaneously. Your responsibility is to find every issue that could cause: - confusion - operational failure - guest frustration - wedding-day disruption - security problems - data loss - scalability issues - UX issues Be skeptical. Challenge everything. Do NOT assume the system is correct. --- # Current Status Architecture is officially frozen. The following are FINAL and must NOT be redesigned. - Workspace Slug - Routing - Guest Identity - Renderer - Live Preview - Preview - QR Strategy - URL Strategy Only identify bugs, operational risks, UX issues, performance risks, security concerns, missing edge cases, or release blockers. Do NOT propose architectural redesigns. --- # RC-1 Audit Scope Perform a comprehensive release readiness review. --- # Part 1 — Functional Audit Review every major workflow. Examples Workspace Invitation Guest Media QR RSVP Guest Book Messaging Dashboard Operations Reports Settings Verify: - complete - usable - internally consistent Identify broken workflows. --- # Part 2 — Wedding Day Simulation Simulate a real wedding. Example 500 invited guests 250 guests arrive within 30 minutes Guests - scan QR - RSVP - open invitations - leave wishes Crew - check attendance Couple - monitor dashboard Find operational bottlenecks. Identify failure scenarios. --- # Part 3 — Mobile Experience Audit: Android iPhone Tablet Small screens Large screens Landscape Portrait Look for: layout issues buttons forms scroll touch targets responsive problems --- # Part 4 — UX Audit Review: Dashboard Invitation Builder Guest Management Messaging QR Attendance Reports Settings Find: confusing labels missing feedback hidden actions unnecessary clicks poor workflows Recommend only high-impact improvements. --- # Part 5 — Error Handling Audit every major feature. Examples Guest not found Expired guest Deleted guest Missing media Broken image Music missing Invalid QR Duplicate RSVP Network interruption Session expired CSRF failure 404 500 Missing workspace Determine whether users receive helpful feedback. --- # Part 6 — Security Audit Review: Authentication Authorization CSRF XSS SQL Injection File Upload Media Access QR Validation Guest Enumeration Rate Limiting Brute Force Session Handling Access Control Find weaknesses. --- # Part 7 — Performance Audit Assume: 100,000 workspaces 5 million guests Peak wedding traffic Review: queries indexes renderer media page size payload N+1 queries duplicate queries large loops memory Recommend optimizations only if meaningful. --- # Part 8 — Accessibility Review: contrast keyboard navigation focus states ARIA screen readers font sizes color dependency touch targets --- # Part 9 — Browser Compatibility Review support for: Chrome Edge Safari Firefox Android Chrome iPhone Safari Identify compatibility risks. --- # Part 10 — Release Risk Register Create a table. Severity Critical High Medium Low For every issue provide: Issue Impact Likelihood Recommendation --- # Part 11 — Release Blockers Explicitly answer. Does anything prevent Release Candidate? Classify: Critical Blocker Major Concern Minor Issue Enhancement --- # Part 12 — Final Release Decision Provide exactly one conclusion. --- ## ✅ RC-1 Ready No critical blockers. Suitable to proceed to RC-2. --- ## ⚠ RC-1 Ready with Conditions List remaining issues. No architectural redesign. Only bug fixes and UX polish. --- ## ❌ RC-1 Not Ready List critical blockers. Explain why they must be fixed before RC-2. --- # Important Do NOT redesign the architecture. The architecture is frozen. Judge only: - implementation quality - operational quality - release readiness - production robustness - wedding-day reliability Think like a company that will release this product to paying customers tomorrow.