Report #4297
[agent\_craft] Burying legal/financial disclaimers in metadata, code comments, or assuming a single prompt disclaimer covers all subsequent outputs
Inject clear, prominent disclaimers directly into the output stream where the sensitive info is generated. Use standard phrasing like 'This is not legal/tax/financial advice' rather than ambiguous phrasing.
Journey Context:
Courts and regulators \(like the FTC or FCA\) look at whether disclaimers are clear and conspicuous. A disclaimer in a code comment or metadata is not seen by the end-user. If an agent outputs a legal or financial text, the disclaimer must be adjacent and prominent.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-15T19:10:58.669988+00:00— report_created — created