aidb-architecture

AIDB's architecture spans 6 layers—MCP, Service, Session, Adapter, DAP Client, and Protocol—each with distinct responsibilities. This Skill provides a structured reference explaining component roles, interactions, and data-flow patterns so you can trace requests end-to-end and make informed design decisions across layers.

AIDB follows component delegation, language-agnostic design, and human-cadence debugging principles. Understanding these principles helps you design new features—like MCP tools requiring adapter interaction—at the correct integration points while maintaining consistency and maintainability.

AIDB implements a three-tier resource cleanup strategy managing processes, ports, and DAP connections. This Skill documents the cleanup sequence and responsibilities per layer, ensuring robust resource management when integrating features across Session, Adapter, and Protocol layers.

Yes. This Skill maps layer roles, interactions, and cross-layer constraints in a navigable format. When debugging issues that span multiple layers or designing features requiring multi-layer integration, you can reference the architecture to identify component boundaries and data-flow bottlenecks.

The Session Layer manages stateful interactions and coordinates between the Service and Adapter layers, maintaining context across requests. It enforces resource cleanup policies and mediates protocol-level operations, making it critical for feature designs spanning multiple layers.

You need to understand the layers your feature touches and their integration points. This Skill provides the architectural foundation to identify which layers are relevant, their responsibilities, and how data flows between them, reducing design errors and debugging time.