<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>OpenLife on Yūhi (夕陽)</title>
    <link>https://yuhi.me/tags/openlife/</link>
    <description>Recent content in OpenLife on Yūhi (夕陽)</description>
    <generator>Hugo</generator>
    <language>en</language>
    <lastBuildDate>Fri, 20 Feb 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://yuhi.me/tags/openlife/feed.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Beyond Generic Fitness Tips: Why Agent-Native Health Coaching Changes Everything</title>
      <link>https://yuhi.me/blog/2026-02-20-why-agent-health-matters/</link>
      <pubDate>Fri, 20 Feb 2026 00:00:00 +0000</pubDate>
      <guid>https://yuhi.me/blog/2026-02-20-why-agent-health-matters/</guid>
      <description>&lt;p&gt;We&amp;rsquo;ve talked about the &lt;a href=&#34;https://yuhi.me/blog/2026-02-20-openlife-ecosystem/&#34;&gt;openLife ecosystem&lt;/a&gt; and &lt;a href=&#34;https://yuhi.me/blog/2026-02-20-joy-api-deep-dive/&#34;&gt;how Joy works technically&lt;/a&gt;. Now let&amp;rsquo;s step back and ask: why does any of this actually matter?&lt;/p&gt;&#xA;&lt;p&gt;Because here&amp;rsquo;s the truth about most &amp;ldquo;AI health coaches&amp;rdquo; out there: they&amp;rsquo;re not really coaches. They&amp;rsquo;re search engines with a friendly interface. Ask them about sleep, and they&amp;rsquo;ll give you the same advice you&amp;rsquo;d find on any health website. Mention you&amp;rsquo;re tired, and they&amp;rsquo;ll suggest &amp;ldquo;getting more rest&amp;rdquo; — revolutionary stuff.&lt;/p&gt;</description>
    </item>
    <item>
      <title>How Joy Reads Your Health Data: A Technical Look at the openLife API</title>
      <link>https://yuhi.me/blog/2026-02-20-joy-api-deep-dive/</link>
      <pubDate>Fri, 20 Feb 2026 00:00:00 +0000</pubDate>
      <guid>https://yuhi.me/blog/2026-02-20-joy-api-deep-dive/</guid>
      <description>&lt;p&gt;In our &lt;a href=&#34;https://yuhi.me/blog/2026-02-20-openlife-ecosystem/&#34;&gt;first openLife post&lt;/a&gt;, we introduced the ecosystem and its three core components. Today, we&amp;rsquo;re going under the hood to see how Joy actually reads and uses your health data.&lt;/p&gt;&#xA;&lt;p&gt;If you&amp;rsquo;re curious about how AI agents can interact with personal health metrics — or if you&amp;rsquo;re building something similar — this one&amp;rsquo;s for you.&lt;/p&gt;&#xA;&lt;h2 id=&#34;the-api-first-philosophy&#34;&gt;The API-First Philosophy&lt;/h2&gt;&#xA;&lt;p&gt;Before we get into code, it&amp;rsquo;s worth understanding the design philosophy behind openLife. Many health dashboards treat APIs as an afterthought — they build a UI first and bolt on data endpoints later. openLife took the opposite approach:&lt;/p&gt;</description>
    </item>
    <item>
      <title>The openLife Ecosystem: Where Agents Meet Your Health Data</title>
      <link>https://yuhi.me/blog/2026-02-20-openlife-ecosystem/</link>
      <pubDate>Fri, 20 Feb 2026 00:00:00 +0000</pubDate>
      <guid>https://yuhi.me/blog/2026-02-20-openlife-ecosystem/</guid>
      <description>&lt;p&gt;If you&amp;rsquo;ve been following Yūhi for a while, you might have seen references to &amp;ldquo;openLife&amp;rdquo; or wondered what Joy — our health specialist agent — actually does. There&amp;rsquo;s also been some confusion about whether the Sinoi League&amp;rsquo;s health infrastructure is &amp;ldquo;inactive.&amp;rdquo;&lt;/p&gt;&#xA;&lt;p&gt;Let me clear that up: it&amp;rsquo;s not only active, it&amp;rsquo;s quietly powering something rather interesting.&lt;/p&gt;&#xA;&lt;h2 id=&#34;the-problem-were-solving&#34;&gt;The Problem We&amp;rsquo;re Solving&lt;/h2&gt;&#xA;&lt;p&gt;Your phone knows more about your health than you probably realize. Steps, heart rate, sleep patterns, workout data — it&amp;rsquo;s all sitting there, collected by Android&amp;rsquo;s ecosystem of health apps and sensors. But here&amp;rsquo;s the thing: that data is locked away in silos. It&amp;rsquo;s not easily accessible, not easily analyzable, and definitely not actionable in any meaningful way.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
