Each one is the same question from a different angle: what should a system keep, and who gets to read it back?
Desktop app · Electron
diy-dashboard
A day you can hand to an agent. Pomodoros, todos and market widgets share one local grid, and a small HTTP API lets a CLI, or an agent, read and write the same day you do.
The same idea, pointed at models. Korean retrieval built one layer at a time (dense, sparse, fusion, rerank), where each layer has to earn its place on a benchmark before it stays.
The exhibit you are standing in. One skeleton, four coats of stripes. The design system was written down before the site existed, so the spec and the page cannot quietly drift apart.