<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Ulyssify Blog</title>
    <link>https://ulyssify.com/blog</link>
    <description>Notes from Ulyssify on building a commitment device, governing an AI coding fleet, and reclaiming focus.</description>
    <language>en</language>
    <atom:link href="https://ulyssify.com/blog/feed.xml" rel="self" type="application/rss+xml"/>
    <item>
      <title>The Assistant Could Not Have Known</title>
      <link>https://ulyssify.com/blog/assistant-could-not-have-known</link>
      <guid isPermaLink="true">https://ulyssify.com/blog/assistant-could-not-have-known</guid>
      <description>Our in-app AI confidently told us a website was blocked. It was not. The fix was not a smarter model: it was two lost facts and one property we would defend hardest.</description>
      <pubDate>Thu, 20 Aug 2026 00:00:00 GMT</pubDate>
    </item>
    <item>
      <title>Enforce, don&#39;t instruct: governing an AI coding fleet</title>
      <link>https://ulyssify.com/blog/enforce-dont-instruct</link>
      <guid isPermaLink="true">https://ulyssify.com/blog/enforce-dont-instruct</guid>
      <description>We build Ulyssify with a fleet of AI coding agents. Here is how we give them judgment about which decisions are theirs, and why we put the ones that matter behind mechanisms instead of words.</description>
      <pubDate>Sat, 15 Aug 2026 00:00:00 GMT</pubDate>
    </item>
  </channel>
</rss>
