ei-tui 0.1.25 → 0.2.0

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

@@ -1,364 +0,0 @@
-import type { ItemUpdatePromptData, PromptOutput } from "./types.js";
-import type { DataItemBase } from "../../core/types.js";
-import { formatMessagesAsPlaceholders } from "../message-utils.js";
-
-const DESCRIPTION_MAX_CHARS = 500;
-
-function formatExistingItem(item: DataItemBase): string {
-  return JSON.stringify({
-    name: item.name,
-    description: item.description,
-    sentiment: item.sentiment,
-    ...('strength' in item ? { strength: (item as any).strength } : {}),
-    ...('relationship' in item ? { relationship: (item as any).relationship } : {}),
-    ...('exposure_current' in item ? { exposure_current: (item as any).exposure_current } : {}),
-    ...('exposure_desired' in item ? { exposure_desired: (item as any).exposure_desired } : {}),
-  }, null, 2);
-}
-
-export function buildHumanItemUpdatePrompt(data: ItemUpdatePromptData): PromptOutput {
-  if (!data.data_type || !data.persona_name) {
-    throw new Error("buildHumanItemUpdatePrompt: data_type and persona_name are required");
-  }
-
-  const typeLabel = data.data_type.toUpperCase();
-  const personaName = data.persona_name;
-
-  const nameSection = data.data_type === "fact" ? `
-Should represent the _type_ of FACT, not the _value_ of the fact.
-
-Examples: "User's Name", "Birthday", "Birthplace", "Hometown", "Job", "Marital Status", "Eye Color", "Hair Color", "Nationality/Citizenship", "Languages Spoken", "Educational Background", "Wedding Anniversary", "Job Anniversary", "Pet Ownership", "Allergies", "Medical Conditions", "Dietary Restrictions"
-
-The only time we should be changing the name of a FACT is if it cannot fit into one of these _types_.
-  `: `
-Should be a short identifier of the ${typeLabel}.
-
-Only update this field for clarification or if further specificity is warranted.
-
-Examples: "Unknown" -> "Brother-In-Law", "Alice's" -> "Alice's Restaurant"
-  `;
-
-  // This data isn't _specific_ to FACTS, but it only makes sense like this for them
-  const itemFactType = data?.existing_item?.name || data.new_item_name;
-  const traitDescriptionSection = `
-A brief characterization of how the Human demonstrates this trait. **1-2 sentences maximum.**
-
-## CRITICAL: Traits are STABLE PATTERNS, not conversation logs
-
-A trait description captures the PATTERN, not the evidence for it.
-
-**Good description**: "Approaches problems methodically, breaking them into smaller components before tackling the whole."
-**Bad description**: "In this exchange, Jeremy demonstrated analytical thinking when he discussed the schema changes, and in the previous conversation he showed the same pattern when..."
-
-The description should:
-- State the trait pattern concisely
-- Focus on HOW the trait manifests in general terms
-- Be useful for a persona meeting this human for the first time
-
-The description should NOT:
-- Reference specific conversations or exchanges
-- Accumulate examples over time ("In this exchange... In this latest exchange...")
-- Include timestamps, dates, or temporal references
-- Exceed 2-3 sentences under any circumstances
-
-**Style**: Write as if describing the person to someone who hasn't met them. Brief, evergreen, pattern-focused.
-
-Examples:
-- "Prefers direct communication; appreciates when others get to the point quickly."
-- "Processes emotions internally before discussing them; may need time before opening up."
-  `;
-
-  const factDescriptionSection = `
-A concise, specific piece of information about the Human's ${itemFactType}.
-
-If ${itemFactType} doesn't make sense as a type of FACT, return an empty object (\`{}\`).
-
-If ${itemFactType} was misinterpreted (i.e., a joke, expression, or otherwise "not literally" a fact), return an empty object (\`{}\`).
-
-## CRITICAL: Facts are OBJECTIVE
-
-FACTS are biographical/circumstantial data. NOT emotional interpretations.
-
-**Good description**: "Parents divorced twice. Second divorce occurred when user was 17/18."
-**Bad description**: "A deep, quiet ache related to mother's absence... a sacred absence shaped by love, loss, and quiet strength..."
-
-The description should record WHAT HAPPENED:
-- Dates, names, places, events, circumstances
-- What the user explicitly stated or clearly implied
-
-The description should NOT include:
-- Ei's poetic interpretation of emotional significance
-- Flowery language about "sacred absences" or "quiet aches"
-- Assumptions about how the user feels (that's what \`sentiment\` is for)
-
-If the user expressed emotion, quote or paraphrase THEIR words, don't embellish.
-
-**Style**: Be factual and concise. Record what the user said or demonstrated, not your interpretation of its deeper meaning. Avoid flowery or poetic language unless the user themselves used such language.
-
-Examples: "Name Unknown" -> "Robert Jordan", "User was married in the Summer" -> "User was married in July, 2006"
-  `;
-
-  const defaultDescriptionSection = `
-A concise, evergreen summary of what is currently known about this ${typeLabel}. Personas use this to recall context and make meaningful references.
-
-## CRITICAL: Synthesize, don't accumulate
-
-Every update must **rewrite** the description as a current-state summary. Never append to it.
-
-**Good description**: "Active project to improve test coverage. Settled on Vitest + E2E harness. Currently focused on pipeline integration and extraction logic coverage."
-**Bad description**: "User asked Sisyphus to create a ticket... Later: pruned overengineered framework... Most recent session: added PR checks..."
-
-The description should:
-- Capture what is true NOW — the current state, decisions made, where things stand
-- Include details a persona would use to show genuine recall ("Oh right, you were working on the pipeline tests")
-- Be useful to a persona meeting this human for the first time
-- Read as a brief summary paragraph, not a session log
-
-The description should NOT:
-- Append "Most recent:", "Latest:", "Current session:", or any temporal marker
-- Accumulate a running history of every conversation that touched this ${typeLabel}
-- Reference specific ticket numbers, commit hashes, or PR numbers unless essential to meaning
-- Exceed 3-4 sentences under any circumstances
-
-**ABSOLUTELY VITAL**: Do **NOT** embellish — personas use their own voice. Capture what is true, not a log of how you got here.
-  `;
-
-  const descriptionSection =
-    data.data_type === "fact" ? factDescriptionSection :
-    data.data_type === "trait" ? traitDescriptionSection :
-    defaultDescriptionSection;
-
-  const strengthSection = data.data_type === "trait" ? `
-## Strength (\`strength\`)
-
-How "strongly" the HUMAN USER shows this TRAIT.
-
-Use a scale of 0 to 1:
-- 0.0: The HUMAN USER is devoid of this trait
-- 0.5: The HUMAN USER shows this trait some of the time
-- 1.0: The HUMAN USER has this trait as a core aspect of their self
-
-Do not make micro-adjustments (0.4 -> 0.5). Close enough is OK for this field.` : '';
-
-  const relationshipSection = data.data_type === "person" ? `
-## Relationship (\`relationship\`)
-
-How the HUMAN USER is currently related to this PERSON.
-
-Once known, changes to this field are infrequent - A HUMAN USER's "Father" may be later clarified to "Step-Father", but is unlikely to become the user's "Uncle".
-
-Examples: "Unknown" -> "Coworker", "Mother" -> "Step-Mother", "Fiance" -> "Spouse"` : '';
-
-  const categorySection = data.data_type === "topic" ? `
-## Category (\`category\`)
-
-The type/category of this TOPIC. Pick the most appropriate from:
-- Interest: Hobbies, activities they enjoy
-- Goal: Things they want to achieve
-- Dream: Aspirational, maybe unrealistic desires  
-- Conflict: Internal struggles, dilemmas
-- Concern: Worries, anxieties
-- Fear: Things that scare them
-- Hope: Positive expectations for the future
-- Plan: Concrete intentions
-- Project: Active undertakings
-
-If the topic doesn't fit neatly, pick the closest match.` : '';
-
-  const exposureSection = (data.data_type === "topic" || data.data_type === "person") ? `
-## Desired Exposure (\`exposure_desired\`)
-
-Represents how much the HUMAN USER wants to talk about this ${typeLabel}.
-
-Scale of 0.0 to 1.0:
-- 0.0: The HUMAN USER never wants to hear about this ${typeLabel}
-- 0.5: The HUMAN USER spends an average amount of time on this ${typeLabel}
-- 1.0: This ${typeLabel} is the sole focus of the HUMAN USER's existence
-
-Do not make micro-adjustments. Close enough is OK for this field.
-
-## Exposure Impact (\`exposure_impact\`)
-
-This data point is NOT in the current data set, but it can be included in your return data.
-
-Exposure Impact measures how much exposure this conversation should count for:
-- "high": Long, detailed conversation exclusively about the ${typeLabel}
-- "medium": Long OR detailed conversation about the ${typeLabel}
-- "low": The conversation touched on this ${typeLabel} briefly
-- "none": The ${typeLabel} was only alluded to or hinted at
-
-This value adjusts the ongoing tracking of \`exposure_current\`.` : '';
-
-  const currentDetailsSection = data.existing_item 
-    ? `\`\`\`json
-${formatExistingItem(data.existing_item)}
-\`\`\`
-
-You are UPDATING an existing ${typeLabel}.`
-    : `**NEW ${typeLabel} - NOT YET IN SYSTEM**
-
-You are CREATING a new ${typeLabel} from scratch based on what was discovered:
-\`\`\`json
-{
-  "name": "${data.new_item_name || 'Uknown'}",
-  "description": "${data.new_item_value || 'Details Unknown'}"
-}
-\`\`\`
-
-Return all fields for this ${typeLabel} based on what you find in the conversation.`;
-
-  const jsonTemplateFields = [
-    '    "name": "User\'s Name",',
-    '    "description": "Their Actual Name",',
-    '    "sentiment": 0.0',
-    data.data_type === "trait" ? ',\n    "strength": 0.5' : '',
-    data.data_type === "person" ? ',\n    "relationship": "Mother-In-Law|Son|Coworker|etc.",\n    "exposure_desired": 0.4,\n    "exposure_impact": "high|medium|low|none"' : '',
-    data.data_type === "topic" ? ',\n    "category": "Interest|Goal|Dream|Conflict|Concern|Fear|Hope|Plan|Project",\n    "exposure_desired": 0.4,\n    "exposure_impact": "high|medium|low|none"' : '',
-    ',\n    "quotes": [\n      {\n        "text": "exact phrase from message",\n        "reason": "why this matters"\n      }\n    ]'
-  ].filter(Boolean).join('');
-
-  const system = `# Task
-
-You are scanning a conversation to deeply understand a ${typeLabel}.
-
-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**.
-
-This means that the 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 ${typeLabel}
-
-This ${typeLabel} will be recorded in the HUMAN USER's profile for agents and personas to later reference.
-
-# Field Definition and Explanation of Expected Changes
-
-## Name (\`name\`)
-${nameSection}
-## Description (\`description\`)
-${descriptionSection}
-## Sentiment (\`sentiment\`)
-
-Represents how strongly the HUMAN USER feels about this ${typeLabel}.
-
-Scale of -1.0 to 1.0:
-- -1.0: There is no ${typeLabel} the HUMAN USER hates more
-- -0.5: The HUMAN USER does NOT like this ${typeLabel}, but recognizes some redeeming qualities
-- 0: The HUMAN USER has no feelings toward this ${typeLabel}
-- 0.5: The HUMAN USER enjoys this ${typeLabel}, but can recognize flaws
-- 1.0: This ${typeLabel} is the sole focus of the HUMAN USER's existence
-
-Do not make micro-adjustments. Close enough is OK for this field.
-${strengthSection}${relationshipSection}${categorySection}${exposureSection}
-
-## Quotes
-
-In addition to updating the ${typeLabel}, identify any **memorable, funny, important, or stand-out phrases** from the Most Recent Messages that relate to this ${typeLabel}.
-
-### What Makes a Quote Worth Preserving
-
-**Prioritize:**
-- Humor, wit, colorful language, creative profanity
-- Emotional outbursts (positive or negative) — the raw stuff
-- Phrases that reveal personality or communication style
-- Things you'd quote back to them later to make them laugh
-- Unique expressions, malaphors, or turns of phrase
-- Quotable moments from EITHER speaker — humans AND AI personas both say memorable things
-
-**NEVER extract these — they are NOT quotes:**
-- Technical identifiers: ARNs, URLs, file paths, UUIDs, config keys, environment variable values, role/policy names
-- AI agent self-talk: "I notice I'm in Plan Mode", "I'll start by...", "Let me help you with...", status updates about the agent's own process
-- AI apologies or acknowledgments: "You're absolutely right", "I apologize for that overreach", "Good decision to revert"
-- Generic AI instructions or tips: "Remember to include X in your prompts", tool usage advice, workflow suggestions
-- Dry technical facts: infrastructure descriptions, process status, batch sizes, system architecture summaries
-- Status updates or process descriptions: "We're running a batch of...", "The pipeline is...", "I'm currently working on..."
-- Generic statements that could come from anyone or any AI session
-- 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?
-- "Does the Pope shit in his hat?" → YES. Hilarious malaphor.
-- "AWSReservedSSO_cmidp-nihl-sandbox-adm_db7b191e026bdd85" → NO. That's a credential.
-- "Slow is smooth. Smooth is fast." → YES (once). Pithy wisdom.
-- "The authentication flow is working correctly now" → NO. Status update.
-- "I built this, and now it's live." → YES. Pride and accomplishment.
-
-**When in doubt, leave it out.** An empty quotes array is always acceptable.
-
-Return them in the \`quotes\` array:
-
-\`\`\`json
-{
-  "name": "...",
-  "description": "...",
-  "sentiment": 0.5,
-  "quotes": [
-    {
-      "text": "exact phrase from the message",
-      "reason": "why this is worth preserving"
-    }
-  ]
-}
-\`\`\`
-
-**CRITICAL**: Return the EXACT text as it appears in the message (spacing, punctuation, formatting, etc.). WE CAN ONLY USE IT IF WE FIND IT IN THE TEXT.
-
-# CRITICAL INSTRUCTIONS
-
-ONLY ANALYZE the "Most Recent Messages" in the following conversation. The "Earlier Conversation" is provided for your context and has already been processed!
-
-The JSON format is:
-
-\`\`\`json
-{
-${jsonTemplateFields}
-}
-\`\`\`
-
-When you return a record, **ALWAYS** include every field (\`name\`, \`description\`, and \`sentiment\` are all REQUIRED fields).
-
-If you find **NO EVIDENCE** of this ${typeLabel} in the "Most Recent Messages", respond with an empty object: \`{}\`.
-
-If you determine **NO CHANGES** are required to the ${typeLabel}, respond with an empty object: \`{}\`.
-
-An empty object, \`{}\`, is the MOST COMMON expected response.
-
-# Current Details of ${typeLabel}
-
-${currentDetailsSection}
-`;
-
-  const earlierSection = data.messages_context.length > 0
-    ? `## Earlier Conversation
-${formatMessagesAsPlaceholders(data.messages_context, personaName)}
-
-`
-    : '';
-
-  const recentSection = `## Most Recent Messages
-${formatMessagesAsPlaceholders(data.messages_analyze, personaName)}`;
-
-  const user = `# Conversation
-${earlierSection}${recentSection}
-
----
-
-Analyze the Most Recent Messages and update the ${typeLabel} if warranted.
-
-**Return JSON:**
-\`\`\`json
-{
-${jsonTemplateFields}
-}
-\`\`\`
-
-If no changes are needed, respond with: \`{}\``;
-
-  return { system, user };
-}
-
-/**
- * Truncate a description to DESCRIPTION_MAX_CHARS for use in prompts.
- * The stored value is unchanged — this only affects what goes into the LLM context.
- */
-export function truncateDescription(description: string): string {
-  if (description.length <= DESCRIPTION_MAX_CHARS) return description;
-  return description.slice(0, DESCRIPTION_MAX_CHARS) + "…";
-}

