A weekly floor written only in a doc is not a floor. It is a wish.
Pattern
Twice daily (pre-peak):
- Compute week-to-date gross (settled days + live today — take max for today if two sources disagree)
- Compare to 70% of
(days_elapsed × daily_floor) - If behind → kick pre-authorized revenue lanes + text the operator
- If on pace → one log line, silence
Why 70%
Full-floor checks too early create false alarms before peak hours. 70% pace leaves room without letting the week die quietly.
Knobs
DAY_FLOOR(example: $2500/wk → ~$357/day)- Safe auto-kick list (no new spend, no config mutation without human)
- Notify bridge (iMessage / local HTTP)
What this is not
It is not an unsupervised money printer. Escalation surfaces work and alerts a human. Daemons that send fan-facing text without approval stay off until they meet the operator standard.
Related
- Community parity doctrine
- $5 runbook + example Python: dajai shop