japri.biz — Audited Domain Portfolio Plan

Current Reality

• This folder contains only plan.md.
• There is no app code or Cloudflare config proving a live japri product here.

Recommended Role

• Treat japri.biz as one alias in the japri domain family.
• Until a real product exists, keep it as a redirect or a minimal landing page.

Cloudflare Rules

• Pages is sufficient for the first live state.
• Do not define separate infrastructure per japri alias before there is a canonical app.

Definition of Done

• The domain has a simple portfolio role.
• The plan no longer invents unsupported architecture.

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