tausicapital-afk/vfw

Purpose and entry points

VFW Console is an internal sales and accounting system for fashion events. It manages sales submissions from pricing through accounting approval and QuickBooks hand-off, preserving financial history and audit records. The production application is a React SPA plus NestJS API; vfw-console.html remains a standalone demo/prototype.

• frontend/src/main.tsx

• frontend/src/App.tsx

• backend/src/main.ts

• vfw-console.html

Frontend application boundary

The React/Vite SPA provides role-aware operational screens for submissions, approval queues, contacts, reporting, payroll, attendance, messaging, email, and administration. Authentication state and API access are centralized, while the shell hosts common navigation and export affordances.

• frontend/src/auth/AuthContext.tsx

• frontend/src/lib/api.ts

• frontend/src/shell/Shell.tsx

• frontend/src/pages/Submissions.tsx

API composition, authentication, and authorization

NestJS is organized into domain modules/controllers registered by the application module. Cookie-backed JWT sessions, Argon2 credentials, invitation/signup and OTP flows establish identity. Guarding and permission checks are centralized rather than delegated to the client.

• backend/src/app.module.ts

• backend/src/auth/auth.controller.ts

• backend/src/auth/auth.service.ts

• backend/src/common/auth.guard.ts

• backend/src/common/acl.ts

Core financial submission lifecycle

Submission is the central financial record. Sales creates priced submissions from catalog inputs; server-side pricing calculates monetary amounts; accounting controls status transitions, accounting fields, invoicing, void/split behavior, and installment plans. PDF invoices/documents and approval evidence are associated at this boundary.

• backend/src/submissions/submissions.controller.ts

• backend/src/submissions/submissions.service.ts

• backend/src/pricing/pricing.service.ts

• backend/src/submissions/invoice-pdf.ts

• backend/src/submissions/installments/installments.service.ts

Persistence, catalog, and audit trail

Prisma defines the authoritative PostgreSQL model and migrations. The schema includes users, invitations, catalog/pricing, submissions, payments, contacts, documents, audit entries, and configuration. Audit/activity services expose append-oriented operational history; data retention favors status transitions and soft deletion over deleting financial records.

• backend/prisma/schema.prisma

• backend/prisma/migrations/20260713040342_init/migration.sql

• backend/src/prisma/prisma.service.ts

• backend/src/audit/audit.service.ts

• backend/src/activity/activity.service.ts

Operational integrations and derived workflows

Approved sales feed export datasets, including a QuickBooks ledger hand-off. Contacts are managed alongside sales. The system also supports real-time messaging via a gateway, inbound/outbound email with configurable provider/accounts, object storage for documents, attendance/profile/payroll workflows, and health probes.

• backend/src/export/export.service.ts

• backend/src/export/datasets/qbo-ledger.dataset.ts

• backend/src/messaging/messaging.gateway.ts

• backend/src/emails/inbound.service.ts

• backend/src/storage/storage.service.ts

Runtime and deployment

Frontend is built by Vite and served by nginx; backend runs Node/NestJS with Prisma against PostgreSQL 16. Local Compose supports database-only development and a full three-container stack. Railway deploys Postgres, backend, and frontend separately; backend startup applies migrations. GitHub Actions define CI, backup, and optional deployment automation.

• docker-compose.yml

• backend/Dockerfile

• frontend/Dockerfile

• backend/railway.json

• .github/workflows/ci.yml