MA
AI INFRASTRUCTURE · AI SYSTEMS ENGINEERING Portfolio / 2026

MUHAMMAD ATASHI

I build the control layer around AI.

Systems that make model behavior measurable, inference economically defensible, agent authority explicit, and real-world automation safe to operate.

06control-plane systems
04applied systems
10deep case studies
EN · FA · ARproduct-language boundary

ENGINEERING POSITION

Models are probabilistic. Production systems do not get to be vague.

I design deterministic boundaries around the parts of AI systems that carry money, authority, release risk, security impact, or external claims.

The work below is organized by the question each system owns — not by framework, model vendor, or demo format.

FLAGSHIP SYSTEMS

Three systems. Three hard operating questions.

InferenceLedger decides which execution path is defensible. AgentGuard binds authorization to runtime execution. ProofDiff makes behavioral change reviewable before release.

01

Inference economics · constrained execution

InferenceLedger

Savings without acceptable quality are not savings.

An evidence-driven inference optimization and decision system that selects execution strategies under explicit cost, latency, quality, reliability, capacity, and deadline constraints.

WorkloadConstraintsCandidatesPolicyExecution
THE QUESTION
Which execution path should we use?
Inference decision economicsOpen case study
02

Runtime execution integrity · agent authorization

AgentGuard

Authorized Action == Credentialed Action == Executed Action.

A runtime execution-integrity boundary that binds deterministic authorization, least-privilege credentials, execution-time revalidation, replay protection, and terminal audit evidence.

ActionIntentAuthorizeReceiptCredentialRevalidate
THE QUESTION
Is this exact action safe to execute?
Runtime action authorization + execution integrityOpen case study
03

Behavioral regression · AI change assurance

ProofDiff

Traditional software has code diff. AI systems also need behavior diff.

A baseline-vs-candidate behavioral change-analysis system for model, prompt, retrieval, agent, tool, memory, orchestration, and decoding changes.

CorpusBaselineCandidateComparatorBehavior Diff
THE QUESTION
What changed in the behavior of my AI system, why did it change, and is it acceptable?
Behavioral change assuranceOpen case study

SYSTEMS LANDSCAPE

A portfolio designed around non-overlapping control boundaries.

Behavior, permission, routing, runtime authority, external claims, and business actions are deliberately separate concerns. The architecture becomes stronger when those boundaries stay explicit.

GOVERNED SYSTEMS

Authority, claims, and business actions — before they become incidents.

These systems keep high-impact decisions inspectable: release-time permissions, evidence-backed enterprise claims, and policy-gated support actions.

APPLIED / INDUSTRY SYSTEMS

The same engineering discipline under product constraints.

Durable background work, multilingual product behavior, heterogeneous evidence, and stateful monitoring — with real interfaces instead of architecture-only diagrams.

Client / company system · end-to-end AI content operations

Content Automation Pipeline

A production-oriented multi-stage content operations platform coordinating research, context retrieval, planning, generation, quality control, SEO, review, publishing, and operational monitoring across AI providers.

Next.js · FastAPI · Celery · PostgreSQLOpen case study ↗

Anonymized commercial system · governed multi-channel conversational commerce

Persian Conversational Commerce

Persian-first governed conversational commerce: persona-driven consultative selling with grounded product truth, safety-before-sales enforcement, bounded commercial relationships, recent-turn context, and multi-channel delivery across web widget, Telegram, and Instagram DM.

Python · FastAPI · Redis · RAGOpen case study ↗

Evidence-grounded analysis · multi-format ingestion

Universal AI Analyzer

Domain-neutral multi-format analysis with deterministic profiling, hierarchical source-grounded synthesis, strict source/chunk validation, and adaptive Telegram reporting.

Python · Pydantic · LLMs · AsyncIOOpen case study ↗

Automation · state reconciliation

Centris Property Monitoring

Scheduled listing discovery, pagination coverage, persisted state reconciliation, detail validation, and controlled Telegram notification for a real-estate monitoring workflow.

n8n · REST · Google Sheets · TelegramOpen case study ↗

RESEARCH ↔ ENGINEERING

Questions become systems that can fail a test.

CONTACT

Building infrastructure for AI systems that have to survive contact with reality.