<?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>Auditability on AI + Quant Engineering</title><link>https://miasyster.github.io/en/tags/auditability/</link><description>Recent content in Auditability 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/auditability/index.xml" rel="self" type="application/rss+xml"/><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>