Embedding Pipeline Service · View 07 of 22 · Structure
The asymmetry this view exists to show
- Everything below Serve is a build path. An index that is already built keeps serving with capture, preparation and embedding all stopped.
- That is why retrieval carries 99.95% monthly, ingest 99.9% and the control plane 99.5% (stated assumptions): a pipeline outage widens freshness rather than removing retrieval.
- The one exception is the permission authority, which is on the hot path by design and fails closed — the single place the platform accepts a hard dependency.
Layer boundaries that matter
- Capture never calls Prepare directly. The change log between them is what makes a backlog survivable and a replay possible.
- Embed never writes to an index. The index builder owns contract enforcement, so a vector cannot land in an index built under a different contract.
- The control plane spans every layer and is reached by none of them on a request path.
Why bands, and only here
- This is the only view in the set drawn as stacked layers. Every other view uses the form its question needs — a context view drawn as bands reads as a layer diagram and answers nothing.
