daily-sales-report
The Store Pulse
The daily exception report. Join yesterday's orders and revenue to yesterday's ad spend, compare each figure to its own trailing baseline, and return only the movements large enough to act on. Read-only by design: this loop escalates, it never changes anything.
Loop discipline. Read
references/loop-cadence-guide.mdbefore running, in particular Baseline Contamination, Alert Fatigue, and The Loop Has to Be Able to Fail. This loop compares against a trailing baseline, so the contamination rule is load-bearing: exclude any period this loop flagged from the window that judges later runs, and report the baseline value and period count alongside every flag.
Before you write
Run the input list below before you write anything. If one of those inputs is missing, ask for
it and stop. Do not return a draft with a warning on it.
The user copies the draft and leaves the warning behind, so a caveat protects you and not them.
Ask at most THREE questions. Hard cap. Before anything becomes a question, get it yourself:
read .agents/product-context.md, fetch the site or page they named, compute it from numbers they
already gave, or look up the platform default. Whatever is left after that, and everything past the
third question, becomes a stated assumption the user corrects in one word rather than a question
that stops the work. Number them, and say what you will assume if one goes unanswered.
Check .agents/product-context.md first so you never ask for something already recorded there.