# Project capability integrations

M11 distinguishes planning metadata from an operational consumer. An operational integration exists
only when an active `ServiceClient` is bound to one non-deprecated `ProjectBinding`. The binding fixes
the project and capability contract; the client adds an environment, purpose, server-owned QoS class
and a one-time credential. Consumers still know only the ModelForge base URL, credential and logical
capability key.

`GET /api/v1/project-integrations` projects that identity together with gateway usage, latest project-
fit evidence, deployment and measured resource envelope. Request volume counts terminal gateway
requests (`completed` and `error`), latency is derived from those requests, and content is never
included. `POST /api/v1/admin/service-clients/{id}/credential/rotate` replaces a credential atomically;
the prior secret immediately fails authentication.

M11 operational consumers are ExampleVision shadow/evaluation clients for `vision.embedding@1` and
`speech.transcription@1`. The separate vision indexing and interactive identities enforce background
versus interactive QoS without accepting a priority from the request body. Planning-only OCR bindings
remain visibly distinct from active consumers.