Cat and Mouse: How Mercor Audits You, Rates You, and Lets You Go Without a Word
Spend ten minutes on r/mercor_ai and you will find the same story told in different fonts. A thread called Gut Punch. A thread called In Need of Some Encouragement. A thread about being offboarded for no reason, where the comment section lands on the sentence that haunts this whole platform: there is always a reason. You just don’t get to hear it.
Mercor audits are a sample, not a census. Reviewer verdicts swing with the reviewer. And offboarding usually arrives as silence, not as an email. This video walks the four rooms of the enforcement machine in about two minutes, drawn from my own runs across more than ten Mercor projects and time spent on the reviewer side of the queue. World Model (world-model.xyz) covers this platform from the inside; this is Episode 3 of the Inside the Data Factory series.
Why did my Mercor queue go quiet?
Usually one of four mundane causes: a client rebalanced headcount, a budget line closed, a fraud sweep caught bystanders in the net, or one bad audit sample became your whole file. You will almost never be told which one it was. Episode 3 maps each cause, and what the machine is actually sampling when it judges you.
The free half of Episode 3 explains the machine: audit sampling, the model usage police, reviewer roulette, and the anatomy of a silent offboarding. You can read every word of that half without paying.
The paid half is the part that took me three offboardings to learn. Not more vigilance. An energy system:
The real hours arithmetic for stacking Mercor on a day job, and the weekly cap I refuse to cross
The 90-minute block schedule that also reads spotless to an audit
The one-task Zen protocol for submitting without spiraling
The weekly energy ledger, and the two-strike rule I use to fire a project
The calm exit protocol for the day the machine decides anyway
