Everything publishes live.
The badge is the product.
CCW is a platform, not a gate. User posts appear immediately. The CCW Verified and CCW Authored badges are applied to already-live content by a human reviewer — and every change, by anyone, is on the permanent public record.
Every post on CCW belongs to one of three classes. The class is shown visibly on every post and in the feed — so you can tell at a glance who wrote it and what standing it carries.
User Post
Submitted by the public. Publishes immediately — no review gate. Protected under 47 U.S.C. § 230 as third-party content. CCW does not pre-screen, endorse, or verify user posts before they appear.
Submitters can edit their own post at any time. Every edit is timestamped in the public changelog. The original submission is preserved permanently.
CCW Verified
A user post that CCW has reviewed. The post was already live; a human reviewer examined the entire post, corrected or removed anything not meeting CCW standards, and documented a primary source for every change CCW made.
The badge signals that CCW stands behind the reviewed content — and steps outside § 230 to do so, relying on truth as an absolute defense. Sources are visible on the page. The full before-and-after changelog is at the bottom of the post.
CCW Authored
First-party content written by CCW. Not § 230 — CCW is the publisher and stands entirely on truth as the defense. Every claim is source-cited before publish. Sources are shown on the page.
The teal treatment is unmistakable by design: "CCW wrote this" must be instantly distinguishable from "a user wrote this" and "CCW reviewed this."
Submit → Publishes live → May be reviewed → May earn the badge.
Publish immediately
The submission form creates a live post. It is in the database and visible immediately. No queue. No approval. Section 230 applies because CCW has not reviewed or materially contributed to the content.
Two triggers queue a post for CCW review
Neither trigger hides or alters the live post — it keeps publishing as-is while queued:
- Correction request. Anyone can file one on any post via the "Request a correction" link at the bottom of the post page. It records the disputed claim and queues the post for whole-post review.
- Repeat-offender signal. When two or more posts reference the same officer, department, or official, those posts are automatically flagged into the review queue. The flag adds weight to the pattern — it never applies a badge.
Whole-post review
A CCW reviewer examines the entire flagged post against the ≥ 2 independent-source standard. Anything that does not meet the standard is corrected or removed. Every change CCW makes is documented with a primary source — court record, official document, or named-outlet reporting. The original user text is preserved in PostVersions.
Badge applied — by a human, explicitly
After review, the CCW Verified badge is applied by a human in the Access-gated admin panel. Triggers never auto-badge. The badge is always a deliberate act with a documented source. On publish: a new PostVersion snapshot is created, a CCW changelog entry with the source is written, and the post's content_class advances to ccw_verified.
Graduation to the static layer
A verified post graduates from the dynamic rendering layer (Worker, request-time) into the static layer (pre-built HTML, served from the CDN edge). The next deploy materializes it as a permanent static page — faster, cleaner for search, and the durable "never buried" form the record takes for the long run.
Every change, by anyone, is on the permanent public record.
At the bottom of every post with a history is a public changelog. It shows every edit — user or CCW — with a timestamp and a label. CCW entries that changed a factual claim also show the source CCW relied on. Nothing is silently overwritten. The original user submission is preserved as version 1, permanently.
This is simultaneously the credibility mechanism and the legal armor. When a subject challenges a verified entry, the full provenance of every claim — who wrote it, when, what changed, and what primary source backs each CCW change — is already on the page, public and verifiable. That record is what the truth defense runs on.
What the CCW Verified badge actually means: A human reviewer examined this post against ≥ 2 independent primary sources, documented their source for every change, and applied the badge explicitly. CCW stands behind the reviewed content — not under § 230, but on truth. The sources are on the page. The before-and-after is in the changelog.
What CCW Documents
- · Officers with documented misconduct in their official role
- · Departments with documented patterns of misconduct or liability
- · Prosecutors with documented patterns of declining to charge misconduct
- · Employment history across departments (gypsy-cop tracking)
- · Settlement amounts tied to specific incidents
- · Outcomes: criminal, civil, administrative
What CCW Does Not Document
- · Private individuals (not public officials in official capacity)
- · Private conduct with no nexus to official responsibilities
- · Off-duty personal conduct unrelated to the official role
- · Social media posts or anonymous forum claims (as evidence)
- · Speculation or editorialized characterization