Agent Protocol
Agents inside Parabellum OS operate under a strict protocol. They cannot act on the operator's behalf without an approved mission, they cannot recurse beyond a defined depth, and every action is logged.
Mission lifecycle
A mission moves through five states: created, dispatched, in progress, handed off, completed. Every state transition is logged with a timestamp, the originating agent, and the result.
Depth limits
No agent can recurse beyond depth 3. The guard is enforced at the orchestrator level. Missions that hit the depth ceiling are escalated to the operator for manual resolution.
if ((mission.depth || 0) >= 3) return;Handoff rules
When an agent reaches the limit of its specialization, it hands off to a more specialized agent rather than attempting the task directly. Handoffs are recorded as state transitions, not as new missions.
Agent roster
- Telegram Agent. Handles mission creation from the operator's Telegram interface.
- Growth Agent. Manages X and social distribution under strict rate and content limits.
- Monitoring Agent. Watches system health, surfaces anomalies, paginates alerts.
- Scheduling Agent. Owns time-based execution and recurring mission dispatch.
- System Health Agent. Tracks infrastructure status and triggers self-repair routines.
- Orchestrator. Routes missions, enforces protocol, settles results.
Override
The operator can interrupt any mission at any state via the Command Interface. Override is final.