# samithcsachi/grid-forecast architecture

> Architecture diagram of the GitHub repository samithcsachi/grid-forecast, generated by GitDiagram from its file tree, README and a sample of source files (last updated 2026-05-24). It is an AI-made overview: check details against the source.

- Interactive diagram: https://gitdiagram.com/samithcsachi/grid-forecast
- Repository: https://github.com/samithcsachi/grid-forecast

## Overview

1. GridForecast is a dual-path forecasting system: an offline ML lifecycle for training/retraining electricity-demand models, and an online serving layer that exposes predictions and health/metrics to consumers. The domain data source is ENTSO-E operational electricity data, with the end goal of 24-hour demand forecasts for grid operations and trading.

2. The public runtime surfaces are a FastAPI service and a Streamlit dashboard. The FastAPI app under `api/` provides `health`, `metrics`, and `predict` routes, plus middleware for logging and rate limiting. The Streamlit app under `app/` is the human-facing visualization layer for forecasts, confidence intervals, and model performance.

3. Online inference flows through `services/prediction_service.py` and `pipelines/inference_pipeline.py`. Requests are converted into features, scored by the active model, and returned via the API. A Redis cache exists in `cache/redis_client.py`, likely used to reduce repeated lookups or speed up serving-path operations.

4. The training path is organized as a staged pipeline in `components/` and `pipelines/training_pipeline.py`. The stages are explicit: data ingestion, validation, transformation, model training, evaluation, drift monitoring, and model registry. This makes the offline lifecycle easy to diagram as a left-to-right sequence from raw data to promoted model artifacts.

5. Data access is separated from modeling. `data_access/entsoe_client.py` pulls external electricity data, while `database_client.py` and `storage_client.py` abstract persistence for processed datasets, artifacts, or metrics. This boundary keeps external I/O out of the training and serving logic.

6. Feature preparation is handled by `feature_store/feature_engineering.py` and `feature_store/feature_store.py`, with `registry.json` acting as a local feature definition registry. This layer sits between raw time-series data and model inputs, and is a key boundary for reproducibility and consistency between training and inference.

7. Model governance is handled by `registry/model_registry.py` and `registry/promotion.py`, with `components/stage_07_model_registry.py` tying registry updates into the pipeline. The repository is designed around explicit model versioning and promotion so that retraining can produce a candidate model before it replaces the currently served one.

8. Monitoring is a first-class subsystem. `monitoring/` covers drift detection, performance monitoring, and alerting, while `services/monitoring_service.py` and `pipelines/monitoring_pipeline.py` wire these checks into the operational flow. The API also exposes a metrics endpoint, indicating the monitoring stack is meant to be consumed by external observability tools.

9. Observability is backed by separate logging, metrics, and tracing modules under `observability/`, plus Prometheus and Grafana configs in `observability/prometheus/` and `observability/grafana/`. At the HTTP layer there is also request logging middleware, so the serving path produces operational telemetry in addition to predictions.

10. Retraining is treated as an operational workflow, not a manual notebook task. `pipelines/retraining_pipeline.py`, `services/retraining_service.py`, and `workers/scheduler.py` support periodic or triggered retraining, likely coordinated with the GitHub Actions `retrain.yaml` workflow. This closes the loop from monitoring signals back to model updates.

11. Deployment and runtime infrastructure are present in `infra/`, `docker-compose.yaml`, and `.github/workflows/`. There is a Dockerfile, nginx config, and AWS deployment documentation, which suggests containerized deployment behind a reverse proxy with CI/CD for build, deploy, and retrain automation. `load_testing/locustfile.py` indicates the serving API is also performance-tested.

12. Configuration and validation are centralized. `configs/*.yaml` and the `config/` package define system parameters and schemas, while `validation/` contains data-quality and schema-validation logic. This creates a clear boundary between environment/config inputs and the core ML pipeline.

13. `tests/` covers API, components, and pipelines, so the repository is structured to validate each architectural layer independently. The research notebooks under `research/` are exploratory artifacts and are separate from the production execution path.

14. In diagram form, the main boundaries are: external data ingestion, feature engineering, model lifecycle/promotion, online serving, monitoring/observability, and deployment automation. The main control points are FastAPI for inference, Streamlit for visualization, the staged pipelines for offline work, and the registry/monitoring loop that keeps the system continuously updated.

