About
I build and lead technology systems and study how software architecture needs to evolve for what comes next.
My work spans software architecture, distributed systems, engineering platforms, AI native systems, and technology leadership. I am especially interested in the decisions and boundaries that determine whether complex systems remain understandable, operable, and trustworthy as they grow.
This site is not intended to be a résumé in website form. It is where I turn practical experience and ongoing research into frameworks, tools, reference architectures, and experiments that other practitioners can inspect and reuse.
What I Work On
Architecture is larger than diagrams.
I tend to approach technology through four connected lenses: the structure of the system, the engineering platform around it, the new behavior introduced by AI, and the leadership decisions that shape all three.
Software Architecture
Designing systems around clear boundaries, explicit tradeoffs, resilience, evolvability, and decisions that can be revisited when evidence changes.
Explore architecture resourcesPlatforms and Engineering Systems
Thinking about the engineering system as a product: paved capabilities, developer experience, operational context, governance, and feedback loops.
Explore platform thinkingAI Native Systems
Exploring what changes when models and agents become active software actors, especially identity, authority, evaluation, observability, and evidence.
Explore AI native engineeringTechnology Leadership
Connecting architecture with operating models, engineering strategy, standards, organizational boundaries, and the decisions that help teams move with clarity.
Explore leadership thinkingHow I Think
Make the decision visible. Make the boundary explicit. Keep the evidence close.
I prefer architecture that makes tradeoffs inspectable instead of hiding them behind vocabulary. A useful model should say what problem it addresses, where it stops, how it can fail, and what evidence would cause the design to change.
That is also how I approach work published here: explain the idea, build something concrete when possible, test the important claim, publish the limitation, and revise when the evidence disagrees.
Original and Practical Work
Some of the work currently being developed in public.
AEG
Separates autonomous intelligence from execution authority so model proposals do not become implicit permission to act.
ExploreSHIELD
Explores how independent evidence can build defensible confidence before a distributed system takes stronger action.
ExploreAI Platform Readiness
A practical way to examine whether an engineering platform is ready to support AI agents alongside human developers.
ExploreArchitecture Decision Framework
A reusable approach for comparing meaningful architecture options without hiding uncertainty behind a weighted score.
ExploreWorking in Public
From ideas to things people can use.
The goal is not simply to publish opinions. Insights explain the thinking, Projects provide usable artifacts, Labs test claims, and evidence records connect results back to the architecture.