20202026 · Iran

Majid Asghari.

I build products and intelligent systems where product strategy, engineering, and real-world constraints meet. The portfolio below is the public record of that work.

Flagship projects4production systems
Public repos15on GitHub
Open sourceMITrouter + UEA
Phoenix2fail-closed
02 / Engineering thinking

How I think about systems.

01

Build for the real constraint

Systems are constrained by the boring parts: data quality, latency, fees, signers, deploys, recovery. The interesting parts are easy by comparison. Optimize for the boring parts first.

02

Make uncertainty explicit

If the system does not know something, the system must say so. Hiding uncertainty turns honest signals into dangerous actions.

03

Separate intelligence from authority

The component that computes opportunity must not be the component that holds the keys. Authority is granted through explicit gates, not proximity to the model.

04

Measure economic reality, not proxy metrics

Transaction count, gross spread, and modelled PnL are intermediate signals. Realized net PnL after every actual cost is the only authority.

05

Production is part of the product

Deployment, rollback, observability, and reconciliation are product capabilities. A system that cannot be safely released is not a product.

06

Prefer systems that fail safely

When uncertainty grows, authority should shrink. Fail-closed is not slow — fail-closed is fast at refusing the wrong thing.

03 / Capabilities

Product, AI, systems, engineering — applied.

Full breakdown →

Product

Strategy, discovery, marketplace mechanics, growth, monetization, experimentation, and analytics — applied to systems that have to ship.

  • Product strategy and discovery
  • Marketplace and platform products
  • Growth and monetization
  • Experimentation and ranking
  • Analytics and operator dashboards

AI / Agents

Models are not the product. Routing, harnesses, evaluation, tooling, and feedback loops are.

  • AI engineering
  • Agent architecture and operating kernels
  • Model routing and provider abstraction
  • Harnesses and tool hygiene
  • Evaluation and failure classification

Systems

Distributed systems, event-driven architecture, observability, reliability, economic controls, and pipelines.

  • Distributed systems
  • Event-driven architecture (NATS, queues)
  • Observability (Prometheus, dashboards)
  • Reliability and protected release
  • Economic controls and risk gates

Engineering

Languages and infrastructure I have shipped against. Each one earned its place on a real system.

  • Python
  • Rust
  • Go
  • TypeScript / JavaScript
  • Solidity
05 / Currently building

What I am working on right now.

The active surfaces are Phoenix (production-observation mode on Arbitrum), Smart Trader (decision intelligence on a live market), Free Best Router (v0.1.0 shipped; expanding provider coverage and scoring), and Universal Engineering Agent (reference implementation, working through profile and harness integrations).

If any of that overlaps with what you are building, I would like to hear about it.

Get in touch GitHub