The third tier combination, and the least-drawn corner of the product. Ruth Kellam pays for the binder; Curtis Boyd works entirely through four texts and four pages. He is not drawn as a lesser builder, and nothing on Ruth's screens says how he got there.
“Curtis: we want the shelving in oak or walnut. I don't mind which. What can you actually get by the 4th?”
Oak, by the 4th
I can get it
Walnut, by the 4th
I can get it
Neither by the 4th
Call me and we will work out the date
Which is why this page has three options and the pricing page has a text field. An earlier draft filed his pricing here too, and it would have forced a second, input-shaped variant of type 1 and split the type in two. Type 1 is exactly one shape for every role that receives it.
Ruth is an institution to Curtis in this exchange — across the boundary, not on the same side of it — so no account, no password is doing its job. On a peer send the identical sentence would be an insult, and the sender never has to pick which: it is derivable from the relationship.
The counter run and the lighting. Ruth hasn't decided either, and she will send this again when she has.
A cumulative spec that goes quietly stale gets ordered against, and the order is wrong by a room. When the lighting lands, this page goes to replaced and points forward — never superseded, which would say do not act at all and leave him with nothing to buy from.
If he tapped got it, Ruth would eventually be shown Curtis saw it and would read that as agreement. It is not, and the gap between the two is the kind of thing that surfaces at the end of a job. A receipt is not a fact about his work.
So an absence can never be read as a decision. A builder who is told only what closed learns that silence means nothing is pending — which is exactly backwards, and is how he ends up ordering a counter Ruth had not chosen.
Periodic, unsolicited, no action, absorbing everything that happened and needs nothing. A homeowner is not waiting to hear which decisions closed, and a builder is not owed a running budget position. The test that keeps it honest: if a payload ever needs an answer, it is not type 4.
A sentence a dashboard cannot say. It is the difference between a status page and somebody telling you where things stand, and it is most of what this tier is for.
That is the send rule doing its work: we never send an account-less person something that does not need them. Break it and the tier degrades into a stream of notifications nobody can triage, because we deliberately gave them nowhere to triage — his inbox is his text app and there is no standing address to hold a list.
Everything that happened and needs nothing collects into the fourth text instead of arriving as a fifth, sixth and seventh. Without it the choice would be between telling him nothing and drowning him.
No sign in, no verify your email, no create an account to continue, no password reset he did not ask for. The front door exists and Curtis never sees any of it — that is the tier, and it is the thing this page exists to make concrete.
Nothing. No no account beside his name, no lighter type on a row he answered, no smaller avatar, no badge. Documents he sent are attributed to Curtis Boyd exactly as documents from a paid builder would be, and a year later the binder cannot tell the two paths apart and must not care. Delivery channel — text, email — is a fact about a message and is fine on a send sheet; it is never a property of a person.
The $1,400 he typed is not validated the way a paid builder's figure is validated, and any cost-of-deciding-late arithmetic downstream runs on it. Nothing in this tier can fix that, because the person typing has no record for us to check it against. Saying so is the honest part; pretending the number carries the same weight would be the dishonest one.
Because both source decks assumed the builder was the paying side. v6 draws a builder with a whole app and a homeowner with a link; the adaptive deck draws a homeowner with a whole app and treats the builder as a name on a row. Neither deck had a reason to draw a builder who is neither — and a product whose second-largest tier combination is undrawn will discover it in support tickets rather than in a mockup.