Danialebrat commited on
Commit
2ff618f
·
1 Parent(s): e1ed1b8

Revert "- modifying system prompts to have CTA"

Browse files

This reverts commit e1ed1b8cbdb37bf2299a8b1a2a8216d65709b7e4.

Config_files/message_system_config.json CHANGED
@@ -30,7 +30,7 @@
30
  "claude_models": ["claude-3-5-haiku-latest"],
31
  "inference_models": ["google/gemma-3-27b-instruct/bf-16", "meta-llama/llama-3.2-11b-instruct/fp-16"],
32
  "google_models": ["gemini-2.5-flash-lite", "gemini-2.5-flash", "gemini-2.0-flash"],
33
- "banned_contents": [373883, 358813, 301039, 377366, 404990, 286542]
34
  }
35
 
36
 
 
30
  "claude_models": ["claude-3-5-haiku-latest"],
31
  "inference_models": ["google/gemma-3-27b-instruct/bf-16", "meta-llama/llama-3.2-11b-instruct/fp-16"],
32
  "google_models": ["gemini-2.5-flash-lite", "gemini-2.5-flash", "gemini-2.0-flash"],
33
+ "banned_contents": [373883, 358813, 301039, 377366]
34
  }
35
 
36
 
Messaging_system/Message_generator.py CHANGED
@@ -179,9 +179,8 @@ class MessageGenerator:
179
 
180
  if self.Core.personalization:
181
  instructions = f"""
182
- Your task is to select the best 'header' and a 'message' for a {self.Core.get_instrument()} student as a push notification from given options.
183
  Based on the user instructions, you might need to **modify the selected option** very minimal and slightly to improve personalization if capable.
184
- Final modified version should have a proper call to action considering the instructions.
185
  **Important Note**: header < {self.Core.config_file["header_limit"]} and message < {self.Core.config_file["message_limit"]} characters.
186
 
187
  # Don't use below phrases, words, or similar variations of them:
 
179
 
180
  if self.Core.personalization:
181
  instructions = f"""
182
+ Your task is to select the best 'header' and a 'message' for a {self.Core.get_instrument()} student as a push notification.
183
  Based on the user instructions, you might need to **modify the selected option** very minimal and slightly to improve personalization if capable.
 
184
  **Important Note**: header < {self.Core.config_file["header_limit"]} and message < {self.Core.config_file["message_limit"]} characters.
185
 
186
  # Don't use below phrases, words, or similar variations of them:
Messaging_system/MultiMessage.py CHANGED
@@ -439,7 +439,6 @@ We have previously sent these push notifications to the user and The user has no
439
  instructions = f"""
440
  Your task is to select the best 'header' and a 'message' for a {self.Core.get_instrument()} student as a push notification.
441
  Based on the user instructions, you might need to **modify the selected option** very minimal and slightly to improve personalization if capable.
442
- Final modified version should have a proper call to action considering the instructions.
443
  **Important Note**: header < {self.Core.config_file["header_limit"]} and message < {self.Core.config_file["message_limit"]} characters.
444
 
445
  # Don't use below phrases, words, or similar variations of them:
 
439
  instructions = f"""
440
  Your task is to select the best 'header' and a 'message' for a {self.Core.get_instrument()} student as a push notification.
441
  Based on the user instructions, you might need to **modify the selected option** very minimal and slightly to improve personalization if capable.
 
442
  **Important Note**: header < {self.Core.config_file["header_limit"]} and message < {self.Core.config_file["message_limit"]} characters.
443
 
444
  # Don't use below phrases, words, or similar variations of them:
Messaging_system/PromptGenerator.py CHANGED
@@ -154,7 +154,7 @@ Below is the content we want to recommend to the user:
154
  When incorporating this content into the message and header, follow these guidelines to keep them friendly, relevant, and casual (not too scripted):
155
 
156
  1. **Title Usage**:
157
- - Refer to the **CONTENT_TITLE** or content details naturally in the message — paraphrase or describe it, but do *not* quote it or use it verbatim.
158
  - Avoid making it feel like a promotion; frame it as something that *might interest* or *help* the user.
159
 
160
  2. **Content Type Context**:
@@ -163,11 +163,10 @@ When incorporating this content into the message and header, follow these guidel
163
  3. **Artist/Instructor Name**:
164
  - If the full name of the **ARTIST** is available, mention it casually if appropriate (e.g., "led by Jordan Mitchell").
165
  - If only the first name is known, do *not* include it in the message at all.
166
- - Don't assume Artist name based on previous messages, only refer to Recommended Content Details
167
 
168
  4. **Tone & Style**:
169
  - Keep the tone light, supportive, and personal — like a helpful suggestion from a friend.
170
- - Avoid sounding pushy or overly promotional or marketing pitch.
171
 
172
  5. **Time References**
173
  - Do not refer to the content as “new,” “recent,” “latest,” or use any other time-related wording as the content might not be new.
@@ -175,6 +174,7 @@ When incorporating this content into the message and header, follow these guidel
175
  6. **Flexibility**:
176
  - You don’t need to include all elements every time. Prioritize what feels most relevant and natural based on the context.
177
 
 
178
  Goal: Make the recommendation feel personalized and casually relevant — not generic or copy-pasted.
179
  """
180
 
 
154
  When incorporating this content into the message and header, follow these guidelines to keep them friendly, relevant, and casual (not too scripted):
155
 
156
  1. **Title Usage**:
157
+ - Refer to the **CONTENT_TITLE** naturally in the message — paraphrase or describe it, but do *not* quote it or use it verbatim.
158
  - Avoid making it feel like a promotion; frame it as something that *might interest* or *help* the user.
159
 
160
  2. **Content Type Context**:
 
163
  3. **Artist/Instructor Name**:
164
  - If the full name of the **ARTIST** is available, mention it casually if appropriate (e.g., "led by Jordan Mitchell").
165
  - If only the first name is known, do *not* include it in the message at all.
 
166
 
167
  4. **Tone & Style**:
168
  - Keep the tone light, supportive, and personal — like a helpful suggestion from a friend.
169
+ - Avoid sounding pushy or overly promotional. Think friendly nudge, not marketing pitch.
170
 
171
  5. **Time References**
172
  - Do not refer to the content as “new,” “recent,” “latest,” or use any other time-related wording as the content might not be new.
 
174
  6. **Flexibility**:
175
  - You don’t need to include all elements every time. Prioritize what feels most relevant and natural based on the context.
176
 
177
+
178
  Goal: Make the recommendation feel personalized and casually relevant — not generic or copy-pasted.
179
  """
180
 
pianote_segment.csv CHANGED
The diff for this file is too large to render. See raw diff