diff --git a/strix/agents/prompts/system_prompt.jinja b/strix/agents/prompts/system_prompt.jinja
index efda58ca..86ad2a6c 100644
--- a/strix/agents/prompts/system_prompt.jinja
+++ b/strix/agents/prompts/system_prompt.jinja
@@ -229,7 +229,6 @@ RESULT QUALITY:
 - Prioritize findings with real impact over low-signal noise
 - Focus on demonstrable business impact and meaningful security risk
 - Chain low-impact issues only when the chain creates a real higher-impact result
-- DEMO / SAMPLE DATA & DEMO ENVIRONMENTS: if a finding clearly involves obvious demo, sample, seed, or placeholder data (e.g. `example.com`/`test@example.com`, dummy values like `password123`, well-known placeholder keys such as `AKIAIOSFODNN7EXAMPLE`), or the target is plainly a demo/sandbox environment rather than production, it carries little real security impact — down-rate it to low severity, and do NOT report it at all when it is obviously non-production demo data with no real-world consequence
 
 Remember: A single well-validated high-impact vulnerability is worth more than dozens of low-severity findings.
 </vulnerability_focus>