dev-adeshina/fiel

Purpose and Entry Points

A Laravel restaurant operations backend: public/customer APIs cover authentication, menus, carts, checkout, payments, and reservations; staff operate a Filament admin panel for menus, kitchen orders, inventory, tables, reporting, and analytics. HTTP enters through public/index.php, API route aggregates in routes/api.php and routes/api/v1/*.php, and CLI work through artisan.

Application Shape and Boundaries

Business logic is organized as bounded domains under app/Domains, rather than controller-centric code. Controllers validate request data, invoke domain Actions, and return API Resources. Actions coordinate Services, Repositories, Eloquent Models, and DTOs; this establishes the primary HTTP-to-domain-to-persistence boundary. Examples: app/Http/Controllers/Order/CheckoutController.php, app/Domains/Order/Actions/CheckoutAction.php, app/Domains/Order/Repositories/OrderRepository.php.

Identity and Authorization

The Auth domain owns user lifecycle: registration, login/logout, password recovery/change, email verification, account deletion, and related events/notifications. Sanctum configuration indicates token-based API authentication; permissions/roles are persisted and enforced by policies. Key paths: app/Domains/Auth/Services/AuthService.php, app/Domains/Auth/Models/User.php, config/sanctum.php.

Catalog, Cart, and Checkout

Menu management models menus, categories, items, variants, modifiers, and time/availability records. Customers add configured items to persistent carts; cart calculation precedes checkout. Checkout produces orders and order items, with status/payment-status state models and a separate inventory integration boundary. Key paths: app/Domains/Menu/Services/MenuItemService.php, app/Domains/Cart/Services/CartCalculationService.php, app/Domains/Order/Services/OrderInventoryService.php.

Payments and External Provider Boundary

Payments are provider-agnostic behind PaymentGatewayInterface and selected by PaymentGatewayManager. Supported gateway implementations include Stripe (card, Apple Pay, Google Pay), Paystack, PayPal, and Flutterwave. Initialization, verification, cancellation, refund, and provider callbacks are modeled separately; inbound webhooks are a critical trust boundary. Key paths: app/Domains/Payment/GatewayInterfaces/PaymentGatewayInterface.php, app/Domains/Payment/Manages/PaymentGatewayManager.php, app/Domains/Payment/Webhooks/StripeWebhookHandler.php.

Restaurant Operations

Inventory records items and movements, with explicit stock-adjustment actions and analytics. Reservations allocate restaurant tables, detect conflicts, and transition statuses; scheduled expiry processing runs from a console command. Kitchen-facing order endpoints/pages support operational status flow. Key paths: app/Domains/Inventory/Actions/AdjustInventoryStockAction.php, app/Domains/Reservation/Services/TableAssignmentService.php, app/Console/Commands/ProcessReservationExpiry.php.

Administration, Data, and Runtime

Filament is the staff UI and directly exposes domain-backed resources plus dashboards for kitchen, sales, inventory, and reservation analytics. Relational persistence is managed through Laravel migrations for users, catalog, carts, orders, payments, inventory, and reservations. Runtime infrastructure is Laravel/PHP with database, cache, queue, mail, filesystem, and payment/service settings configurable under config/; Vite supplies frontend assets. Key paths: app/Providers/Filament/AdminPanelProvider.php, app/Filament/Pages/KitchenDashboard.php, database/migrations/2026_05_14_233653_create_orders_table.php.