This site is deliberately scoped to what's actually being built first: the Three Doors homepage, a single-tier Online Puja, Free Puja Consultation, and Astrology with two selection paths. The PRD_Online_Puja_Platform document describes a larger long-term vision — Offline On-Site Puja with GPS tracking, premium/custom Pandit selection, a full admin operations dashboard, and a weighted automated allocation engine. None of that full-vision scope is built into this HTML mockup; it's tracked here so nothing discussed gets lost.
| Item | Full Vision (PRD) | Phase 1 MVP (built here) |
|---|---|---|
| Puja tiers | Complete Puja + Guided Puja (customer self-arranges Samagri) | Single tier only — “Online Puja”; Guided Puja removed |
| Offline Puja | Full on-site service, GPS tracking, min. 20 Pandits/city | Not in scope — Phase 1 is Online only, per the Three Doors |
| Pandit selection | Automated by default; Custom/Premium selection for a fee (+₹1000–2000) | Manual allocation by Admin for Phase 1; no premium selection yet |
| Astrologer selection | Not separately specified in the PRD | Two explicit paths: best-available auto-connect, or browse & select |
| Allocation algorithm | Full weighted formula (Skill/Rating/Proximity), skill-tier priority, sequential escalation | Simple rule for Consultation Pandits: eligibility checks + lowest workload |
| Admin dashboard | Full metrics — GMV, booking funnel, studio occupancy gauge, escalation alerts, dispute queue | Backend panel scoped to registration, expert profile/mode, and astrologer quality only |
The PRD states 60 seconds in two places (end-to-end flow step 5; the Pandit Ji use-case table) but 30 seconds in three other places (Dispatch & Fallback Rules text; the allocation-algorithm diagram itself, “Sends 30-sec alert to #1 Match”; Admin escalation alerts, “3 consecutive attempts” at 30 seconds). The 30-second figure appears more often and is embedded directly in the algorithm's own diagram — this mockup treats that as the likely intended value, but it should be confirmed with the client before implementation rather than assumed.
Section 3.3 calls it an “acceptance timer” for the primary booking, while Section 6.1.2 separately describes “Reaching Delays” after 3 failed 30-second attempts — these two are consistent with each other (both 30s), which further reinforces that 30 seconds is likely correct and the 60-second mentions were an editing slip.
