A live look inside my head: what I've built over the past year and what state each thing is currently in. Statuses are honest — some of this runs every day, some is specced and waiting, some is parked on purpose. Updated when reality changes, not on a schedule.
A weekly public log of the actual work — what got built, what broke, what I almost sent and didn't. The constraint is the product: every week, whether the week was impressive or not. The streak trains a muscle two decades of institutional work never did.
The workspace behind the research: methodology write-ups, a status board, and point-in-time archives — documented while being built, not after it works. The structure is live; entries land as systems get verified against the archive. No scripts, self-hosted fonts, every section its own citable URL.
A design experiment: the same brief handed to three frontier models, four single-page answers, published side by side with their code intact. One of them became the King Nuggets Lab. The house rule applies to the exhibits too — read what the code does, not what it says it does.
Market research built on cycle methodology — counts measured trough to trough, anchors and invalidations stated up front. The archive grows every day whether anything publishes or not; issues go out only when the analysis clears the bar. One rule underneath it all: the model interprets, it never decides.
The pipeline that feeds King Nuggets: [one honest paragraph on current state — what the data pipeline does today, what the backtest harness covers, what's validated vs. in progress. Keep it methodology-level; no signals, no thresholds.] Built under a standing rule: no infrastructure without a named analytical or publishing requirement.
The preparedness system I actually run for my own household, documented so another Floridian can use it: food and water planning, offline communications, evacuation decision points, and the history of why flooding here happens the way it does. A storm passing a hundred miles offshore put water where people didn't expect it — understanding that turned out to matter more than any supply list. This one jumps the queue because it's immediately useful to somebody besides me, and the season doesn't wait for my publishing schedule.
Half a dozen scheduled jobs run in the background — a capture system feeding the second brain, an inbox scanner, a policy-headline monitor, and feeds pulling frontier-model and macro signals each morning. The one worth admitting is Hermes. It was built to run research, understand what it found, and get better at it. It does none of that, because I never built the layer around it that would let it — and I never built that layer because every time I approached it I got friction instead of a path, and taking the friction as a verdict was easier than pushing through it. That's what happens when you let the low-resistance direction pick the roadmap.
Statuses use three words on purpose: running, specced, parked. If something sits parked for long enough, it either gets a requirement or gets deleted — that's the point of saying so in public.
— Patrick King, CMT