stage6-multi-agent

Multi-agent routing in n8n uses an integrated router to classify operator prompts and dispatch them to the correct sub-agents, such as ops, code, research, or infra, reducing manual reconfiguration. It enforces a Macro-F1 gate to maintain routing quality and reliability.

The Macro-F1 gate threshold for routing deployment is 0.85 or higher. This metric ensures routing quality and prevents drift during the deployment and maintenance of the modular n8n-based router with Telegram integration.

Yes, you can use n8n for free-form Hebrew routing through a Telegram interface. The router utilizes an append-only operational flow to assign operator prompts to the correct sub-agents, ensuring reliable task dispatch.

You need ADR-guided architecture during Macro-F1-gated deployment and re-deployments of the multi-agent router. It maintains structural reliability and references existing architectural decisions to prevent drift in the n8n workflows.

Sub-agent routing fails during re-deployment if the Macro-F1 gate falls below 0.85. You must verify the gate remains green and check the SKILL.md DoD for safety validation and ADR references to ensure correct workflow initialization.

Initializing a Stage 6 n8n router requires completing Stages 1 through 5 first. You must deploy the router and its sub-agents, then verify the Macro-F1 gate stays green to ensure safe and validated operational flow.