SYSTEM ARCHITECTURE TAXONOMY
Architectural Navigation Map — Orchestration between Deterministic Kernel and Stochastic Engine
Eber Cruz — Software Engineer | C-FARARONI Project
March 2026 · Engineering Notes
Fararoni: System Topology and Execution Flow
Architecture Diagram
Click on the image to enlarge · High-resolution vector SVG
Technical Legend
FARARONI CORE — Dual Engine (Rabbit-Turtle)
The core operates with a dual execution model: RABBIT (Fast) for low-latency responses on deterministic commands and TURTLE (Expert) for tasks requiring deep LLM reasoning. The Kernel automatically decides which engine to activate based on the input complexity level.
5-Level Cascade (STAGE 1-5)
Routing is structured in 5 progressive execution stages:
- STAGE 1 — Direct Shell: Operating system commands (
pwd,ls,git status) executed without LLM intervention. - STAGE 2 — Intent Mapping: Natural phrases ("do the commit") deterministically translated to shell sequences.
- STAGE 3 — Basic LLM: Tasks requiring minimal context understanding, processed by the Rabbit engine.
- STAGE 4 — Advanced LLM: Refactoring and complex analysis, processed by the Turtle engine with tools.
- STAGE 5 — Agentic Orchestration: Multi-step tasks coordinated by the specialized agent SWARM/HIVEMIND.
Specialized Agents (SWARM)
The ecosystem features specialized autonomous agents operating under the SWARM/HIVEMIND pattern:
| Agent | Role | Function |
|---|---|---|
| COMMANDER | Coordinator | Orchestrates the mission and assigns tasks to other agents |
| STRATEGIST | Planner | Designs execution strategy and technical specifications |
| BUILDER | Constructor | Implements code and writes tests |
| RESEARCHER | Investigator | Gathers technical and architectural context |
| SCOUT | Explorer | Navigates the filesystem and maps project structure |
| SENTINEL | Guardian | Quality assurance and security validation |
| OPERATOR | Operator | Executes system commands and manages processes |
| WIZARD | Specialist | High-complexity tasks and self-healing |
Zero-Trust Protection Triad
Three defense-in-depth layers protect code integrity at stochastic levels:
- Kill-Switch (ReflexionGuard): Destructive hallucination detector based on Jaccard/Volume metrics. Operates at DEFCON levels (1, 3, 5) depending on threat severity.
- Git Saga Protocol: Transactional isolation through ephemeral branches. Each LLM operation occurs in a disposable branch; only merged if validation passes.
- Shadow Backups (SovereignJournal): Immutable persistence via Chronicle Queue. Every code state is backed up before any modification.
Sovereign Event Bus
The system's internal communication operates on a Sovereign Event Bus with dual architecture:
- Chronicle Queue (Disk-based): High-persistence bus for critical events and operations journal.
- NATS (Enterprise): Low-latency bus for real-time micro-agent communication.
The Bus Outbox pattern with SQLite Journal ensures no event is lost, even during system failures.
Communication Channels (Sidecars)
The Gateway Sidecar architecture enables integration with multiple agnostic transports under the S.A.T.I. protocol:
- WhatsApp Sidecar — Meta API
- Telegram Sidecar — Bot API
- Discord Sidecar — WebSocket
- iMessage Sidecar — Native macOS
The OmniChannelRouter with ChannelAccessGuard manages channel routing and access security through Zero-Trust Allowlist.
Entry Points
The system exposes three access interfaces:
- CLI InteractiveShell (JLine3): Interactive terminal for direct Kernel control via stdin/stdout.
- REST Server (:7070): HTTP API for programmatic integration with curl/Postman clients.
- Gateway Sidecar (:7071): Entry point for external messaging channels.
The Callback (:9999) handles asynchronous agent responses to egress adapters.