<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"><channel><title>The Comm Layer</title><description>I write about AI communications and fraud at the platform layer. A decade on both sides of the comms API: American Express, Twilio, now Microsoft. The hard problems are about accountability and architecture, not better models. Views my own.</description><link>https://www.archanakumari.fyi/</link><item><title>Why a 94.7%-accurate smish classifier is a false-positive machine in production</title><link>https://www.archanakumari.fyi/blog/article_precision_vs_prevalence/</link><guid isPermaLink="true">https://www.archanakumari.fyi/blog/article_precision_vs_prevalence/</guid><description>Same model. Two prevalence assumptions. ~75 percentage points of precision difference. This is why public-benchmark accuracy does not transfer to fraud production</description><pubDate>Sat, 30 May 2026 00:00:00 GMT</pubDate></item><item><title>Friction Debt</title><link>https://www.archanakumari.fyi/blog/friction-debt/</link><guid isPermaLink="true">https://www.archanakumari.fyi/blog/friction-debt/</guid><description>Friction debt is the cost a platform accumulates every time it makes it easier for users to do actions at scale</description><pubDate>Sun, 17 May 2026 00:00:00 GMT</pubDate></item><item><title>The Eval You Run When the Clock Is Running</title><link>https://www.archanakumari.fyi/blog/post1_lightweight_eval/</link><guid isPermaLink="true">https://www.archanakumari.fyi/blog/post1_lightweight_eval/</guid><description>Most writing about evaluation assumes you have time. It assumes a held-out dataset, a labeling panel, a power analysis, weeks of iteration. That assumption is fine for shipping decisions. It is useless during an active attack</description><pubDate>Mon, 25 May 2026 00:00:00 GMT</pubDate></item><item><title>The Eval That Decides Whether You Ship</title><link>https://www.archanakumari.fyi/blog/post2_heavy_eval/</link><guid isPermaLink="true">https://www.archanakumari.fyi/blog/post2_heavy_eval/</guid><description>The companion to this post described the lightweight evaluation: the one you run under a clock, when a campaign is active and a response ships in hours. This post describes the other instrument. The heavy evaluation is what gates a model release. It is slow, deliberate, and expensive, and those properties are features rather than defects.</description><pubDate>Wed, 27 May 2026 00:00:00 GMT</pubDate></item><item><title>Rules Are the Bones, Models Are the Muscle</title><link>https://www.archanakumari.fyi/blog/post3_rules_vs_ml/</link><guid isPermaLink="true">https://www.archanakumari.fyi/blog/post3_rules_vs_ml/</guid><description>This is the third post in a short series on evaluating fraud detection. The first covered the lightweight evaluation you run during an active campaign. The second covered the heavy evaluation that gates a model release. This one steps back to a question that comes up every time someone reviews a detection system for the first time.</description><pubDate>Sat, 30 May 2026 00:00:00 GMT</pubDate></item></channel></rss>