IMPORTANT
AI Assist Note (Knowledge Heritage): This document is part of the "Sovereign Reality" documentation.
- @docs ARCHITECTURE:Documentation
- Failure Path: Information drift, legacy terminology, or documentation mismatch.
- Telemetry Link: Cross-reference with
execution/parity_guard.pyresults.
AI Assist Note
Automated governance and architectural tracking.
🔍 Debugging & Observability
Traceability via parity_guard.py.
🪐 Architecture Overview: Tadpole OS
Intelligence Level: High (Sovereign Context)
Status: Verified Production-Ready
Version: 1.1.13
Last Hardened: 2026-04-17 (Alignment Patch)
Classification: Sovereign
🎯 Executive Summary
What is Tadpole OS?
Tadpole OS is a high-performance, local-first runtime for sovereign multi-agent swarms. It enables the orchestration of complex, recursive AI workflows where high-level "strategic" nodes delegate tactical missions to specialists, all while maintaining strict privacy, cost controls, and human-in-the-loop oversight.
Why was it built this way?
The architecture is rooted in the philosophy of Sovereign Intelligence. Unlike cloud-locked agent frameworks, Tadpole OS prioritizes resilience and observability. By utilizing a "Gateway-Runner-Registry" pattern in Rust, the system ensures memory safety, sub-millisecond telemetry, and verifiable auditability using cryptographic Merkle trails.
What is new in the current iteration?
- Hardened Security: Integrated binary Merkle hash-chaining and the "Neural Shield" redaction engine.
- Budget Guard: Kernel-level fiscal enforcement with real-time token-burn metering.
- Modernized Interface: Full React 19 and Tailwind v4 integration with "State-Preserved Detachment" for multi-monitor operation.
- Split-Brain Memory: Hybrid RAG implementation combining SQLite precision with LanceDB vector scalability.
🛰️ Core System Topology
The following diagram illustrates the macro-structure of the Tadpole OS lifecycle, from the frontend dashboard to the sandboxed execution environment.
graph TD
subgraph "Sovereign Layer (Frontend)"
Dashboard["Ops_Dashboard (React 19)"]
Registry["Agent_Store (Zustand)"]
Vault["Neural_Vault (SubtleCrypto)"]
Visualizer["Swarm_Visualizer (Detachable)"]
end
subgraph "Intelligence Layer (Backend)"
Axum["Axum Gateway (0.8)"]
State["AppState (state/mod.rs hubs)"]
Runner["Agent_Runner (runner/mod.rs)"]
Telemetry["Telemetry_Hub (pulse.rs)"]
Memory["Vector_Memory (LanceDB)"]
Audit["Merkle_Audit (audit.rs)"]
end
subgraph "Persistence & Nodes"
SQLite[("tadpole.db (sqlx)")]
Bunker["Bunker Nodes (mDNS)"]
Files["Workspace_FS (Sandboxed)"]
end
Dashboard -- "WS/REST" --> Axum
Axum --> State
State --> Runner
State --> Telemetry
Runner --> Telemetry
Runner --> Memory
Runner --> Audit
Audit --> SQLite
Runner -- "I/O" --> Files
Registry -- "Identity Sync" --> State
State -- "mDNS Discovery" --> Bunker🏗️ The "Gateway-Runner-Registry" Pattern
Tadpole OS operates as a distributed state machine:
- Registry: Manages the persistent identities and capabilities of agents and providers.
- Gateway: Provides the high-concurrency Axum-based interface for the dashboard and external adapters.
- Runner: A stateful execution loop that manages the mission lifecycle, recruitment of specialists, and integration of findings.
📄 Documentation Suite
To maintain high navigability, the architecture is decomposed into focused modules:
- 🛡️ Security Model: Policies, Merkle Audits, and Encryption.
- 🤖 Agent Runner Workflow: Execution lifecycles and Swarm Protocols.
- 🧠 Knowledge & Memory: Hybrid RAG, LanceDB, and Ingestion.
- ⚛️ State Management: Zustand stores, Portals, and React 19.
🤖 Context for AI Assistants
- State Ownership: The Rust engine is the primary source of truth for agent configurations.
- Tool Protocol: All agent tools must return an
anyhow::Result<String>. - Sovereignty: ID 1 (Agent of Nine) is the primary strategic orchestrator.
