One template, seven copies. A link renders the build as of the moment it was sent and never updates — when the thing underneath moves, the page dies rather than re-rendering. Every dead page says what to do now, and only one of the eight blocks.
This is yours and it stays open until Friday the 29th.
Shaker, paint grade
$12,400 · 5 weeks
Shaker, rift oak
$18,900 · 7 weeks
Slab, rift oak
$21,300 · 7 weeks
Quoted: a second delivery, from the cabinet shop's terms. Assumed: two idle days for the installer.
Send Dave my pick I have a question firstIt stays open until Friday the 29th. A page that only mentions its deadline after passing it was never honest about having one. And what that sentence promises is the deadline, not liveness — it can still be superseded, replaced or withdrawn before Friday.
There is no standing address, so somebody with four open decisions has four texts rather than a list. That is why the send rule is load-bearing: we never send an account-less person something that does not need them. Break it and the tier degrades into notifications nobody can triage, because we deliberately gave them nowhere to triage them.
The prices are chips of fact, not verdicts. Coloring a delta as a clash tells the reader an option is the wrong one before they have weighed it — and in this product's own worked example, the dearest candidate is the right one for reasons that have nothing to do with price.
And here it is deliberately not a link at all — nothing else needed from you is the honest what-to-do-now. A dead page still has to end with one, and sometimes the right one is that it is handled.
A receipt states a fact about the record. Thanks! is the product having a personality at the one moment somebody wanted a confirmation, and it is also the tell that this page has become a marketing surface.
Not somebody, not another recipient. The whole value of the state is that it tells him which of the two of them moved, and the token knows because it was minted for him and not for the decision.
Text Dave if that isn't what you wanted. The page cannot reopen a settled decision — an account-less person may assert facts about their own work and may not void somebody else's record — so what it offers is the human channel, which is the one that actually works here.
Not because it is urgent, but because it is a genuine clash: the page in front of the reader contradicts the record. Every other death here is neutral, and coloring one of those as an alarm would spend the one signal that means this is wrong.
The forward pointer is what separates this from frame 5, and superseded may not have one. What it always has is text Dave — and you have not missed anything, because the first thing somebody reads into a page like this is that they were too slow.
Asking a question does not close a decision. The original stays live — frozen, simply not yet superseded — and when the answer arrives it mints a new link carrying the question, the answer and the same options. The original goes here and points at it.
A reader who acts on a superseded page has done damage; one who acts on a replaced page has wasted a trip. They were a single state in an early draft of the identity spec, which would have produced one behavior for two situations — and would have told the builder's register that a live send was dead.
He did not say why here is the honest sentence, and it is better than the plausible one. A page that guesses at the sender's motive is a page that will eventually guess wrong to somebody's cost.
The content moving versus the window closing. The builder's own screen inventory reached the same distinction independently, from the other end: locked is not invalid.
Not you missed this. The page names what the deadline was for — the shop needed the order to hold a slot — which is the fact, and leaves the reader to draw the conclusion. It is also the only state that carries a date line, because it is the only one where the date is the content.
Because there is nothing else on the page. Every other death has a frozen moment behind it and a what-to-do-now that names a person; this one has neither, and a state carrying an action is not blocking. A dead link is never rung 3 except for an invalid token.
Which is the whole reason it looks different. Saying so — the link is what carries that — is better than a bare 401 and better than pretending: a stranger who cannot see whose message this was needs to be told that is why, not left to assume we are hiding it.
No sign in, no verify your email, no create an account to continue. This is the page most likely to grow one, and an account-less person meeting a login wall is the failure the whole tier is built to avoid.
Which is why there is no expiry treatment on it. The as-of line does all the work, and it says the useful thing: this is a record of a week rather than a picture of today.
An earlier draft of the identity spec said the digest “never dies” and conflated the two. Every link dies — including this one — when the project completes or the relationship that minted it ends, whichever comes first. A permanent unauthenticated URL showing somebody's build is a data-exposure bug, not a convenience.
Not asking you yet, with the reason. So an absence can never be read as a decision — which is the job this kind of link exists to do, and 33-the-digest is where it is drawn properly.
Seven of the eight are the same block: a title, a sentence, and a what-to-do-now. What changes is the eyebrow — the state, printed in its own mark ink: settled once, a person once, a clash once, neutral four times — and whether there is a forward pointer. Six tinted grounds carried this until 2026-09-05, which asked the reader to learn a color code to find out what happened. Nothing else. If a ninth state is ever proposed, the test is whether it changes what the reader should do next; if it only changes what an engineer would investigate, it is a cause and it does not reach a screen.
A live-updating link page. The one failure freezing exists to prevent. Every page here is a moment, and a page that refreshed itself would mean the reader could be looking at numbers that changed while they read — which is exactly the lie the freeze rule is for.
A shared link instead of one per recipient. Frame 3 becomes unwritable: the best a shared token can say is this has been answered, and the whole value of the state is naming who moved.
A dead page with no action. Six of these seven end in text Dave and the seventh ends in nothing else needed from you. It is the cheapest thing to leave out and the thing that turns a considered dead end into a wall.
Issuance. The link infrastructure exists and is unreachable: the public routes are registered, tokens are hashed and carry a recipient and a label, and the minting function has two callers — both command-line tools — with a doc comment saying it must never become a route. Building that route is the builder's Send door and the backend phase. This page draws what it serves.