One small, honest ML system per day, each built end to end on Hopsworks. Same shape every time: an FTI (feature, training, inference) pipeline, a real result with its caveats, and a served model you can poke at. No notebooks-that-never-ship, no accuracy without a holdout, no demo wired to a mock.
| # | system | the question | result | published | repo |
|---|---|---|---|---|---|
| 001 | README Vaporware Score | does a repo get abandoned, from its README text alone? | ROC-AUC 0.76 | 2026-06-29 | readme-vaporware-score |
| 002 | Asteroid Doomsday-o-meter | how big is an asteroid (so, how dangerous), from its Gaia spectrum alone? | size error ×1.13 vs ×1.34 blind | 2026-06-30 | asteroid-size-from-light |
| 003 | Phishing at Issuance | is a freshly issued TLS certificate phishing, from its hostname alone? | ROC-AUC 0.78 holdout vs 0.50 blind | 2026-07-01 | phish-at-issuance |
Every repo in the series follows the same mould, so they read as siblings.
Shape. An FTI system on Hopsworks. Sources to a feature pipeline to a
Feature Group, a Feature View to training to the Model Registry, a deployment to
an endpoint, an app that calls it. The skeleton lives in
templates/diagram.mmd.
Banner. Generated, not hand-drawn, so 30 of them stay consistent. Dark canvas, emerald accent, the Hopsworks hop-mark as the fixed brand, only title/tagline/emoji/index change per repo.
python tools/make_banner.py \
--title "My System" \
--tagline "What it predicts, in one honest sentence." \
--emoji "🧪" --index 002 --out assets/banner.svgREADME. Result first (with the metric and the holdout), then caveats, then
architecture (the diagram plus a file-by-file map), then reproduce, then the
served demo. Start from templates/README.template.md.
Honesty rules. The label is named and its proxy is stated. There is a holdout number, not just cross-validation. No feature leaks the label. Heavy fits run as Hopsworks jobs, not in a terminal. Feature extraction is one shared function so training and serving cannot skew.
mkdir ../my-new-system && cd ../my-new-system
cp -r ../awesome-ml-systems/tools . # the banner generator
cp ../awesome-ml-systems/templates/README.template.md README.md
python tools/make_banner.py --title "..." --tagline "..." --index NNN
# fill the README, paste templates/diagram.mmd, then add a row to the table above