beautyleg.in — Audited Domain Plan

Current Reality

• The implementation evidence points to the same core stack used for the beautyleg product family:
  • Node/Express runtime in beautyleg/
  • Worker path in beautyleg-worker/
  • Pages path in beautyleg-cf/
• This domain should be treated as an additional brand or route surface for the same media product, not as an independent application with its own invented infrastructure.

Recommended Role

• Use beautyleg.in only if it has a clear market or language purpose.
• If it is an alias or campaign domain, keep it thin:
  • redirect to the canonical product domain, or
  • serve a tightly scoped localized/campaign entrypoint backed by the same Cloudflare data plane.

Cloudflare Rules

• Reuse the shared D1, R2, KV, and Worker architecture from the primary BeautyLeg product.
• Do not create a separate app stack just because the domain is different.
• Keep canonical, sitemap, auth, and payment behavior centralized.

Definition of Done

• The domain has a clear role: redirect, localized entrypoint, or campaign surface.
• It does not require a separate origin app.
• It runs on the same Cloudflare-native product stack as the main BeautyLeg deployment.

⚙ HARD CONSTRAINTS (enforced for all sites)

This domain MUST operate within these constraints — no exceptions:

• 100% Cloudflare serverless — Workers + D1 + R2 + KV + Workers AI + Vectorize. NEVER PM2, NEVER VPS, NEVER Docker in production path.
• 100% AI-automated — every customer interaction, every moderation decision, every transaction reconcile = AI. No manual queue, no live human chat support, no physical fulfillment.
• 1-operator solo — one person can run the entire operation from a phone. No team meetings, no shared inbox, no shift rotation.
• WhatsApp AI bot for all support (24/7, instant response, no SLA promises that need humans).
• Mayar QRIS for all Indonesian payments (subscription auto-renew, no manual invoicing).
• Indonesian UI primary — bahasa-first, English fallback only where unavoidable.
• Privacy — opt-in only, delete-on-request honored within 24h (cron-driven).
• No physical goods, no inventory — digital products + affiliate referrals only.

If the plan above describes any flow that violates these constraints, treat the plan as ASPIRATIONAL only and rework before building. The constraint trifecta wins.