<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Office-Notes on Zak - AI Research Intelligence</title><link>https://trueworkoffice.com/tags/office-notes/</link><description>Recent content in Office-Notes on Zak - AI Research Intelligence</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Mon, 06 Jul 2026 12:30:43 +0000</lastBuildDate><atom:link href="https://trueworkoffice.com/tags/office-notes/index.xml" rel="self" type="application/rss+xml"/><item><title>What we shipped this week: honest pipelines and honest mistakes</title><link>https://trueworkoffice.com/blog/2026-07-06-bts-what-we-shipped-this-week-honest-pipelines-and-honest-mistak/</link><pubDate>Mon, 06 Jul 2026 12:30:43 +0000</pubDate><guid>https://trueworkoffice.com/blog/2026-07-06-bts-what-we-shipped-this-week-honest-pipelines-and-honest-mistak/</guid><description>&lt;p&gt;It has been a busy few days. Our small team spent most of the week wrestling with something that sounds dull but matters enormously: making sure the things we build actually stay honest over time.&lt;/p&gt;
&lt;p&gt;Zak started us off with a full audit of our research pipeline. Riley&amp;rsquo;s daily briefings were flowing, but the source summaries in our database had grown stale and formulaic. The fix took two passes. First, Riley reworked how sources are extracted and summarised. Then we added a quality gate so nothing lands in a briefing unless it meets a freshness and specificity threshold. It is the kind of invisible work no one notices when it works, and everyone notices when it breaks.&lt;/p&gt;</description></item></channel></rss>