bijaksana.net — Audited Domain Plan

Current Reality

• The real implementation evidence in this workspace is the shared bijaksana-worker/.
• There is no separate .net app code that justifies a standalone infrastructure plan.

Recommended Role

• Use bijaksana.net as a redirect or segmented front door into the same product.
• If it stays live, it should be driven by the same Worker routes and shared state.

Cloudflare Rules

• Reuse the same Worker, KV, AI binding, and operational model.
• Keep wallet/auth and notification logic centralized.

Definition of Done

• The domain has one clear purpose.
• It runs on the shared bijaksana Worker stack without creating duplicate 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.