version: "1.0.0" name: ciel-orchestration-and-routing description: CIEL's master routing layer for task classification and multi-agent specialist access. license: MIT metadata: ciel-version: 1.0.0 ciel-extension: ciel.yaml

CIEL ADAPTATION: Orchestration & Routing (The Command Layer)

This skill formalizes the "Alloy" orchestration model. it prioritizes domain-specific specialist routing and conflict resolution between layers.

Routing Hierarchy (The Council Table)

Classify all requests against these domains in priority order:

1. Design & Frontend: UI/UX, animations, accessibility -> ui-ux-design + gsap-animation-suite.
2. Deep Logic & Refactoring: Rust, Python, Go, systems, migrations -> agents-claude-code.
3. Memory & Context: History, Knowledge Graph, Palace -> ciel-knowledge-and-memory.
4. Operations & Assets: GWS, Docker, Git, terminal execution -> google-workspace-management + container-and-deployment.

Classification Protocol

1. Detect Domain: Identify keywords and intent.
2. Resolve Conflicts:

• Logic vs Visual: Logic decisions take precedence (UI adapts to backend truth).
• System vs Logic: Tooling stability is a prerequisite for logic changes.

1. Activate specialist: Dispatch to the 100+ specialized CIEL agents at ~/.claude/agents/.
2. Sequence: Logic -> System -> Frontend.

Agent Specialist Access

CIEL maintains tie-breaking authority for all logic decisions. specialists (e.g., rust-ranger, ml-maestro) auto-activate based on task context. The Orchestrator MUST announce: "Routing to [Specialist] for [Reason]."

Anti-Patterns

• The Domain Blur: Starting a frontend change before the backend API is verified.
• Amnesiac Routing: Failing to use a specialist for a deep technical domain (e.g., implementing crypto without security-sentinel).
• Naked Implementation: Bypassing the routing table to write code directly for a multi-domain task.