How this is written

Every entry is the same shape. An expectation stated as somebody would actually say it, what the machinery does instead, and why the difference exists. If the third part is missing, the entry does not go up.

The rules

No verdicts

Nothing here is marked true or false. An expectation is not a claim, it is a guess made with a model borrowed from ordinary services, and grading it teaches nothing.

A mechanism every time

The interesting part is never that people are wrong. It is why the system produces that particular wrong answer so reliably.

Judgements are labelled

Where a page states an opinion, it says so in the sentence. Where a number would be a guess, no number appears.

Nothing is measured that cannot be

No uptime, no status, no last checked date, no proportion of vendors who are honest. This board has no way to know any of it.

The expectation is quoted fairly

It is written as a reasonable person would say it, not as a straw version that is easy to knock down.

Why the format is a pair

Advice pages fail in a specific way. They tell you what to do, you agree, and then the moment arrives and you do something else, because the advice was stored as a rule and the moment presents as an ordinary situation. Rules do not fire when nothing seems wrong, and nothing seems wrong is the normal condition of every failure on this board.

Naming the expectation works better because you recognise yourself in it. Once you have seen your own assumption written down and taken apart, the situation itself becomes the trigger rather than a remembered rule.

What the board covers and what it leaves out

• Covered: addresses, the front door, accounts, money, orders and disputes. All of it about the mechanics of using a platform.
• Not covered: products, sourcing, packaging, or anything about avoiding detection. Those are not the subject and will not be added.
• Not covered: the honesty of any particular vendor or platform. Nothing here can measure it.
• Not covered: anything requiring live knowledge. See the addresses page for why status claims are absent.

Where the material comes from

The expectations are the ones that show up repeatedly in public discussion, phrased the way people phrase them. The mechanisms are the ordinary published behaviour of onion services, chain payments, escrow processes and postal systems. None of it is inside knowledge and none of it needs to be, because these gaps are structural rather than secret.

Where an entry describes something that varies between platforms, it says so rather than stating a policy as universal. Escrow timers, confirmation counts and dispute deadlines all differ, and a board that pretended otherwise would be wrong in the most useful part of every page.

Corrections

A mechanism described wrongly here is worse than no page at all, because the format is confident by design. Anything demonstrably incorrect gets rewritten rather than annotated, and entries whose mechanism no longer holds get removed instead of being left up with a note.

Why there are no numbers

A board like this could easily carry statistics. How many orders end in a dispute, what share of vendors exit, how often a set rotates. All of it would be invented, because the data does not exist outside the platforms and would not be published honestly if it did. A made up figure is more damaging than no figure, since people remember numbers and act on them long after they have forgotten where the number came from.

The one count that appears anywhere here is the number of entries, which can be checked by reading them.

The full list of entries is on the home page, and the plain description of who publishes this is on the about page.