<?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>Separation of Concerns on AI + Quant Engineering</title><link>https://miasyster.github.io/en/tags/separation-of-concerns/</link><description>Recent content in Separation of Concerns on AI + Quant Engineering</description><generator>Hugo</generator><language>en</language><lastBuildDate>Thu, 02 Apr 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://miasyster.github.io/en/tags/separation-of-concerns/index.xml" rel="self" type="application/rss+xml"/><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></channel></rss>