Architecture overview

The docs/architecture/ section is the canonical Agentstration Technical Architecture Document (DAT). Architecture documentation conventions define the ownership boundaries between LikeC4, Markdown, Mermaid, and ADRs, the interactive architecture publishes the shared structural model, and the migration inventory tracks the progressive consolidation of existing sources.

Agentstration is a modular monolith with explicit resource-family, Runtime, Work, and Flow boundaries. The repository contains one authoritative server/API, independently hostable Console and Workplace shells, autonomous AEP extensions, and an Aspire development orchestrator. The shared interactive C4 model is the sole structural source for L1 through selected L3 views.

The DAT is organized by concern:

• Context and constraints
• System context, containers, server components, and API transport composition
• Dynamic execution views, including Work, Flow, Agent, Tool, AEP, and MCP paths
• Resource and persistence models
• Standalone deployment and tenancy/isolation
• Implementation mapping, dependency rules, the detailed current-state inventory, and the initial reconciliation baseline

The dominant design rules are local-first operation, provider-neutral application contracts, separate persistence boundaries, reconstructible runtime objects, and shared use cases across REST, Razor, MCP, and workers.

Packs form a distribution layer above these resource owners. Installation delegates each contained manifest to its owning module and records provenance; Packs never enter the execution path. See Packs and ADR-0037.

The detailed implementation inventory remains available in Architecture: current implementation.