A little less magic.
A lot more control.
Exploring the system around the model: useful tools, shared context, clear responsibilities, and a way to see what happened.
The model is one part of the product.
Adnan’s agent-system work explores how to coordinate models, tools, and tasks without losing control of the larger workflow. OM5 is his model-agnostic operating-model and harness concept.
The focus is practical: decide what needs to happen, give each part a bounded job, keep useful evidence, and make important actions inspectable.
Questions worth making visible
What was the agent asked to do? Which information did it use? Which tool did it call? Where did it need a human? A portfolio should make those choices easier to inspect, not hide them behind the word “agentic.”
From experiments to useful systems
More autonomy is not automatically more value.
This case-study space is designed for approved architecture diagrams, worked examples, evaluation cases, and demonstrations of those boundaries. It distinguishes an independent prototype from a deployed customer system.
A connection to enterprise work
At Equinix, Adnan used Claude and an existing Atlassian MCP integration to simplify program reporting. That is different from authoring the integration itself. The website and guide preserve that distinction.