01-Product / 01.01.Project-Overview

01.01.Project Overview

01.01. Project Overview

Introduction

Car Pulse Tracker (CPT) is a full-stack platform designed to generate comprehensive, verified PDF reports for Tesla vehicles. It leverages the Tesla Fleet API to acquire real-time battery health, charging history, and service data.

High-Level Architecture

The system is built as a modular monolith following a Connect-First (v2) session-based architecture.

• Frontend (WUI): Vue 3 (TypeScript) SPA using Pinia for state management and Tailwind CSS for styling.
• Backend (API): FastAPI (Python) handles OAuth orchestration, vehicle data acquisition, and report generation.
• Utility (UTL): Docker and Make-based orchestration for local development and CI/CD.
• Infrastructure (INF): Terraform-managed GCP resources (Cloud Run, GCS, Secret Manager, Memorystore).
• Configuration (CNF): YAML-based multi-environment configuration pipeline.

Documentation Map

02. Architecture & Design

• 02.01. Core Data Architecture: The source of truth for the session-based data acquisition model.
• 02.02. Tesla Integration Design: Detailed mapping of Tesla Fleet API responses to internal models.
• 02.03. UI Design System: Glassmorphism and Tailwind-based design principles.

03. Development & Setup

• 03.01. API Setup: Backend setup guide.
• 03.02. WUI Setup: Frontend setup guide.
• 03.08-03.11 Style Guides: Coding and naming conventions.

04. Integrations

• 04.01. Tesla API: OAuth flow and endpoint proxying.
• 04.02. Payment Integration: Stripe and PayPal integration strategy.

05. Specifications

• 05.01. Puppeteer PDF Spec: The proactive high-fidelity PDF generation flow.

06. Operations & Scalability

• 06.01. API Operations: Production deployment and maintenance.
• 06.05. Scalability Analysis: System limits and scaling strategy.

Key System Flows

1. Data Acquisition (v2)

1. User connects Tesla via OAuth (managed by cpt-api).
2. API fetches vehicle inventory and creates an OrderSession in Redis.
3. User selects a report package and vehicle(s).
4. API triggers background data acquisition and normalization into a VehicleSnapshot.

2. Proactive PDF Generation

1. Upon successful fetch, cpt-api triggers pdf-api (Puppeteer).
2. pdf-api renders the report in a clean "print-view" route.
3. PDF is uploaded to GCS and a download hook is registered in Redis.
4. User clicks download and receives the pre-generated PDF.

Security & Privacy

• Statelessness: No PII stored in persistent databases; everything is transient in Redis with strict TTLs.
• Isolation: Each request is scoped to a high-entropy session_id.
• Cleanup: Background tasks ensure sensitive data (PDFs, traces) are deleted shortly after use.

---

Maintained by BNC CPT Team