Python tests
API, scoring, drift and asset contract
Synthetic model observability · Python proof
A bounded model-monitoring platform built with synthetic network-service telemetry, keeping lineage, drift and limitations visible.

API, scoring, drift and asset contract
Measured by the final local pytest run
Generated 1,100-sample holdout only
1,440px desktop and 390px mobile
The slice is deliberately small: one safe telemetry problem, one reproducible artefact and enough surrounding evidence to challenge it.
Seed 404 creates bounded infrastructure telemetry with controlled label noise.
A random forest is accepted only when generated holdout ROC AUC reaches 0.85.
FastAPI validates the reading and persists probability, band, signals and version.
Population stability and Prometheus metrics expose changes around the model.
Stack selected from employer evidence
After .NET and Java, Lumen responds to Python, data, model-monitoring and cloud-service signals in target banking and telecommunications roles without becoming another oversized flagship.
Typed APIs and a second backend ecosystem beyond .NET and Java.
A reproducible training path, model artefact and explicit release gate.
Every synthetic reading keeps its inputs, output and model version together.
Input-distribution change and service behaviour remain inspectable.
A non-root runtime and pinned verification workflow.
Training and seeded interface data are visibly synthetic.
Each score records the model version that produced it.
PSI compares recent inputs with the training baseline.
PostgreSQL keeps the measured input and result together.
Ruff, strict mypy and nine pytest checks passed locally on 07 September 2026 with 91.76% statement coverage under a targeted warning policy. Project-owned deprecations are promoted to errors; one understood third-party warning is filtered. Docker/PostgreSQL readiness, Prometheus output and one complete desktop/mobile scoring flow remain the separate 15 July 2026 checkpoint.
Generated infrastructure telemetry only; no person or customer data
Contextual signals orient investigation but are not causal explanations
Holdout metrics do not claim performance on a real telecommunications network
Local repository and noindex case study; no public or cloud deployment implied
Local repository and noindex; not presented as a deployed system.
Quality gates refreshed 07 September 2026 · Docker/browser checkpoint 15 July 2026.