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.

A close you can live with

Four conditions about finishing. The last of them depends on a card three stages earlier, which turns the map into a loop rather than a line.

Stage H is about ending an order in a way you can live with, and about still being the same person to the market the next time you arrive. It is the last stage on the map and it contains the only card that reaches backwards far enough to make the graph a loop.

The stage runs on sequence rather than on effort. Almost everything that goes wrong here is an ordering problem: value released before a problem was noticed, a complaint written before it could be stated clearly, a verdict published before the outcome was known. None of those are failures of care. They are failures of order, and order is exactly what a dependency map is for.

What enters this stage

Four arrows arrive. The simultaneity card and the waiting condition both feed escrow still holding. The listing condition reaches two stages forward to feed describing a problem. The reception condition feeds feedback after the outcome.

What leaves this stage

Nothing leaves the map, because there is nothing after stage H. But two arrows arrive at the final card from a long way back: the address storage condition in stage C and the recovery phrase condition in stage D. That is the loop. If either of those was false, coming back tomorrow fails, and the next session starts again from stage C with nothing carried over.

Why the map closes rather than ends

If this was false in an earlier stageWhat you notice in stage H
The address was only ever in a browser tabYou cannot find your way back at all
The phrase was never written downYou can find the door but cannot open it
The password lived only in memoryThe same, one week later instead of one day
The listing was never readYou can arrive and log in, and still have no case

Read that table as four different ways of ending up back at the start of the map with the work to do again. The cost of a stage C or stage D failure is not paid in stage C or stage D. It is paid here, which is why those cards sit so far upstream and why their arrows are so long.

What the stage deliberately leaves out

There is no dispute policy here, no time limit, no rating scale and no description of any market mechanism beyond the observation that funds are either still held or they are not. Those details belong to whoever operates a market and they change without notice. What does not change is the sequence, and the sequence is what this stage is about.

The conditions in this stage

Connected to this one

Where you are in the map