ei-tui 0.5.4 → 0.6.1

package/src/prompts/human/person-update.ts

@@ -1,4 +1,4 @@
-import type { PromptOutput } from "./types.js";
+import type { PromptOutput, ParticipantContext } from "./types.js";
 import type { Person, Message } from "../../core/types.js";
 import { formatMessagesAsPlaceholders } from "../message-utils.js";
 
@@ -10,11 +10,26 @@ export interface PersonUpdatePromptData {
   messages_context: Message[];
   messages_analyze: Message[];
   persona_name: string;
+  participant_context?: ParticipantContext;
+  known_identifier_types?: string[];
+}
+
+function participantContextSection(ctx: ParticipantContext | undefined): string {
+  if (!ctx) return "";
+  const lines: string[] = ["# Participant Context", "The following may help you understand who is in this conversation.", ""];
+  lines.push(`## Persona: ${ctx.persona_name}`);
+  if (ctx.persona_description) lines.push(ctx.persona_description);
+  lines.push("");
+  lines.push("## Human User");
+  if (ctx.human_name) lines.push(`Name: ${ctx.human_name}`);
+  if (ctx.human_age !== undefined) lines.push(`Age: ${ctx.human_age}`);
+  lines.push("");
+  return lines.join("\n");
 }
 
 function formatExistingPerson(person: Person): string {
   return JSON.stringify({
-    name: person.name,
+    identifiers: person.identifiers ?? [],
     description: person.description,
     sentiment: person.sentiment,
     relationship: person.relationship,
@@ -29,118 +44,159 @@ export function buildPersonUpdatePrompt(data: PersonUpdatePromptData): PromptOut
   }
 
   const personaName = data.persona_name;
+  const isNewItem = data.existing_item === null;
+  const humanName = data.participant_context?.human_name;
+
+  const builtInTypes = ['Full Name', 'First Name', 'Nickname', 'Email', 'GitHub', 'Discord',
+    'Roblox', 'Reddit', 'Twitter', 'FF14', 'Relationship', 'Ei Persona'];
+  const userTypes = data.known_identifier_types ?? [];
+  const allTypes = [...new Set([...builtInTypes, ...userTypes])].join(', ');
+
+  const personRelationship = data.existing_item?.relationship ?? data.new_person_relationship ?? 'Unknown';
+  const personName = data.existing_item?.name ?? data.new_person_name ?? 'Unknown';
+
+  // ── WHO YOU ARE ANALYZING ──────────────────────────────────────────────────
+  // This section anchors the model on the target person before anything else.
+  // Local models lose context from long prompts — this must be first.
+
+  const personFocusSection = isNewItem
+    ? `# WHO YOU ARE ANALYZING
+
+NEW PERSON — not yet in system
+Relationship: ${personRelationship}
+Name: ${personName === 'Unknown' ? 'Not yet known' : personName}${data.new_person_description ? `\nWhat we know: ${data.new_person_description}` : ''}
+
+Your ONLY job is to find information about the HUMAN USER's **${personRelationship}** in the conversation and create their record. Ignore all other people mentioned — they each have their own separate records.`
+    : `# WHO YOU ARE ANALYZING
+
+EXISTING PERSON RECORD — update only if the Most Recent Messages contain new information
+Name: ${personName}
+Relationship: ${personRelationship}
+
+Current record:
+\`\`\`json
+${formatExistingPerson(data.existing_item!)}
+\`\`\`
 
-  const nameSection = `The person's actual name, or the clearest available identifier.
+Your ONLY job is to update THIS SPECIFIC PERSON's record based on the Most Recent Messages. Ignore all other people mentioned — they each have their own separate records.`;
 
-Only update when you learn something more specific.
+  // ── TASK ──────────────────────────────────────────────────────────────────
 
-Examples: "Unknown woman" → "Carol", "Mom" → "Carol (Mom)", "David" → "David Kim"`;
+  const taskSection = isNewItem
+    ? `# Task
 
-  const descriptionSection = `A concise summary of who this person is and how they relate to the HUMAN USER. Personas use this to recognize this person and engage meaningfully when they come up.
+You are creating a new PERSON record based on what you find about the HUMAN USER's **${personRelationship}** in the conversation.
+
+The record you create will be referenced by personas in future conversations — keep it accurate, brief, and useful.`
+    : `# Task
+
+You are scanning a conversation to update a PERSON record in the HUMAN USER's life.
+
+Apply changes to the record above **ONLY IF DOING SO WILL PROVIDE THE HUMAN USER WITH A BETTER EXPERIENCE IN THE FUTURE**.
+
+Detail you add should:
+1. Be meaningful, accurate, or still true to the HUMAN USER in six months or more
+2. **NOT** already be present in the record above`;
+
+  // ── DESCRIPTION SECTION ───────────────────────────────────────────────────
+  // New: shorter, no "don't accumulate" guidance (nothing to accumulate yet)
+  // Existing: full synthesis guidance
+
+  const descriptionSection = isNewItem
+    ? `A concise summary of who this person is and how they relate to the HUMAN USER. Keep it brief and factual — only what you can confirm from the conversation.
+
+- Capture who this person IS — their role in the user's life
+- Be useful to a persona who's never heard this person's name before
+- 1-3 sentences maximum
+- If you know their birth date or birth year, include it as a date (e.g. "born 1986-10-28") — never as a current age (ages change, dates don't)
+
+**ABSOLUTELY VITAL**: Do **NOT** embellish. Record only what the user actually said or demonstrated.`
+    : `A concise summary of who this person is and how they relate to the HUMAN USER. Personas use this to recognize this person and engage meaningfully when they come up.
 
 ## CRITICAL: Synthesize, don't accumulate
 
 Every update must **rewrite** the description as a current-state summary. Never append to it.
 
-**Good description**: "Borfinda, partner of 12 years. Former marine biologist, now stay-at-home parent. Tends to ground the user when they spiral; dry sense of humor. Two kids together."
+**Good**: "Borfinda, partner of 12 years. Former marine biologist, now stay-at-home parent. Tends to ground the user when they spiral; dry sense of humor. Two kids together."
 
-**Bad description**: "Borfinda was mentioned when the user talked about moving. In a later conversation she came up again during the work stress discussion. Most recently the user said she was supportive."
+**Bad**: "Borfinda was mentioned when the user talked about moving. In a later conversation she came up again during the work stress discussion. Most recently the user said she was supportive."
 
 The description should:
 - Capture who this person IS — their role, characteristics, relationship texture
 - Include what the HUMAN USER has revealed about them over time
-- Be useful to a persona who's never heard this person's name before
 - Read as a brief, confident summary — not a log of when they were mentioned
+- Not exceed 3-4 sentences
 
 The description should NOT:
 - Append "Most recently:", "Latest mention:", or any temporal marker
 - Accumulate a session-by-session history of every time this person came up
 - Speculate about the person based on thin evidence
-- Exceed 3-4 sentences under any circumstances
+- Record someone's age — record their birth date or birth year instead (e.g. "born 1981" not "age 44")
 
 **ABSOLUTELY VITAL**: Do **NOT** embellish — personas use their own voice. Record what the user actually said or demonstrated, not your interpretation of its emotional significance.`;
 
-  const relationshipSection = `## Relationship (\`relationship\`)
+  // ── IDENTIFIERS ───────────────────────────────────────────────────────────
 
-How the HUMAN USER is currently related to this PERSON.
-
-Once known, this field changes infrequently — a "Father" may later be clarified to "Step-Father", but is unlikely to become "Uncle".
-
-Keep it concise and specific. Avoid vague labels.
-
-Examples: "Unknown" → "Coworker", "Mother" → "Step-Mother", "Fiance" → "Spouse", "AI Persona" → "AI Companion"`;
+  const identityGuard = humanName
+    ? `CRITICAL: The HUMAN USER is ${humanName}. They wrote these messages. Do NOT assign their names, nicknames, or handles as identifiers for this person's record — UNLESS this IS the user's own Self record (relationship: "Self").`
+    : `CRITICAL: The HUMAN USER wrote these messages. Do NOT assign their own names or handles as identifiers for this person's record — UNLESS this IS the user's own Self record (relationship: "Self"). Do NOT return \`relationship: "Self"\` unless you are certain this record is about the human user themselves.`;
 
-  const exposureSection = `## Desired Exposure (\`exposure_desired\`)
+  const isUnknownNewPerson = isNewItem && personName === 'Unknown';
+  const unknownIdentifierGuard = isUnknownNewPerson
+    ? `\nThis person's name is not yet known. ONLY add \`identifiers\` if their name, handle, or email is explicitly stated in the conversation about THEM specifically — not inferred, not guessed.`
+    : '';
 
-How much the HUMAN USER wants to talk about this PERSON.
+  const identifierSection = `${identityGuard}${unknownIdentifierGuard}
 
-Scale of 0.0 to 1.0:
-- 0.0: Never wants to hear about this PERSON again
-- 0.5: Average amount of engagement
-- 1.0: This PERSON is the sole focus of their existence
+If you spot a platform handle, username, email, nickname, or full name explicitly mentioned in the conversation that isn't already in the person's identifiers, include it in \`identifiers_to_add\` (updates) or \`identifiers\` (new records). Always mark exactly one identifier as \`"is_primary": true\` — prefer the most formal or complete name.
 
-Do not make micro-adjustments. Close enough is OK.
-
-## Exposure Impact (\`exposure_impact\`)
-
-Not in the current data — but include it in your response.
-
-How much this conversation should count toward exposure tracking:
-- "high": Long, detailed conversation exclusively about this PERSON
-- "medium": Long OR detailed conversation about this PERSON
-- "low": The conversation touched on this PERSON briefly
-- "none": Only alluded to or hinted at`;
-
-  const currentDetailsSection = data.existing_item
-    ? `\`\`\`json
-${formatExistingPerson(data.existing_item)}
-\`\`\`
+For persons with a known relationship (Father, Mother, Sibling, etc.), also look for informal terms the HUMAN USER uses to address or refer to THAT SPECIFIC PERSON (\`Dad\`, \`Pop\`, \`Mom\`, \`Sis\`, etc.) and add them as \`{ "type": "Relationship", "value": "..." }\` identifiers.
 
-You are UPDATING an existing PERSON.`
-    : `**NEW PERSON — NOT YET IN SYSTEM**
+NEVER add dates, ages, birthdays, or anniversaries as identifiers. These are not identifying labels — if known, include them in the description instead.
 
-You are CREATING a new PERSON from what was discovered:
-\`\`\`json
-{
-  "name": "${data.new_person_name ?? "Unknown"}",
-  "description": "${data.new_person_description ?? "Details unknown"}",
-  "relationship": "${data.new_person_relationship ?? "Unknown"}"
-}
-\`\`\`
+Known identifier types: ${allTypes}. If unsure of type, use \`Nickname\`.`;
 
-Return all fields based on what you find in the conversation.`;
+  // ── OUTPUT FORMAT ─────────────────────────────────────────────────────────
 
-  const jsonTemplate = `{
-    "name": "...",
+  const jsonTemplate = isNewItem
+    ? `{
+    "identifiers": [
+      { "type": "Full Name", "value": "Borfinda Lastname", "is_primary": true },
+      { "type": "Nickname", "value": "Borfi" }
+    ],
+    "description": "...",
+    "sentiment": 0.0,
+    "relationship": "Mother|Friend|Coworker|AI Companion|etc.",
+    "exposure_desired": 0.5,
+    "exposure_impact": "high|medium|low|none",
+    "quotes": [
+      { "text": "exact phrase from message", "reason": "why this matters" }
+    ]
+  }`
+    : `{
+    "identifiers_to_add": [{ "type": "GitHub", "value": "handle" }],
     "description": "...",
     "sentiment": 0.0,
     "relationship": "Mother|Friend|Coworker|AI Companion|etc.",
     "exposure_desired": 0.5,
     "exposure_impact": "high|medium|low|none",
     "quotes": [
-      {
-        "text": "exact phrase from message",
-        "reason": "why this matters"
-      }
+      { "text": "exact phrase from message", "reason": "why this matters" }
     ]
   }`;
 
-  const system = `# Task
-
-You are scanning a conversation to deeply understand a PERSON in the HUMAN USER's life.
+  // ── SYSTEM PROMPT ASSEMBLY ─────────────────────────────────────────────────
+  // Order: WHO (anchor) → task → participant context → field definitions →
+  //        output format. Person details are in WHO, not repeated at the bottom.
 
-Your job is to take that analysis and apply it to the record we already have **IF DOING SO WILL PROVIDE THE HUMAN USER WITH A BETTER EXPERIENCE IN THE FUTURE**.
+  const system = `${personFocusSection}
 
-This means detail you add should:
-1. Be meaningful, accurate, or still true to the HUMAN USER in six months or more
-2. **NOT** already be present in the description or name of the PERSON
+${taskSection}
 
-This PERSON will be recorded in the HUMAN USER's profile for agents and personas to later reference.
+${participantContextSection(data.participant_context)}# Field Definitions
 
-# Field Definitions
-
-## Name (\`name\`)
-${nameSection}
+## Identifiers
+${identifierSection}
 
 ## Description (\`description\`)
 ${descriptionSection}
@@ -158,40 +214,55 @@ Scale of -1.0 to 1.0:
 
 Do not make micro-adjustments. Close enough is OK.
 
-${relationshipSection}
+## Relationship (\`relationship\`)
 
-${exposureSection}
+How the HUMAN USER is currently related to this PERSON.
 
-## Quotes
+Once known, this field changes infrequently — a "Father" may later be clarified to "Step-Father", but is unlikely to become "Uncle".
+
+Keep it concise and specific. Avoid vague labels.
+
+Examples: "Unknown" → "Coworker", "Mother" → "Step-Mother", "Fiance" → "Spouse", "AI Persona" → "AI Companion"
+
+## Desired Exposure (\`exposure_desired\`)
+
+How much the HUMAN USER wants to talk about this PERSON.
+
+Scale of 0.0 to 1.0:
+- 0.0: Never wants to hear about this PERSON again
+- 0.5: Average amount of engagement
+- 1.0: This PERSON is the sole focus of their existence
+
+Do not make micro-adjustments. Close enough is OK.
 
-In addition to updating the PERSON, identify any **memorable, funny, important, or stand-out phrases** from the Most Recent Messages that relate to this PERSON.
+## Exposure Impact (\`exposure_impact\`)
 
-### What Makes a Quote Worth Preserving
+Not in the current data — but include it in your response.
+
+How much this conversation should count toward exposure tracking:
+- "high": Long, detailed conversation exclusively about this PERSON
+- "medium": Long OR detailed conversation about this PERSON
+- "low": The conversation touched on this PERSON briefly
+- "none": Only alluded to or hinted at
+
+## Quotes
+
+Identify any **memorable, funny, important, or stand-out phrases** from the Most Recent Messages that relate to this PERSON.
 
 **Prioritize:**
 - Humor, wit, colorful language, creative profanity
 - Emotional outbursts (positive or negative) — the raw stuff
 - Phrases that reveal how the HUMAN USER feels about this PERSON
 - Things you'd quote back to them later to make them laugh or think
-- Unique expressions or turns of phrase about or from this PERSON
-- Quotable moments from EITHER speaker — humans AND AI personas both say memorable things
 
-**NEVER extract these — they are NOT quotes:**
+**NEVER extract these:**
 - Technical identifiers: ARNs, URLs, file paths, UUIDs, config keys
-- AI agent self-talk: "I notice I'm in Plan Mode", "I'll start by...", status updates
-- AI apologies or acknowledgments: "You're absolutely right", "I apologize for that"
+- AI agent self-talk or apologies
 - Generic statements that could apply to anyone
-- Credentials, secrets, connection strings, or anything that looks like an access token
-
-**The litmus test**: Would you bring this up at a bar with a friend? Would it make someone laugh, think, or feel something?
-- "She's the only person who can make me feel simultaneously stupid and brilliant" → YES.
-- "Borfinda was mentioned in the context of the Minnesota discussion" → NO. That's a note, not a quote.
-
-**When in doubt, leave it out.** An empty quotes array is always acceptable.
 
-**CRITICAL**: Return the EXACT text as it appears in the message. **WE CAN ONLY USE IT IF WE FIND IT IN THE TEXT.**
+**CRITICAL**: Return the EXACT text as it appears in the message.
 
-# CRITICAL INSTRUCTIONS
+# Output
 
 ONLY ANALYZE the "Most Recent Messages". The "Earlier Conversation" is provided for context only — it has already been processed.
 
@@ -199,19 +270,17 @@ ONLY ANALYZE the "Most Recent Messages". The "Earlier Conversation" is provided
 ${jsonTemplate}
 \`\`\`
 
-When returning a record, **ALWAYS** include \`name\`, \`description\`, and \`sentiment\`.
+When returning a record, **ALWAYS** include \`description\` and \`sentiment\`. Do NOT return \`relationship: "Self"\` unless this record IS the human user themselves.
 
-If you find **NO EVIDENCE** of this PERSON in the "Most Recent Messages", respond with: \`{}\`
+If you find **NO EVIDENCE** of the HUMAN USER's **${personRelationship}** in the "Most Recent Messages", respond with: \`{}\`
 
 If **NO CHANGES** are required, respond with: \`{}\`
 
 An empty object is the MOST COMMON expected response.
-
-# Current Details of PERSON
-
-${currentDetailsSection}
 `;
 
+  // ── USER PROMPT ───────────────────────────────────────────────────────────
+
   const earlierSection =
     data.messages_context.length > 0
       ? `## Earlier Conversation
@@ -223,19 +292,25 @@ ${formatMessagesAsPlaceholders(data.messages_context, personaName)}
   const recentSection = `## Most Recent Messages
 ${formatMessagesAsPlaceholders(data.messages_analyze, personaName)}`;
 
+  const personReminder = personName !== 'Unknown'
+    ? `Remember: You are analyzing the record for **${personName}** (${personRelationship}). Focus only on information about this specific person.`
+    : `Remember: You are analyzing the record for the HUMAN USER's **${personRelationship}**. Focus only on information about this specific person.`;
+
   const user = `# Conversation
 ${earlierSection}${recentSection}
 
 ---
 
-Analyze the Most Recent Messages and update the PERSON if warranted.
+${personReminder}
+
+Analyze the Most Recent Messages and ${isNewItem ? 'create the PERSON record' : 'update the PERSON record'} if warranted.
 
 **Return JSON:**
 \`\`\`json
 ${jsonTemplate}
 \`\`\`
 
-If no changes are needed, respond with: \`{}\``;
+If no ${isNewItem ? 'information found' : 'changes are needed'}, respond with: \`{}\``;
 
   return { system, user };
 }

package/src/prompts/human/topic-update.ts

@@ -250,7 +250,7 @@ ONLY ANALYZE the "Most Recent Messages". The "Earlier Conversation" is provided
 ${jsonTemplate}
 \`\`\`
 
-When returning a record, **ALWAYS** include \`name\`, \`description\`, and \`sentiment\`.
+When returning a record, always include \`sentiment\`. Include \`name\` only if you are changing it; omit it to keep the existing name. Always include \`description\` when returning a record.
 
 If you find **NO EVIDENCE** of this TOPIC in the "Most Recent Messages", respond with: \`{}\`
 

package/src/prompts/human/types.ts

@@ -26,7 +26,10 @@ export interface TopicScanPromptData extends BaseScanPromptData {
   participant_context?: ParticipantContext;
 }
 
-export interface PersonScanPromptData extends BaseScanPromptData {}
+export interface PersonScanPromptData extends BaseScanPromptData {
+  participant_context?: ParticipantContext;
+  known_identifier_types?: string[];
+}
 
 export interface FactFindPromptData {
   persona_name: string;
@@ -50,6 +53,7 @@ export interface TopicScanCandidate {
 
 export interface PersonScanCandidate {
   name: string;
+  identifiers?: Array<{ type: string; value: string; is_primary?: boolean }>;
   description: string;
   relationship: string;
   reason: string;

package/src/prompts/index.ts

@@ -28,19 +28,12 @@ export type {
 
 export {
   buildPersonaTraitExtractionPrompt,
-  buildPersonaTopicScanPrompt,
-  buildPersonaTopicMatchPrompt,
-  buildPersonaTopicUpdatePrompt,
+  buildPersonaTopicRatingPrompt,
 } from "./persona/index.js";
 export type {
   PersonaTraitExtractionPromptData,
-  PersonaTopicScanPromptData,
-  PersonaTopicScanCandidate,
-  PersonaTopicScanResult,
-  PersonaTopicMatchPromptData,
-  PersonaTopicMatchResult,
-  PersonaTopicUpdatePromptData,
-  PersonaTopicUpdateResult,
+  PersonaTopicRatingPromptData,
+  PersonaTopicRatingResult,
   TraitResult,
 } from "./persona/types.js";
 

package/src/prompts/message-utils.ts

@@ -1,17 +1,12 @@
 import type { Message } from "../core/types.js";
+import { getMessageContent } from "../core/handlers/utils.js";
 
 const MESSAGE_PLACEHOLDER_REGEX = /\[mid:([a-zA-Z0-9_-]+):([^\]]+)\]/g;
 
-/**
- * Returns the display text for a message from its structured fields.
- * - action_response as _italics_
- * - verbal_response as plain text
- * - silence_reason shown so the user understands why a persona stayed silent
- */
 export function getMessageDisplayText(message: Message): string | null {
   const parts: string[] = [];
-  if (message.action_response) parts.push(`_${message.action_response}_`);
-  if (message.verbal_response) parts.push(message.verbal_response);
+  const content = getMessageContent(message);
+  if (content) parts.push(content);
   if (message.silence_reason) {
     const name = message.speaker_name ?? 'Persona';
     parts.push(`[${name} chose not to respond because: ${message.silence_reason}]`);
@@ -20,23 +15,14 @@ export function getMessageDisplayText(message: Message): string | null {
   return parts.join('\n\n');
 }
 
-/**
- * Builds the content string for a ChatMessage sent to the LLM.
- * Unlike getMessageDisplayText (which is for frontend rendering and skips silence),
- * this includes ALL structured fields so the persona has full conversational context:
- *   - action_response as _italics_
- *   - verbal_response as plain text
- *   - silence_reason as "You chose not to respond because: ..."
- */
 export function buildChatMessageContent(message: Message): string {
   const parts: string[] = [];
-  if (message.action_response) parts.push(`_${message.action_response}_`);
-  
-  // Synthesis messages: wrap with context for LLM, but stored value is clean prompt
-  if (message._synthesis && message.verbal_response) {
-    parts.push(`[The user used your conversation to generate an image. The full prompt was: "${message.verbal_response}"]`);
-  } else if (message.verbal_response) {
-    parts.push(message.verbal_response);
+  const content = getMessageContent(message);
+
+  if (message._synthesis && content) {
+    parts.push(`[The user used your conversation to generate an image. The full prompt was: "${content}"]`);
+  } else if (content) {
+    parts.push(content);
   }
   if (message.silence_reason) {
     parts.push(`You chose not to respond because: ${message.silence_reason}`);

package/src/prompts/persona/index.ts

@@ -1,16 +1,9 @@
 export { buildPersonaTraitExtractionPrompt } from "./traits.js";
-export { buildPersonaTopicScanPrompt } from "./topics-scan.js";
-export { buildPersonaTopicMatchPrompt } from "./topics-match.js";
-export { buildPersonaTopicUpdatePrompt } from "./topics-update.js";
+export { buildPersonaTopicRatingPrompt } from "./topics-rate.js";
 export type {
   PersonaTraitExtractionPromptData,
-  PersonaTopicScanPromptData,
-  PersonaTopicScanCandidate,
-  PersonaTopicScanResult,
-  PersonaTopicMatchPromptData,
-  PersonaTopicMatchResult,
-  PersonaTopicUpdatePromptData,
-  PersonaTopicUpdateResult,
+  PersonaTopicRatingPromptData,
+  PersonaTopicRatingResult,
   TraitResult,
   PromptOutput,
 } from "./types.js";

package/src/prompts/persona/topics-rate.ts

@@ -0,0 +1,95 @@
+import type { PersonaTopicRatingPromptData, PromptOutput } from "./types.js";
+import { formatMessagesAsPlaceholders } from "../message-utils.js";
+
+export function buildPersonaTopicRatingPrompt(data: PersonaTopicRatingPromptData): PromptOutput {
+  if (!data.persona_name) {
+    throw new Error("buildPersonaTopicRatingPrompt: persona_name is required");
+  }
+  if (!data.topics || data.topics.length === 0) {
+    throw new Error("buildPersonaTopicRatingPrompt: topics array is required and must not be empty");
+  }
+
+  const personaName = data.persona_name;
+
+  const topicList = data.topics
+    .map(t => `- **${t.name}**: ${t.description_hint}`)
+    .join("\n");
+
+  const system = `# Task
+
+You are rating how much each of ${personaName}'s topics was discussed in recent messages.
+
+Your ONLY job is to rate exposure for the provided topics. Do NOT invent new topics. Do NOT analyze deeply. Just rate what you observe.
+
+# ${personaName}'s Topics
+
+${topicList}
+
+# Rating Scale
+
+For each topic, rate how much it was discussed in the "Most Recent Messages":
+
+- **none**: Topic not mentioned or only trivial reference
+- **low**: Mentioned briefly (1-2 messages, passing reference)
+- **medium**: Discussed with some depth (3-5 messages or sustained engagement)
+- **high**: Major focus of conversation (6+ messages or intense discussion)
+
+# Critical Rules
+
+1. **ONLY rate what's actually in the messages**. Do not infer or imagine.
+2. **"none" is the expected answer for most topics most days**. Only rate higher if there's clear evidence.
+3. **Rate based on the Most Recent Messages section ONLY**. Earlier conversation is context.
+4. **Do NOT invent new topics**. Only rate the topics listed above.
+
+# Response Format
+
+Return JSON with ratings for each topic:
+
+\`\`\`json
+{
+  "ratings": [
+    {
+      "topic_id": "uuid-here",
+      "exposure_impact": "none"
+    },
+    {
+      "topic_id": "another-uuid",
+      "exposure_impact": "medium"
+    }
+  ]
+}
+\`\`\`
+
+**Return JSON only.**`;
+
+  const earlierSection = data.messages_context.length > 0
+    ? `## Earlier Conversation (context only)
+${formatMessagesAsPlaceholders(data.messages_context, personaName)}
+
+`
+    : '';
+
+  const recentSection = `## Most Recent Messages (rate exposure based on these)
+${formatMessagesAsPlaceholders(data.messages_analyze, personaName)}`;
+
+  const user = `# Conversation
+${earlierSection}${recentSection}
+
+---
+
+Rate how much each of ${personaName}'s topics was discussed in the "Most Recent Messages".
+
+**Return JSON:**
+\`\`\`json
+{
+  "ratings": [
+    {
+      "topic_id": "topic-uuid",
+      "exposure_impact": "none" | "low" | "medium" | "high"
+    }
+  ]
+}
+\`\`\``;
+
+  return { system, user };
+}