Changelog

What changed in Verity, newest first.

Entries describe what an operator or administrator will notice. Where a change alters what Verity claims — rather than what it looks like — that is called out, because those are the changes worth reading twice.

By month

September 2026	CI green again: the security scan and a database test that only passed locally.
August 2026	Country scoping and Bahrain. Contracts, templates and signing — by link, and bilingual. Freelancers.

Why it is split

One month of entries ran to six hundred lines. A changelog nobody scrolls to the end of is one that stops being read, and a month is the unit people actually ask about — "what changed in August?" rather than "what changed in entry forty?"

A new file per month. Nothing is rewritten when it is added.

What a good entry says

Three things, and the third is the one that gets skipped:

• What an operator will notice. Not the class that changed
• What it replaces, where something was wrong before — a fix nobody can see is a fix nobody trusts
• What it still does not do. The gap between "it shipped" and "it works everywhere" is where the surprises are, and the changelog is where somebody looks for them afterwards

Where a change alters a claim — what Verity asserts about a merchant, or how strongly — that is marked, because it changes what a compliance officer may rely on.