<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Kubernetes on oceanheart.ai</title>
    <link>https://www.oceanheart.ai/tags/kubernetes/</link>
    <description>Recent content in Kubernetes on oceanheart.ai</description>
    <generator>Hugo</generator>
    <language>en-gb</language>
    <lastBuildDate>Fri, 10 Apr 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://www.oceanheart.ai/tags/kubernetes/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Halo</title>
      <link>https://www.oceanheart.ai/projects/halo/</link>
      <pubDate>Fri, 10 Apr 2026 00:00:00 +0000</pubDate>
      <guid>https://www.oceanheart.ai/projects/halo/</guid>
      <description>&lt;h2 id=&#34;what-it-is&#34;&gt;What it is&lt;/h2&gt;&#xA;&lt;p&gt;A personal engineering tool layer. Halo is a set of small CLI modules, work tracking, memory, briefing synthesis, email triage, journaling, agent orchestration, each with an explicit command surface and its own isolated store. The design rule is that a human and an agent reach for the same tool the same way: there is no separate &amp;ldquo;agent API&amp;rdquo; bolted on after the fact, because the CLI &lt;em&gt;is&lt;/em&gt; the API.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
