Why Root18D exists
A working space for connecting cloud-scale systems, agentic AI, and the lessons hidden inside delivery.
The most useful lessons rarely arrive as finished case studies. They begin as a pattern in a live-site issue, a recurring question from a customer, a design tension, or an experiment that changes how a team sees the system.
Root18D is where I make those patterns visible.
From delivery to learning
Azure Commerce sits at the intersection of technology, economics, identity, capacity, and customer trust. A change that looks small in one layer can create an entirely different outcome in another. The work is not only to solve the immediate problem, but to preserve what the problem taught us.
That is also how I think about agentic systems. A useful agent does more than execute a task. It observes the result, evaluates the signal, and carries the learning into the next loop.
The goal is not automation for its own sake. The goal is a system that becomes clearer, safer, and more useful with every cycle.
What I will write about
- Azure Commerce architecture and transactional experience
- Agentic loops, evaluation, and applied AI
- Cloud-scale telemetry, capacity, and live-site learning
- Program leadership across business and engineering boundaries
These are field notes rather than final answers. Some will become frameworks. Some will remain questions. Both are useful.