Architecture
A structure designed for reliability and security
Our deployment is built on a hierarchical and modular architecture. Each component has a precise role, clear boundaries, and a single responsibility.
Primary command and alert channel. Persistent sessions with the operator.
Client channel. Monitoring daemon polls message database, one-shot sub-agents per message.
3-layer pipeline: fixed script, isolated sandbox, sender allowlist.
Communication Channel
Primary interface for the human operator
Main Agent
Central orchestrator — receives, analyzes, delegates
Specialized Agents
Executors dedicated to a specific task or context
Human Supervisor
Absolute control. Can stop, reconfigure or replace any component. Authority cannot be bypassed by the system.
Technical Supervisor
Intermediate governance layer. Defines rules, limits and agent permissions. Continuous oversight.
Executing Agent
Operates within the defined framework. No autonomy outside granted permissions. Each session is isolated.
Session Isolation
Each conversation is handled in an independent session. No cross-contamination between contexts.
External Monitoring Daemon
A monitoring process runs independently from the agent. It can trigger alerts or shut down the system without going through the agent.
Messaging as Primary Interface
A single command channel for the operator. Simple, auditable, resistant to complex interfaces that obscure intent.
Local Persistent Memory
Agent state is saved locally. No cloud service dependency for operational continuity.