https://xkv.org/tags/release/ Recent content in Release on XKV.org Hugo en-us Mon, 19 Oct 2026 00:00:00 +0000 https://xkv.org/how-xkv-was-tested-with-1000-kills-torn-writes-and-a-million-revisions/ Mon, 19 Oct 2026 00:00:00 +0000 https://xkv.org/how-xkv-was-tested-with-1000-kills-torn-writes-and-a-million-revisions/ <p>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&rsquo;s <a href="https://github.com/explainable-kv/xkv/tree/main/test/results">test results</a>, written by one script on a 2-CPU Linux machine.</p> <p>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.</p> https://xkv.org/xkv-0.1.0-is-released-as-an-open-source-key-value-store-that-remembers-why/ Mon, 19 Oct 2026 00:00:00 +0000 https://xkv.org/xkv-0.1.0-is-released-as-an-open-source-key-value-store-that-remembers-why/ <p>XKV 0.1.0 is out. It&rsquo;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.</p> <p>The release has four parts. The Go package, with no dependencies, stores everything in one file. The <code>xkv</code> 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 <a href="https://xkv.org/demo/">live demo</a> is built on it. Four example programs act out the case studies on this site.</p>