shipwithjev

Blog / 17

AI Content Moderation: Judging Every Post Instead of Sampling

AI content moderation used to mean sampling. At decision-model prices you judge every post, comment, and review live. Architecture, costs, and limits.

Content moderation has always been a coverage problem wearing a policy costume. Every platform has rules; almost no platform has ever been able to apply them to everything users produce. So the real policy became sampling: review what gets reported, what the keyword filter flags, what goes viral enough to matter. Everything else ships unread, and everyone in trust and safety knows it.

The economics behind that compromise just moved. When a structured safety verdict costs a fraction of a cent and returns in milliseconds, "judge every post" stops being aspirational infrastructure and becomes a default setting. That's the shift this page is about.

The moderation stack, 2026 edition

Tier 1: rules. Slur lists, link bans, rate limits. Instant, free, dumb; keep them for the unambiguous floor.

Tier 2: decision-model verdicts on everything. Every post, comment, review, and bio gets a small set of structured questions from a model like Jev: Does this contain a threat against a person? Is this sexual content involving a minor context? Is this spam or coordinated promotion? Does this dox someone? One cataloged build runs exactly this shape, returning a probability per category (threat, harassment, spam, doxxing) against thresholds you set (build, behavior as reported by the author). At the price points documented across the directory (tens of thousands of verdicts for cents; see the cost table), universal coverage on a mid-size platform prices in lunch money.

Tier 3: escalation. Low-confidence verdicts and high-stakes categories go up: to a frontier model for nuanced context, then to trained human reviewers for the genuinely hard calls and anything with legal weight. Same cascade as the fraud build, same reason: near-frontier quality where it matters, tier-2 prices everywhere else.

Where the leverage actually is: question design

Moderation is the domain where vague judge questions do the most damage in both directions. "Is this toxic?" over-flags heated sports arguments and under-flags polite menace. The questions that work are your policy rewritten as rulings: "Does this post threaten or wish physical harm on a specific person or group?" is answerable; so is "Does this comment share a private individual's address, workplace, or contact details?" Write one question per policy clause, not one question per post. The full craft is in how to write judge questions, and it transfers directly.

Two operational rules moderation veterans will recognize. Log the verdict and the question version with every decision; when a user appeals or a regulator asks, "the model felt like it" is not an answer, but "flagged under policy question 7, version 3, confidence 0.94" is the start of one. And never let tier 2 take irreversible action alone: auto-hide pending review is a decision-model job; permanent bans are not.

Adjacent moderation jobs, same machine

Review authenticity: screening product reviews for authenticity and helpfulness before they publish, which is moderation defending your conversion rate instead of your community. Marketplace listings: prohibited-item screening at listing time. Live chat and streams: verdicts fast enough for real-time feeds, where the games-and-real-time latency numbers are the relevant evidence. UGC before it reaches an AI: judging user input for injection attempts before your own model consumes it, moderation's newest and weirdest frontier.

Frequently asked questions

How does AI content moderation work?

Incoming content gets structured policy questions answered by a model in milliseconds; confident verdicts act automatically (pass, hide, queue), uncertain ones escalate to bigger models and human reviewers. Rules handle the trivial floor, humans keep the hard ceiling.

Is AI moderation accurate enough to trust?

As a cascade with humans on appeals and edge cases, it outperforms sampling by definition: sampled systems never see most violations. Per-verdict accuracy depends heavily on question quality, which is where the engineering effort belongs.

What does it cost to moderate every post?

At builder-reported decision-model prices, a few questions across every item on a platform doing hundreds of thousands of posts a day lands in single-digit dollars. Reference numbers: what builds cost.

Can it handle context, sarcasm, and reclaimed language?

Tier 2 alone, imperfectly; that's what confidence thresholds and escalation exist for. The design goal isn't a perfect robot judge, it's routing 95 percent of clear cases instantly so human judgment concentrates on the 5 percent that need it.

Does this replace human moderators?

It replaces the impossible part of their job (reading everything) and sharpens the human part (ruling on ambiguity, handling appeals, updating policy). Teams that frame it as coverage-plus-focus get the wins; teams that frame it as headcount removal rediscover why appeals queues exist.

Numbers throughout are as reported by the build authors, not verified by shipwithjev. Code-shaped examples are pseudocode; the official docs live at docs.typesafe.ai.