Skip to content
View azank1's full-sized avatar
🧠
🧠

Organizations

@delivery-app-us

Block or report azank1

Block user

Prevent this user from interacting with your repositories and sending you notifications. Learn more about blocking users.

You must be logged in to block users.

Content in all repositories owned by your account will be closed.
Maximum 250 characters. Please don’t include any personal information such as legal names or email addresses. Markdown is supported. This note will only be visible to you.
Report abuse

Contact GitHub support about this user’s behavior. Learn more about reporting abuse.

Report abuse
azank1/README.md

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

Portfolio Metaorcha dev.to X Email

Now

  • Production · CRM DevOps and AI engineering (conveyancing + 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.

Repos, most involved first

01 Metaorcha. Live, open source, Apache 2.0. One goal in, a verified multi-agent run out, across MCP, A2A and computer use. Every run leaves a signed receipt that verifies offline. 02 seamkit. On npm, open source, Apache 2.0. Deterministic production checks for code mostly written by agents: verdicts read back from what is live, with no model inside. Proven on real deploys. 03 agent-check. v1.1.0, open source, MIT. Flags the risky agent setup a repo ships to every clone, and the CI agents that issue or PR text from outsiders can drive. One line in a workflow. 04 guardrails-kit. Open source, MIT. Fail-closed Claude Code hooks for team repos: no pushes to main, no destructive commands, no secrets written or read. Input it cannot parse is blocked. 05 CDV. Open source research preview. An agent never grades its own work: a deterministic floor and an LLM critic score each step, the stricter wins, and a Bayesian loop decides when to stop. 06 Code Desks. Open source, MIT. Run an office of AI coding sessions from your terminal: named desks, gated handoffs, and a meter that reads what each desk really used.

More: commit-city · bizopsmap · RP2A · ML Trend Probability · sdca-raqqr · strategy-builder-ai · notion-mcp · claude-agent

Measured

  • 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

Recent public activity

date where what outcome
Oct 31 agent-check v1.1.0: now flags comment-triggered checkouts, and documents a fix for every finding released
Oct 31 guardrails-kit fail-closed Claude Code hooks for team repos, with tests released
Oct 19 tmux #5775 ^ matched again mid-string in format substitutions, since 2019 applied upstream 10 h later, regress test credited
Oct 18 blackbox_exporter #1715 target URLs percent-decoded twice since 0.29.0 open, awaiting review
Oct 16 huggingface_hub #5180 hf skills add --force replaced a skill with a symlink to itself fixed in-house in v2.3.0, report credited
Oct 15 ECC #3591 SessionStart hook crashed in every project on plugin installs merged Oct 29; on Windows 0/27 → 26/27 hooks passing
Oct 15 vercel-plugin #343 session-start context overran Claude Code's hook output cap open; a Vercel engineer extended it on the branch
Oct 15 BMAD-METHOD #3094 update drops the config of a module kept without a source open issue

What the feedback taught:

  • A minimal reproduction with a regression test gets applied as written. Without one, maintainers rewrite the fix in-house, which is fine when the credit stays.
  • Big projects merge in batches. ECC took two weeks; meanwhile an outside contributor verified the fix independently, which helped it land.
  • When a maintainer pushes to your branch, follow their direction. The Vercel change grew from a trim into splitting the context into parts under the cap.
  • Severity should follow what the job can actually do, not the pattern it matches. agent-check grades that way.

Writing

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

Stack

  • Agents · MCP, A2A, computer use, LangGraph, LLM evaluation, Claude Code, Codex, Cursor
  • Agent security · Claude Code hooks and permissions, MCP config review, GitHub Actions agent jobs
  • 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

Activity

GitHub streak stats for azank1: total contributions, current streak and longest streak

On carving your own path

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.

Pinned Loading

  1. solvent-labs-org/metaorcha solvent-labs-org/metaorcha Public

    multi model capable single harness orchestrator. Apache 2.0 runtime for multi-protocol agent orchestration: one goal in, a verified multi-agent run out across MCP, A2A, and Computer-Use and whateve…

    Python 5 4

  2. commit-city commit-city Public template

    Your GitHub, as a living 3D city. Swap github.com → commit.city on any user, org or repo and watch a year of commits build it.

    HTML 4

  3. cdv cdv Public

    Conservative Dual-Verify — judging AI agent work with a deterministic floor + LLM critic (stricter score wins) and Bayesian stopping. Research preview, frozen at v1.0.1; active development continue…

    Python 4

  4. ML-ProbabalisticTrend ML-ProbabalisticTrend Public

    Machine Learning Trend Probability Indicator - azank1

    Python 4

  5. zk2p zk2p Public

    ZK-proof settlement research prototype — trust-minimized P2P exchange using zero-knowledge proofs and DKIM-verified attestations. Research/PoC.

    TypeScript

  6. quant-pm quant-pm Public

    A pip-installable CLI + library that uses PERT analysis, Gantt scheduling, and multi-developer workload modeling to produce monthly payout breakdowns, timeline projections, and both static (PNG/Exc…