Simor
Data Infrastructure for Production AI
Practical writing on AI data engineering, feature stores, and the infrastructure choices that determine whether AI systems work in production.
Input guardrails check whether a user prompt is safe. Output guardrails check whether a model response is appropriate. Agent guardrails check whether the actions an agent takes are within bounds. Thes
Machine learning teams face a version control problem that Git does not solve. Git tracks code changes, but ML experiments change more than code — they change hyperparameters, datasets, model architec
Single-agent systems have predictable failure modes. The agent calls a tool, the tool fails, the agent receives an error and decides what to do next. The failure is contained to the single agent's con
The Model Context Protocol gives AI agents a standardized way to discover and invoke external tools. In development, MCP works well with a local server running on localhost and a handful of tools. The
A healthcare analytics company received notice on a Tuesday afternoon that their primary AI infrastructure vendor was filing for Chapter 7 bankruptcy. The platform hosted their patient risk stratifica
Traditional application observability focuses on three signals: request latency, error rates, and resource utilization. If the request returns a 200 in under two hundred milliseconds, the system is he
A critical open-source library used by thousands of companies, including several Fortune 500 firms, is maintained by one person in their spare time. This is not a hypothetical. It is a description of
When an AI agent can call external tools, the security boundary shifts from the model to the tool layer. The model generates a request to call a tool. The tool executes against real systems — reading
The guardrail problem in AI is a tension between two failure modes. Too few guardrails and the system produces harmful, inaccurate, or brand-damaging outputs. Too many guardrails and the system refuse