A prerequisite map for Zion Market. Read the arrows, not the list. Dependency map Onion addresses
zionmarket.biznothing works until

This is not a to-do list and not a walkthrough. It is a set of conditions and the arrows between them, so you can see what your problem is actually waiting on.

Zion Market onion addresses, printed here exactly as they were supplied

Two strings, reproduced character for character as they were handed to this site. Neither one is ranked above the other and neither carries a label, because a label would be a claim and this site is not in a position to make one. Nothing here opens them, so nothing here can tell you what happens when you do.

H1 · A close you can live with

A condition that must already be true

Escrow is still holding when the problem appears

The funds have to still be held by the mechanism at the moment you discover something is wrong, or there is nothing left to argue about.

Confirm by: Look at the order state before you send any message about a problem, and read what it says about who currently holds the value.
Not this: Not a claim that escrow protects you. It only says that the sequence matters more than the mechanism.

Two events, and which of them comes first

The card names two events and one relation between them. One is the moment the value stops being held by the mechanism and becomes the other side's. The other is the moment you find out that something about this order is not what the listing described. The condition is that the discovery comes first.

The word invites a debate about trust, and that debate is not the subject here. Whether a held sum is safer than an unheld one is a question about the mechanism, and this site does not answer it. Whether you still have something to point at when you open your mouth is a question about ordering, and ordering is the part that is yours.

What changes at release is not your tone and not your evidence. It is the object of the sentence you are about to write. Before release, a message about a problem is a claim on something that has not gone anywhere, and the person reading it knows that. After release, the same words ask them to hand back something they now hold. The facts are identical. The second kind of request can be refused with silence, which costs the refuser nothing.

This is also why pressure to close early is itself information. A request to end the order before the thing is in your hands is a request to move the value across exactly that boundary. It does not prove that whoever asked is dishonest, and this card makes no such accusation. It tells you what granting it does, which is to convert every argument you might have tomorrow into a favour you will have to ask for.

What the holding rests on

The total is covered at the moment you press the button is the reason there is a held sum at all. If the value never left cleanly, or left short, nothing is sitting in the mechanism and this card has no subject. The whole of stage E feeds that one moment, and this is where the moment either pays for itself or does not.

You can wait without doing anything supplies the temperament. Most early releases end the discomfort of an open order rather than decide anything about the order. Closing feels like resolution, and it is the one action available to you that cannot be undone from your side. It tends to get taken at the moment your judgement is worst.

Both upstream conditions were settled before the parcel was even sent, and nothing you do at this stage repairs either of them. See the dependency map for how far back the chain runs.

What an order with nothing held cannot support

Directly downstream is you can describe the problem in the market's own terms, and that card assumes a reader with a reason to read carefully. Once the value has moved, your careful account of a state, a date and a difference from the listing text is being read by somebody who has already received everything this transaction was going to give them. The text does not get worse. Its leverage goes to zero, which is a different problem and not one that better writing fixes.

Stage H is a single chain, so the failure runs the length of it.

Cannot holdThe reason it cannot
A problem you can describeStill writable, but addressed to somebody with no remaining interest in the outcome. A claim on a held sum becomes a request for a favour, and a favour has no mechanism behind it.
Feedback after the outcome is knownThe outcome you would report is now partly one you produced by closing early. You either publish a verdict that omits your own part in it or publish nothing, and both add noise.
Being able to come back tomorrowThe account survives intact. What you come back to includes an order that ended in a way you cannot characterise, so the use you can make of it is smaller.

The size of that damage is worth stating precisely, because overstating it is its own dishonesty. An early release breaks no account, no address store and nothing in stages A through E. What it destroys is narrow: the position from which anything you say next carries weight. That is one card wide, and it happens to be the card the remainder of the map is built on, which is why a small mistake matters out of proportion to its size. What happens when a condition is false describes the pattern in general.

The evening you close it early

The order sits in whatever state it sits in, and that state names, somewhere, who currently holds the value. The pull to be finished is strong. You take the action that ends it. Nothing warns you, because from the system's point of view an order that ends is an order behaving normally.

Later the difference surfaces. A count, a form, something the listing text was specific about and the delivered thing is not. You write the message and it sends. It looks exactly like a message that will be answered, and that is the misleading part, because on your screen a message about a closed order and one about an open order are the same object.

Then nothing, and no error, because nothing has errored. The confusion lands on the market, and people conclude the process failed them. The process was never engaged. The message that would have started it went out a day after the only thing that made it a claim had gone.

Reading the state before you type

The check runs on your side and requires opening nothing new. Before writing the first word of any message about a problem, read the order as it stands and find the part that says who holds the value now. Whatever it is called where you are, it is readable without asking anybody.

A pass: you can state in one short sentence, without hedging, who holds it at this moment. A fail is a shrug, or the discovery that the answer is the other side, which is worth learning before drafting. Do not ask the other side what state the order is in. That question moves the answer into their gift when it was already on your side of the screen. Some of the vocabulary is set out in the words used here.

Not an opinion about escrow

This card does not say that a holding mechanism protects you, and it publishes no rules about release. It says that two events have an order, and that one ordering leaves you with something. Do not confuse it with deciding in advance what happens if nothing arrives, which is about naming a day while the decision is still cheap. This one is about the state of the value on the day you named.

The chain around this condition

Read downwards. Everything above this card has to hold before it can, and everything below it is waiting on it. Two levels are shown in each direction; the full graph is on the dependency map.

Connected to this one

Where you are in the map