Changelog

Changelog

A record of what changed and when. Short on purpose. A change that affects a document in review is recorded here whether or not it was comfortable, and a superseded entry stays visible rather than being quietly deleted.

01

Entries

10 November 2026

Second verification pass: fifty-four registers, and two countries that already issued the keys

Seven registers added across North America, Europe and Asia. The pattern that keeps repeating is a state that has already built the cryptography and still publishes no file.

Read the full entry

9 November 2026

RevowAnchor is deployed and verified

Ethereum mainnet, block 26,379,202. The deployments table in RVW-7 is no longer empty and the document moves to review.

Read the full entry

9 November 2026

RevowAnchor: the suite is green, and it is still not deployed

Sixteen tests pass, including three invariants checked across 128,000 calls each. The deployments table stays empty until there is an address.

Read the full entry

9 November 2026

Register index: the first shape, before any of it was checked

Superseded the same day. Kept because a lab that deletes its wrong drafts is harder to trust than one that leaves them up.

Read the full entry

9 November 2026

RVW-1: licence references keep their leading zeros

A reference is a string, never a number, and an implementation that parses it will eventually be wrong.

Read the full entry

9 November 2026

First verification pass on the register index

Forty-seven registers checked by hand. Denmark amended its law so the register records why an approval ended instead of deleting the person. The European Union legislated most of this for one trade in 2006, Italy did it for every regulated profession in 2012, Poland deleted its register in 2014, Estonia has every component of a signed register except the signed file, and three jurisdictions keep the register that counts in a room.

Read the full entry

02

What belongs here

A log records a change: a field renamed, rows added to the register index, a specification moving between draft and review. It is dated and it is read once.

An argument that is still worth reading in a year belongs in the notes instead. Keeping them apart is the only way the good arguments do not get buried under version bumps.

Read this page as Markdown