What counts as an answer, and when it has to arrive
The condition has two halves and both are strict. There has to be a reply, and the reply has to have arrived while value was still on your side of the arrangement. A reply that comes afterwards is not this condition being satisfied late. It is a different fact about a different situation, because by then the information no longer changes anything you can do.
The reasoning is plain. Before you commit, you are the one holding the thing the other side wants, and their incentive to write back is at its highest. If a message goes unanswered at that point, it is not going to be answered faster once the incentive has been removed. Silence collected before commitment is free. The same silence collected afterwards is expensive, and it is exactly the same silence.
What you are collecting is narrow. A reply tells you that somebody is reading the channel and that the channel works in both directions. It also lets you compare the reply against the listing text, which is the only cheap consistency check available anywhere in this stage. It does not tell you whether the arrangement will end well, and treating it as though it does is a mistake that this card exists partly to prevent.
The two conditions that make the question possible
The listing is one you have actually read supplies the question itself. The instruction is deliberately counterintuitive: ask something whose answer is already written down. That way the reply carries two pieces of information rather than one. You learn whether a reply comes, and you learn whether the reply agrees with the text you have in front of you. Ask something the listing does not cover and you learn only the first.
You can log in a second time supplies the ability to read the answer. Messages sit inside the session. A reply that arrives while you cannot get back in is a reply that did not arrive, in every sense that matters here. This is also why the two upstream cards are genuinely separate: one gives you something to ask, the other gives you somewhere to hear it.
Both upstream conditions are satisfiable before any value moves at all, which makes this the last card in the stage whose cost is still nothing. The Roots and endings page groups the cards by how expensive they are to leave until later.
The instant this one is holding up
Only one card sits directly below this, and it is the one everything else in the second half of the map hangs from: The total is covered at the moment you press the button. That card is about several conditions being true at the same instant. An unanswered question is a condition that is still open at that instant, and it is the only one of them that was free to close.
The mechanism is about what the commitment does to your options. Before it, the cheapest available action is to ask and wait. After it, the cheapest available action is to ask and wait, and it no longer works, because the thing that made writing back worthwhile has already changed hands. You have not lost the ability to send messages. You have lost the reason anybody has to read them.
Because the commitment card feeds You decided in advance what happens if nothing arrives and Escrow is still holding when the problem appears, the consequence travels. A plan for nothing arriving is much harder to write when you already suspect there is nobody at the other end, and the suspicion is the thing you could have resolved for free.
| Pressing without an answer | What that costs later |
|---|---|
| One unknown left open | It is the only unknown that was free to close |
| No consistency check on record | Nothing to compare a later statement against |
| A silent channel already established | Later silence carries no new information |
| A plan written under suspicion | The waiting card starts under strain rather than at rest |
What the skip looks like on the screen
You write, you see the message in the thread, and nothing happens. There is no failure indicator, because nothing failed. Unanswered and unread look identical from your side, and the interface has no obligation to tell you which one you are looking at.
So you wait a while and then decide the silence probably means nothing, which is a reasonable thought and also the exact point at which the free information gets thrown away. You commit. Now the same empty thread is a different object. You reread your own message looking for something wrong with the wording, you consider sending a second one, and you start assembling explanations out of nothing. None of that is available as evidence later, because a thread with one message in it says the same thing whichever explanation is true.
Sending one plain question and reading the reply properly
Send one question, phrased plainly, whose answer is already in the listing. One question, not a list, because a list gives the other side the option of answering the easy part and you will not notice which part they skipped.
A pass is a reply that arrives and agrees with the text. A fail comes in three recognisable forms: nothing comes back at all; something comes back that contradicts the listing; or something comes back that answers a question you did not ask. The third is the one people misread as a pass, because a reply arrived and it was friendly. Check that the sentence in front of you addresses the thing you wrote.
Speed is worth exactly what it is: a fact about how often somebody reads a queue. It is not evidence of care, competence or good intent. If you catch yourself converting a fast reply into a character judgement, the word you want is in Words used here rather than in the message.
Not a judgement of the person answering
It is not a character test and it is not vetting. It measures one property, which is whether a channel returns anything before you have committed. It is also not a second copy of The listing is one you have actually read. That card asks what the text says. This one asks whether anyone stands behind it.