Software engineer working on AI agents and the systems that check them. I turn research questions into working software: measurable, inspectable, and useful past the demo.

• Production · CRM DevOps and AI engineering (conveyacning + transport-routing real-time system scaling): the harness around live production CRMs/CMSs. The method
• Building · Metaorcha, an open runtime where one goal becomes a verified multi-agent run. Metabot, the agent on top, is in progress.
• Writing · The Harness Layer, field notes on agent harnesses, each with an artifact you can re-run.

Code behind the live ones: metaorcha · bizopsmap · commit-city
More: RP2A · ML Trend Probability · sdca-raqqr · strategy-builder-ai · notion-mcp · claude-agent · all 16 builds

• 5/5 multi-protocol runs verified live, best wall clock 13 s · Metaorcha
• 41% fewer agent steps than a fixed budget, replicated to the digit, along with the case that breaks it · field note 009
• 5.4B tokens metered over 30 days and 31k turns, 97% of them from cache · Code Desks
• 25 typed MCP tools behind a production voice-ordering agent · RP2A
• 290+ tests under a multi-tenant restaurant OS, built by a five-person team I led · Zayup
• 3 weeks to a complete React Native MVP, directing a three-developer team · DeliveryOS

The Harness Layer: field notes on agent harnesses, each with sources, its limits and an artifact you can re-run.

• When should an agent stop? · Sep 2026 · artifact
• Web chat is not a coding environment · Sep 2026
• Pacing the frontier does not watch the agents · Sep 2026
• Models converged. Trust hasn't. · Aug 2026
• I turned GitHub into a 3D city, then pressed A and saw who is really writing the code · launch post, Oct 2026

• Agents · MCP, A2A, computer use, LangGraph, LLM evaluation, Claude Code, Codex, Cursor
• Production · FastAPI, Next.js, Postgres, Supabase, pgvector, Redis, Vercel, Cloudflare Workers
• Stats · OpenTelemetry, Bayesian optimization, backtesting, KMeans and PCA
• Languages · Python, TypeScript, SQL, Bash, Solidity

Side quests used to be what you did after work. I made them the work, and made it respectable.

The method was simple: doubt every source except my own judgment, then keep retraining how I decide things, scoring each move by how much it widened my exposure to lucky breaks. Run that loop long enough and your choices converge on the handful that actually pay off, while a small share of every attempt still goes to wandering on purpose.

Where it led: companies with nobody on payroll, built one day at a time as my way out of a class that was never meant to move.

If you want a path that's genuinely yours, my one piece of advice is to defend your mind like it's production. Trends flip. Focus erodes. Someone will always be trying to slip their narrative past your filters and edit your worldview for you. Don't accept the patch.

Outlast the noise and you win.

Working on agent runtimes, protocol bridges or verification? Open an issue on Metaorcha or email me.

_{azanhyder-port.vercel.app · metaorcha.ai · dev.to · X · LinkedIn · azanhyder49@gmail.com · It's all relative.}