Wedding invitation product — planning hub
Updated: 21 October 2026 · Client V1.
Latest plan: BDT0 for new hosting/services. Free-first design, onboarding and delivery specifies four product surfaces, direct client handoff, compact Bangla hierarchy, ordered implementation batches and release/usage limits. Netlify Free is the first commercial-compatible hosting candidate to qualify; current Vercel remains personal preview. No migration, new account or paid purchase is claimed by this planning update.
Current Jamdani invitation is the product foundation. Backend/auth, wedding isolation, seller workflow, autosave, named links, RSVP/wishes, corrections, private CSV, pause/resume and private photo processing are implemented. Bangla is primary; English is secondary. 21 October hardening and rehearsal: 228 tests, typecheck/build/runtime, fresh isolated local HTTP/Auth/Storage and four hosted rollback proofs pass. One/two-event controls, meaningful publication validation, publish-first states, pinned sharing scope and session recovery are fixed. Actual hosted five-photo/RSVP/wish/revocation rehearsal passed on a separate fictional wedding. Vercel personal preview is live: actual customer OTP/session, large photo upload, publish, named RSVP/wish and revocation were verified. Intended seller AAL2, real phones/performance and recovery/operations remain. External commercial handoff is unqualified.
Start here
| File | Owns |
|---|
| memory.md | User decisions, verified state, constraints and next-session handoff |
| plan.md | Scope, build order, end-to-end milestone and gates |
| architecture.md | Stack/migration, identity, tenancy, transactions, cache/media/jobs/recovery |
| website-design.md | Mobile couple/seller screens, template preservation, type/layout/motion/states |
| task.md | Production implementation progress and remaining acceptance gates |
| Data/API | Entities, constraints, metrics, endpoints, revisions/idempotency/export |
| Corner cases | 96 prioritized scenarios across the entire delivery flow |
| Release gates | Device/performance/security/recovery/commercial evidence |
| Decisions | Confirmed choices, defaults, unresolved policy and blocking points |
Authority: plan for scope/order; architecture for system rules; design for UX; data/API for contracts; task for execution; memory for context. Update affected files together. Client V1 overrides conflicting older notes. Planned scenarios are not passed tests.
First production milestone
Seller confirms Order X → separately activates intended verified customer → couple publishes → creates named household/event allowance → guest opens on another phone and replies → correct couple sees it. Wedding Y cannot access X's data via UI, APIs, SQL, objects or exports.
Public buyer gets no management before confirmation/activation. Guest never enters own name; general invitation is view-only. One template; Bangla/English only. No gateway, realtime service or marketing rewrite is needed merely to start proving this slice.
Current implementation evidence
- v6.4 compact layout/music:82 tests at that historical checkpoint, browser screenshots; not rerun by this documentation pass.
- v6.3 gallery/opening: max-five-photo reel, color/hierarchy, immediate scroll after deliberate opening.
- v6.1 performance: LCP3.46s misses2.5s; not latest-build measurement.
- Physical phone sheet: LAN reachability confirmed; complete device/listening qualification pending.
- Named guest delivery: 143 tests; actual local OTP/MFA, two-client HTTP/Edge RSVP/wishes, responsive management UI and hosted database proofs. Source/run guide covers local/hosted configuration and SMTP handoff.
Retained supporting material
- Reference walkthrough, page index, feature matrix, catalogue.
- e-Nimontron flow, dashboard video: visible evidence, not competitor backend inspection.
- Figma source review, inspiration board, gift study.
- AI Studio prompt, Figma/Claude prompt, artwork prompts. Older broad prompts are supplementary; current scope/architecture wins.
- Previous root snapshot, including deferred public-site details and historical task IDs. Old “current/latest” labels are historical.
The user created free Dawat Staging and approved its migrations. OTP email delivery and real customer login are verified; one audited free test workspace is active and unpublished. No paid upgrade or guest messaging occurred. Hosted database provisioning does not mean the frontend is publicly deployed or launch-qualified.
