lesson 7 of 7 · the ml-system option — six boring stages that get a repo taken seriouslythe ml-system option — six boring stages that get a repo taken seriouslylesson 7 of 7 · the ml-system option — six boring stages that get a repo taken seriouslythe ml-system option — six boring stages that get a repo taken seriouslylesson 7 of 7 · the ml-system option — six boring stages that get a repo taken seriouslythe ml-system option — six boring stages that get a repo taken seriouslylesson 7 of 7 · the ml-system option — six boring stages that get a repo taken seriouslythe ml-system option — six boring stages that get a repo taken seriouslylesson 7 of 7 · the ml-system option — six boring stages that get a repo taken seriouslythe ml-system option — six boring stages that get a repo taken seriouslylesson 7 of 7 · the ml-system option — six boring stages that get a repo taken seriouslythe ml-system option — six boring stages that get a repo taken seriouslylesson 7 of 7 · the ml-system option — six boring stages that get a repo taken seriouslythe ml-system option — six boring stages that get a repo taken seriouslylesson 7 of 7 · the ml-system option — six boring stages that get a repo taken seriouslythe ml-system option — six boring stages that get a repo taken seriouslylesson 7 of 7 · the ml-system option — six boring stages that get a repo taken seriouslythe ml-system option — six boring stages that get a repo taken seriouslylesson 7 of 7 · the ml-system option — six boring stages that get a repo taken seriouslythe ml-system option — six boring stages that get a repo taken seriouslylesson 7 of 7 · the ml-system option — six boring stages that get a repo taken seriouslythe ml-system option — six boring stages that get a repo taken seriously
Checkpoint
One last thing before we move on. pass this to mark the lesson done, or skip and keep moving.
Last exercise of the capstone. Three candidate systems sit in
your portfolio folder; decide which one goes in the README.
Write readiness_report(system) returning a dict with:
stages_present: how many of the sixREQUIREDstages appear insystem["stages"]gate:"ship"ifeval_accuracy >= gate_threshold, else"hold"portfolio_ready:Trueonly when all six stages are present AND the gate says"ship"
The runner prints one line per system. Note what it punishes: price-model has the best accuracy of the three and still fails — no monitoring hook, no portfolio. Expected output:
churn-predictor: 6/6 stages, gate ship, ready: True
price-model: 5/6 stages, gate ship, ready: False
spam-filter: 6/6 stages, gate hold, ready: False