<?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>Architecture on AI + Quant Engineering</title><link>https://miasyster.github.io/en/tags/architecture/</link><description>Recent content in Architecture on AI + Quant Engineering</description><generator>Hugo</generator><language>en</language><lastBuildDate>Fri, 08 May 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://miasyster.github.io/en/tags/architecture/index.xml" rel="self" type="application/rss+xml"/><item><title>Cross-Model Review Is Architecture, Not Heuristic</title><link>https://miasyster.github.io/en/posts/cross-model-review-is-architecture/</link><pubDate>Fri, 08 May 2026 00:00:00 +0000</pubDate><guid>https://miasyster.github.io/en/posts/cross-model-review-is-architecture/</guid><description>Single-LLM self-reflection has a structural blind spot — the model tends to confirm its own output. QuantGPT enforces a hard rule in factor-mine SKILL Phase 0.5: Claude must consult DeepSeek before designing a new factor family. Not a suggestion, a hard rule. This isn&amp;rsquo;t redundancy — it&amp;rsquo;s the antidote to structural bias.</description></item><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>Why I Build Agent Infrastructure, Not Agents</title><link>https://miasyster.github.io/en/posts/why-agent-infra-not-agent/</link><pubDate>Fri, 01 May 2026 00:00:00 +0000</pubDate><guid>https://miasyster.github.io/en/posts/why-agent-infra-not-agent/</guid><description>While everyone is building Agent frameworks, I chose a different path: build infrastructure for Agents, not the Agent itself. Not because I can&amp;rsquo;t build Agents, but because the Agent layer is a consumable — infrastructure is an asset.</description></item><item><title>Skill Orchestration > Agent Loop Chains: Why Dumb Pipelines + Smart Tools Beat Smart Pipelines + Dumb Tools</title><link>https://miasyster.github.io/en/posts/skill-orchestration-over-agent-loops/</link><pubDate>Thu, 30 Apr 2026 00:00:00 +0000</pubDate><guid>https://miasyster.github.io/en/posts/skill-orchestration-over-agent-loops/</guid><description>Current AI Agent frameworks obsess over building complex loop chains: Planner → Executor → Reflector → Re-planner. I chose the opposite: tools are stateless pure functions, and the LLM decides the call sequence itself. Not because loop chains aren&amp;rsquo;t cool — but because they put decision authority in the wrong place.</description></item><item><title>The Expression Parser Is a Compiler, Not eval()</title><link>https://miasyster.github.io/en/posts/expression-parser-is-a-compiler/</link><pubDate>Wed, 29 Apr 2026 00:00:00 +0000</pubDate><guid>https://miasyster.github.io/en/posts/expression-parser-is-a-compiler/</guid><description>QuantGPT&amp;rsquo;s core is an 870+ line hand-written recursive descent parser supporting 80+ operators, automatic cross-sectional/time-series grouping, and dual-mode compilation. Not because I didn&amp;rsquo;t know eval() is simpler — but because what eval() can&amp;rsquo;t do happens to be what matters most.</description></item><item><title>API Guard Pattern: Why Calling Functions Directly Is Forbidden</title><link>https://miasyster.github.io/en/posts/api-guard-pattern/</link><pubDate>Tue, 28 Apr 2026 00:00:00 +0000</pubDate><guid>https://miasyster.github.io/en/posts/api-guard-pattern/</guid><description>QuantGPT uses threading.local to enforce a runtime guard: all backtest calls must go through the API boundary. Direct function calls raise an exception. Not because the function is dangerous — but because a system without boundaries can&amp;rsquo;t be audited.</description></item><item><title>Anti-Overfit Is Architecture, Not a Plugin</title><link>https://miasyster.github.io/en/posts/anti-overfit-is-architecture/</link><pubDate>Mon, 27 Apr 2026 00:00:00 +0000</pubDate><guid>https://miasyster.github.io/en/posts/anti-overfit-is-architecture/</guid><description>Most backtest systems treat anti-overfit as an optional add-on check — run the backtest, then test for overfitting if you feel like it. QuantGPT builds it into the scoring system and evolution engine: anti-overfit results directly affect factor scores, and the evolution engine reads anti-overfit metrics to decide its next strategy. Factors that haven&amp;rsquo;t proven robustness don&amp;rsquo;t even qualify for iteration.</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><item><title>Why I Didn't Use Multi-Agent Architecture for My Quant Research System</title><link>https://miasyster.github.io/en/posts/why-not-multi-agent/</link><pubDate>Thu, 02 Apr 2026 00:00:00 +0000</pubDate><guid>https://miasyster.github.io/en/posts/why-not-multi-agent/</guid><description>Multi-agent is the hot paradigm in AI engineering. I chose single agent + state machine for my AI-driven quant research system. Not because multi-agent is too hard, but because the problem structure doesn&amp;rsquo;t match.</description></item></channel></rss>