One Static HTML File With No Version Control Was Running My Whole Dashboard

A single static HTML file with no version control ran my entire personal dashboard, the one tracking every active build. One bad edit could have wiped out months of project tracking with no way to undo it. That's the kind of risk that sits quietly for a long time until you actually notice it.

First move was simple: bring it into Claude Code, where every change has history.

The second move took longer to land on. Instead of treating the dashboard as one app needing a cleanup, I reframed it as an operating system, not just a display, but something that should eventually trigger work, hold memory across sessions, and route tasks to the right agent. That reframe changed what got built next.

The four layers

For the eventual desktop version, I chose Electron over Tauri, mainly because the existing code was already plain HTML and JavaScript, so there was no new language to learn just to wrap it. The technical snag came weeks later, while building the kernel itself: getting Electron's preload script talking to the main process without breaking the existing dashboard, since Electron enforces strict isolation between those two for security reasons.

This is a "the thinking is the part that determines whether the build goes smoothly" piece, and I want to keep that front and center rather than lead with the code. The reframe happened weeks before any code got written. That's the part that made the actual build, kernel first, then memory, go as smoothly as it did once it started.