A home for what changes

Arkeion is a database where every version is still alive — nothing is ever silently overwritten, and the past stays addressable with AS OF. It would be strange, then, for the project’s own history to live only in scattered commit messages and release tarballs. So this is the changelog: what shipped, when, and why it matters — kept in the open, the way the engine keeps yours.

One feed, two kinds of entry

We use this as both a changelog and a blog. Every entry is one of two kinds, and a badge tells you which at a glance.

A Release entry pins a version and documents what changed in the engine — measured, not marketed. A Post entry is where we explain the reasoning: why a design decision went the way it did, why sovereignty is a feature and not a compliance checkbox, and where the project is headed. Some months are dense with releases; some are quieter and more reflective. Both belong here.

Why in the open

A database earns trust by being inspectable — hash-chained history, verify(), an engine you can read line by line. The same logic applies to the project around it. If we ask you to trust Arkeion with your data, the least we can do is keep our own record where you can read it, correct it, and hold us to it.

Check back here, or watch the source — the commits and the changelog tell the same story from two distances.