The juudd panel shows only what the platform measured. Where a design asked for more, we drew the nearest true thing instead. Three screens asked for facts we do not have, and each one got the same answer.
A picture of a claim is still a claim. A screen can be transcribed faithfully and still lie, because the customer reads the panel as a record of what happened. That makes it the worst place to invent data.
There are no version numbers
The mock-ups drew a deploy as v12, with a column of v12, v11 and v10 down the page and a button to roll back to v11.
No such thing exists. A version is a timestamp, a dash and eight characters of a hash of the files, so versions sort by time as plain strings and nothing has to be parsed to order them. A real one looks like 20260824T091241000Z-a6218360.
We could have counted the stored versions and called the newest the twelfth. We did not, for one reason: the number would disagree with every tool your assistant calls. list_deploys and publish_deploy name a deploy by the string the store keeps. A panel that taught you "v12" would hand you a name that nothing else answers to, and the first time you pasted it into a conversation it would fail.
So the panel shows the hash half, a6218360. It is the part that tells one deploy from another, and the timestamp it drops is already in the column beside it. A short commit hash reads the same way. The whole string stays within reach: it is the hover title on the cell, and it is the string in the roll-back line the panel offers you to paste, because that line is going to a tool.
Nothing records what changed
The mock-up's deploy history had a Change column with a sentence per version: "Notes API reads through the row-level policy".
Nothing writes that sentence. A deploy is a bundle of files and a manifest. There is no commit message, and deploy_site takes a site, a hostname, files, functions and a routing choice, and no description. Adding a field for the assistant to fill in would make the column show what a model said it did, which is a different claim from what was deployed, and a worse one to keep in a history.
The column shows what was in the version: how many files, and how many server functions when there are any. It is headed Contents, not Change, so the header does not promise the other thing.
A link being used is never reported back
The mock-up drew a site as "Handed over", with "link used" and a date beside it.
Handing over a database is two steps, and we see only the first. The panel, or the transfer_database tool, mints a one-time link and records the moment it was made. The transfer itself happens when a person opens that link, outside this system, and nothing reports back when they do.
So the panel says "Hand-over made" with "link made" and the date. The hand-over page says in as many words that nothing has moved yet, that a link being created is not proof it was used, and that one which expires unused costs nothing to replace. The timestamp is written only after the link has been minted, so a failure cannot read as a hand-over. And there is a test asserting that the reply never says the database was transferred, moved, or now belongs to you.
A hand-over is also a fact about a database, not about a site. A site whose database has left still serves every request it served before, so the Status column says only whether the site serves.
What it gives up
This rule is a limit on the interface, and it gives up some of the screen. A history without sentences is plainer than one with them, and a status column that cannot say "Handed over" will sometimes understate what has happened.
We accept that because the alternative fails quietly. A sentence the platform made up reads as true, and a customer has no way to tell it from a recorded one.
A sequence number is not ruled out. If one is ever wanted, it has to be adopted by the tools first, so the name on the panel and the name in the conversation are the same name.
The rule, once
The panel states what was measured and nothing else; where a design asks for more, draw the nearest true thing and say so. The tools and what they return are listed in the docs.