Micro-Retirement Workspace
A personal operating system, not a demo. Built to run my own days during a career break, then instrumented to tell me the truth about how I actually spent them.
daily use
no backend
retrospectives
daily briefings
the problem
A career break is easy to romanticize and easy to lose track of. I wanted one place that held the practical (habits, finances, family calendar, learning) and the honest (a journal that couldn't quietly disappear the way good intentions do). The constraint was that it couldn't become another app I abandoned in week three.
the approach
Built as a single HTML file. No framework, no build step, no backend. All data lives in the browser's local storage. An AI bridge (a small JavaScript API exposed on the page) lets a daily scheduled task push a morning briefing straight into the app by reading calendar and inbox signals and writing them into local state.
The constraint was deliberate: anything that added infrastructure had to earn its place against "does this still work if I open my laptop in six months." No server to maintain, no account system, no dependency that could quietly break.
what shipped
Habit tracking, a daily briefing card assembled from calendar and email signals, a finance and family-events log, a learning log, and a monthly retrospective generator that turns weeks of raw tracking into a calendar heatmap and a written summary: deep work shipped, exercise days, learning signals, social connection, family time, with no editorializing, just what happened.
The build itself iterated the way a real product does. An early version tried to fit everything into one dense daily view, then got restructured into a clearer layout once it was obvious the dense version didn't survive contact with actual daily use. Small, dated changes over weeks, not a single build-once artifact.
a sample retro
Each month the workspace generates a written retrospective from that month's tracked data. It's built to report the gap honestly rather than smooth it over. A lightly redacted excerpt, stripped of anything personally identifying:
"17 active exercise days this month, the strongest consistency yet. A structured routine plus a formal check-in kept the streak intact."
"21 deep work days, the best month on record. The AI and learning stack finally turned into a steady output loop instead of sporadic bursts."
what I learned
The interesting output of a self-tracking system isn't the dashboard, it's the monthly retro that reports what actually happened, without smoothing it over. Some months read like the one above. Others don't, and the tool has to say that just as plainly. That honesty turned out to be the actual product decision, not the layout, not the color palette.