# Project integrations

Projects consume versioned capabilities through scoped service identities. A project integration
contains a `Project`, `ProjectBinding`, optional `ProjectEvaluationBinding`, service client and
project-owned data plane. It never contains a concrete model path, runtime, node or artifact
selector.

ExampleRAG is the first operational integration. Its production retrieval remains `CURRENT`; M6 adds
an operator-only `SHADOW` target. Both targets are server-owned identifiers, not public arbitrary
collection parameters. Text is transient in the Gateway payload store and never copied into
ModelForge audit or metric labels.

Service clients have a fixed scheduler workload priority. The ExampleRAG reindex identity is scoped to
`rag.embedding@1` and `background`, so the consumer cannot escalate bulk work to production.

M13 registers `examplerag.qdrant-reindex` as the first typed stateful migration contract. ExampleRAG owns
chunk enumeration/hashes, Gateway embedding calls, Qdrant writes and alias inspection; ModelForge
owns immutable intent, approval, policy, progress evidence and external-truth journaling. Isolated
LAB aliases never grant the production client a new target. ExampleVision remains a blocked dry-run
candidate while its external production validation is deferred.