Six numbers: the five Netradyne driving rates, and the FICO score that sits with them. They are the hardest exclusions on the sheet — no research step, no judgement call, no appeal path built into the rule. Over the line is over the line.
All five come off the weekly Amazon Scorecard, one column each, one row per driver. They are rates, not counts — events per hour of driving — so a short week and a long week are compared on the same footing. Amazon sources them from Netradyne, the in-cab camera system.
| Rate | What trips it | Threshold | Result |
|---|---|---|---|
| Seatbelt Off Rate | Driving with the belt unbuckled. Includes the short hop between stops — the camera does not care that it was twenty feet. | > 0.4 | Ineligible |
| Speeding Event Rate | Over the posted limit by Netradyne's margin, on its read of the road's speed limit. | > 0.4 | Ineligible |
| Distractions Rate | Eyes or hands off the task — phone in hand, looking away from the windshield, reaching across the cab. | > 0.4 | Ineligible |
| Following Distance Rate | Too close to the vehicle ahead for the speed being driven. | > 0.4 | Ineligible |
| Sign/Signal Violations Rate | Rolled stop signs, red lights, missed signals. | > 0.4 | Ineligible |
The threshold is 0.4, and it is strictly greater-than: a rate of exactly 0.4 passes. This matters more often than it sounds like it should, because Netradyne's rates land on round numbers constantly.
Not the credit score. Amazon's FICO here is a composite safe-driving score on a 1–850 scale, built from the same Netradyne telematics that feed the five rates above — so it is not independent evidence, it is the same evidence scored a second way. It became a real exclusion on 2026-09-20, on Dan's call, and sits immediately next to the safety rates because it is a safety number: "just like the .4 safety rule."
| Score | Means | Result |
|---|---|---|
| 800–850 | Passing band. | Passes this rung |
| 1–799 | A real score, below the band. | Ineligible |
| blank / "No Data" / 0 | No score yet — not a bad score. | Rule does not fire |
Adding FICO changed no past verdict — nobody in the entire archive scores in the 1–799 band. The regression test asserts exactly that, so the rung is proven inert on history rather than assumed to be.
Safety is rung 4 and FICO rung 5 of ten. Everything above them — Damage, Terminated, Attendance — comes out of Jake's tracker rather than the Scorecard, so it is checked first. Everything below is either a delivery-quality number or something that needs research.
Because the ladder stops at the first match, the order among rungs 1–8 only decides which reason gets printed for a driver who breaches several. It never decides who gets paid. Safety was moved to print above POD on 2026-09-20 for exactly that reason: when a driver breaks both, "Safety" is the more useful thing to see on the sheet than "POD".
| Stage | What happens |
|---|---|
| Source | Amazon's weekly DSP Scorecard PDF, one row per driver. Read straight off the PDF with pdftotext -layout — no hand-typing since 2026-09-20. |
| Upstream | Netradyne (idms.netradyne.com) is where individual events can be reviewed and, where wrong, disputed. |
| Rule | rules.py — constants SAFETY_MAX and FICO_MIN_ELIGIBLE. One copy, both stations. |
| Output | The Final_Cut tab of the biweekly workbook, which feeds payroll directly. |
Dan confirmed on 2026-08-25 that the Scorecard itself — not GeoTab, not a separate telematics export — is the source of truth for the safety thresholds. That is why no second system needs to agree before a safety exclusion stands.
DIN6 and DII5 run the identical rules off one file. They did not always: until 2026-09-20 each station had its own copy, 0.4 was written down twice, and the copies had already drifted — DII5's was written before Attendance became a real exclusion and never gained that rung, so a DII5 driver with an attendance occurrence was paid a bonus a DIN6 driver with the same occurrence lost. Unifying them was proven behaviour-neutral across 447 driver-weeks with 0 verdict changes.
rules.py (SAFETY_MAX, FICO_MIN_ELIGIBLE).
Narrative from references/ripple-bonus-rules-at-a-glance.md and
references/ripple-bonus-correction-vocabulary.md. Last checked 2026-09-20.