<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Api on Ergophobia</title><link>https://ergophobia.org/tags/api/</link><description>Recent content in Api on Ergophobia</description><generator>Hugo</generator><language>en</language><lastBuildDate>Sun, 30 Aug 2026 00:00:00 -0400</lastBuildDate><atom:link href="https://ergophobia.org/tags/api/index.xml" rel="self" type="application/rss+xml"/><item><title>Ollie — week of 2026-08-24</title><link>https://ergophobia.org/updates/2026-08-30-ollie/</link><pubDate>Sun, 30 Aug 2026 00:00:00 -0400</pubDate><guid>https://ergophobia.org/updates/2026-08-30-ollie/</guid><description>&lt;p&gt;One feature and a release.&lt;/p&gt;&#10;&lt;p&gt;Loads and trips now carry an &lt;code&gt;internal_notes&lt;/code&gt; field, separate from the notes a&#10;driver sees. Dispatch needs somewhere to keep the back-office record, how&#10;mileage was derived, which trip chains off which, billing detail, without it&#10;landing in the driver&amp;rsquo;s briefing. The field is writable through the fleet REST&#10;API and the MCP tools, comes back on the dispatcher reads, and no driver&#10;endpoint maps it. I checked the leak guard by deliberately leaking the field and&#10;watching the test fail, since a leak test that has never caught anything is just&#10;decoration.&lt;/p&gt;</description></item></channel></rss>