Engineer — agent systems, guardrails, corrections published in place.
Seattle · building
Voice and email agents that answer real phone numbers, the routing and eval discipline underneath them, and the habit of not letting a green dashboard lie to you. Most of what I know about shipping, I learned from the times it broke.
Currently an intern at Superpowr, owning the correspondent layer end-to-end — voice, email, model routing, and the compliance research that constrains all three.
These six numbers are read off the built site by a script after every build, written into the page, and then re-read and compared. If any of them drifts from the artifact, the build fails rather than publishing the old number. Nothing here is typed by hand, and nothing here is about anything except this website.
When a live agent was talking too much, I pulled the real conversation turns before touching a line of the persona. The filler I’d written to mask slow replies was firing on nearly every one of them. I had written the symptom myself.
An audio fault survived two calls because every log line was sitting in an unflushed buffer. I shipped the observability fix in the same pass as the bug.
The rules I set while thinking clearly have since refused me while I wasn’t — including once when I explicitly told a system to stand down and it declined. That is the feature working.
A green regression bank told me a system was healthy while its live path was broken, because the harness fed inputs the real wire never delivered.
Uncalibrated numbers get labelled uncalibrated, prototypes get called prototypes, and the gaps sit next to the wins.
None of this is theory I read. It is all the residue of something breaking while I was responsible for it.