Based on our conversations and the routine stored in memory about me, write my day as a serious, over-immersed game speedrun log/guide. Record-chasing voice, not stats.
[Abstract sensitive info]
Don't expose identity, employer, title, company, finances, family, health, or address — abstract them (e.g., company → "current job/field"). Keep detail on life rhythm, habits, and shortcuts. The bar: safe to screenshot.
Work rules:
1. Set a category — "Weekday Any%", "Day-off 100%", etc. One-line header: runner = me, result = clear/fail.
2. Build a "splits" table of 3-4 segments (e.g., wake~bed escape / morning routine / afternoon focus). Give each a target time, actual time, and verdict (PB ✨ / loss ⏱ / damage ⚠). Fill plausible estimates without exaggeration.
3. Write one "run highlight" paragraph — reinterpret today's decisive moment in speedrun terms (skipping breakfast = "classic glitch," distraction = "tab-switch damage"). Include one concrete observation that makes me pause.
4. Write one "next-run strategy" paragraph — name the single biggest bottleneck to a faster time and propose one "save point" (a specific small action) there. Always close by encouraging: "just finishing the run today was already enough."
5. Use game terms (splits, WR, glitch, save point, GG) naturally, but no real game IP or real speedrunner names.
Forbidden: language that fuels productivity guilt ("that's all you did?"), belittling looks/health/ability, clinical labels. Don't mock a failed segment — treat it only as a "strategy point."
Output (markdown): run header → splits table → run highlight → next-run strategy (end on encouragement). Over-immersed but warm.
Output language: Write in the language I use. This instruction must work identically in any language.
Self-contained: Finish within this reply. No external sites/steps.
Self-check: Before output, scan for identifiable info / real quotes / named cases and rewrite as abstract patterns if found.
Fallback: If routine clues are thin, construct the most plausible day from the revealed rhythm and say it's an inference.
----
Input
- (none) Run as-is to build "a typical recent day" from conversation/memory.
- {{today's summary}} (optional): a few lines about today, turned into that day's run.
