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.

H2 · A close you can live with

A condition that must already be true

You can describe the problem in the market's own terms

The problem has to be expressible as a difference between what the listing said and what happened, with the dates attached.

Confirm by: Write the complaint in three sentences with no adjectives and see whether it still says anything.
Not this: Not a template. Templates read as templates, and a reader can tell.

A claim has parts; a mood does not

The condition is that the problem can be stated as a difference between two things: what the listing text said, and what is in front of you, with the dates attached. Three components make it a claim. A state, meaning what the order is and what did or did not arrive. A date. And a difference, meaning the specific point at which the listing text and the world stopped matching. Any account with those parts can be acted on, or rejected on its merits, which is also a result.

A complaint made of adjectives is a mood. Wrong, bad, useless, nothing like it was supposed to be. Each is a true report of your internal state and none is a report about the order. They cannot be agreed with or disagreed with, because they name no fact anybody could check.

This matters because of where the reader sits. Whoever reads the complaint is working from your text alone. They were not at your door. They cannot see the parcel, and they have no access to the argument you have been having in your head since yesterday. Everything they will ever know about the physical situation is what you typed, and a sentence that assumes shared knowledge has told them nothing.

Describing it in the market's own terms means using the vocabulary the system uses for its states and its objects, whatever those turn out to be, rather than the vocabulary of grievance. A reader working inside that system can locate a state you named correctly. They cannot locate a thing you invented a word for, and they will not spend long guessing.

Where the description gets its raw material

Escrow is still holding when the problem appears supplies the reader. It is what makes a careful description worth writing rather than merely satisfying to write.

The listing is one you have actually read supplies the other term of the comparison, and a difference needs two terms. Without it you have only what happened and no baseline. In practice that produces complaints which are really disappointments: the thing that arrived was not what you pictured, and the listing never said it would be.

The dates come from the same place. Quantities, forms and conditions are stated once in the listing and are not restated later. See also the answer that arrived before you spent anything, which is the other written record of what was agreed.

What a mood cannot carry

Downstream is feedback goes up after the outcome is known, and the connection is not obvious until you look at it. Orders reach outcomes because somebody stated a position that could be resolved one way or the other. A described problem produces a decision, even an unfavourable one, and a decision is a known outcome you can report honestly. A mood produces no decision. It produces a conversation that trails off and an order that ends by exhaustion.

That leaves you at the feedback card with nothing to report except how you felt about something that was never adjudicated, so you publish the feeling. In the record it is indistinguishable from a verdict about a resolved case, because the record has no column for how much was actually established. That is the point where one person's inability to describe a problem becomes everybody else's bad information.

Cannot holdThe reason it cannot
Feedback after the outcomeThere is no outcome to wait for. An undescribed problem does not resolve, it fades, and what gets published is the mood at the point of giving up.
Coming back as the same accountThe account persists, but it carries an unfinished argument and an entry written in frustration. You return to a mess you made rather than to a closed order.

There is a second cost, upstream rather than down. Everything from being able to log in a second time onward was satisfied in order to reach a position where your account of events counts for something. Reading the listing properly, asking a question first, keeping the value where it belonged: all of it was preparation for a moment when you would have to say precisely what went wrong. Failing here undoes none of that. It leaves it unspent, which produces the familiar complaint that doing everything properly changed nothing. It changed nothing at the last step, the only one where the preparation had to become words.

The message that reads as noise

You write it late, on the day you found out, and you write it hot. Four lines, mostly adjectives, one question mark on its own. It reads back strong, because it accurately expresses how annoyed you are, and that accuracy is easy to mistake for accuracy about the order.

It arrives to somebody holding your text and nothing else. Any reply asks for specifics: what state, what date, what the listing said. You now supply them from memory, and memory has been busy. The dates have softened into about a week ago. The listing text has been replaced in your head by your summary of it, which is a different and more favourable document. Whatever you send second is weaker than what you could have sent first, and it looks like a story that grew in the telling.

The confusion lands on the reader, who comes across as evasive. In fact the first message contained no decidable question, and everything after it is reconstruction under pressure.

Three sentences with the adjectives removed

Write the complaint, delete every adjective, and read what is left. The check is subtractive, which is why it works. A pass looks like three sentences that still carry a state, a date and one specific point where the listing text and the delivered thing disagree. A fail looks like sentences that collapse into nothing, or into a report that something arrived and you are unhappy. Read the survivors aloud as though you had not been there.

This site prints no template, deliberately. A template hands you the shape and lets you keep the absence: you fill the slots, it comes out looking like a complaint, and the one field only you could supply, the specific difference, is the field most likely to end up generic. Templates also circulate, so a reader who has seen the form reads the form rather than your facts and discounts the whole thing. Removing words fails loudly when there is nothing underneath. Filling boxes never does.

Not a script, and not a grievance

This card is not about being polite and not about being firm, because tone is not the variable. It is not how to read a card applied to complaints, and it describes no dispute procedure, because this site does not know one. It is about whether your text contains anything a stranger could act on.

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