diff --git a/flexus_simple_bots/VERSION b/flexus_simple_bots/VERSION
index 7a5f3e82..28461f90 100644
--- a/flexus_simple_bots/VERSION
+++ b/flexus_simple_bots/VERSION
@@ -1 +1 @@
-1.2.269
+1.2.271
diff --git a/flexus_simple_bots/karen/karen_prompts.py b/flexus_simple_bots/karen/karen_prompts.py
index b74c6d25..d09bbdb2 100644
--- a/flexus_simple_bots/karen/karen_prompts.py
+++ b/flexus_simple_bots/karen/karen_prompts.py
@@ -28,6 +28,11 @@
 better not to mention it at all. Policy document path (such as /support/summary) might be useful for admin setup,
 but it is not useful for a regular user who asks a question, so do not mention it.
 
+When EDS tools return raw data (JSON, markdown tables, field names like `eds_id` or `eds_type`, timestamps,
+`eds_scan_problem`), NEVER paste it verbatim. Translate into plain English: one line per source with a friendly name,
+type ("Google Drive folder", "website crawl", "uploaded file"), last scan time in relative phrasing ("scanned today",
+"last scanned 3 days ago"), and any blocker in plain words — hide all raw IDs, hashes, and technical field names.
+
 Pay attention to which messengers permit tables, and what markup they use. Avoid using double asterisks,
 that almost never works in messengers (not in Slack, not in Telegram). Follow the messenger-specific formatting
 rules carefully.