How finnovusconsulting/test works
Project Type and Purpose
• This is a full-stack, enterprise-grade AI platform (“Finnovus AI”) providing financial insights via a multi-agent system (the “Finnovus Five”), plus BI modules (reporting, payroll, file collaboration), multilingual voice, credit/billing, RBAC security, and JSON export APIs.
File Structure (inferred from README)
• Top-level service folders for each AI agent: /ace-advisory, /hannan-tax, /lex-compliance, /predictive-evaluation (NOVA Forecasting).
• Business modules: /reports, /file-collaboration, /payroll, /billing, /credit-cockpit.
• Shared/backend code under server/: engines (ace-engine.ts, hannan-tax-engine.ts, lex-compliance-engine.ts, voice-engine.ts), routes (routes.ts), billing/payment (payment-manager.ts), storage layer, enhanced payroll/reporting services.
• Shared schema definitions: shared/schema.ts.
• Frontend code under client/: pages in client/src/pages/*.tsx, Vite, Tailwind, shadcn/ui, Wouter routing, TanStack Query.
• Config files: package.json, drizzle.config.ts, environment variables, Replit deployment.
README for Architectural Insights
• Frontend: React+TypeScript SPA served by Vite Dev Server/static hosting.
• Backend: Node.js + Express.js monolith (modularized into sub-services) with Passport.js sessions.
• Database: PostgreSQL accessed via Drizzle ORM.
• External Integrations: OpenAI GPT-4, Stripe, SendGrid, Make.com webhooks.
• Security: RBAC, rate limiting, input sanitization, audit logging.
Main Components & Relationships
a. Frontend (Browser SPA)
• Pages/components call backend JSON APIs over HTTPS.
• State management with TanStack Query; routing with Wouter.
b. API Gateway (Express.js)
• Central server/routes.ts routes to sub-modules.
• Middlewares: authentication/session, RBAC, rate limiter, input sanitizer, audit logger.
c. Business Logic Modules (Node services)
• AI Engines: ACE, Hannan Tax, LEX Compliance, NOVA Forecasting, Voice Engine.
• BI Modules: Reporting, File Collaboration, Enhanced Payroll, Credit & Billing.
• Each module exports its own route handlers and credits-billing logic.
d. Data Layer
• PostgreSQL database (schema in shared/schema.ts).
• Drizzle ORM for queries and migrations.
• Storage layer for file uploads (Excel, CSV, docs).
e. External Services
• OpenAI API for LLM calls (GPT-4).
• Stripe for payments.
• SendGrid for emails.
• Make.com via JSON-export webhooks.
f. Infrastructure & Deployment
• Replit auto-scaling with health checks and TLS.
Architectural Patterns & Design Principles
• Modular Monolith: logically separated modules within one Express app.
• Credit-based billing interceptor on each service.
• Shared middleware for security, logging, sessions.
• Multi-agent design: each AI engine is a separate component interacting via unified API.
• Clear separation of concerns: UI vs. API vs. data vs. external integrations.