Apparently, I’m a product now.
This website has an API, an MCP server, and far too many machine-readable files. I am still a person. The machinery makes my public work easier to understand; it does not turn me into an on-demand service.
Yes, it behaves like a product
It has structured data, documented interfaces, predictable responses, and several ways for people and agents to explore the same information. That is intentional. Building the portfolio this way is part useful infrastructure, part experiment, and part example of how I like to make things.
But I am not one
The site cannot determine my availability, quote a rate, accept a brief, promise an outcome, or decide whether we would work well together. Those things need context, judgement, timing, and an actual conversation. When they are unknown, the interfaces are designed to say so.
What the machinery is for
A product tries to deliver a repeatable capability on demand. This portfolio does something smaller: it gives you a reliable path through my public work, then gets out of the way. If that work feels relevant, the useful next step is still human.
Still curious?
Look through the work, inspect the strangely serious agent infrastructure, or simply say hello.