Architecture Dashboard | Remote Production

Welcome to the Architecture Dashboard

Explore Remote Production's solution architecture, understand how systems cooperate, and navigate our process landscape.

security Core Architectural Principle

Every user interaction flows through Cloudflare. No exceptions. This ensures consistent security, global performance, and complete visibility.

layers Hybrid Platform Architecture

flowchart TB
    subgraph Users["👥 USERS & CUSTOMERS"]
        Staff[Staff & Operators]
        Customers[Customers & Partners]
        Systems[External Systems]
    end

    subgraph Cloudflare["☁️ CLOUDFLARE EDGE PLATFORM"]
        subgraph Security["🔒 Security Layer"]
            ZT[Zero Trust Access
SSO Authentication]
            WAF[WAF & DDoS
Protection]
        end
        subgraph Compute["⚡ Compute Layer"]
            Workers[Workers
APIs & Logic]
            Pages[Pages
UIs & Dashboards]
        end
        subgraph Data["💾 Data Layer"]
            D1[D1 Database]
            KV[KV Cache]
            R2[R2 Storage]
        end
        Tunnel[Cloudflare Tunnel]
    end

    subgraph PrivateCloud["🏢 PRIVATE CLOUD - Proxmox"]
        VMs[Virtual Machines
Specialized Workloads]
        Storage[TrueNAS Storage
Media & Archives]
        ProcNodes[Proc Nodes
Video Processing]
    end

    %% User access - ALL through Cloudflare
    Staff --> ZT
    Customers --> WAF
    Systems --> WAF

    %% Security to Compute
    ZT --> Workers
    ZT --> Pages
    WAF --> Workers
    WAF --> Pages

    %% Compute to Data
    Workers --> D1
    Workers --> KV
    Workers --> R2

    %% Cloudflare to Private Cloud via Tunnel
    Workers --> Tunnel
    Tunnel --> VMs
    Tunnel --> Storage
    Tunnel --> ProcNodes

    %% Styling
    classDef users fill:#e3f2fd,stroke:#1976d2,stroke-width:2px
    classDef security fill:#c8e6c9,stroke:#388e3c,stroke-width:2px
    classDef compute fill:#fff3e0,stroke:#f57c00,stroke-width:2px
    classDef data fill:#fff3e0,stroke:#f57c00,stroke-width:2px
    classDef tunnel fill:#ff9800,stroke:#e65100,stroke-width:2px,color:#fff
    classDef private fill:#e8eaf6,stroke:#3f51b5,stroke-width:2px

    class Staff,Customers,Systems users
    class ZT,WAF security
    class Workers,Pages compute
    class D1,KV,R2 data
    class Tunnel tunnel
    class VMs,Storage,ProcNodes private

Users - All access through Cloudflare (no exceptions)

Security - Zero Trust authentication, WAF protection

Cloudflare - Edge compute, storage, and caching

Tunnel - Secure connection to Private Cloud

Private Cloud - Proxmox VMs, storage, video processing

troubleshoot Service Diagnostics and Multi-Level Problem Resolution Framework

🎯 Enterprise Epic: Comprehensive observability and debugging capability across all API services

Epic Goal: Enable any stakeholder—from L1 support to senior developers—to efficiently diagnose, debug, and resolve issues across all API-based services through standardized tooling, operational knowledge, and multi-level resolution workflows.

graph TB
    subgraph Epic["Enterprise Epic: Service Diagnostics Framework"]
        subgraph Standards["Architecture Standard"]
            API[API Request Logging
Machine-to-Machine Dialogues
Multi-Level Views]
            Workflows[Problem Resolution Workflows
L1 to L2 to Developer Escalation]
        end

        subgraph Knowledge["Operational Knowledge"]
            Skill[Service Diagnostics Skill
Claude Code Integration
Debugging Patterns]
            Training[Training Materials
Runbooks
Best Practices]
        end

        subgraph Implementation["Reference Implementation"]
            POC[POC in Resource Dispatcher
Incoming Requests Log UI
Dialogue Storage]
            Library[Reusable TypeScript Library
Logging Functions
UI Components]
        end

        subgraph Enablement["Organizational Enablement"]
            DevStandards[Development Standards Update
Required for New Services
Code Review Checklist]
            Rollout[Rollout to Existing Services
Process Conductor
Architecture Dashboard]
        end
    end

    subgraph Stakeholders["Multi-Level Stakeholders"]
        L1[Level 1: Support
Quick Health Check
Status Overview]
        L2[Level 2: Support Engineer
Functional Diagnosis
Detailed Summary]
        L3[Level 3: Senior Developer
Technical Analysis
Complete Audit Trail]
    end

    subgraph Outcomes["Success Outcomes"]
        FastDebug[Integration debugging
reduced to under 15 min]
        Empowerment[L1 resolves 30 percent more
issues without escalation]
        ClaudeCode[Efficient Claude Code
assisted resolution]
    end

    API --> POC
    API --> Library
    Skill --> Training
    POC --> Rollout
    Library --> Rollout
    Library --> DevStandards
    Workflows --> Training

    POC --> L1
    POC --> L2
    POC --> L3

    L1 --> FastDebug
    L2 --> Empowerment
    L3 --> ClaudeCode

    classDef standard fill:#e3f2fd,stroke:#1976d2,stroke-width:2px
    classDef knowledge fill:#fff3e0,stroke:#f57c00,stroke-width:2px
    classDef impl fill:#f3e5f5,stroke:#7b1fa2,stroke-width:2px
    classDef enable fill:#e8f5e9,stroke:#388e3c,stroke-width:2px
    classDef stakeholder fill:#fce4ec,stroke:#c2185b,stroke-width:2px
    classDef outcome fill:#e0f2f1,stroke:#00796b,stroke-width:2px

    class API,Workflows standard
    class Skill,Training knowledge
    class POC,Library impl
    class DevStandards,Rollout enable
    class L1,L2,L3 stakeholder
    class FastDebug,Empowerment,ClaudeCode outcome

Epic Components (8 Tasks)

Architecture Standard

Define EA standard for API observability with machine-to-machine dialogue logging

Service Diagnostics Skill

Codify debugging knowledge for Claude Code-assisted problem resolution

POC in Resource Dispatcher

Build reference implementation with Incoming Requests Log UI

Reusable Library

Extract common patterns into TypeScript utilities and UI components

Multi-Level Workflows

Document L1 to L2 to Developer escalation paths and procedures

Rollout to Services

Deploy to Process Conductor, Architecture Dashboard, and existing services

Development Standards

Integrate into project creation, code review, and compliance processes

Training Materials

Create runbooks and training for support teams and developers

Epic Status & Dependencies

pending_actions

Epic Status: Planning Phase

Awaiting CTO approval per governance model

check_circle

Task 1: Architecture Standard

Defined and submitted to enterprise-continuum

schedule

Tasks 2-8

Pending approval to proceed with implementation

Dependencies

Requires: CTO approval, TypeScript standards compliance, Cloudflare infrastructure access
Enables: Faster integration debugging, better Claude Code-assisted development, reduced escalations to senior developers

explore Architecture Views

account_tree

architecture Architecture Dashboard