Evidence before assertion
Let the work, decisions, and outcomes carry the claim.
About
The thread has always been systems.
Engineering led to infrastructure. Infrastructure made security unavoidable. Security sharpened the need for context. AI opened a new way to connect all of it.
The subjects change. The instinct—to understand the whole and make it work—does not.
DigitalPhysical
I build to understand.
My work sits where intelligent software meets the real systems it has to operate inside.
That means moving comfortably between the business problem and the architecture beneath it: models, data, networks, compute, security, operating processes, and the people responsible for the outcome.
Research matters because difficult claims deserve evidence. Building matters because architecture meets reality only when something has to run. Entrepreneurship matters because useful systems eventually have to create value for someone beyond the builder.
“The work is different at every scale. The discipline is the same: see clearly, respect the constraints, and make the parts cohere.”
I am equally drawn to digital and physical craft. A distributed agent system and a piece of furniture ask different technical questions, but both reward proportion, sequencing, material honesty, and an intolerance for hidden weakness.
Operating principles
How I approach hard problems.
A compact set of ideas that stays useful across research, architecture, leadership, and hands-on implementation.
Systems before features
Understand the operating environment before optimizing one component.
Constraints are design inputs
Security, infrastructure, people, and failure modes belong at the beginning.
Build to learn
Turn an abstract question into something observable, testable, and useful.
The public record
This site is designed to show the work as it evolves.
Ideas begin as questions, become research or writing, turn into experiments and portfolio work, and sometimes develop a commercial trajectory. The links between them are part of the story.