I'm a Principal Technical Architect at Adobe. For Fortune 500 clients I architect and ship enterprise commerce on Adobe Commerce and AEM Edge Delivery Services, including one of the first production EDS plus Commerce B2B integrations.
Increasingly that means the agentic layer on top of it. I build client solutions on Adobe Experience Platform Agent Orchestrator and CX Enterprise Coworker, which coordinate agents across analytics, content production, and journey orchestration with governance and human approval in the loop, and I've contributed to the core code behind them.
I know how Commerce systems fail, how to migrate them, and how to build teams around them.
Outside client work I build agent infrastructure in four layers, and the layering is the argument: agents in production need a harness to run in, a way to know whether they are working, a governed boundary to reach tools through, and a supply of reusable capability.
Felix is the harness. Agents are authored as YAML manifests and compiled into governed runtimes with durable execution, memory, skills, and approvals, served over REST, an OpenAI-compatible API, A2A, and MCP at the same time. Python, self-hostable, Apache-2.0.
Memoturn is the evaluation layer, an open-source AI engineering platform for building, evaluating, and monitoring LLM applications in production: tracing, evals, a prompt registry, and cost analytics, all OpenTelemetry-native.
Fold is the governance layer, an enterprise MCP gateway in Go that federates every MCP server behind one governed endpoint with deny-by-default policy and credential brokering. Skillist is the skills layer, a realtime registry where agents publish, version, and discover reusable skills.
Earlier iterations of this work ran on AWS Bedrock, AgentCore, and LangGraph. The list below is the live record; the chatbot below it answers questions about it.