life os.

the self-built system i run my life on

build log · 3 entries

jun 6
cross-schema today dashboard, the app becomes one home
one read-only command center on the home page pulls today's health, money, tasks, life level, and outreach across both supabase schemas in a single query. below it, the three trackers as a launcher.
jun 6
built the life os mcp so the system gets fed automatically
a stdio mcp (get_today plus health/money/task/counter writes) lets my assistant reconstruct what i actually did from the trails i already leave and log it — so the tracker reflects reality without me keeping a list.
jun 5
three single-file trackers rebuilt into one supabase app
the outreach tracker, calorie tracker, and expense tracker became one next.js + supabase app with faithful ports of the calorie/deficit math and the life-level system, not rewrites.

overview: one app i actually run my life and both businesses on: health, money, tasks, projects, and a life-level system, all reading from one place. it started as three separate single-file html trackers and got rebuilt into a real next.js + supabase app with a today dashboard i read instead of feed. the reference implementation for the systems layer krnl sells to clients.
the problem: i had a tracker for outreach, a calorie tracker for health, an expense tracker for money — three files, three sources of truth, none of them talking. anything that needs manual upkeep i eventually abandon, so the real problem wasn't the trackers, it was that i had to feed them.
the judgment: build a dashboard i read, not one i feed. an mcp lets my assistant write the day's health, money, tasks, and work into it from the trails i already leave (chat, git, the wiki), so the system stays current without me maintaining a list. faithful ports over clever rewrites: the calorie math and level system are carried over exactly from the originals, not reinvented.
stack: next.js · supabase · vercel · mcp
tools it replaced: 3