MESA Core · v0.9.3

DAO repository boundaries

v0.9.3 source: docs/adr/0012-memory-dao-repository-boundaries.md

This guide has equivalent English and Turkish versions. The source sections behind this page are at the bottom.

DAO repository boundaries#

This maintained decision records design rationale at v0.9.3. Current architecture and runtime contracts define implemented behavior; retired decisions remain historical context.

Read the maintained reference#

The source below includes status, rationale and consequences. Start with the decision index and architecture.

Source reference for this page

The sections of the upstream file that back this page, unchanged. Source section links open the appendix automatically.

  • Status: Accepted; catalog boundary implemented, subsequent extractions remain proposals.

MemoryDAO remains the compatibility façade for existing V3/V4 callers, but

it no longer owns the tenant/workspace/dataset hierarchy directly.

CatalogRepositoryPort is the first focused boundary: it owns catalog scope

transactions and immutable identity-collision checks while exposing no raw

SQLite connection.

Subsequent extractions must preserve the same shape: a narrow typed port,

one transaction owner per aggregate, compatibility delegation in MemoryDAO,

and a repository-level contract test before callers are moved. Candidate next

boundaries are ingestion/mutation, projection recovery, and retrieval; they

must not be extracted as a broad mechanical rewrite.