Skip to main content

​
Orchestration Domain

The Orchestration domain contains 2 critical agents that coordinate all other agents and enforce SO1’s stage-gated execution model.

​
Overview

AgentStagePurpose
Factory OrchestratorCross-cuttingTask decomposition and multi-agent coordination
FORGE GatekeeperCross-cuttingStage gate validation and VTM production
Orchestration agents operate across all FORGE stages, providing coordination and compliance throughout the lifecycle.

​
When to Use

Use Factory Orchestrator

  • Complex multi-agent tasks
  • Unclear which agent to use
  • Multiple domains involved
  • Need task decomposition

Use FORGE Gatekeeper

  • Validate stage transitions
  • Generate VTM reports
  • Audit agent compliance
  • Check gate conditions

​
Domain Characteristics

​
Cross-Cutting Nature

Unlike other domains that operate in specific FORGE stages, Orchestration agents work across all stages: 
┌────────────────────────────────────────────────────────────┐
│              FACTORY ORCHESTRATOR                          │
│         (coordinates all agent activity)                   │
├────────────────────────────────────────────────────────────┤
│                                                            │
│  Stage 0   Stage 1   Stage 2   Stage 3   Stage 4   Stage 5│
│  ┌──────┐ ┌──────┐ ┌──────┐ ┌──────┐ ┌──────┐ ┌──────┐   │
│  │Plan  │→│Design│→│Impl  │→│Docs  │→│Valid │→│Deploy│   │
│  └───┬──┘ └───┬──┘ └───┬──┘ └───┬──┘ └───┬──┘ └───┬──┘   │
│      │        │        │        │        │        │      │
│      ▼        ▼        ▼        ▼        ▼        ▼      │
│  ┌────────────────────────────────────────────────────┐   │
│  │            FORGE GATEKEEPER                        │   │
│  │        (validates each transition)                 │   │
│  └────────────────────────────────────────────────────┘   │
└────────────────────────────────────────────────────────────┘

​
Primary Responsibilities

ResponsibilityFactory OrchestratorFORGE Gatekeeper
Task decomposition✅ Primary❌
Agent selection✅ Primary❌
State management✅ Primary❌
Gate validation❌✅ Primary
VTM production❌✅ Primary
Compliance audit❌✅ Primary

​
Usage Examples

​
Example 1: Multi-Domain Task

Use the Factory Orchestrator to build a complete GitHub-to-Slack 
notification system with:
- n8n workflow for event processing
- API endpoint for webhook reception  
- Runbook for operations
- Documentation for the team
Orchestrator will:
  1. Decompose into 4 tasks
  2. Assign: Workflow Architect, Hono Backend, Runbook Writer, Mintlify Author
  3. Define execution order (some parallel, some sequential)
  4. Coordinate handoffs between agents

​
Example 2: Gate Validation

Use the FORGE Gatekeeper to validate that all Stage 2 exit gates 
are satisfied before proceeding to Stage 3.
Gatekeeper will:
  1. Check all Stage 2 agents completed
  2. Verify exit conditions met
  3. Generate validation report
  4. Update VTM with results

​
Integration Points

​
Control Plane API

EndpointUsed ByPurpose
/api/workflowsFactory OrchestratorCreate n8n workflows
/api/jobsFactory OrchestratorTrack execution state
/api/validationFORGE GatekeeperSubmit gate validations

​
Veritas Integration

AgentConsumesProduces
Factory OrchestratorTask decomposition patterns, routing heuristicsMulti-step chains
FORGE GatekeeperCompliance patterns, audit templatesValidation tasks

​
Outputs

Task Breakdown (Markdown):
  • Requirement analysis
  • Task decomposition
  • Agent assignments
  • Execution order
  • Risk assessment
Agent Assignments (YAML):
  • Task-to-agent mapping
  • Dependencies
  • Parallel execution groups
Execution Log (Markdown):
  • Timeline of agent invocations
  • Decision records
  • State transitions

​
Best Practices

Use the Factory Orchestrator when:
  • ✅ You have a complex task spanning multiple domains
  • ✅ You’re unsure which specific agent to use
  • ✅ You need automatic task decomposition
  • ✅ You want coordinated multi-agent execution
Skip the Orchestrator when:
  • ❌ You know exactly which single agent you need
  • ❌ Task is simple and domain-specific
  • ❌ You prefer manual agent selection
The Gatekeeper is automatically invoked by:
  • Factory Orchestrator at each stage transition
  • Individual agents when producing final output
Manually invoke Gatekeeper to:
  • Audit an existing implementation
  • Generate VTM for documentation
  • Validate compliance before deployment
Both agents log all decisions in ADR format:
date:ISO8601|context:[situation]|decision:[choice]|rationale:[why]|consequences:[impact]|status:accepted
This ensures full traceability of orchestration choices.

Factory Orchestrator

Detailed agent documentation

FORGE Gatekeeper

Detailed agent documentation

FORGE Stages

Stage-gated execution model

VTM Documentation

Verification & Traceability Matrix