# Orchestration Layer
The Orchestration Layer is responsible for building AI workflows and agents that consume governed capabilities exposed by the AI Fabrix Dataplane.
Orchestration does not integrate directly with enterprise systems and does not implement access control logic. Its sole responsibility is to coordinate reasoning, workflow steps, and tool invocation using pre-governed interfaces.
In AI Fabrix, orchestration is intentionally decoupled from data access to preserve security, auditability, and architectural clarity.
Orchestration in the Overall Architecture
Orchestration sub-articles
- Orchestration Concepts — What orchestration means in AI Fabrix, separation from data access, identity-aware tool consumption
- Orchestration Options — Flowise, Microsoft Copilot, n8n, and custom agent frameworks
- Agent and Workflow Design — MCP tool invocation, versioning, environment promotion, failure handling and observability
Key takeaway: By separating thinking from data access, AI Fabrix enables safe evolution of agents and workflows without reintroducing security, compliance, or audit risk.