Back to Architecture
Coordination Layer
Orchestration Patterns
Two-tier orchestration architecture enabling both within-capability and cross-capability agent coordination.
Two-Tier Architecture
Tier 1: Capability Orchestrator
Within-capability orchestration using Q-Learning based agent selection and RIGOR execution.
Scope: BUILD, OPERATE, SECURE, GOVERN, OPTIMIZE, EVOLVE
- Q-Learning agent routing
- RIGOR phase execution
- ACMF mode enforcement
- Pattern application
Tier 2: Meta-Orchestrator
Cross-capability coordination for complex workflows spanning multiple domains.
Scope: PLATFORM-level workflows
- Cross-capability workflows
- Full SDLC orchestration
- Incident response flows
- Multi-agent coordination
Orchestration Patterns
Sequential
One phase after another (default RIGOR execution)
Use case: Standard task executionParallel
Multiple agents work simultaneously
Use case: Independent subtasksGroup Chat
Agents collaborate with shared context
Use case: Collaborative problem solvingHierarchical
Manager agent coordinates worker agents
Use case: Complex delegated tasksDebate
Multiple agents debate solutions
Use case: Critical decisionsExample Workflows
// Full SDLC Workflow (Meta-Orchestrator)
BUILD → SECURE → OPERATE
req-ai → planner-ai → architect-ai → coder-ai → tester-ai → review-ai
↓
security-ai → policy-ai
↓
deploy-ai → observe-ai
// Incident Response Workflow
OPERATE → BUILD → GOVERN
observe-ai (detect) → incident-ai (triage) → debug-ai (diagnose)
↓
coder-ai (fix) → tester-ai (validate)
↓
govern-ai (audit) → deploy-ai (rollout)