<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/"><channel><title>System Design on AI + Quant Engineering</title><link>https://miasyster.github.io/en/tags/system-design/</link><description>Recent content in System Design on AI + Quant Engineering</description><generator>Hugo</generator><language>en</language><lastBuildDate>Fri, 01 May 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://miasyster.github.io/en/tags/system-design/index.xml" rel="self" type="application/rss+xml"/><item><title>Agent-Native Architecture: Designing Systems for Agents, Not Humans</title><link>https://miasyster.github.io/en/posts/agent-native-architecture/</link><pubDate>Fri, 01 May 2026 00:00:00 +0000</pubDate><guid>https://miasyster.github.io/en/posts/agent-native-architecture/</guid><description>When the system operator changes from a human to an LLM Agent, design principles need fundamental rethinking. Humans need GUIs and documentation. Agents need semantically clear tools and constraints that throw errors.</description></item><item><title>If Research Isn't Reproducible, It Isn't Research</title><link>https://miasyster.github.io/en/posts/atomic-versioning/</link><pubDate>Fri, 03 Apr 2026 00:00:00 +0000</pubDate><guid>https://miasyster.github.io/en/posts/atomic-versioning/</guid><description>The most common lie in ML research is &amp;rsquo;the results looked great last time.&amp;rsquo; What code was used last time? What data version? What parameters? Nobody can say. I used filesystem transactions (temp directory → atomic rename) to create immutable snapshots of every iteration, turning &amp;rsquo;last time&amp;rsquo;s results&amp;rsquo; from a memory into a queryable fact.</description></item><item><title>Let AI's Code Run — But Don't Let It Run Away</title><link>https://miasyster.github.io/en/posts/sandbox-defense-in-depth/</link><pubDate>Fri, 03 Apr 2026 00:00:00 +0000</pubDate><guid>https://miasyster.github.io/en/posts/sandbox-defense-in-depth/</guid><description>AI-generated code must be executed — otherwise it&amp;rsquo;s just text. But execution means risk. I didn&amp;rsquo;t choose container isolation or RestrictedPython. Instead I designed a three-layer defense: reject dangerous structures at compile time via AST, replace the entire builtins at runtime, and enforce OS-level resource limits as a backstop. Each layer handles a different class of risk. Overlapping but not redundant.</description></item><item><title>Why I Didn't Use LangChain — The Design Logic Behind a Custom FSM Orchestration Engine</title><link>https://miasyster.github.io/en/posts/why-i-built-my-own-fsm-engine/</link><pubDate>Fri, 03 Apr 2026 00:00:00 +0000</pubDate><guid>https://miasyster.github.io/en/posts/why-i-built-my-own-fsm-engine/</guid><description>LangChain, LangGraph, CrewAI, PydanticAI — no shortage of AI orchestration frameworks. I evaluated all of them and built my own. Not NIH syndrome. When you need failure-mode-driven mutation strategies, phase-aware multi-model routing with different temperatures, and adaptive evolution based on trajectory analysis, the abstraction layers of general-purpose frameworks become obstacles to route around.</description></item><item><title>AI as Operator, Kernel as Law — Why AI Shouldn't Have Architectural Authority</title><link>https://miasyster.github.io/en/posts/ai-as-operator/</link><pubDate>Thu, 02 Apr 2026 00:00:00 +0000</pubDate><guid>https://miasyster.github.io/en/posts/ai-as-operator/</guid><description>Letting AI drive research workflows doesn&amp;rsquo;t mean letting AI decide how the system runs. I made a key separation: AI is just the operator, the execution engine is the law. This decision came from a failure.</description></item><item><title>Endgame Thinking: Design for the Audit Before You Design the Feature</title><link>https://miasyster.github.io/en/posts/design-for-the-endgame/</link><pubDate>Thu, 02 Apr 2026 00:00:00 +0000</pubDate><guid>https://miasyster.github.io/en/posts/design-for-the-endgame/</guid><description>Most systems are designed to run first, then audited as an afterthought. I inverted the order — first define what questions the system must answer when things go wrong, then work backwards to what each layer must record. This inversion reshaped the entire architecture.</description></item></channel></rss>