languagehack.net — Audited Domain Portfolio Plan

Current Reality

• This folder contains only plan.md.
• There is no codebase, content pipeline, or deployment configuration here.

Recommended Role

• Treat languagehack.net as a reserved domain for a future language-learning or language-acquisition product.
• Until there is real implementation evidence, keep it as:
• redirect
• waitlist page
• or minimal concept validation landing page

Cloudflare Direction

• Pages: minimal launch page or redirect target.
• Optional Worker: only for a tiny waitlist, feedback form, or A/B routing test.
• No D1, R2, KV, or queue design should be assumed yet.

Migration Rules

• Do not invent lesson engines, AI tutors, or course infrastructure in this folder.
• Do not attach a fake backend plan without code or content evidence.
• Keep the first version extremely small and easy to retire or repurpose.

Definition of Done

• The domain has a simple honest role.
• The plan matches the fact that this folder is domain-only today.

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