# haole3435/generate-meeting architecture

> Architecture diagram of the GitHub repository haole3435/generate-meeting, generated by GitDiagram from its file tree, README and a sample of source files (last updated 2025-04-05). It is an AI-made overview: check details against the source.

- Interactive diagram: https://gitdiagram.com/haole3435/generate-meeting
- Repository: https://github.com/haole3435/generate-meeting

## Overview

##### Project Type and Purpose
- This is a full-stack application designed to automatically generate meeting minutes. It processes audio (or text) inputs by converting audio to text, summarizing content, extracting key points, and generating a professional Word document.
- The README clearly splits the system into Frontend (Streamlit), Backend (FastAPI), and Core Processing (handling transcription, text analysis, etc.).

##### Main Components
a. Frontend:
- Mention that it provides an intuitive user interface.
b. Backend:
c. Core Processing:
- Inside the backend workflow, identify a core module that includes:
- Audio Processing (conversion of uploaded audio files to a standardized format like WAV using FFmpeg)
- Transcription utilizing OpenAI Whisper
- Text Analysis and Summarization using GPT-4 (abstract summaries, extraction of key points, action items, and sentiment analysis)
d. Output Generation:
- A component where processed data is formatted into a professional Word document and saved under the outputs directory.
e. Auxiliary Components:
- A component for “Schemas/Models” to represent how data is structured and validated within the system.

##### Relationships and Interactions
- From the Frontend to the Backend, representing API calls and data submission (file uploads and form inputs).
- From the Backend to the Core Processing module, indicating the initiation of audio conversion/transcription and text analysis workflows.
- From Core Processing to Output Generation to show that processed and analyzed information is formatted into Word documents.
- Communication between containerized services if considering Docker (e.g., inter-service communication within a Docker network).

##### Architectural Patterns & Technology Highlights
- Layered architecture: separation of concerns is achieved by having discrete components for the frontend (UI), backend (API and data orchestration), and core processing (business logic and analytics).
- Use of FastAPI (backend) and Streamlit (frontend) as major frameworks.
- That the system uses Python modules to encapsulate processing logic (chains.py, models.py, processing.py).
- External dependencies like FFmpeg for audio processing and the OpenAI API for both transcription and text analysis.

##### Detail and Clarity
- Every component is as detailed as possible. For example, under “Core Processing”, subdivide into “Audio Processing”, “Transcription”, and “Text Analysis”.
- Sub-notes to mention that the “Schemas/Models” component (located under app/schemas) defines the data structure and validation rules.

## Diagram (Mermaid)

```mermaid
flowchart TD
    %% Global nodes
    FE("Frontend (Streamlit)"):::frontend
    BE("Backend (FastAPI)"):::backend
    SM("Schemas/Models"):::schemas
    ES("External Services (FFmpeg & OpenAI API)"):::external
    OG("Output Generation (Word Document)"):::output

    %% Subgraph for Core Processing
    subgraph "Core Processing"
        CP1("Audio Processing (FFmpeg Conversion)"):::processing
        CP2("Transcription (OpenAI Whisper)"):::processing
        CP3("Text Analysis & Summarization (GPT-4)"):::processing
        CP1 -->|"converted"| CP2
        CP2 -->|"transcribed"| CP3
    end

    %% Subgraph for Deployment Configuration
    subgraph "Deployment"
        DC1("docker-compose.yml"):::deployment
        DC2("Dockerfile"):::deployment
    end

    %% Connections between main components
    FE -->|"API_call"| BE
    BE -->|"initiate_processing"| CP1
    CP3 -->|"format_data"| OG
    BE -->|"validate_data"| SM

    %% Connections to External Services (dashed arrows)
    CP1 -.->|"uses"| ES
    CP2 -.->|"uses"| ES
    CP3 -.->|"uses"| ES

    %% Deployment configuration dependencies (dashed arrows)
    DC1 -.->|"deploys"| FE
    DC1 -.->|"deploys"| BE
    DC1 -.->|"deploys"| CP1
    DC2 -.->|"builds"| BE

    %% Click Events
    click FE "https://github.com/haole3435/generate-meeting/blob/main/app/frontend/main.py"
    click BE "https://github.com/haole3435/generate-meeting/blob/main/app/backend/main.py"
    click CP1 "https://github.com/haole3435/generate-meeting/blob/main/app/core/processing.py"
    click CP2 "https://github.com/haole3435/generate-meeting/blob/main/app/core/chains.py"
    click CP3 "https://github.com/haole3435/generate-meeting/blob/main/app/core/models.py"
    click OG "https://github.com/haole3435/generate-meeting/tree/main/app/backend/outputs"
    click SM "https://github.com/haole3435/generate-meeting/blob/main/app/schemas/model.py"

    %% Styles
    classDef frontend fill:#ffcc00,stroke:#333,stroke-width:2px;
    classDef backend fill:#66ccff,stroke:#333,stroke-width:2px;
    classDef processing fill:#ccffcc,stroke:#333,stroke-width:2px;
    classDef output fill:#ff9999,stroke:#333,stroke-width:2px;
    classDef schemas fill:#ccccff,stroke:#333,stroke-width:2px;
    classDef external fill:#ffccff,stroke:#333,stroke-width:2px;
    classDef deployment fill:#d9d9d9,stroke:#333,stroke-width:2px;
```
