peterpan.mobi — Audited Domain Plan

Current Reality

• The actual Peterpan implementation is already represented by the main peterpanband.com/ codebase.
• This .mobi domain should not be treated as a different product unless there is strong evidence of a mobile-specific market strategy.

Recommended Role

• Prefer one of two outcomes:
  • redirect to the canonical Peterpan site
  • or keep it as a campaign/mobile acquisition domain backed by the same Cloudflare stack

Cloudflare Rules

• Reuse the primary Peterpan Pages + Worker + D1 architecture.
• Do not create a separate mobile-only backend.
• Keep SEO canonicalization strict to avoid duplicate content.

Definition of Done

• The domain has one clear role.
• It runs on the same Cloudflare-native product stack as the main Peterpan property.
• It does not introduce duplicate runtime infrastructure.

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