Skip to content

About

Solution Architect / AI Architect — enterprise AI, agents, and cloud architecture.

I write about the systems I work on — agent architecture, enterprise AI platforms, and the parts of cloud architecture that only become interesting once something is in production and someone is paged about it.

Most articles here ship with a working proof-of-concept. A diagram is cheap; a running implementation is where the tradeoffs actually show up, and where a claim can be checked rather than believed.

What I write about

  • agent architecture
  • MCP and tool protocols
  • enterprise AI platforms
  • AI security and trust boundaries
  • AWS serverless architecture
  • production readiness
  • AI observability
  • RAG and retrieval architecture
  • distributed systems

Going further

Six principles are on the homepage. These four sit underneath them, and matter most once a system is already in production.

  1. Knowledge needs a promotion path.

  2. Authorization must travel with retrieval.

  3. Evaluate the system, not just the answer.

  4. Reliability has to surround the model.

Who it's for

Architects and senior engineers making decisions they will have to live with: CTO, CIO, Engineering Director, Principal Engineer, Solution Architect, AI Architect, and anyone else who has to answer for a system after it ships.