japri.in — Audited Domain Portfolio Plan

Current Reality

• This folder contains only plan.md.
• There is no code, asset pipeline, or deploy configuration in this folder.

Recommended Role

• Treat japri.in as one reserved domain inside the broader japri domain family.
• Its near-term role should be one of:
• redirect to the main japri property
• tiny validation page
• or localized/alternate campaign alias

Cloudflare Direction

• Pages: default delivery for redirect or minimal landing page.
• Optional Worker: only if the domain needs lightweight routing logic or form capture.
• No heavier runtime should be planned here yet.

Migration Rules

• Do not assign a standalone product architecture to this folder.
• Do not create duplicated infrastructure for a domain that currently has no code.
• Keep this domain subordinate to the broader japri product decision.

Definition of Done

• The domain role is explicit and minimal.
• The plan matches current evidence instead of projecting a fake app.

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