Field notes
Engineering notes from building Virtunity
Longer technical writing about the systems behind the product: how they are built, where they failed, and what the numbers showed afterward.
Running a fleet of coding agents alone
What a one-person company learned running four kinds of coding agent against one repository: the launcher, the brief contract, the five stop classes, the four-line log, and the audit that found the instruction files disagreeing with each other.
Read the note →A tuner too sensitive to be useful
A per-frame blend weight is not a time constant. Six defects in a web tuner's needle, the single cents-domain smoother that replaced two fighting filters, and the rise-time tests that pinned it.
Read the note →Scripts do the deterministic steps
Where the model stops and the script starts, drawn twice in one day: a social publisher that hashes approved copy and refuses drift, and a contact importer that reports counts only.
Read the note →Making a model cite its sources
Building a lesson-to-practice-plan pipeline that refuses to invent homework: structured extraction, deterministic evidence validation, bounded repair, and the four failure modes that shaped them.
Read the note →