MESA Core · v0.9.3

Tenant/dataset authorization

v0.9.3 source: docs/adr/0011-v4-tenant-dataset-authorization.md

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

Tenant/dataset authorization#

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

Context#

An agent ID describes a compute/persona context. Treating a client-provided

agent or session ID as the tenant boundary allowed ambiguous ownership and

made dataset-scoped provenance impossible.

Decision#

V4 authorization resolves principal→tenant→workspace→dataset→agent→session on

the server. Roles are inherited OWNER, WRITER, READER; purge and rollback

require explicit permissions. Server-created sessions bind an immutable

dataset set. DAO storage filters use the verified scope.

Consequences#

New deployments must provision keys, roles and agent permissions before v4

catalog/session calls. Request metadata cannot grant authority.

Rollback#

Disable v4 and use the v3 lexical-core compatibility API. Weakening the v4

boundary is not a supported rollback.