Skip to main content
The EMEP system dependency map shows how data, models, and control flow through the platform from initial discovery to final deployment. This page documents the primary pipeline, optional side branches, and the decision points that route models between subsystems.

Primary Pipeline

The primary pipeline is the closed loop that every model must traverse to reach RELEASED or DEPLOYED status. No model bypasses a stage unless explicitly marked as a side branch.

Stage Descriptions

Optional Side Branches

The following branches are not part of the primary loop. They feed into it or consume its outputs.

Fine-Tuning Branch

Fine-tuning produces specialist models that may then be merged. It is optional and never required.
See ADR-0004. The primary loop does not depend on fine-tuning. This branch exists to support teams that want to produce task-specific inputs for merging.

RAG Downstream Branch

RAG consumes EMEP-produced models but never creates them.
See ADR-0005. Any request to include RAG in the primary loop must be rejected. RAG is a Phase 9 optional integration at best.

Storage Tiers

Data flows through three storage tiers during pipeline execution.