the current chapter — /now · confirmed 18 days ago
The one page I won’t fake.
So it stays real instead of tidy. Here’s what actually has my hours right now — dated, and rewritten when it changes, not written once and left to rot. What isn’t here is the private layer I keep offline until it earns a spot, not something faked to fill the space.
Everywhere else on this site, a status is measured with a value or it reads unknown. A /now page’s value is its date — so this one is derived, not typed: the build reads the last date a human confirmed these lines (2026-07-25) and prints the distance from today. Recent enough to trust as written. Past four months it downgrades itself and says so, because the one thing this page is named after not doing is pretending.
on right now
- research Undergrad RA in UW’s DAIS lab, on the cryo-EM → 3D-protein-structure pipeline: preprocessing, PyTorch and OpenCV training passes, backbone trace alignment, PyMOL renders. No paper byline — the work is real regardless.
- agents Building the correspondent layer at Superpowr — a voice-and-email agent, and a guardrail around every action it can take. Most of the attention lately is on the eval battery: making the tests attack the thing instead of flattering it.
- this site Rebuilding it in the open. The build fails on a single byte of JavaScript or a number that’s drifted from what it claims — the honesty is wired in, not promised. You’re reading a current draft of it.
- this week Smaller and more annoying than it sounds: my own checks kept passing when they shouldn’t have. A gate that turned out to cover five pages out of fourteen. The same gate blind to fifteen images because they sat one directory down. Then one that failed loudly about a file nothing on the site even loads, with a confident explanation that was wrong. Three ways of being sure about my own work and wrong about it, in a day — and none of them were the code breaking. They were the instrument breaking, quietly, while reporting fine. So the week went on the instrument rather than the output.
- shipping 62 commits to this site in the last 30 days. Counted by the build from the repository itself, not typed in — so it drops when I stop, which is the point of putting it here.
- school CS + Data Science at the University of Washington (’27).
- off the clock Still making music, still releasing none. The day that changes, this line gets a link instead of an excuse.
- kept offline The reading stack and the 3 a.m. what-ifs — the genuinely private layer. Absent on purpose, because inventing it is the one thing this page is named after not doing.
the throughline
The honest version, not the bullet list: right now it’s basically one obsession — building things that can’t lie to me. Not won’t; can’t. Tests that go at my own system trying to break it, instead of the ones that just confirm what I was hoping. A build that won’t ship if a number stops matching what the page says about it. Walls I put up on a clear day so the rushed version of me can’t talk his way back through them later. It’s the same reflex every time, and most of what I’m doing lately is finding new places to bolt it on.
The one I actually go back and forth on is range. Oceans, brains, street safety, access, now agents — everyone sensible says pick a lane, and I keep not doing it. I think it’s that I’m not loyal to the field, I’m loyal to the move, and the move travels. Whether that’s real focus or just me dodging the harder work of going deep on one thing — genuinely don’t know yet. Ask me in a year.
Want the part I keep offline? The fastest path is to just ask for it.