// About — Mohamed Saadi
Closing the Gap Between
Research and Production.
AI initiatives rarely stall because the research is wrong. They stall because the distance between a demonstrated capability and a production-grade, observable, economically viable system is structural — and almost always underestimated. That distance is the work.
The method has not changed across a decade: identify which research advances will hold under production constraints, understand them at the mathematical level, then build the architecture and the engineering practices that make them operable by teams who were not hired to run AI platforms.
Three paradigm shifts, three times arriving before the market had a standard playbook.
"The scarce competence in applied AI is not knowledge of the research. It is judgment about which research survives contact with production — and the architecture to make it survive."
01 / Enterprise Impact
Internal developer platform and AI/ML platform · OpenShift + AWS · 100+ daily jobs · 10+ teams
From months of bespoke infrastructure per business application to days of configuration on a shared platform. An organizational transformation metric, not an engineering throughput metric — it changed what data teams could credibly commit to.
FinOps governance across the platform estate: right-sized spot capacity for training, reserved capacity for inference, automated idle reclamation, and per-team attribution surfaced alongside latency and error rate.
Sustained across 100+ daily training jobs and production inference services. Multi-zone deployment, automated failover, alerting with defined thresholds on every critical path — including consumer lag, which is where silent failure accumulates.
Median resolution from four hours at platform launch to under ninety minutes. Runbook automation, span-level tracing, and drift alerting cross-correlated with upstream pipeline health.
02 / On Environments
On Environment Transferability.
A career with significant depth in one industrial group raises a legitimate question about transferability. The answer lies in the constraint profile rather than the logo.
A large regulated utility is not one environment. It is three operating simultaneously: a compliance-bound institution where auditability precedes velocity, a legacy integration surface where core systems are immovable and must be surrounded rather than replaced, and an internal startup building a capability that did not previously exist inside an organization of 150,000 people. Most difficult enterprise AI deployments are a subset of that combination.
Greenfield conditions are covered separately. Independent product architecture — zero budget, no inherited team, no existing infrastructure, every decision owned end to end — is as distant from a regulated industrial context as environments get. Pharmaceutical supply chain work under GxP-adjacent validation requirements provided a third culture again: the engineering principles transferred, the execution model was rebuilt entirely.
03 / A Pattern, Repeated Three Times
Three Technology Transitions, Delivered Early.
Research signal: Distributed computing, columnar storage, stream processing
Enterprise data platform with reusable components and near real-time serving, delivered while Big Data remained exotic in French industrial groups.
Research signal: Reproducible pipelines, feature stores, model governance, platform engineering
Cloud-native IDP replacing a shadow IT estate. Delivery lead time ÷9. Governance restructured as a service after a prescriptive first attempt stalled adoption.
Research signal: Multi-agent coordination, retrieval engineering, evaluation science, neuro-symbolic reasoning
Evaluation harnesses as infrastructure, deterministic agent orchestration, hybrid retrieval with reranking, inference economics, regulatory alignment under the EU AI Act.
04 / On the 2016 Research
Why the Research Background Matters.
The LIP6 work on distributed multi-agent negotiation appears here for one reason: it provides a strong theoretical foundation for designing modern autonomous and multi-agent systems.
Assessing an agentic orchestration design reduces to the same questions posed of negotiating agents in 2016. What is the communication protocol and is it typed? How is partial state reconciled across agent boundaries? What are the failure modes when an agent receives contradictory signals from concurrent tool calls? How does the system recover from a mid-execution fault without full replay? What bounds termination?
That grounding is what separates a framework that demonstrates well from one that holds under production load. The compute changed by orders of magnitude. The formal questions are unchanged.
2016 · École Nationale Polytechnique × LIP6 / CNRS Paris
A Multi-Agent Negotiation Approach for Supply Chain Management
188 pages · JADE · Nash Bargaining · Coalition Formation · AUML
05 / Trajectory
-
2015–16
Research — Distributed Multi-Agent Systems
LIP6 / CNRS Paris. Autonomous agents negotiating under incomplete information. Nash bargaining, coalition formation, belief revision. The coordination primitives contemporary agentic frameworks now implement.
-
2017
ML Engineering — Regulated Supply Chain
Sanofi. Demand forecasting across a pharmaceutical distribution network. 8% stock reduction with no service degradation. First demonstration that adoption process, not model quality, is the binding constraint in regulated environments.
-
2017–19
Wave I — Enterprise Data Platform
EDF. Reusable platform components across 10+ production pipelines. Near real-time Customer 360 on Spark, HBase, Phoenix, Elasticsearch — consuming immovable upstream systems without modifying them.
-
2019–21
Wave II — Cloud Native IDP & MLOps
EDF via NeoStair. Internal developer platform on OpenShift replacing a fragmented shadow IT estate. 20+ applications, 20+ developers, 100+ daily workflows. Delivery lead time reduced by a factor of nine.
-
2021–Now
Wave III — GenAI & Agentic Architecture
EDF Group. Platform governance for 10+ teams under generative technology velocity. Evaluation harnesses, agentic state machines, retrieval engineering, inference economics, EU AI Act alignment.
06 / Architecture Positions
Opinions Formed Under Production Load.
A tool inventory demonstrates nothing. What follows are architectural positions where the correct answer was not obvious, and the reasoning that resolved them.
Deterministic state machines over free-form LLM routing
Agent reliability is a property of the harness, not the model.
Framework abstractions that hide the state machine feel elegant until an agent hallucinates a tool signature or loops silently against a token budget. An explicit graph makes every transition typed, observable, and restartable from checkpoint. Termination criteria and step budgets are architectural requirements, not tuning parameters. The trade is developer ergonomics for operational resilience — in production that exchange is never close.
Evaluation harness as infrastructure, not as a gate
Unobservable systems are unoperable. Non-determinism does not exempt.
Classical accuracy metrics do not transfer to generative systems, and distribution shift arrives as semantic drift rather than statistical drift. The functioning pattern: golden datasets versioned alongside prompts, regression suites in CI on every prompt or model change, LLM-as-judge calibrated against human annotation with inter-rater agreement tracked to catch judge drift. Retrieval quality measured separately from generation quality — conflating the two hides which stage actually failed.
Hybrid retrieval and reranking over naive vector search
Reference RAG implementations do not survive adversarial corpora.
Dense embeddings alone underperform on corpora where documents are lexically near-identical but semantically distinct — regulatory text being the canonical case. Hybrid retrieval reconciling BM25 with dense vectors through reciprocal rank fusion, followed by cross-encoder reranking on the candidate set, recovers the precision that pure vector search discards. Chunking strategy is determined empirically per corpus; assumed fixed windows are a reliable source of silent quality loss.
Cost per resolved task over cost per token
Token-level accounting reports regressions as improvements.
An architecture that halves token consumption while doubling retry rates will appear as a 50% cost win under per-token measurement. The correct unit is cost per successfully resolved task. Model routing and cascades handle the tractable majority on smaller models with escalation reserved for genuine complexity; semantic caching absorbs high-repetition query classes. Cost attribution belongs in the same observability plane as latency and error rate, not in a separate finance report.
Selective feature store adoption
Feature stores earn their operational cost in roughly 40% of cases.
Feature stores solve training-serving skew, a real and expensive problem, at the price of substantial operational overhead. The break-even sits at sub-hour refresh cycles combined with genuine cross-team feature reuse. Below that threshold, versioned feature pipelines with enforced schema contracts are simpler, cheaper, and materially more debuggable.
07 / Technical Reference
Production surface area. Depth varies by domain — the boundary between "operated at scale" and "evaluated and rejected" is available on request for any entry.
Agentic Systems
Generative AI Engineering
LLMOps & Evaluation
MLOps
Cloud Native & Platform
Governance & Observability
08 / Current
NeoStair EURL
Independent Architecture Practice
Senior architecture engagements for enterprise AI platforms. Current mandate: GenAI platform governance, agentic system design, and LLMOps at an industrial group operating under regulated constraints.
SeriesMind — early stage
Agentic Time Series Intelligence
Specialized autonomous agents under deterministic orchestration with human-in-the-loop checkpoints, conformal prediction for distribution-free confidence intervals, and an evaluation harness treated as primary infrastructure. The architectural positions above, implemented without inherited constraints.
09 / Beyond the Screen
The Athlete
Former professional handball player. Cycling as sustained commitment — the Tour de France routes ridden across Europe each year, stage by stage. Hyrox competition through the winters.
The Mind
Iyengar Yoga, the school of structural precision. Alongside sustained interest in neuroscience, cognitive science, and contemplative traditions.
The Listener
Cosmic jazz — Ibrahim Maalouf, Dhafer Youssef, Avishai Cohen. Structured improvisation and the discipline of constraint.
The Aesthetic
Brutalism and neo-brutalist architecture. Structures that expose their logic and carry their weight without ornament.
Available for senior engagements
AI Platform Architecture · Agentic Systems · LLMOps · MLOps · Cloud Native
Paris region & remote · Minimum six months · via NeoStair EURL
Get in touch