> ## Documentation Index
> Fetch the complete documentation index at: https://docs.fincelo.app/llms.txt
> Use this file to discover all available pages before exploring further.

# Multi-Agent Orchestration

> How agents communicate via the event bus and coordinate actions.

### ORCHESTRATION — Q\&A

***

**Q: How do agents coordinate without conflicting?**

The Orchestration Layer manages:

1. Event routing: which agent reacts to which event
2. Priority: higher priority agents go first on the same event
3. Conflict prevention: cooldown locks per customer per channel
4. Sequencing: some actions must happen in order (e.g. generate quote before sending)
5. Rollback: if an agent action fails, the orchestration layer triggers rollback if marked rollback-capable

***

**Q: What are orchestration rules?**

Configurable trigger chains. Example:
"When Renewal Agent marks a contract as At Risk → Customer Intel Agent runs a
full health assessment within 2 hours → CFO Co-pilot includes it in tomorrow's briefing."

Rules are stored in the `orchestration_rules` table.
Finance teams can create custom chains in Settings → Agents → Orchestration.

***

**Q: What is multi-agent debate?**

Level 5 enhancement (roadmap, 2027). Before high-stakes autonomous decisions
(e.g. write-off above ₹10L, legal referral), two agents independently assess
the situation and present opposing arguments. A third agent moderates.
The CFO sees the debate summary before approving. Designed to prevent AI echo-chamber.

***