Rihario System Architecture

This document outlines the high-level architecture of the Rihario autonomous testing platform. It serves as the canonical reference for system behavior, security isolation, and decision-making logic.

1. High-Level Design

Rihario is designed as a distributed, event-driven system. It separates the Control Plane (Dashboard, API) from the Execution Plane (Worker Nodes, Browser Containers). This ensures that user data and test execution are strictly isolated.

2. Core Components

2.1 The Control Plane

The Control Plane handles user authentication, project management, and test scheduling. It exposes a REST API consumed by the frontend dashboard and CI/CD integrations.

• API Gateway: Routes requests and enforces rate limits.
• Scheduler: Manages the queue of pending tests (FIFO with priority overrides).
• Result Aggregator: Processes streams from workers (logs, video chunks) and stores them in hot storage (S3-compatible).

2.2 The Execution Plane (Workers)

Workers are stateless compute units that execute the actual tests.

• Isolation: Each test runs in a fresh, ephemeral Docker container.
• Browser Engine: We use a customized build of Chromium/Playwright with the Chrome DevTools Protocol (CDP) exposed to our AI agent.
• The AI Agent: A node.js process that "drives" the browser. It does not use pre-defined scripts. Instead, it observes the DOM and decides on actions based on the Goal.

3. Key Technologies

3.1 IronMan HUD (Computer Vision)

Rihario creates a real-time overlay on the video stream called the "IronMan HUD." This is not just a visual effect; it is a debugging tool. It maps the AI's internal "Attention Map"—what elements it considers important—directly onto the visual output, allowing users to see why the AI clicked a button.

3.2 Self-Healing Memory

When a test succeeds, Rihario stores a Semantic Fingerprint of the critical elements (Login Button, Nav Link). If the CSS selectors change in a future build (e.g., `btn-primary` becomes `btn-red`), Rihario uses the fingerprint to find the element again by its text, position, and attributes, healing the test automatically.

3.3 Rage Bait Heuristics

The system monitors for "Frustration Signals":

• Rapid Clicking: >3 clicks on the same coordinate in 500ms.
• Dead Clicks: Clicks on elements with `cursor: pointer` that trigger no network or DOM change.
• Cursor Thrashing: Rapid, erratic mouse movement indicating confusion.

4. Security & Privacy

Tests are executed in a sandbox. No data persists on the worker node after the container terminates. We support whitelisted IPs for testing internal staging environments.