The longest-running project in the toolkit is a record that has nothing to do with any client. It is the reason half of the toolkit exists.
Drum patterns built on anchor-shift logic — the snare locked on beats two and four, the kick and hi-hat shifting underneath in defined pocket states — required a generator that did not exist as an off-the-shelf tool. The record needed it; the record could not be honest without it. So the tool was written.
The tool is now part of the practice. A brand film that needed a rhythm bed for its second act used the engine. A motion graphics piece that needed pulse-locked transitions used the engine. The same code that decides whether a metalcore drum fill sits inside the bar or rushes the next one decides whether a typographic transition lands clean.
This is what the cross-surface thing means in practice. The personal work and the client work share infrastructure. The record sharpens the practice; the practice gives the record a place to land. Neither one is a hobby on top of the other.
There are operators who would not hire a practice whose principal is also writing a record. There are also operators who would only hire that practice. The honest disclosure is that the artifacts in the toolkit came from somewhere — most of them came from work that was not commissioned. If that is a disqualification, the disqualification is right.
The record is not on the homepage. It does not need to be; it is on the work register, alphabetized next to the audit pipeline. Two artifacts the practice owns. Both of them work.
— Cross-surface · 2026 / 04