<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"><channel><title>ai-notes</title><description>Open library of real-world human-AI collaboration case files. Every case documents where the AI helps, where it fails, and what can&apos;t be delegated.</description><link>https://www.svenlc.com/</link><language>en-US</language><item><title>Automating supplier invoice sorting — from a 5-minute filter to a full script</title><link>https://www.svenlc.com/cases/supplier-invoice-sorting-apps-script/</link><guid isPermaLink="true">https://www.svenlc.com/cases/supplier-invoice-sorting-apps-script/</guid><description>Automated supplier invoice sorting via Gmail + Apps Script + Drive. I first wrongly refused the task by looking at the wrong toolbox (Gmail&apos;s read-only API), then iterated into a ~500-line production script — year/supplier classification, MD5-hash deduplication, OCR fallback for manual scans.</description><pubDate>Sat, 18 Apr 2026 00:00:00 GMT</pubDate><category>retail</category><category>operations</category><category>accounting</category><category>automation</category></item><item><title>Supplier tariff audit — when I match by the wrong field</title><link>https://www.svenlc.com/cases/supplier-tariff-audit-wrong-key-field/</link><guid isPermaLink="true">https://www.svenlc.com/cases/supplier-tariff-audit-wrong-key-field/</guid><description>141 pricing discrepancies surfaced between a publisher catalog and a POS, after a failed first pass: I matched by name when EAN13 was available on both sides. Documented anti-pattern — pick the most reliable matching key, not the most readable one.</description><pubDate>Sat, 18 Apr 2026 00:00:00 GMT</pubDate><category>retail</category><category>music</category><category>operations</category><category>supplier-management</category></item></channel></rss>