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.

G1 · A parcel that can arrive

A condition that must already be true

Somebody can take delivery at that address

On the day, at that address, there has to be a person or a place capable of accepting the item without redirecting it.

Confirm by: Ask what physically happens to an ordinary parcel at that address when nobody answers the door.
Not this: Not a delivery estimate. This site prints no timings and no expected windows.

Capacity to accept, on the day, at that door

The condition is narrow and physical. Somewhere behind that address there has to be a person, or a standing arrangement, that can take an ordinary parcel out of somebody else's hands and keep it. Not a person who lives there in general, but one present at the unknown moment the item turns up, or a place permitted to hold what turns up. The word doing the work is capable: capacity on the day, not intention and not ownership.

It is written around redirection because redirection is the real outcome. An item that cannot be handed over does not evaporate and does not wait at the door until you are free. It is taken somewhere else, and the somewhere else is a building with a counter, a queue, opening hours nobody consulted you about, and a person at the front who asks who you are and expects a document that answers. The carrier decides that, not you. The words this site uses for these states are collected in Words used here.

So the question is not whether the address can receive post. Almost every address can. It is whether this item, at the moment it arrives, meets something that ends its journey there. A shared entrance with an intercom nobody answers gives one answer, a house where somebody is always in gives another, and a workplace post room gives a third that holds only while the room is open.

The single line this rests on

One card sits above this one: the delivery address is written the way the post wants it. The dependency is blunt. A badly formatted address never reaches the door, so the question of who stands behind it is never asked. Sorting is mechanical and unsympathetic: a line in the wrong order, or a postcode in a shape the destination service does not use, resolves into somewhere else or into a tray a person works through later. Either way the item has left the path this card describes.

That ordering is not reversible. Format is a property of what you typed and can be corrected before you commit. Capacity to accept is a property of a building on a day, and no retyping changes it. On Dependency map this stage hangs off the order stage at two points, and this card is one of them.

What stalls behind a door nobody opened

Two cards wait on this one, and they fail in different ways.

The first is the name on the parcel fits the door it arrives at. A name is only tested when a handover is attempted. If nobody takes the item, the name is never read out, never queried, never accepted and never refused. The test is deferred, and it returns in a worse form. At a door the question is whether this address knows this name. At a counter it is whether you can prove you are that name, checked against different evidence entirely. So this card does not merely come before the name card. It decides which of the two tests the name is put through.

The second is feedback goes up after the outcome is known. An item held somewhere else is a suspended outcome: it has not arrived and it has not failed. Anything published in that state is a forecast dressed as a report, which is what that card exists to prevent. The failure here does not delay the ending. It removes the thing the ending describes.

Cannot holdThe reason it cannot
The name is tested at the doorNo handover is attempted, so nobody reads the name to anybody at that address.
A refusal stays cheap and localA refusal at a door ends there. A redirection ends at a counter with a queue and an identity check.
The order has an outcome to reportAn item held elsewhere has neither arrived nor failed, so there is nothing yet to describe.

There is a further effect not drawn as an edge. A parcel retrievable only by queueing and being identified is the sort of fact that makes people act, and the most tempting of those actions takes escrow is still holding when the problem appears with it. You can wait without doing anything absorbs that pressure far better when this card is true.

The failure nothing on your screen reports

Skipping this produces no signal where you are looking. The order state knows nothing about doors. You see a line of text saying what it said before, for longer than you expected, and a suspicion growing in whichever direction you were already inclined. The actual event was a card left in a communal hallway, an intercom nobody answered, or a signature taken by the neighbour who signs for everything and has since gone away.

So the confusion lands elsewhere. You re-read the address you typed and find nothing, because the address was fine. You go back to the listing, then to the other side, who can see less of this than you can. Any message any system produces points at the market, because the market is the only surface in front of you with messages on it. Hallways do not send notifications, and by the time a piece of paper surfaces, the item is somewhere that requires an identity check to leave.

A question you can answer without getting up

Ask what physically happens to an ordinary parcel at that address when nobody answers. You already know, because ordinary parcels have arrived there before. A pass is a specific, boring answer: it is left with a named neighbour, it goes into a secure box, somebody is always in, the post room signs for everything. A fail is an answer with a gap in it: it depends, usually somebody is around, they normally leave it somewhere. Usually describes the common case, which is not the case you are worried about.

If the honest answer is a counter, that is not automatically a fail. It fails only if you cannot or will not do what a counter requires, which is attend in person and be identified. Deciding that now is the job of you decided in advance what happens if nothing arrives. None of this needs a timing. You are establishing a capability, which is a state you can check today.

The check costs nothing, uses only what you already know about a building, and is the one part of stage G you can settle before anything is committed.

The border with the line above it

This is not the question of whether the post can find the address. That is upstream, and it is a fact about typing rather than about people. It is also not an estimate of when anything happens, because this site publishes no timings. How to read a card explains why every entry here is written as a state rather than as a step.

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