# OUDEA Matrix Binding — v0.1 Final Draft

OUDEA v0.1 uses Matrix(.org) federation as its initial protocol substrate.

OUDEA Core defines implementation-independent concepts such as:

- operational roles: `supply`, `demand`, `exchange`
- resource kinds: `entity`, `dataset`, `product`
- DEID identity and classification
- References
- Search / public discovery projection
- Find resolution
- Exchange behavior

A Matrix binding may map these concepts to Matrix-specific containers and protocol operations.

## Boundary

This binding MUST NOT make raw Matrix room state, event layouts, bot topology, queue/event flows, access-control implementation, storage layout, deployment details or other bytEM internals part of OUDEA Core merely because the reference implementation uses them.

Only Matrix-level information required for independent OUDEA interoperability should become normative binding material.

## Current status

OUDEA v0.1 defines the architectural Matrix binding boundary required by the Core specification. It deliberately does not publish private bytEM event/state layouts, exact room internals, bot architecture, queue/event flows, deployment topology or implementation-specific security controls.