High-Level Architecture (Pebble Orchestrator)¶

This document describes the Technical Foundation and Data Flow for the Pebble Business Orchestrator. For a phase-by-phase delivery schedule, see the MVP Scope.

System Overview¶

The Pebble Orchestrator is a multi-entity, event-driven architecture built to unify chaotic communication (Email) into structured operational workflows (Kanban → CRM → ERP).

• Multi-Entity Architecture: Parallel data silos for legal entities (e.g., entity_A, entity_B) with cumulative reporting.
• Visual-First Workspaces: Leveraging React-based Kanban boards for triage.
• Sync-Heavy Design: Bi-directional connectors for Odoo, Zoho, Focus RT, and Business Central.
• AI-Augmented Logic: Stream classification (Sales vs Ops vs Tender) based on intent.

Orchestrator Diagram¶

flowchart TB
    subgraph Channels["Communication Channels"]
        A1[Outlook / Office 365]
        A2[Third-Party APIs]
        A3[Excel / Bulk Data]
    end

    subgraph Ingestion["Ingestion Layer"]
        B[Email Listener Service]
        C[Batch Ingestion API]
    end

    subgraph Core["Core Orchestration Engine"]
        D[Classification / Stream Selection]
        E[Work Shifting Engine]
        F[Workflow / SLA Manager]
    end

    subgraph Workspace["Visual Workspace"]
        G[Business Kanban UI]
        H[Sales Follow-up Dash]
    end

    subgraph Sync["Integration Layer"]
        I[CRM Connector]
        J[ERP Connector]
    end

    subgraph Data["Data & Identity"]
        K[(Multi-Entity Master DB)]
        L[(Email Card Store)]
        M[(Validation Cache)]
    end

    A1 --> B
    A2 --> B
    A3 --> C
    B --> D
    C --> D
    D --> E
    E --> F
    F --> G
    F --> H
    G <--> I
    H <--> J
    I <--> K
    J <--> L
    K <--> M

Core Operational Components¶

1. Ingestion & Triage¶

Purpose: Listen to sales@, logistics@, and tender@ mailboxes. - Action: Converts every email thread into a persistent "Email Card". - Strategy: Deduplicates against existing Prelead/CRM data to prevent "Duplicate Lead Burnout".

2. Stream Classification (AI)¶

Purpose: Direct incoming cards to the correct functional board. - Streams: - CRM Stream: New enquiries, meeting requests, follow-ups. - ERP Stream: Orders, Invoices, Payment notifications. - Tender Stream: NIT documents, Bid requirements.

3. Visual Kanban (Wekan/Taiga Logic)¶

Purpose: The primary UI for user interaction. - Architecture: A state-machine where column transitions (e.g., Negotiation → Closed Won) trigger bi-directional sync with CRM/ERP systems.

4. Integration Bus¶

Purpose: Bi-directional synchronisation with external systems. - Master-Slave Logic: Pebble acts as the source of truth for Engagement, while CRM/ERP remains the source of truth for Financials.

Multi-Entity Data Strategy¶

To support multi-entity organizations (e.g., 3 legal entities), the architecture employs a Federated Master Data approach.

Technical Performance Targets¶

Security & Compliance¶

• Auth: JWT-based RBAC (Role-Based Access Control).
• Audit: Every card move and attribute change is logged for SLA tracking.
• Privacy: TLS 1.3 for all data in transit; AES-256 for credentials/tokens.

← Back to Use Cases | View MVP Scope