Spend ramp alert — Smith missed a 3x Vercel ramp under the $100/day floor

Add a relative spend trigger: a vendor whose trailing-3-day average is >=2x its prior-14-day median AND >= $10/day over it pages once (dedup, reaction on repeats). Backtest against Vercel Oct 1-10. RULED 2026-10-11: first fire is Oct 8, not the Oct 3-5 originally asked for.

Why Oct 8, not Oct 3-5 — and the receipts

That target assumed Vercel's normal level was ~$12/day; the real bill shows mid-September at $30-36/day, so the 14-day median is $18.78 and the ramp is smaller than it felt. Three independent instruments agree on the series to the cent. Both settings that would have reached Oct 5 were rejected on their merits (receipts fda085d78, faa4d287d), not tuned to fit. Ship with tests.

Status is DERIVED from each row’s own PR, decision and prod-evidence links by bin/refresh-tracker spend-ramp-alert — never typed. Last refreshed 2026-10-14 23:48Z.

Overall
—
 
—
Shipped
—
Merged
—
In flight
—
Open
—
Waiting on you
Groups — click to filter
Status
—

Every row opens: when it was added, why it exists, and the links that prove it. Rows waiting on a human carry a Decide → link straight to the answerable question on the decisions page. Statuses are re-derived from live PR, decision and prod-evidence state by bin/refresh-trackers; nothing here is typed by hand, and merged is not shipped until a prod_evidence permalink says the fix was exercised in production.

PropFlow Docs