When suppliers change what they promise

Every commitment document behind a score on this site is re-read weekly. When one changes, the date and the wording are kept, permanently, and from a start date that cannot be back-dated.

197 commitment documents have changed since this desk began watching on 2026-08-05. Each row is a document a score depends on, the date it moved, and what it now says.

What exactly is being watched?

Every source document recorded against a score on this site, the vendor's own pricing page, product documentation, published terms or brand standard. Currently 182 documents across 50 suppliers and 7 instruments.

Each is re-fetched weekly and hashed with volatile page furniture stripped out, so a rotating build identifier or a changing session token does not read as a changed commitment. When the hash moves, both the previous and the current text are kept. The record is append-only, and a build gate fails if it ever shrinks — a deleted delta cannot be recovered by a later run.

Does a change mean a supplier got better or worse?

This page does not say, and will not. A supplier may have clarified wording, corrected an error, reorganised a page, or genuinely added or withdrawn a commitment. Deciding which is a ruling, it rests on reading the document, and a human makes it — it arrives as a re-score with a dated changelog, not as an automatic adjustment.

What is asserted here is narrow and checkable: this document was one thing on this date and is another now, and here are the passages that differ.

Why does a record like this get harder to copy over time?

Because it can only be accumulated. A competing publication can produce a better-looking ranking next quarter, but it cannot state what a supplier's commitment page said before it started watching. That gap never closes, it widens by exactly one week, every week.

It is also why this page ships while it is empty. The date it starts is the asset.