# PROJECT.md # Inveetaire Project Overview Version: 1.0 Status: ACTIVE --- # Project Summary Project Name Inveetaire Product Type Wedding Management Platform (SaaS) Target Market Indonesia Primary Users - Couple - Wedding Organizer (WO) - Event Crew - Super Admin Guest users do not require accounts. --- # Vision Create a single operational workspace that connects everyone involved in a wedding. One Wedding. One Workspace. Everyone Aligned. --- # Product Positioning Inveetaire IS: ✓ Wedding Management Platform ✓ Guest Management Platform ✓ Wedding Day Operation Platform ✓ Vendor Coordination Platform ✓ Planning Dashboard ✓ Reporting Platform Inveetaire IS NOT: ✗ Digital Invitation Builder ✗ Accounting Software ✗ CRM ✗ Vendor Marketplace ✗ WhatsApp Replacement ✗ Wedding Inspiration Website --- # Product Philosophy Technology supports the event. Technology never becomes a dependency that can stop the event. The goal is operational awareness, not automation. Every feature should reduce confusion. Every screen should answer: "What does the user need to know right now?" --- # Core Lifecycle Every Workspace moves through these phases. Planning ↓ Invitation ↓ RSVP ↓ Wedding Day ↓ Reporting ↓ Archive --- # Workspace Model One Workspace represents one customer. A Workspace contains: - Couple - Wedding Events - Guests - Vendors - Communications - Media - Dashboard - Reports - Settings Workspace is the highest business boundary. Every operational record belongs to exactly one Workspace. --- # Event Model A Workspace contains one or more Wedding Events. Examples: Wedding - Holy Matrimony - Reception Engagement - Engagement Ceremony Future - Sangjit - Tea Pai - After Party Guests may be invited to one or more Events. Operational data is Event-specific. Guest experience remains unified. --- # Guest Philosophy One Guest ↓ One Guest Code ↓ One Invitation URL ↓ One QR Code ↓ One Guest Journey Invitation content is generated dynamically based on assigned Events. --- # User Roles Super Admin Platform management. Couple Workspace owner. Event Crew Wedding day operation. Guest No account. Uses invitation URL only. --- # Main Modules Core Authentication Workspace Theme Engine Guest Management Invitation RSVP Communication Vendor Dashboard Wedding Day Reports Settings Super Admin --- # Architecture Principles Modular Architecture Service Layer Thin Controllers Fat Services Reusable Components Workspace Isolation Soft Delete Audit Logging Future Ready --- # Technology Stack Backend Native PHP 7.4 Frontend HTML5 TailwindCSS Alpine.js FontAwesome Database MariaDB / MySQL Hosting Shared Hosting (cPanel) Future PostgreSQL Laravel React REST API --- # Design Principles Keep everything simple. Never sacrifice reliability for fancy features. Every workflow must still work if the internet becomes unstable. Every feature must support real wedding operations. --- # AI Reminder This document explains WHAT the project is. Implementation rules belong in: AI.md Architecture belongs in: SAD Database belongs in: DDD PDD Implementation belongs in: MIB Coding rules belong in: TCS Never duplicate those documents. Reference them instead. --- ## AI Independence Inveetaire is AI-agnostic. No implementation shall depend on a specific AI model or chat history. Project knowledge must live inside the repository. Every AI assistant is replaceable. Before implementation, every AI must synchronize itself using: - AI.md - PROJECT.md - WORKFLOW.md - IMPLEMENTATION_ROADMAP.md - Project Documentation - AI Responses - Current Repository State Chat history must never be considered the source of truth. The repository is the source of truth. --- # Final Statement Every decision made in this project should support one objective: Helping couples, Wedding Organizers, and event crews stay aligned throughout the entire wedding lifecycle. If a feature does not contribute to that objective, it should be questioned before implementation.