Design the failure state
Timeouts, retries, stale approvals, partial effects, and unknown outcomes belong in the architecture from the beginning.
Muhammad Atashi
Working thesis
The model can propose. The system still has to decide what may be trusted, released, or executed.
I work where capable models become operational software: LLM serving and inference decisions, agent authorization, behavioral release assurance, retrieval and orchestration, and durable business workflows.
The recurring engineering problem is the same: make behavior observable, authority explicit, decisions reproducible, and failure states recoverable without pretending uncertainty disappeared.
LLM systems & inference infrastructure
AI agent security & execution integrity
Behavioral evaluation & release assurance
Governed AI operations
WHY THIS WORK
I trust precise uncertainty more than polished confidence. An inconclusive result is often more useful than a dashboard showing everything in green, because it makes the limits of what is known visible.
That principle guides how I build and evaluate systems, from model migrations and agent actions to release decisions, publishing workflows, selling assistants, and monitoring tools. I keep asking the same questions: What was authorized? What did we observe? What changed? What is still not established?
I would rather ship a focused system with clear limits than a broad system that makes claims it cannot support. For me, good engineering means testable claims, understandable refusals, traceable effects, and clear responsibilities.
Engineering principles
Three constraints I keep carrying from one system into the next.
Timeouts, retries, stale approvals, partial effects, and unknown outcomes belong in the architecture from the beginning.
Models may interpret and propose; deterministic policy and review boundaries decide what is allowed to change the outside world.
A preferred optimization or release decision must be able to lose when the evidence does not support it.
Jun 2024 – Mar 2026
Built governed conversational commerce across Instagram DMs and Telegram, LangGraph workflows, and an editorial-bound content publishing pipeline.
Apr 2022 – Mar 2024
Cut p95 serving latency from 850 ms to under 200 ms on the vLLM inference stack (PagedAttention, dynamic batching), with Redis semantic caching and Celery/Kafka pipelines.
May 2021 – Feb 2022
Built ML/NLP evaluation pipelines; a prompt-engineering program lifted task accuracy by 15%.
Evidence, authority, failure handling.
mohammadaliatashi@icloud.com ↗