Machine learning · Manufacturing quality

From prediction to better decisions.

An end-to-end ML system that turns production data into cost-based quality decisions—and gives engineers the evidence to review uncertain parts.

PythonLightGBMDuckDBFastAPIReact
LINEGATE / REVIEW CONSOLEHuman review
Review console showing a part score, production route, and evidence summary

A model score. A clear next step.

Connect failure predictions to inspection costs, supporting evidence, and an engineer’s judgment.

PredictPriceReview
1.18Mlabeled production parts
~$2,090modeled savings per shift*
25.7%of holdout parts routed to review
9features quarantined

*Offline holdout estimate versus shipping all parts, under project cost and volume assumptions. Not measured factory savings. See results and limitations →

The product

Built for the person making the call.

A focused review workspace brings the model’s prediction and the part’s production history into one view.

Expanded review console with multi-line production route and validated evidence citations

Understand the recommendation

See the part’s score against ship, review, and inspect zones defined by the cost policy.

Inspect the supporting evidence

Follow the production route and read an agent summary whose citations are checked against returned evidence.

Make and record a decision

Ship, scrap, or escalate with keyboard actions. Confirmed decisions are stored as labels for future training.

View full-size console capture ↗
01 / Architecture

System architecture

The decision path runs left to right: verified data, a LightGBM ensemble, a dollar-priced policy, and a review console. Agents sit above it and can only reach the model through the leakage warden.

INTERACTIVE DIAGRAMPan · Zoom · Search · Guided stories
No LLM scores a partLightGBM scores parts; the cost policy selects actions. Agents propose, explain, or prepare policy changes.
The warden has a vetoThree leak tests plus a deterministic rule the model cannot override.
People own the edgesUncertain parts go to reviewers; cost changes arrive as unmerged PRs.
02 / Sequence

A feature proposal, end to end

How an agent's idea becomes a scored feature, or a quarantine: parsed and dry-run SQL, a sandbox with one split and no labels, three leak tests, and an evaluation bar measured from placebo runs.

INTERACTIVE DIAGRAMPan · Zoom · Search · Guided stories
Guarded before registeredOnly one SELECT over sandbox views; no windows, labels, or holdout Ids.
Stricter verdict winsIf the model approves a leak, the rule quarantines it, and a quarantine is final.
Beat the noiseAccepted only if MCC and average precision clear two placebo standard deviations.
03 / Data flow

From raw sensor files to priced decisions

Hash-verified files become Parquet with proven row counts, split by production time. The holdout is sealed before any model exists and scored exactly once at the end.

INTERACTIVE DIAGRAMPan · Zoom · Search · Guided stories
Contract firstEvery raw load verifies sha256; no code path substitutes sampled data.
Dollars, not accuracyInspect $6.50, scrap $42, field failure $1,850 drive the threshold.
Transparent evaluationHoldout MCC of 0.110 is published alongside validation MCC of 0.227.
Results with context

Measured outcomes.
Documented tradeoffs.

This portfolio project uses historical Bosch competition data. The sealed holdout was evaluated once, and the findings include both the gains and the limitations.

Read the evaluation scorecard ↗
MCC · validation → holdout0.227 → 0.110
Holdout cost per shift · policy / ship all$18,010 / $20,099
Feature-search acceptance gateNot passed

Performance declined on later production data. No proposed feature cleared the noise-calibrated acceptance bar. Cost estimates evaluate the policy threshold, not realized savings from human review.