The record
Changelog
What changed in this product, and when — including the days it broke. The list below is not written by hand. It is generated from this repository's commit history, which is where the work is actually recorded, so it cannot quietly stop mentioning the bad weeks.
Most of these entries name a defect. That is deliberate. A supplier who tells you what went wrong, and when, is easier to check than one who never has a bad quarter — and this is a company that sells you a way to check things.
How this page is made
A build script reads git log for this site's directory and writes a file. This page renders that file and nothing else. Every entry is a commit's own subject line and the opening paragraph of its message, word for word.
-
- Commits read
- —
- every commit that touched this site's files, in this repository's history.
-
- Entries below
- —
- what the list actually shows, grouped by the day the work landed.
-
- Withheld
- —
- read, judged unpublishable, and counted here rather than dropped in silence.
The list is curated, and this is the whole of the rule
An entry is held back only when it names one of three things:
- a security weakness that is not closed;
- a credential, key or token;
- a customer, or material held in confidence for one.
Nothing else is filtered. An entry is not held back for being embarrassing, and several of them are — an outage caused by a comment, a test that had been passing for months while measuring nothing, a price list that lost money on every stamp it sold. Those are the entries worth publishing. The reasons for the withheld ones stay in the build script, because stating why an entry was withheld is usually the same as publishing it.
Two things this page cannot do, said plainly
It is not live. Regenerating the file is a deliberate step taken before a deploy, not something that runs on its own, so this page lags the repository by however long it has been since somebody ran it. The date it was generated is at the foot of the record below; compare it with today and you have the size of the gap. It is built this way on purpose: a changelog that can fail a build is a changelog that gets deleted.
Nothing here links to a commit. The repository is not public, so there is no address to send you to. An entry is the message and the date, and that is all it can honestly be until the source is published.
The vocabulary drifted, and the old words are left alone. Older entries use colour names for outcomes that this product has since stopped using — the four lights are red, amber, white and anchored, and no light is called green. Editing the history to match today's vocabulary would destroy the one property this page has, which is that nobody rewrote it.
The record
Newest first. Each entry is one commit: its subject, then the opening paragraph of its message.
The list has not been read into this page. The entries live in /data/changelog.json and are fetched when the page opens. If this notice is still here, that fetch has not completed — the script did not run, or the file did not answer.
The file is plain text and is meant to be readable on its own. Open the link above and you have the same record this page would have drawn, in the same order.
What we publish instead of a dashboard
This page, and the things it points at, are the whole of what one company can put in public without inventing a number. There is no visitor counter, no waitlist figure and no revenue chart. This site runs no analytics of any kind and there is no waitlist, so the first two would have nothing behind them; a figure with nothing behind it is worse than a blank.
What we cannot claim, in a table Plans and what a stamp costs Check a stamp yourself