juling-qianjiang

Multi-agent load balancing uses risk assessment by scoring capability match, health, load, and historical quality, then parsing soul.md constraints to calculate rebellion risk and switch authority modes. This prevents boundary violations during multi-tool task dispatch.

To prevent boundary violations, you can parse soul.md constraints to extract persona capabilities, limits, and invocation rules. The system enforces boundary-aware governance by assigning primary and support spirits with governance-aware authority modes.

The best way to implement fallback protection is executing deterministic degradation or simulated inner fallback strategies. When tools are unavailable, the system uses caching, local computation, or internal alternatives, generating a tracked recovery plan and escalation contract.

Yes, multi-agent formation supports single-possession, dual-attunement, and night-parade modes. It generates primary and support spirit divisions, invocation queues, parallel channel semantics, and execution checkpoints for batch dispatch and fallback recovery.

Yes, you can use soul.md parsing to convert limits and invocation rules into boundary constraints. When calculated rebellion risk rises, the system automatically shrinks permissions by switching to sealed-command or cautious-attunement authority modes to prevent overreach.

You should avoid automated spirit dispatch when your tasks require deterministic external tool availability without degradation, as the system relies on simulated fallback and local computation alternatives when health scores drop or tools fail during execution.