beautyleg.pro — Audited Domain Plan

Current Reality

• The real implementation lives in the shared BeautyLeg codebases:
  • beautyleg/
  • beautyleg-worker/
  • beautyleg-cf/
• This domain should not be planned as a separate platform unless there is product evidence for a distinct paid/pro tier surface.

Recommended Role

• Treat beautyleg.pro as one of:
  • a redirect to the primary domain
  • a premium membership landing surface
  • a segmented acquisition domain backed by the same Worker/D1/R2 stack

Cloudflare Rules

• Reuse the same Cloudflare-native control plane as the main BeautyLeg deployment.
• Keep auth, billing, entitlement, and media storage centralized.
• Do not fork databases or asset stores per alias domain.

Definition of Done

• The domain has one explicit business purpose.
• It operates on the shared BeautyLeg Cloudflare stack.
• There is no separate origin runtime or duplicated infrastructure just for this alias.

⚙ 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.