Game Rules — the daily model

How it works. Each logged set is converted to effort-adjusted reps before it hits the engine:

Bank-day continuation is the core SOT correction over the old model: a finished battle is not a dead battle. Later completers preserve their streak, earn participation credit, feed team totals and keep the feed alive — the SOT's words: "the battle does not become meaningless after somebody wins."

Worked example (from the v4 e2e): target 200. Marco (casual ×1.25) logs 48 push-ups → 60 reps. I steal 10% of Priya's completed 100 → +10 to me, Priya keeps 100 (pure gain). My plank hold of 11s → 1 rep. Then 195 push-ups → 206 ≥ 200: Daily Win, battle stays open, Priya finishes her 200 and banks the day (streak 1), Jack misses at the deadline — failed day, streak resets.

Failed days: at the clock's close, any eligible player under target fails the day — streak resets to zero, failed-day counter increments, the recap says so plainly. An armed Group Shield converts a failed day into a streak-preserved one (consumed at the close it saves).

Exercises convert too (a working proposal — the official table is an open SOT gap): burpee ×2.0, push-up/squat/lunge/dip ×1.0, mountain climbers/jump rope ×0.5, and timed holds at 10 seconds = 1 rep (plank, wall sit).

The measured-heart-rate blend from the earlier engine (70% %HRR / 30% declared tier) remains in game-core, waiting on straps — see Verification.

• Banked day — reached your target after the winner: streak +1, participation credit, history dot ✓.
• Failed day — under target at the close: streak → 0, ✗ in the history, comeback framing never shame (founder directive).
• Rest day — no battle scheduled today: the home screen says the streak is safe and names the next battle day (SOT #29/#101).
• Shield save — an armed Group Shield converts every failure at that day's close into streakPreserved, then the shield is consumed.

Streak truth lives in the engine's season record (recordBattleDay → battleStandings) — the live UI's optimistic counts reconcile there at every close, so a mid-day crash can't corrupt a streak.

Charity mechanics exactly: each player's contribution agrees up-front (points are the trial currency — the demo displays 1 point as $1); at season end the pot totals, the platform fee (5% default, always disclosed) is deducted on screen, the winner picks from the eligible list, and the donation lands with a receipt code. The winner never receives cash — stakes without gambling. Cash wagering is explicitly deferred by the SOT (licensing/KYC/geo — not V1).

The economy question, answered in code: SOT Q240–242 are open — how are cards acquired, how is power kept fair, do they expire? Our live answer: a season-1 founder pack, then a daily drop each battle day, a hold cap of 4 with leftovers carrying across battles (no expiry — cards are kept, not burned by time), and the draft-from-3 + catch-up curve from the v2 engine remains the proposal for competitive fairness. The v4 app plays all of it; this wiki keeps the receipts.

How it works. A 1-second ticker recomputes the remaining time and the urgency level (Battle live → Final 3 hours → Final hour → Final 30 → DO OR DIE); at the level-3 threshold the whole screen washes red and the copy pushes the log. A Time Freeze overlays everything with ice while it runs. At the deadline the day auto-closes exactly once: logging locks, completions/failures/shield-saves are stamped, the day folds into the season record, and the next scheduled battle opens.

Close-call detection (SOT #98) fires when the lead gap is under 5% of target with the leader past 70% — the "anything can happen" banner.

How it works. Win detection happens inside logSet — the engine decides, the app renders. The win moment generates a 780×936 canvas share card (PNG download / clipboard copy). Tone awareness (cheeky / neutral / corporate-safe) swaps every line of winner and failure copy — the same state speaks three dialects. See App Screens → v4 for the full screen-by-screen walk including the critical states (offline, sync conflict, rest day).