Week Revenue Floor Escalator: Markdown That Actually Enforces
·1 min read·tools
Share

Week Revenue Floor Escalator: Markdown That Actually Enforces

DAJAI Stewart

Turn a weekly revenue floor into a twice-daily pace check—WTD gross vs 70% of expected, safe kickstarts, operator notify, silence when on pace.

A weekly floor written only in a doc is not a floor. It is a wish.

Pattern

Twice daily (pre-peak):

  1. Compute week-to-date gross (settled days + live today — take max for today if two sources disagree)
  2. Compare to 70% of (days_elapsed × daily_floor)
  3. If behind → kick pre-authorized revenue lanes + text the operator
  4. 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

Sovereign stack field notes

Local AI, multi-desk news, and infrastructure you actually own.

Related