Files
stack/docs/3-architecture
Jason Woltje 12abdfe81d feat(#93): implement agent spawn via federation
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>
2026-02-03 14:37:06 -06:00
..

Architecture

Technical architecture and design principles for Mosaic Stack.

Chapters

  1. Overview — System design and component architecture
  2. Authentication — BetterAuth integration and OIDC flow
  3. Design Principles — PDA-friendly patterns and UX guidelines

Architecture Principles

  • Type Safety First: Shared types prevent frontend/backend drift
  • Multi-Tenant Ready: Row-level security with workspace isolation
  • PDA-Friendly: Calm, stress-free language and visual design
  • Modular: Plugin architecture for extensibility

Technology Decisions

Key architectural choices and their rationale:

  • BetterAuth over Passport.js for modern authentication
  • Prisma ORM for type-safe database access
  • Monorepo with pnpm workspaces for code sharing
  • PostgreSQL + pgvector for AI-ready data storage

Next Steps

  • Review API for implementation details
  • Check Development for workflow standards