# Operational Capability Contracts

## M6 project consumption

`rag.embedding@1` remains model-agnostic. Its native response includes the immutable
`embedding_space_id`, dimension and normalization contract. Consumers validate all three. Workload
priority is identity-owned scheduler policy and is not accepted from the invocation payload.

`rag.embedding@1` accepts one non-empty string or a batch of at most eight strings. Each string is
bounded by the configured character limit and the whole request by the gateway payload limit. It
returns finite, normalized 1024-dimensional vectors, an immutable embedding-space ID, request ID,
usage and cold/queue/load/inference/total timing metadata.

The contract is backend-authoritative. Incompatible dimension, normalization, tokenization or API
schema changes require a new capability version. An underlying deployment may change within v1
only when the output contract remains compatible; embedding-space identity still changes and has
`requires_reindex` migration semantics.

The operational SLO boundary is a bounded 16-request deployment queue, one measured concurrent
inference, and explicit timeout/backpressure failures. Input retention is disabled by default.