'''Do not make any visual modifications. The phrases I write are commands to understand what I want, not to be written down. Understand their content well, then execute what is required.''' PHASE 4 — AI SNIPER™ HUB CUSTOMER ACCOUNTS & MAP SUBSCRIPTION ARCHITECTURE We are now working ONLY on the AI SNIPER™ Hub website project. IMPORTANT: This phase must NOT modify or access the separate AI SNIPER™ MAP project. The MAP application is a separate Python application that will eventually run at: https://app.aisniperhub.com The AI SNIPER™ Hub website is: https://aisniperhub.com OBJECTIVE Prepare the AI SNIPER™ Hub website to commercially sell AI SNIPER™ MAP and manage its customers, orders, subscriptions, and future MAP access. This is the commercial/customer-management foundation. DO NOT implement final MAP license enforcement in this phase. ================================================== 1. PROTECT THE EXISTING WEBSITE The current AI SNIPER™ Hub website is already working. DO NOT redesign, rebuild, or disturb existing: - Homepage - Product pages - AI SNIPER™ Smart Money Trading System - AI SNIPER™ AUTO - AI SNIPER™ AGENTS - AI SNIPER™ MAP product page - Research Hub - AI Assistant - Checkout UI unless specifically required - Existing orders - Existing admin - Existing navigation - Existing footer - Existing styling - Existing working functionality Make only the minimum changes required for this phase. ================================================== 2. CUSTOMER ACCOUNT FOUNDATION Create/prepare a proper customer account system for website customers. A customer account should support: - Customer ID - Name - Email - Account status - Registration date - Last login - Purchased products - Orders - Subscription information - MAP access information Do not expose sensitive customer information publicly. ================================================== 3. AI SNIPER™ MAP PRODUCT Ensure AI SNIPER™ MAP exists as a properly defined commercial product in the website's product/order architecture. The product should be identifiable internally as: AI SNIPER™ MAP Do not change the existing product branding or product-page design unless absolutely necessary. Prepare the product architecture to support different future plans, for example: - Monthly - Annual Do NOT add Lifetime unless specifically approved later. ================================================== 4. SUBSCRIPTION FOUNDATION Prepare the website database/backend to support subscription-based MAP access. At minimum the subscription model should be capable of storing: - Customer ID - Product ID - Plan - Subscription status - Start date - Renewal date - Expiration date - Cancellation status - Payment reference - External subscription/customer ID if required - Created/updated timestamps Support statuses such as: ACTIVE TRIAL PAST_DUE CANCELLED EXPIRED Do not invent payment-provider data. ================================================== 5. ORDER → SUBSCRIPTION RELATIONSHIP Prepare a clean relationship: CUSTOMER ↓ ORDER ↓ MAP PRODUCT ↓ SUBSCRIPTION ↓ MAP ACCESS ENTITLEMENT The system must be able to determine: Which customer purchased MAP? Which plan did they purchase? Is their subscription active? When does it expire? What MAP access should they receive? Do not yet enforce this against the MAP application. ================================================== 6. CHECKOUT PREPARATION Review the existing checkout/payment architecture. Ensure that when a customer purchases AI SNIPER™ MAP, the system can create the appropriate: Customer + Order + Product + Subscription record Do NOT replace the existing payment provider. Do NOT introduce a new payment provider unless specifically required and approved. Do NOT expose payment secrets in frontend code. If the existing payment system is not yet capable of recurring subscriptions, document exactly what is missing instead of making a large architectural change. ================================================== 7. CUSTOMER DASHBOARD Prepare the existing customer account area to eventually show: MY PRODUCTS MY ORDERS MY SUBSCRIPTIONS AI SNIPER™ MAP ACCESS ACCOUNT SETTINGS For AI SNIPER™ MAP, eventually the customer will see something similar to: AI SNIPER™ MAP Plan: [Plan] Status: Active Renewal: [Date] [ LAUNCH AI SNIPER™ MAP ] Do NOT activate the actual MAP launch connection yet unless it can safely be added without affecting the existing account system. ================================================== 8. MAP ACCESS RECORD Create a clean backend concept for MAP entitlement/access. For example: MAP_ACCESS - Customer/User ID - Product ID - Subscription ID - Access status - Granted date - Expiration date - MAP user identifier - Created/updated timestamps This will later be used by the MAP application to determine whether a customer is authorized. IMPORTANT: Do not create fake license keys. Do not hardcode access. Do not rely on a frontend button to provide security. The actual access decision will eventually be verified server-side. ================================================== 9. FUTURE MAP CONNECTION Prepare the website architecture for this future flow: Customer buys MAP ↓ Payment confirmed ↓ Order created ↓ Subscription created ↓ MAP entitlement created ↓ Customer can launch MAP ↓ MAP verifies entitlement ↓ MAP access granted For Phase 4, implement the website-side foundation only. Do NOT yet require the MAP application to trust a frontend request. Please ask for remaining part of this section and i will send you the 2nd part once all above done.