package/src/prompts/human/trait-scan.ts

@@ -1,115 +0,0 @@
-import type { TraitScanPromptData, PromptOutput } from "./types.js";
-import { formatMessagesAsPlaceholders } from "../message-utils.js";
-
-export function buildHumanTraitScanPrompt(data: TraitScanPromptData): PromptOutput {
-  if (!data.persona_name) {
-    throw new Error("buildHumanTraitScanPrompt: persona_name is required");
-  }
-
-  const personaName = data.persona_name;
-
-  const taskFragment = `# Task
-
-You are scanning a conversation to quickly identify important TRAITS of the HUMAN USER. Your ONLY job is to spot admissions, observations, or other indicators of TRAITS. Do NOT analyze them deeply. Just detect and flag.`;
-
-  const specificNeedsFragment = `## Specific Needs
-
-Your job is to quickly identify:
-1. Which TRAITS were mentioned or observed
-    a. Only flag TRAITS that were actually discussed, not just tangentially related
-    b. Be CONSERVATIVE - only suggest genuinely important, long-term relevant TRAITS
-        i. Ignore: greetings, small talk, one-off mentions, jokes
-    c. Be CLEAR - state your \`reason\` for including this TRAIT with any evidence you used`;
-
-  const guidelinesFragment = `## Guidelines
-
-**A TRAIT Is:**
-* type_of_trait: Personality Patterns
-  * Values: Introverted, Reserved, Extroverted, Detail Oriented, Analytical
-* type_of_trait: Communication Style
-  * Assertive, Passive, Empathetic, Curious, Narrative
-* type_of_trait: Behavioral Tendencies
-  * Risk-Taker, Cautious, Spontaneous, Decisive
-* type_of_trait: Cognitive Style / Learning Approach
-  * Logical, Creative, Intuitive, Visual Learner
-* type_of_trait: Emotional Traits / Regulation
-  * Emotionally Resilient, Optimistic, Pessimistic, Calm, Anxious
-* type_of_trait: Work Ethic / Task Orientation
-  * Diligent, Proactive, Organized, Ambitious, Persistent
-* type_of_trait: Social Orientation
-  * Collaborative, Independent, Competitive, Supportive, Gregarious
-* type_of_trait: Approach to Change & Adversity
-  * Adaptable, Resilient, Flexible, Open-minded
-* type_of_trait: Motivational Drivers
-  * Achievement-Oriented, Altruistic, Curiosity-Driven
-* type_of_trait: Ethical & Moral Stance
-  * Principled, Honest, Integrity-Driven, Fair-minded
-
-**A TRAIT Is NOT:**
-- Biographical data: Name, Nickname, Birthday, Location, Job, Marital Status, Gender, Eye Color, Hair Color
-- Other unchangeable Data: Wedding Day, Allergies
-- General Topic: Interests, hobbies
-- People: Real people in their life: Wife, Husband, Daughter, Son, etc.
-- Personas: AI personas they discuss
-- Characters: Fictitious entities from books, movies, stories, media, etc.`;
-
-  const criticalFragment = `# CRITICAL INSTRUCTIONS
-
-ONLY ANALYZE the "Most Recent Messages" in the following conversation. The "Earlier Conversation" is provided for your context and has already been processed!
-
-The JSON format is:
-
-\`\`\`json
-{
-  "traits": [
-    {
-        "type_of_trait": "The type of trait from the list above",
-        "value_of_trait": "A short description of the trait",
-        "reason": "The justification of including this specific trait"
-    }
-  ]
-}
-\`\`\`
-
-**Return JSON only.**`;
-
-  const system = `${taskFragment}
-
-${specificNeedsFragment}
-
-${guidelinesFragment}
-
-${criticalFragment}`;
-
-  const earlierSection = data.messages_context.length > 0
-    ? `## Earlier Conversation
-${formatMessagesAsPlaceholders(data.messages_context, personaName)}
-
-`
-    : '';
-
-  const recentSection = `## Most Recent Messages
-${formatMessagesAsPlaceholders(data.messages_analyze, personaName)}`;
-
-  const user = `# Conversation
-${earlierSection}${recentSection}
-
----
-
-Scan the "Most Recent Messages" for TRAITS of the human user.
-
-**Return JSON:**
-\`\`\`json
-{
-  "traits": [
-    {
-        "type_of_trait": "The type of trait from the list above",
-        "value_of_trait": "A short description of the trait",
-        "reason": "The justification of including this specific trait"
-    }
-  ]
-}
-\`\`\``;
-
-  return { system, user };
-}