<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Watch on XKV.org</title>
    <link>https://xkv.org/tags/watch/</link>
    <description>Recent content in Watch on XKV.org</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Mon, 19 Oct 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://xkv.org/tags/watch/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>XKV Now Streams Every Change as It Commits, With the Reason Attached</title>
      <link>https://xkv.org/xkv-now-streams-every-change-as-it-commits-with-the-reason-attached/</link>
      <pubDate>Mon, 19 Oct 2026 00:00:00 +0000</pubDate>
      <guid>https://xkv.org/xkv-now-streams-every-change-as-it-commits-with-the-reason-attached/</guid>
      <description>&lt;p&gt;XKV 0.3.0 adds watch. A program asks the store for every new revision, and gets each one the moment its transaction commits: the key, the value, who wrote it, why, and the earlier changes that caused it. So the part of a system that reacts to a change also knows the reason for it.&lt;/p&gt;&#xA;&lt;p&gt;That covers the jobs people usually bolt onto a config store with polling or triggers. Refresh a cache when a price changes. Tell a person when a limit drops, along with the risk score behind it. Write an audit line. Start a job when an AI agent changes a setting, with the tool call it gave as its reference.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
