Skip to content

Low-Level Module Descriptions

Summary: This document provides a detailed breakdown of the individual modules and components within STRIDE. It complements the High-Level Architecture Diagram by offering a more granular view.

1. Auth Service (Google SSO)

1.1. Responsibilities

  • Handles Google SSO authentication and role-based access control (Sales, Enablement, Admin).
  • Issues and validates JWTs for secure API access.
  • Maintains audit logs for all login and access events.

1.2. Module Interaction Diagram

sequenceDiagram
    participant User
    participant WebApp as Web App
    participant APIGateway as API Gateway
    participant AuthService as Auth Service
    participant DB as Database

    User->>WebApp: Login with Google SSO
    WebApp->>APIGateway: /auth/callback (Google token)
    APIGateway->>AuthService: Validate Google token
    AuthService->>DB: Fetch user/role
    DB-->>AuthService: Return user record
    alt Valid User
        AuthService->>APIGateway: Issue JWT
        APIGateway-->>WebApp: 200 OK with JWT
    else Invalid
        AuthService-->>APIGateway: Unauthorized
        APIGateway-->>WebApp: 401 Unauthorized
    end

2. Content Ingestion Service

2.1. Responsibilities

  • Connects to Notion, Google Drive, and public APIs to ingest sales collateral.
  • Deduplicates, indexes, and stores content assets in the database.
  • Triggers tagging workflows for new/updated content.

2.2. Key Flows

  • Scheduled sync jobs for Notion/Drive.
  • Manual upload via UI.
  • Bulk import via CSV.

3. Tagging Engine

3.1. Responsibilities

  • Applies and enforces structured tags (industry, stage, outcome, product, relevance) to all content.
  • Supports tagging via UI and CSV upload.
  • Validates tagging standards and prevents untagged content from being discoverable.

3.2. Key Endpoints

  • POST /api/v1/assets/{id}/tags: Apply tags to a content asset.
  • GET /api/v1/tags: List all tags and their usage.

4. Search Engine

4.1. Responsibilities

  • Indexes all content and tags for fast, contextual search.
  • Supports natural language queries and advanced filters.
  • Ranks results by relevance and usage.

4.2. Key Endpoints

  • GET /api/v1/search?q=...: Search content by query and filters.

5. Smart Content Pack Builder

5.1. Responsibilities

  • Allows users to compile, export, and share personalized content packs (case studies, decks, narratives).
  • Supports PDF export and sharing via link.

5.2. Key Flows

  • Select content → Compile pack → Download/share as PDF.

6. Analytics & Reporting

6.1. Responsibilities

  • Tracks content usage, search trends, and win rates.
  • Provides dashboards and exportable reports for enablement and leadership.

6.2. Key Endpoints

  • GET /api/v1/analytics/usage: Usage stats by content, tag, and user.
  • GET /api/v1/analytics/search: Search trends and gaps.

For implementation details, refer to the Code Walkthroughs.