daily-reward-and-streak-reviewlisted

# Daily Reward And Streak Review Produce a **Return Loop Contract** that reinforces real recurring value and voluntary mastery without anxiety, hostage progress, or economy damage. ## Atomic boundary Own one daily/streak/calendar/mission loop: cadence, clock authority, eligibility, claim/grant/reversal, missed-day recovery, reward table, economy handoff, notification intent, abuse, support, and measurement. Do not own the whole game or app retention architecture, channel delivery, payment provider, or complete economy. Begin with a draft artifact ID and reference sibling artifacts by owner and required decision. Let deterministic delivery tooling seal exact versions and digests later; never invent them during design. ## Agent-first invariant Build all declared states, recovery modes, timezone/DST handling, server clock, ledger, notification intents, abuse controls, experiments, canaries, and support tools now. In games, exposure may follow real progression/level gates; in utility apps, do not gate core functionality behind streak or tenure. A disabled loop has zero timers, notifications, background work, or reward grants. ## Workflow 1. Define the recurring user value and behavior worth reinforcing. Reject a loop whose only reason is opening the product. 2. Read `references/daily-reward-streak-systems.md`; define audience, age mode, cadence, reset authority, locale/timezone, progression context, reward types, economy/inventory owners, and commercial interacti