Factory Orchestrator

The Factory Orchestrator is the master coordinator for the SO1 Automation Factory. It analyzes requirements, decomposes tasks, selects agents, and orchestrates execution across all FORGE stages.

Quick Reference

Property	Value
Domain	Orchestration
FORGE Stage	Cross-cutting (all stages)
Version	1.0.0
Repository	so1-agents/orchestration

Overview

Use this agent when: You have a complex task spanning multiple domains or you’re unsure which specific agent to use.

The Factory Orchestrator is your entry point for complex SO1 automation tasks. Instead of manually selecting and coordinating multiple agents, the Orchestrator:

Analyzes your requirements
Decomposes them into atomic tasks
Selects appropriate agents for each task
Coordinates execution across FORGE stages
Manages state and handles failures

Core Capabilities

Requirement Analysis

Parse natural language, spec files, or structured requests

Task Decomposition

Break complex requirements into discrete,actionable tasks

Agent Selection

Route tasks to appropriate domain agents automatically

Stage Orchestration

Progress through FORGE stages with user approval

When to Use

✅ Use Factory Orchestrator for:

Complex multi-agent workflows
Tasks spanning multiple domains (e.g., automation + engineering + docs)
Unclear which specific agent is needed
Automatic task decomposition and parallel execution optimization

❌ Skip Orchestrator for:

Simple, single-agent tasks (e.g., just generating an n8n workflow)
When you know exactly which agent you need
Quick one-off operations

Usage Examples

Multi-Domain Task
Ambiguous Request
Full-Stack Feature

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:

Decompose into 4 tasks
Assign agents: Workflow Architect, Hono Backend, Runbook Writer, Mintlify Author
Define execution order (parallel where possible)
Coordinate handoffs and validate outputs

Use the Factory Orchestrator to help me set up automated 
deployment monitoring and alerting.

Orchestrator will:

Ask clarifying questions (which platform? what alerts?)
Decompose based on answers
Select appropriate agents (Railway Deployer, Webhook Engineer, etc.)
Coordinate implementation

Use the Factory Orchestrator to implement user authentication:
- Backend API endpoints
- Frontend login UI
- Database schema
- API documentation
- Deployment configuration

Orchestrator will:

Assign TypeScript Shared for schemas (Stage 1)
Parallel: Hono Backend + Next.js Frontend (Stage 2)
API Documenter for specs (Stage 3)
Railway Deployer for deployment (Stage 4)
Mintlify Author for docs (Stage 5)

Outputs

Task Breakdown Document

# Task Breakdown: GitHub-Slack Integration

## Summary
Build automated notification system from GitHub events to Slack

## Requirements Analysis
- **Domain**: automation, engineering, documentation
- **Complexity**: medium
- **Estimated Stages**: 2, 3, 5

## Task Decomposition

### Task 1: n8n Workflow Design
- **Agent**: workflow-architect
- **Stage**: 2 (Implementation)
- **Inputs**: GitHub webhook events, Slack channel
- **Outputs**: n8n workflow JSON

### Task 2: Webhook API Endpoint
- **Agent**: hono-backend
- **Stage**: 2 (Implementation)
- **Dependencies**: None (parallel with Task 1)
- **Outputs**: Hono route handler

### Task 3: Operational Runbook
- **Agent**: runbook-writer
- **Stage**: 5 (Deployment)
- **Dependencies**: Task 1, Task 2
- **Outputs**: Markdown runbook

## Execution Order
1. Task 1 + Task 2 (parallel, Stage 2)
2. Task 3 (sequential, Stage 5, after 1+2)

Agent Assignments (YAML)

generated_by: factory-orchestrator
timestamp: 2026-03-10T09:30:00Z

assignments:
  - task_id: 1
    task_name: "n8n Workflow Design"
    agent: "workflow-architect"
    stage: 2
    priority: high
    
  - task_id: 2
    task_name: "Webhook API Endpoint"
    agent: "hono-backend"
    stage: 2
    priority: high
    
  - task_id: 3
    task_name: "Operational Runbook"
    agent: "runbook-writer"
    stage: 5
    priority: medium
    depends_on: [1, 2]

execution_plan:
  parallel_groups:
    - group_id: 1
      tasks: [1, 2]
      stage: 2
  
  sequential:
    - group: 1
      then: 3

FORGE Gate Compliance

Entry Gate

Before orchestration begins, the following must be satisfied:

Requirements specification provided (text, file, or structured)
Target outcome clearly defined
User has confirmed intent to proceed

Exit Gate

Orchestration completes when:

All required stages completed successfully
All deliverables produced and validated
VTM generated by FORGE Gatekeeper
User has confirmed completion

Decision Logging

All orchestration decisions are logged in ADR format:

date:2026-03-10T09:30:00Z|context:[n8n workflow request]|decision:[route to workflow-architect]|rationale:[standard n8n pattern]|consequences:[Stage 2 execution]|status:accepted

Integration Points

Control Plane API

Endpoint	Purpose
`/api/workflows`	Create and monitor n8n workflows
`/api/jobs`	Track orchestration execution state

Veritas Integration

Consumes:

vrt-orchestr8: Task decomposition patterns
vrt-agentrte: Agent routing heuristics

Produces:

Multi-step execution chains (draft prompts)

Agent	Relationship
FORGE Gatekeeper	Validates stage transitions, produces VTM
All domain agents	Orchestrated by Factory Orchestrator

Agents Overview

Orchestration

Automation

Engineering

DevOps

Documentation

Prompts

Incident

Factory Orchestrator

Factory Orchestrator

Quick Reference

Overview

Core Capabilities

Requirement Analysis

Task Decomposition

Agent Selection

Stage Orchestration

When to Use

✅ Use Factory Orchestrator for:

❌ Skip Orchestrator for:

Usage Examples

Outputs

Task Breakdown Document

Agent Assignments (YAML)

FORGE Gate Compliance

Entry Gate

Exit Gate

Decision Logging

Integration Points

Control Plane API

Veritas Integration

Source Files

Agent Definition

FORGE Gates Config

Agents Overview

Orchestration

Automation

Engineering

DevOps

Documentation

Prompts

Incident

​Factory Orchestrator

​Quick Reference

​Overview

​Core Capabilities

Requirement Analysis

Task Decomposition

Agent Selection

Stage Orchestration

​When to Use

​✅ Use Factory Orchestrator for:

​❌ Skip Orchestrator for:

​Usage Examples

​Outputs

​Task Breakdown Document

​Agent Assignments (YAML)

​FORGE Gate Compliance

​Entry Gate

​Exit Gate

​Decision Logging

​Integration Points

​Control Plane API

​Veritas Integration

​Related Agents

​Source Files

Agent Definition

FORGE Gates Config

Factory Orchestrator

Quick Reference

Overview

Core Capabilities

When to Use

✅ Use Factory Orchestrator for:

❌ Skip Orchestrator for:

Usage Examples

Outputs

Task Breakdown Document

Agent Assignments (YAML)

FORGE Gate Compliance

Entry Gate

Exit Gate

Decision Logging

Integration Points

Control Plane API

Veritas Integration

Related Agents

Source Files