How tactspace/complimo works
Main Components
• Frontend Component:
• Next.js application.
• Sub-components: Chat (ChatInterface, ComplianceList, FileUpload), Navigation (Navbar), and data visualization.
• React & TypeScript usage.
• Backend Component:
• Integration points with external libraries like LangChain and OpenAI.
• Dependencies on Poppler-utils for PDF processing.
• Data ingestion elements such as the CSV file with data points.
• Infrastructure:
• Dockerized environments for both frontend and backend (Dockerfiles in each directory).
• Docker Compose orchestrator (docker-compose.yml) that ties the services together.
• Environment variables configuration (e.g., API keys and URLs in .env files).
• External Services / Dependencies:
• OpenAI API: For AI functionalities.
• ChromaDB: As the vector store for handling document and compliance data.
• Optional: Any external monitoring or logging services (if applicable; but primarily focus on the documented ones).
Relationships and Interactions
• Bidirectional data flow between the frontend and backend.
• How the frontend makes API requests to the backend, with endpoints exposed by FastAPI.
• A data path for document uploads leading to PDF processing via Poppler-utils.
• Docker infrastructure: how the docker-compose setup launches both services and possibly links to other containers (if present).
Architectural Patterns and Design Principles
• Separation of concerns:
• Frontend for user interaction and rendering.
• Backend for business logic, AI integrations, and compliance checking.
• Use of containerization (Docker) to maintain isolated, scalable, and reproducible environments.
• Optionally, if there is any microservice-like boundary in the backend (for instance, if compliance checking is modular), you may note it.