plus.id — Audited Domain Portfolio Plan

Current Reality

• This folder contains only plan.md and no implementation evidence.
• The previous large Cloudflare stack described here was not supported by code or audit data.

Recommended Role

• Use plus.id as a canonical plus brand candidate only if the product is actually defined.
• Until then, keep it as:
  • a redirect, or
  • a simple landing page on Cloudflare Pages

Cloudflare Rules

• Keep the first deployment minimal.
• Add Worker logic only if there is a concrete lead capture or validation flow.
• Avoid inventing D1/R2/KV architecture before the product exists.

Definition of Done

• The domain has a simple, explicit role.
• The plan reflects current evidence instead of fictional 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.