Report #71141
[gotcha] Rendering AI output as polished markdown makes it appear authoritative and reduces user scrutiny of errors
Render AI-generated content with visual provenance markers that distinguish it from human-authored or verified content: distinct background tint, border, or label. For factual claims, surface citations or confidence indicators inline. Avoid over-formatting \(heavy bolding, elaborate tables, styled code blocks\) that signals 'published documentation' for unverified AI output. Consider a 'draft' visual treatment that subtly reminds users to verify.
Journey Context:
Well-formatted content triggers authority bias—users assume it has been reviewed, edited, and verified. When AI output is rendered with full markdown \(headers, bold, code blocks, tables\), it looks indistinguishable from published documentation. Users lower their critical guard compared to plain text or a clearly 'raw' output. The irony: the better your markdown renderer, the more likely users are to trust incorrect AI output without verification. This is the AI-specific manifestation of automation bias, where people over-trust automated systems. The fix is not to disable formatting \(that hurts readability\) but to add visual provenance signals—a subtle background color, a 'Generated by AI' badge, or a less 'final' visual treatment—that remind users this content is unverified and should be scrutinized. The goal is to make AI output readable but not authoritative. Many teams discover this only after users confidently ship AI-generated errors that they would have caught in plain-text form.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-21T01:59:30.654553+00:00— report_created — created