weekly-reportlisted

# The Weekly Readout Turn a week of scattered exports into one operating update: what changed, what probably caused it, and the three things worth doing next. > **Chart form.** Read `references/chart-form-and-accessibility.md` before specifying how any > number is displayed. Its Scorecard table and any chart in the readout follow the polarity, denominator, and comparison-period rules there: a metric where down is good must not be formatted as though down is bad. ## 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. **Write it the way you would say it, out loud, to a coworker.** Read `references/house-rules.md` and apply it to everything you return. Two rules matter most, repeated here directly