12abdfe81d
Implements FED-010: Agent Spawn via Federation feature that enables spawning and managing Claude agents on remote federated Mosaic Stack instances via COMMAND message type. Features: - Federation agent command types (spawn, status, kill) - FederationAgentService for handling agent operations - Integration with orchestrator's agent spawner/lifecycle services - API endpoints for spawning, querying status, and killing agents - Full command routing through federation COMMAND infrastructure - Comprehensive test coverage (12/12 tests passing) Architecture: - Hub → Spoke: Spawn agents on remote instances - Command flow: FederationController → FederationAgentService → CommandService → Remote Orchestrator - Response handling: Remote orchestrator returns agent status/results - Security: Connection validation, signature verification Files created: - apps/api/src/federation/types/federation-agent.types.ts - apps/api/src/federation/federation-agent.service.ts - apps/api/src/federation/federation-agent.service.spec.ts Files modified: - apps/api/src/federation/command.service.ts (agent command routing) - apps/api/src/federation/federation.controller.ts (agent endpoints) - apps/api/src/federation/federation.module.ts (service registration) - apps/orchestrator/src/api/agents/agents.controller.ts (status endpoint) - apps/orchestrator/src/api/agents/agents.module.ts (lifecycle integration) Testing: - 12/12 tests passing for FederationAgentService - All command service tests passing - TypeScript compilation successful - Linting passed Refs #93 Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com>
Mosaic Orchestrator
Agent orchestration service for Mosaic Stack built with NestJS.
Overview
The Orchestrator is the execution plane of Mosaic Stack, responsible for:
- Spawning and managing Claude agents
- Task queue management (Valkey-backed)
- Agent health monitoring and recovery
- Git workflow automation
- Quality gate enforcement callbacks
- Killswitch emergency stop
Architecture
Part of the Mosaic Stack monorepo at apps/orchestrator/.
Controlled by apps/coordinator/ (Quality Coordinator).
Monitored via apps/web/ (Agent Dashboard).
Development
# Install dependencies (from monorepo root)
pnpm install
# Run in dev mode (watch mode)
pnpm --filter @mosaic/orchestrator dev
# Build
pnpm --filter @mosaic/orchestrator build
# Start production
pnpm --filter @mosaic/orchestrator start:prod
# Test
pnpm --filter @mosaic/orchestrator test
# Generate module (NestJS CLI)
cd apps/orchestrator
nest generate module <name>
nest generate controller <name>
nest generate service <name>
NestJS Architecture
- Modules: Feature-based organization (spawner, queue, monitor, etc.)
- Controllers: HTTP endpoints (health, agents, tasks)
- Services: Business logic
- Providers: Dependency injection
Configuration
Environment variables loaded via @nestjs/config.
See .env.example for required vars.
Documentation
- Architecture:
/docs/ORCHESTRATOR-MONOREPO-SETUP.md - API Contracts:
/docs/M6-ISSUE-AUDIT.md - Milestone: M6-AgentOrchestration (0.0.6)