Main entry points: [`SRC/GridForecast_Electricity_Demand_Predictor/components/stage_01_data_ingestion.py`](https://github.com/samithcsachi/grid-forecast/blob/main/SRC/GridForecast_Electricity_Demand_Predictor/components/stage_01_data_ingestion.py) (Ingest), [`SRC/GridForecast_Electricity_Demand_Predictor/registry/model_registry.py`](https://github.com/samithcsachi/grid-forecast/blob/main/SRC/GridForecast_Electricity_Demand_Predictor/registry/model_registry.py) (Registry), [`SRC/GridForecast_Electricity_Demand_Predictor/services/prediction_service.py`](https://github.com/samithcsachi/grid-forecast/blob/main/SRC/GridForecast_Electricity_Demand_Predictor/services/prediction_service.py) (Prediction svc), [`SRC/GridForecast_Electricity_Demand_Predictor/pipelines/inference_pipeline.py`](https://github.com/samithcsachi/grid-forecast/blob/main/SRC/GridForecast_Electricity_Demand_Predictor/pipelines/inference_pipeline.py) (Infer pipeline)

## Diagram (Mermaid)

```mermaid
flowchart TD

subgraph group_runtime["Runtime"]
  node_prediction_service["Prediction svc<br/>serving service"]
  node_inference_pipeline["Infer pipeline<br/>inference pipeline"]
  node_redis_cache[("Redis cache<br/>[redis_client.py]")]
  node_fastapi_app["FastAPI<br/>http api<br/>[fastapi_app.py]"]
  node_streamlit_app["Streamlit<br/>dashboard<br/>[streamlit_app.py]"]
end

subgraph group_offline["Offline ML"]
  node_training_pipeline["Train pipeline<br/>offline pipeline"]
  node_stage_ingest["Ingest<br/>pipeline stage"]
  node_stage_transform["Transform<br/>pipeline stage"]
  node_stage_train["Train<br/>pipeline stage"]
  node_stage_eval["Evaluate<br/>pipeline stage"]
  node_retraining_pipeline["Retrain pipe<br/>retraining pipeline"]
  node_retraining_service["Retraining svc<br/>workflow service"]
end

subgraph group_data["Data & Features"]
  node_entsoe[("ENTSO-E<br/>external data source<br/>[entsoe_client.py]")]
  node_db_client["DB client<br/>persistence adapter<br/>[database_client.py]"]
  node_storage_client["Storage client<br/>artifact store adapter<br/>[storage_client.py]"]
  node_feature_engineering["Feature eng<br/>feature builder"]
  node_feature_store["Feature store<br/>feature registry<br/>[feature_store.py]"]
  node_schema_registry["Feature schema<br/>registry file<br/>[registry.json]"]
end

subgraph group_governance["Governance"]
  node_data_validation["Data validation<br/>quality checks<br/>[data_quality.py]"]
  node_schema_validation["Schema checks<br/>schema validation"]
  node_model_registry[("Registry<br/>[model_registry.py]")]
  node_promotion["Promotion<br/>[promotion.py]"]
  node_monitoring_pipeline["Monitor pipe<br/>monitoring pipeline"]
  node_monitoring_service["Monitoring svc<br/>ops service"]
end

subgraph group_ops["Ops & Observability"]
  node_scheduler["Scheduler<br/>[scheduler.py]"]
  node_observability["Telemetry<br/>observability stack<br/>[metrics.py]"]
end

node_entsoe -->|"source data"| node_stage_ingest
node_stage_ingest -->|"checks"| node_data_validation
node_data_validation -->|"schema"| node_schema_validation
node_stage_ingest -->|"prep input"| node_feature_engineering
node_feature_engineering -->|"publish"| node_feature_store
node_feature_store -->|"defs"| node_schema_registry
node_db_client -.->|"persistence"| node_storage_client
node_training_pipeline -->|"orchestrates"| node_stage_ingest
node_training_pipeline -->|"orchestrates"| node_stage_transform
node_stage_transform -->|"feeds"| node_stage_train
node_stage_train -->|"scores"| node_stage_eval
node_stage_eval -->|"registers"| node_model_registry
node_promotion -->|"promotes"| node_model_registry
node_monitoring_pipeline -->|"runs"| node_monitoring_service
node_monitoring_service -->|"emits"| node_observability
node_fastapi_app -->|"serves"| node_prediction_service
node_prediction_service -->|"executes"| node_inference_pipeline
node_inference_pipeline -->|"reads features"| node_feature_store
node_inference_pipeline -->|"loads model"| node_model_registry
node_prediction_service -.->|"cache"| node_redis_cache
node_fastapi_app -->|"telemetry"| node_observability
node_streamlit_app -.->|"visualizes"| node_model_registry
node_retraining_service -->|"coordinates"| node_retraining_pipeline
node_retraining_pipeline -.->|"triggered by"| node_monitoring_service
node_scheduler -.->|"triggers"| node_retraining_service
node_scheduler -.->|"runs"| node_monitoring_pipeline
node_observability -.->|"observes"| node_fastapi_app

click node_entsoe "https://github.com/samithcsachi/grid-forecast/blob/main/SRC/GridForecast_Electricity_Demand_Predictor/data_access/entsoe_client.py"
click node_db_client "https://github.com/samithcsachi/grid-forecast/blob/main/SRC/GridForecast_Electricity_Demand_Predictor/data_access/database_client.py"
click node_storage_client "https://github.com/samithcsachi/grid-forecast/blob/main/SRC/GridForecast_Electricity_Demand_Predictor/data_access/storage_client.py"
click node_feature_engineering "https://github.com/samithcsachi/grid-forecast/blob/main/SRC/GridForecast_Electricity_Demand_Predictor/feature_store/feature_engineering.py"
click node_feature_store "https://github.com/samithcsachi/grid-forecast/blob/main/SRC/GridForecast_Electricity_Demand_Predictor/feature_store/feature_store.py"
click node_schema_registry "https://github.com/samithcsachi/grid-forecast/blob/main/SRC/GridForecast_Electricity_Demand_Predictor/feature_store/registry.json"
click node_data_validation "https://github.com/samithcsachi/grid-forecast/blob/main/SRC/GridForecast_Electricity_Demand_Predictor/validation/data_quality.py"
click node_schema_validation "https://github.com/samithcsachi/grid-forecast/blob/main/SRC/GridForecast_Electricity_Demand_Predictor/validation/schema_validation.py"
click node_training_pipeline "https://github.com/samithcsachi/grid-forecast/blob/main/SRC/GridForecast_Electricity_Demand_Predictor/pipelines/training_pipeline.py"
click node_stage_ingest "https://github.com/samithcsachi/grid-forecast/blob/main/SRC/GridForecast_Electricity_Demand_Predictor/components/stage_01_data_ingestion.py"
click node_stage_transform "https://github.com/samithcsachi/grid-forecast/blob/main/SRC/GridForecast_Electricity_Demand_Predictor/components/stage_03_data_transformation.py"
click node_stage_train "https://github.com/samithcsachi/grid-forecast/blob/main/SRC/GridForecast_Electricity_Demand_Predictor/components/stage_04_model_training.py"
click node_stage_eval "https://github.com/samithcsachi/grid-forecast/blob/main/SRC/GridForecast_Electricity_Demand_Predictor/components/stage_05_model_evaluation.py"
click node_model_registry "https://github.com/samithcsachi/grid-forecast/blob/main/SRC/GridForecast_Electricity_Demand_Predictor/registry/model_registry.py"
click node_promotion "https://github.com/samithcsachi/grid-forecast/blob/main/SRC/GridForecast_Electricity_Demand_Predictor/registry/promotion.py"
click node_monitoring_pipeline "https://github.com/samithcsachi/grid-forecast/blob/main/SRC/GridForecast_Electricity_Demand_Predictor/pipelines/monitoring_pipeline.py"
click node_prediction_service "https://github.com/samithcsachi/grid-forecast/blob/main/SRC/GridForecast_Electricity_Demand_Predictor/services/prediction_service.py"
click node_inference_pipeline "https://github.com/samithcsachi/grid-forecast/blob/main/SRC/GridForecast_Electricity_Demand_Predictor/pipelines/inference_pipeline.py"
click node_redis_cache "https://github.com/samithcsachi/grid-forecast/blob/main/SRC/GridForecast_Electricity_Demand_Predictor/cache/redis_client.py"
click node_fastapi_app "https://github.com/samithcsachi/grid-forecast/blob/main/SRC/GridForecast_Electricity_Demand_Predictor/api/fastapi_app.py"
click node_streamlit_app "https://github.com/samithcsachi/grid-forecast/blob/main/SRC/GridForecast_Electricity_Demand_Predictor/app/streamlit_app.py"
click node_monitoring_service "https://github.com/samithcsachi/grid-forecast/blob/main/SRC/GridForecast_Electricity_Demand_Predictor/services/monitoring_service.py"
click node_retraining_pipeline "https://github.com/samithcsachi/grid-forecast/blob/main/SRC/GridForecast_Electricity_Demand_Predictor/pipelines/retraining_pipeline.py"
click node_retraining_service "https://github.com/samithcsachi/grid-forecast/blob/main/SRC/GridForecast_Electricity_Demand_Predictor/services/retraining_service.py"
click node_scheduler "https://github.com/samithcsachi/grid-forecast/blob/main/SRC/GridForecast_Electricity_Demand_Predictor/workers/scheduler.py"
click node_observability "https://github.com/samithcsachi/grid-forecast/blob/main/SRC/GridForecast_Electricity_Demand_Predictor/observability/metrics.py"

classDef toneNeutral fill:#f8fafc,stroke:#334155,stroke-width:1.5px,color:#0f172a
classDef toneBlue fill:#dbeafe,stroke:#2563eb,stroke-width:1.5px,color:#172554
classDef toneAmber fill:#fef3c7,stroke:#d97706,stroke-width:1.5px,color:#78350f
classDef toneMint fill:#dcfce7,stroke:#16a34a,stroke-width:1.5px,color:#14532d
classDef toneRose fill:#ffe4e6,stroke:#e11d48,stroke-width:1.5px,color:#881337
classDef toneIndigo fill:#e0e7ff,stroke:#4f46e5,stroke-width:1.5px,color:#312e81
classDef toneTeal fill:#ccfbf1,stroke:#0f766e,stroke-width:1.5px,color:#134e4a
class node_prediction_service,node_inference_pipeline,node_redis_cache,node_fastapi_app,node_streamlit_app toneBlue
class node_training_pipeline,node_stage_ingest,node_stage_transform,node_stage_train,node_stage_eval,node_retraining_pipeline,node_retraining_service toneAmber
class node_entsoe,node_db_client,node_storage_client,node_feature_engineering,node_feature_store,node_schema_registry toneMint
class node_data_validation,node_schema_validation,node_model_registry,node_promotion,node_monitoring_pipeline,node_monitoring_service toneRose
class node_scheduler,node_observability toneIndigo
```

## Components

### Runtime

Online prediction and human-facing interfaces

- [Prediction svc](https://github.com/samithcsachi/grid-forecast/blob/main/SRC/GridForecast_Electricity_Demand_Predictor/services/prediction_service.py): serving service · Converts requests to features and model outputs · `SRC/GridForecast_Electricity_Demand_Predictor/services/prediction_service.py`
- [Infer pipeline](https://github.com/samithcsachi/grid-forecast/blob/main/SRC/GridForecast_Electricity_Demand_Predictor/pipelines/inference_pipeline.py): inference pipeline · Orchestrates online feature prep and scoring · `SRC/GridForecast_Electricity_Demand_Predictor/pipelines/inference_pipeline.py`
- [Redis cache](https://github.com/samithcsachi/grid-forecast/blob/main/SRC/GridForecast_Electricity_Demand_Predictor/cache/redis_client.py): cache · Speeds repeated serving-path lookups · `SRC/GridForecast_Electricity_Demand_Predictor/cache/redis_client.py`
- [FastAPI](https://github.com/samithcsachi/grid-forecast/blob/main/SRC/GridForecast_Electricity_Demand_Predictor/api/fastapi_app.py): http api · Serving API with health, metrics, and predict routes · `SRC/GridForecast_Electricity_Demand_Predictor/api/fastapi_app.py`
- [Streamlit](https://github.com/samithcsachi/grid-forecast/blob/main/SRC/GridForecast_Electricity_Demand_Predictor/app/streamlit_app.py): dashboard · Human-facing visualization and analysis app · `SRC/GridForecast_Electricity_Demand_Predictor/app/streamlit_app.py`

### Offline ML

Training, retraining, and batch lifecycle

- [Train pipeline](https://github.com/samithcsachi/grid-forecast/blob/main/SRC/GridForecast_Electricity_Demand_Predictor/pipelines/training_pipeline.py): offline pipeline · Coordinates staged model training lifecycle · `SRC/GridForecast_Electricity_Demand_Predictor/pipelines/training_pipeline.py`
- [Ingest](https://github.com/samithcsachi/grid-forecast/blob/main/SRC/GridForecast_Electricity_Demand_Predictor/components/stage_01_data_ingestion.py): pipeline stage · Pulls raw electricity data into the system · `SRC/GridForecast_Electricity_Demand_Predictor/components/stage_01_data_ingestion.py`
- [Transform](https://github.com/samithcsachi/grid-forecast/blob/main/SRC/GridForecast_Electricity_Demand_Predictor/components/stage_03_data_transformation.py): pipeline stage · Cleans and prepares training features · `SRC/GridForecast_Electricity_Demand_Predictor/components/stage_03_data_transformation.py`
- [Train](https://github.com/samithcsachi/grid-forecast/blob/main/SRC/GridForecast_Electricity_Demand_Predictor/components/stage_04_model_training.py): pipeline stage · Fits the forecasting model · `SRC/GridForecast_Electricity_Demand_Predictor/components/stage_04_model_training.py`
- [Evaluate](https://github.com/samithcsachi/grid-forecast/blob/main/SRC/GridForecast_Electricity_Demand_Predictor/components/stage_05_model_evaluation.py): pipeline stage · Scores candidate models and metrics · `SRC/GridForecast_Electricity_Demand_Predictor/components/stage_05_model_evaluation.py`
- [Retrain pipe](https://github.com/samithcsachi/grid-forecast/blob/main/SRC/GridForecast_Electricity_Demand_Predictor/pipelines/retraining_pipeline.py): retraining pipeline · Operational retraining workflow · `SRC/GridForecast_Electricity_Demand_Predictor/pipelines/retraining_pipeline.py`
- [Retraining svc](https://github.com/samithcsachi/grid-forecast/blob/main/SRC/GridForecast_Electricity_Demand_Predictor/services/retraining_service.py): workflow service · Triggers and manages retraining runs · `SRC/GridForecast_Electricity_Demand_Predictor/services/retraining_service.py`

### Data & Features

External ingestion, persistence, and feature preparation

- [ENTSO-E](https://github.com/samithcsachi/grid-forecast/blob/main/SRC/GridForecast_Electricity_Demand_Predictor/data_access/entsoe_client.py): external data source · Domain electricity data source for demand forecasting · `SRC/GridForecast_Electricity_Demand_Predictor/data_access/entsoe_client.py`
- [DB client](https://github.com/samithcsachi/grid-forecast/blob/main/SRC/GridForecast_Electricity_Demand_Predictor/data_access/database_client.py): persistence adapter · Abstraction for database-backed storage · `SRC/GridForecast_Electricity_Demand_Predictor/data_access/database_client.py`
- [Storage client](https://github.com/samithcsachi/grid-forecast/blob/main/SRC/GridForecast_Electricity_Demand_Predictor/data_access/storage_client.py): artifact store adapter · Abstraction for datasets, models, and metrics storage · `SRC/GridForecast_Electricity_Demand_Predictor/data_access/storage_client.py`
- [Feature eng](https://github.com/samithcsachi/grid-forecast/blob/main/SRC/GridForecast_Electricity_Demand_Predictor/feature_store/feature_engineering.py): feature builder · Transforms raw time-series data into model inputs · `SRC/GridForecast_Electricity_Demand_Predictor/feature_store/feature_engineering.py`
- [Feature store](https://github.com/samithcsachi/grid-forecast/blob/main/SRC/GridForecast_Electricity_Demand_Predictor/feature_store/feature_store.py): feature registry · Local feature definitions and reproducible feature access · `SRC/GridForecast_Electricity_Demand_Predictor/feature_store/feature_store.py`
- [Feature schema](https://github.com/samithcsachi/grid-forecast/blob/main/SRC/GridForecast_Electricity_Demand_Predictor/feature_store/registry.json): registry file · Static feature definition registry · `SRC/GridForecast_Electricity_Demand_Predictor/feature_store/registry.json`

### Governance

Registry, validation, drift, and performance controls

- [Data validation](https://github.com/samithcsachi/grid-forecast/blob/main/SRC/GridForecast_Electricity_Demand_Predictor/validation/data_quality.py): quality checks · Schema and data-quality validation layer · `SRC/GridForecast_Electricity_Demand_Predictor/validation/data_quality.py`
- [Schema checks](https://github.com/samithcsachi/grid-forecast/blob/main/SRC/GridForecast_Electricity_Demand_Predictor/validation/schema_validation.py): schema validation · Validates expected structure and fields · `SRC/GridForecast_Electricity_Demand_Predictor/validation/schema_validation.py`
- [Registry](https://github.com/samithcsachi/grid-forecast/blob/main/SRC/GridForecast_Electricity_Demand_Predictor/registry/model_registry.py): model registry · Stores model versions and active artifacts · `SRC/GridForecast_Electricity_Demand_Predictor/registry/model_registry.py`
- [Promotion](https://github.com/samithcsachi/grid-forecast/blob/main/SRC/GridForecast_Electricity_Demand_Predictor/registry/promotion.py): model promotion · Promotes evaluated candidates to serving · `SRC/GridForecast_Electricity_Demand_Predictor/registry/promotion.py`
- [Monitor pipe](https://github.com/samithcsachi/grid-forecast/blob/main/SRC/GridForecast_Electricity_Demand_Predictor/pipelines/monitoring_pipeline.py): monitoring pipeline · Runs drift and performance checks · `SRC/GridForecast_Electricity_Demand_Predictor/pipelines/monitoring_pipeline.py`
- [Monitoring svc](https://github.com/samithcsachi/grid-forecast/blob/main/SRC/GridForecast_Electricity_Demand_Predictor/services/monitoring_service.py): ops service · Coordinates drift, performance, and alerting · `SRC/GridForecast_Electricity_Demand_Predictor/services/monitoring_service.py`

### Ops & Observability

Telemetry, deployment, and operational tooling

- [Scheduler](https://github.com/samithcsachi/grid-forecast/blob/main/SRC/GridForecast_Electricity_Demand_Predictor/workers/scheduler.py): worker scheduler · Runs periodic or triggered jobs · `SRC/GridForecast_Electricity_Demand_Predictor/workers/scheduler.py`
- [Telemetry](https://github.com/samithcsachi/grid-forecast/blob/main/SRC/GridForecast_Electricity_Demand_Predictor/observability/metrics.py): observability stack · Logging, metrics, tracing, and dashboards · `SRC/GridForecast_Electricity_Demand_Predictor/observability/metrics.py`

## Connections

- ENTSO-E → Ingest: source data · Raw electricity data enters the ingestion stage
- Ingest → Data validation: checks · Ingested data is validated before downstream use
- Data validation → Schema checks: schema · Validation enforces expected structure
- Ingest → Feature eng: prep input · Raw data is prepared for feature construction
- Feature eng → Feature store: publish · Engineered features are stored for reuse
- Feature store → Feature schema: defs · Feature definitions are tracked in the local registry
- DB client → Storage client: persistence · Persistence layer separates database and artifact storage
- Train pipeline → Ingest: orchestrates · Training pipeline starts with ingestion
- Train pipeline → Transform: orchestrates · Training pipeline prepares features
- Transform → Train: feeds · Transformed features feed model training
- Train → Evaluate: scores · Trained candidate is evaluated
- Evaluate → Registry: registers · Accepted artifacts are versioned in the registry
- Promotion → Registry: promotes · Promotion updates the active served model
- Monitor pipe → Monitoring svc: runs · Monitoring pipeline delegates operational checks
- Monitoring svc → Telemetry: emits · Monitoring outputs telemetry and alerts
- FastAPI → Prediction svc: serves · API routes request prediction logic
- Prediction svc → Infer pipeline: executes · Prediction service uses the inference pipeline
- Infer pipeline → Feature store: reads features · Online inference reuses the feature layer
- Infer pipeline → Registry: loads model · Scoring uses the active registered model
- Prediction svc → Redis cache: cache · Serving path can use Redis for repeated lookups
- FastAPI → Telemetry: telemetry · HTTP layer contributes logs, metrics, and traces
- Streamlit → Registry: visualizes · Dashboard shows forecast and performance views
- Retraining svc → Retrain pipe: coordinates · Retraining service orchestrates workflow execution
- Retrain pipe → Monitoring svc: triggered by · Monitoring signals can initiate retraining
- Scheduler → Retraining svc: triggers · Scheduled workers initiate retraining runs
- Scheduler → Monitor pipe: runs · Workers can execute monitoring jobs
- Telemetry → FastAPI: observes · Telemetry stack covers API runtime behavior
