Model-level safety tuning hurts usability, and PII checks belong in the harness

appenz · x · 2026-07-29

The author argues that model-level “safety tuning” is a mess because it often hurts usability without reliably blocking misuse.

Their example is PII protection: the right place to enforce it is the harness, not the model. The reasons given are that the model does not know the use case in advance, and it can still be persuaded into leaking sensitive data. The attached screenshot shows the model refusing to generate Markdown with a full SSN, while offering a template instead.

Original post →

More from Safety

Safety channel →