# Architecture

`tiny-convmem-mcp` currently proves only the MCP integration boundary. The
executable composes an mcpc stdio server and registers a single `health` tool.

Future conversation-memory work is split into these dependencies:

```text
MCP transport and tools  ->  domain contracts  <-  storage adapters
```

- `src/mcp` translates MCP requests and responses. It may depend on mcpc and
  domain contracts, but it must not contain persistence logic.
- `src/domain` will own conversation and message concepts without depending on
  mcpc or a database.
- `src/storage` will implement domain persistence contracts using a storage
  engine selected in the next design phase.

No conversation schema, retention policy, search behavior, or storage engine is
implied by the current scaffold.