Release on XKV.org

How XKV Was Tested With 1000 Kills, Torn Writes and a Million Revisions

Mon, 19 Oct 2026 00:00:00 +0000

A store that keeps the reason behind every value is only useful if it keeps the value too. So before 0.1.0 went out, each promise XKV makes got a test aimed straight at it, and every number below sits in the repository’s test results, written by one script on a 2-CPU Linux machine.

The promises are short. A transaction is all or nothing. An acknowledged write survives a crash. Committed data is never dropped quietly. Compaction never breaks a chain of causes. Here is how each was tried.

XKV 0.1.0 Is Released as an Open Source Key-Value Store That Remembers Why

Mon, 19 Oct 2026 00:00:00 +0000

XKV 0.1.0 is out. It’s a small key-value store for Go that keeps one thing other stores throw away: the reason. Every write records who made it, why, and which earlier change caused it. Ask a value how it got there and XKV walks the chain back, across keys, to where it started.

The release has four parts. The Go package, with no dependencies, stores everything in one file. The xkv command reads and writes that file from a shell and can serve it over HTTP for other languages. A WebAssembly build runs the same code in a browser, and the live demo is built on it. Four example programs act out the case studies on this site.

XKV Can Now Swap Changes Between Stores and Keep the Reasons Behind Them

Mon, 19 Oct 2026 00:00:00 +0000

XKV 0.2.0 is out, and it adds exchange. One store writes its recent changes to a file, another store reads them in, and every change arrives with its actor, its reason, its ref and its causes. Ask the second store why a value is what it is, and you get the same chain the first store would give you.

That matters wherever the same settings live in more than one place. A service and its staging copy. Two sites that each take local writes. A laptop that was offline for a day. Copying values between them is easy. Copying the story behind them is what usually gets lost, and with it any chance of answering “who changed this, and why” on the receiving side.

XKV Now Streams Every Change as It Commits, With the Reason Attached

Mon, 19 Oct 2026 00:00:00 +0000

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.

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.