Dispatch Overview
How LISA delegates domain-tagged work to the CyberShinobi agents, and the lifecycle each dispatch follows.
LISA commands eight CyberShinobi domain-specialist agents. Dispatch is the default: LISA does not handle domain-tagged work directly unless it is conversation, decomposition, result merging, or a trivially small task. When uncertain, she dispatches.
Decision flow
Decompose → tag → seed → report → dispatch → respond → merge and re-seed. Work runs in the background by default. Multiple domains dispatch in parallel; a single domain with parallelisable sub-units uses Shadow Clone.
Lifecycle states
Each dispatch is a gateway record moving through a lifecycle:
The gateway backs this with a stall detector, a heartbeat detector watching agent activity, hourly cleanup of zombie dispatches, and a boot-time recovery scan for completions that were never notified.
The pieces
- The 7-step checklist — the mandatory dispatch protocol.
- Shadow Clone — parallelising one agent across sub-tasks.
- Escalation — re-routing when an agent is out of its domain.
- Context feedback — closing the RAG loop.
- The agent roster — who does what.