XKV on SoftDevStudio.com

XKV Launches as a Key-Value Store That Remembers Why Each Value Changed

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

XKV, the studio’s twenty-second project, is for the small values that cause big trouble: credit limits, prices, timeouts, feature switches, and the settings AI agents now change on their own. A normal store keeps the value and forgets the story. XKV makes every write say who made it and why, and lets it name the earlier changes that caused it, on any key. Ask a value why and it walks the chain back. A credit limit of 50 points at a risk score of 0.82, which points at a card dispute billing recorded from a bank notice.

XKV Streams Each Change the Moment It Commits, Reason Included

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

XKV 0.3.0 adds watch. A program gets every new revision as its transaction commits, with the writer, the reason and the changes that caused it, so whatever reacts to a change, a cache refresh, an alert or an audit line, also knows why it happened. It’s Watch in Go, xkv watch in a shell, and a stream over HTTP that a browser can read and resume.

Revisions arrive in order, each once, never half a transaction, and a restarted watcher picks up where it stopped. A watcher in another process follows the file, and if compaction removed changes it hadn’t reached it says so instead of skipping them. Twenty writers killed with SIGKILL mid-stream lost none of their 3,996 acknowledged transactions on the watcher’s side. The live demo now shows changes arriving as you make them. With exchange in 0.2.0, that completes the plan YK approved.

XKV Swaps Changes Between Stores and Keeps the Reasons With Them

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

XKV 0.2.0 adds exchange. One store exports its recent changes as a file, another imports it, and every change arrives with its actor, reason, ref and causes, so Why gives the same chain on both sides. Think of a service and its staging copy, two sites that each take writes, or a laptop that was offline for a day.

Each change carries what its writer had seen of the key, so an import can tell an update from a conflict without trusting clocks. In a conflict the later change wins on every store and the other one stays in the key’s history. Twenty pairs and 90 rings, stars and meshes of stores, with clocks up to 74 minutes apart, all ended with the same values; 40 kills during an import left nothing half done; a fuzzer rewrote files 3.6 million times without a panic. Stores from 0.1 open as before and upgrade with one command. Watch, a live stream of new changes, is next.