Skip to content

PiAgent_Daemon_Architecture.md

Latest commit

 

History

History
53 lines (43 loc) · 2.3 KB

PiAgent_Daemon_Architecture.md

File metadata and controls

53 lines (43 loc) · 2.3 KB

Jarvis Universal System Architecture v2.0

This document outlines the architecture for the "All-Rust" highly performant Jarvis ecosystem. We have moved away from Python-based agent cores to achieve maximum security, memory safety, and native system integration.

System Flow

graph TD
    subgraph Host_Hardware [Host Device - Drone/Mac/EV]
        direction TB
        
        subgraph Nervous_System [Rust Supervisor Daemon]
            WM[Watchdog Service]
            SM[Hardware Telemetry Monitor]
        end

        subgraph Brain_Core [Rust Agentic Core]
            LLM[Native OpenRouter/LLM Engine]
            Comm[Encrypted Comm Layer: Telegram/Radio]
            Context[Identity & Context Manager]
        end

        subgraph Modular_Extensions [Dynamic Rust Plugins / WASM]
            Ext1[Drone MAVLink Plugin]
            Ext2[Programmer Desktop Plugin]
        end

        WM -->|1. Spawns & Keeps Alive| Brain_Core
        SM -->|2. Injects Telemetry| Brain_Core
        Brain_Core -->|3. Loads Device Tools| Modular_Extensions
        Comm <-->|4. Encrypted User Input| Brain_Core
    end
Loading

1. The Nervous System (Rust Daemon)

  • Role: Pure Watchdog.
  • Action: Starts automatically on system boot (via systemd/launchd).
  • Responsibility: Injects hardware context (RAM, CPU, Device Type) into environment variables and keeps the Agentic Core running. It handles zero LLM logic.

2. The Brain (Rust Agentic Core)

  • Role: The execution pipeline.
  • Why Rust instead of Python? Maximum performance, memory safety (crucial for drones), concurrent tool execution, and zero-dependency deployments (no pip installs needed on a military drone).
  • Responsibility:
    1. Opens connection to User (Telegram for Desktop, Encrypted Mesh Radio for Defense).
    2. Parses user intent using OpenRouter/Local LLaMA APIs.
    3. Executes system tasks directly natively.

3. The Polymorphic Extensions (Modular Tooling)

The Agentic Core is universal. It doesn't know what it is until it loads its extensions. We use a high-performance plugin architecture (e.g., WebAssembly (WASM) or dynamic Rust libraries).

  • Drone Extension: Provides takeoff(), read_gps().
  • Programmer Extension: Provides git_commit(), read_file().
  • EV Extension: Provides read_can_bus(), set_climate().