I was building this site, and I kept noticing I was making systems. The navigation needed a taxonomy, so I built a three-tier classification. The copy needed a voice, so I built a voice protocol with verification checklists. The AI kept contradicting its own decisions, so I built a governance protocol and embedded it in the project root. Every problem became a structure, and every structure became a tool, and at some point I was sitting there looking at all of it and I thought: why does my brain turn everything into a fucking system.

And the thing is, it wasn’t just the site. I have a system in the kitchen. I have a system for the plants in the backyard. I built defaults for the household so nobody has to make decisions at 7 AM because breakfast was taking 90 minutes. I looked at the site and I looked at the kitchen and I looked at the backyard and they were all the same operation. I just hadn’t put them next to each other before.

Where it started

I think I know. I figured this out recently, and it surprised me, because it goes back further than I expected.

My father was a construction superintendent. He held the entire picture of a building while fifty trades worked their piece. Electricians, plumbers, ironworkers, framers, each one responsible for their channel and none of them responsible for how it all came together. The whole picture only existed in his head. I watched that for years before I had any language for what I was seeing, and I think that’s where the pattern started. Something about watching someone hold the whole while everyone else works the parts. I learned it by watching before I knew I was learning it.

Screenprinting is where it locked in as a skill I could name. At SVA, then at USA Tees in Brooklyn, then at Atlas Embroidery in Fort Lauderdale. Separation means you never work on the image. You work on a channel, one color at a time, and the whole composition exists only in your head while you’re building a single plate. You decide how colors interact when they overprint before any of that is visible. It’s the same operation my father was running, just on a light table instead of a job site.

And the screenprinting vocabulary (separation, registration, overprint, channel) became the vocabulary I use for everything. SCSS cascades. Function chains. Multi-agent workflows. You’re always working on a channel, and the whole only comes together when the layers register.

The naming happened while building this site

I knew I’d been doing this across different kinds of work for a long time. What I didn’t know, until I was sitting here trying to organize twenty-five years of it into a portfolio, was that it was all the same operation.

I had to sort everything into categories and I kept finding the same thing underneath. Encore, the enterprise platform I maintained for twelve years: I built the structure that let the software keep running while everything around it changed. Aiden-Jae, the jewelry brand: I built the system that made the quality visible through the screen. Savepoint Protocol: I built the markup that captures where thinking shifts before the context closes.

Every single one of those is: take something fragile, build structure around it, make the structure holdable by someone other than me. I kept staring at my father’s work and my own work and seeing the same pattern. The person who holds the whole picture, and then the structure that makes the picture holdable so it doesn’t depend entirely on that person. I just didn’t connect it until I had to put it all in one place.

The flame

I described it to a friend like this: the tiny flame of creative intent needs structure built around it to survive the build. In all cases. The flame is the original intent of the work. The creative process is brutal. It has to go through production, through other people’s hands, through time, through entropy. The structure doesn’t create the flame. It keeps the wind off it while you’re carrying it through.

And it goes both directions. Bringing craft-level attention to modern tooling, and bringing modern technological approaches and syntax down to handcraft. The construction superintendent and the screen printer and the software architect are all running the same process: decompose the whole into workable pieces, build each piece with fidelity to the original intent, and make sure the pieces register when they come back together.

Leaning in

The methodology was instinctive before it was articulated. It was running in screenprinting and construction and software and fiction for twenty-five years before I had a name for it. I just couldn’t see it as one thing until I had to put it all in one place.

My brain turns everything into a system because that’s how I hold things together. The kid who grew up watching his father hold buildings together in his head, the screen printer who never stopped separating things into channels, the software architect who kept the platform running for twelve years while everything around it changed. All the same operation. I only recently figured that out, and it felt good to figure it out.