FAQ
How do reviews work?
The poster or the claimant triggers request_review. Validators fetch the submission URL (or inline text) and the source_url live inside a non-deterministic block, then an LLM returns strict JSON: per-requirement PASS/FIX, overall PASS/FIX/FAIL, reason, accessible. Consensus requires independent validators to re-run and agree on overall + per-requirement results. RETRY (model/fetch failure) and UNREADABLE (dead or login-gated link) do not consume an attempt.
What happens on Fix?
First FIX moves the bounty to NEEDS_FIXES — submit one revision. A second non-PASS ends the claim and reopens the bounty.
Can the poster reject work?
No. The brief is immutable and validators decide. The poster cannot reclaim funds while a valid claim is active, while a review is pending, or while an appeal window is open.
How do appeals work?
Once per bounty, within 24h of the review. The poster can appeal a PASS; the writer can appeal a FIX or FAIL. Attach exactly 0.001 GEN. The verdict is re-reviewed: upheld forfeits the bond, a flip returns it, and an inconclusive retry returns it. Appeals close once the bounty is paid.
Which links work?
Public GitHub files/PRs/gists, raw markdown, and public pages. Login-gated Google Docs, private Notion, dead links, and URL shorteners cannot be reviewed. Pages must be under 20,000 characters so validators see the whole work; oversized pages return RETRY instead of a silent partial verdict.
AI-written work?
Posters should state their stance in the brief. Validators cannot reliably detect AI text; there is no plagiarism detection in v1.
Supported languages?
Launch with major pairs (EN↔ES/FR/DE/PT). Low-resource language judging varies — say so in the brief.
Is this real money?
No. Prototype on GenLayer StudioNet. No real funds. Escrow is demo GEN only.