Reviewer work

Review a case from assignment to recorded decision.

Qualify once. The queue assigns an eligible case. Read its record, submit a reasoned decision, and let account quorum determine the result.

Your next step

Open review work

Reviews are records-only and currently unpaid. No XMR moves in this release.

Review controls

How each case moves.

  1. 1

    Qualify

    A reviewer accepts the current policy, passes a rules check, waits through a cooldown, and completes calibration cases. Passing raises the cost of abuse; it does not prove identity.

  2. 2

    Receive a case

    The system assigns work from the oldest eligible cases. Sellers, buyers, and the operator do not choose their reviewers. Conflicts and prior participation exclude an account.

  3. 3

    Reach quorum

    Routine publication needs matching decisions from two distinct eligible accounts in a three-account pool. A disagreement calls the remaining reviewer; silence never counts as approval. Account quorum does not establish different human operators.

  4. 4

    Report a concern

    A signed-in account can record a bounded concern for a future report workflow. Reports do not automatically hide a public record or open a new panel in this release.

Failure modes

What the system must do when trust breaks.

Coordinated accounts

Cooldowns, calibration, low starting capacity, random cases, conflict exclusions, and recorded decision history raise the cost of a Sybil cluster and preserve evidence for later review. They do not prove separate human operators or prevent every coordinated vote.

False reports

A report records the concern and its target, but it does not automatically quarantine content. Publication, rejection, and appeal states remain authoritative until a separate report adjudication flow is implemented and tested.

Reviewer disappears

Assignments expire and return to the pool. A missed deadline does not approve, reject, release money, or lower the quorum.

Bad decision

The owner gets one appeal per revision. Appeal reviewers are new to the case, and an overturned removal waits through a 48-hour release delay rather than appearing instantly. That delay is not a second challenge process.

The honest boundary

Software cannot remove every legal or human judgment.

A production marketplace still needs a lawful emergency-response path for credible imminent harm and binding orders. That path can be held by a separately governed provider or threshold safety council; it should not be disguised as automatic consensus.

Current release: no mainnet custody, verified stake, mediator payout, or automatic settlement.

Read the operating rules →