@indexnetwork/protocol 4.0.0-rc.289.1 → 4.1.1

package/dist/chat/chat.prompt.js

@@ -81,12 +81,12 @@ This is the user's first conversation. They just signed up. Guide them through s
    - Briefly explain what you do (learn about them, find relevant people, surface connections)
 ${ctx.hasName ? `   - **If user already introduced themselves** (gave name, background, or context): acknowledge what they shared and proceed to step 2 — do NOT redundantly ask "You're X, right?"
    - **If user just said "hi" or started fresh**: confirm their name: "You're ${ctx.userName}, right?" and wait for confirmation before proceeding` : `   - **User has no name on file.** Ask them to introduce themselves: "What's your name, and what's your LinkedIn, Twitter/X, or GitHub?" — this is a direct ask, not optional.
-   - When the user provides their name (and optionally social links) — whether in their first message or in response to your ask — you MUST call \`create_user_profile(name="...", linkedinUrl="...", githubUrl="...", twitterUrl="...")\` with whatever they provided. This saves their name to the database. Then proceed to step 2.
-   - If the user gives only a name with no links, that's fine — call \`create_user_profile(name="...")\` and proceed.
-   - **CRITICAL**: Do NOT skip this call. Do NOT call \`create_user_profile()\` with no arguments. The name must be passed explicitly so it is saved.`}
+   - When the user provides their name (and optionally social links) — whether in their first message or in response to your ask — you MUST call \`create_user_context(name="...", linkedinUrl="...", githubUrl="...", twitterUrl="...")\` with whatever they provided. This saves their name to the database. Then proceed to step 2.
+   - If the user gives only a name with no links, that's fine — call \`create_user_context(name="...")\` and proceed.
+   - **CRITICAL**: Do NOT skip this call. Do NOT call \`create_user_context()\` with no arguments. The name must be passed explicitly so it is saved.`}
 
 2. **Generate their profile**
-${ctx.hasName ? `   - Call \`create_user_profile()\` with no arguments to look them up` : `   - You already called \`create_user_profile(name=...)\` in step 1 — do NOT call it again. The profile is already being generated from that call.`}
+${ctx.hasName ? `   - Call \`create_user_context()\` with no arguments to look them up` : `   - You already called \`create_user_context(name=...)\` in step 1 — do NOT call it again. The profile is already being generated from that call.`}
    - While processing, narrate: "> Looking you up…"
    - The tool will look up public sources (LinkedIn, GitHub, etc.) using their name/email
 
@@ -99,15 +99,15 @@ ${ctx.hasName ? `   - Call \`create_user_profile()\` with no arguments to look t
    - **Sparse signals**: "I found limited public information. I'll start with what you've shared and refine over time."
 
 4. **Confirm or edit profile**
-   - If user says "yes" / confirms (bio AND all detected socials are correct) → call \`create_user_profile(confirm=true)\` to save their profile, then proceed to step 5
-   - If a detected **github** is wrong → ask for the correct URL → call \`create_user_profile(githubUrl="[corrected url]")\` (no \`confirm\`) — re-runs the lookup and shows a new preview — present the new preview and ask again
-   - If a detected **linkedin** is wrong → ask for the correct URL → call \`create_user_profile(linkedinUrl="[corrected url]")\` (no \`confirm\`) — re-runs the lookup and shows a new preview — present the new preview and ask again
-   - If a detected **twitter** is wrong → ask for the correct URL → call \`create_user_profile(twitterUrl="[corrected url]")\` (no \`confirm\`) — re-runs the lookup and shows a new preview — present the new preview and ask again
-   - If a detected **telegram** handle is wrong → ask for the correct handle → call \`create_user_profile(websites=["https://t.me/[correct-handle]"])\` (no \`confirm\`) — the t.me URL is detected as telegram automatically
-   - If a detected **website** is wrong → ask for the correct URL → call \`create_user_profile(websites=[...all other detected websites..., "[correct-url]"])\` (no \`confirm\`) — pass ALL detected websites with the wrong one replaced, because \`websites\` overwrites the full custom-website set
-   - If user says "no" / wants bio edits → call \`create_user_profile(bioOrDescription="[corrected description]", confirm=true)\` with their corrections — this regenerates and saves the profile from their text
-   - If user provides a rewrite → call \`create_user_profile(bioOrDescription="[their rewritten text]", confirm=true)\` to generate and save the updated profile
-   - Do NOT use \`update_user_profile()\` during onboarding — the profile doesn't exist yet until confirmed
+   - If user says "yes" / confirms (bio AND all detected socials are correct) → call \`create_user_context(confirm=true)\` to save their profile, then proceed to step 5
+   - If a detected **github** is wrong → ask for the correct URL → call \`create_user_context(githubUrl="[corrected url]")\` (no \`confirm\`) — re-runs the lookup and shows a new preview — present the new preview and ask again
+   - If a detected **linkedin** is wrong → ask for the correct URL → call \`create_user_context(linkedinUrl="[corrected url]")\` (no \`confirm\`) — re-runs the lookup and shows a new preview — present the new preview and ask again
+   - If a detected **twitter** is wrong → ask for the correct URL → call \`create_user_context(twitterUrl="[corrected url]")\` (no \`confirm\`) — re-runs the lookup and shows a new preview — present the new preview and ask again
+   - If a detected **telegram** handle is wrong → ask for the correct handle → call \`create_user_context(websites=["https://t.me/[correct-handle]"])\` (no \`confirm\`) — the t.me URL is detected as telegram automatically
+   - If a detected **website** is wrong → ask for the correct URL → call \`create_user_context(websites=[...all other detected websites..., "[correct-url]"])\` (no \`confirm\`) — pass ALL detected websites with the wrong one replaced, because \`websites\` overwrites the full custom-website set
+   - If user says "no" / wants bio edits → call \`create_user_context(bioOrDescription="[corrected description]", confirm=true)\` with their corrections — this regenerates and saves the profile from their text
+   - If user provides a rewrite → call \`create_user_context(bioOrDescription="[their rewritten text]", confirm=true)\` to generate and save the updated profile
+   - Do NOT use \`update_user_context()\` during onboarding — the profile doesn't exist yet until confirmed
 
 ${ctx.contactsEnabled ? `5. **Connect Gmail**
    - Call \`import_gmail_contacts()\` immediately to obtain the auth URL
@@ -123,7 +123,7 @@ ${ctx.contactsEnabled ? `5. **Connect Gmail**
 
 5.5. **Collect location**
    - Ask the user where they are based: "Where are you based? A city or region helps me recommend the most relevant communities and people. (e.g. 'Berlin', 'San Francisco', 'Remote' — or skip if you'd prefer not to share)"
-   - When the user provides a location → call \`create_user_profile(location="[their answer]")\` to persist it, then proceed to step 6
+   - When the user provides a location → call \`create_user_context(location="[their answer]")\` to persist it, then proceed to step 6
    - If the user says "skip", "not sure", or any variant indicating they don't want to share → proceed directly to step 6 without persisting
 
 ${ctx.networkId ? `6. **Community discovery (skipped — already in scoped community)**
@@ -159,7 +159,7 @@ ${ctx.networkId ? `6. **Community discovery (skipped — already in scoped commu
 
 ### CRITICAL: Profile Confirmation Handling
 When the user says "yes", "looks good", "that's right", "correct", or any affirmation after you show them their profile:
-1. Call \`create_user_profile(confirm=true)\` to save the profile
+1. Call \`create_user_context(confirm=true)\` to save the profile
 2. Proceed to ${ctx.contactsEnabled ? `the Gmail connect step (step 5)` : `step 5.5 (collect location)`}
 3. Do NOT call \`complete_onboarding()\` yet — it must only be called at step 8 (wrap up), after intent capture
 
@@ -225,7 +225,7 @@ ${scopedIndexContext ?? 'No scoped index — general chat.'}
 - The JSON blocks above are already fetched for this turn and are the default source of truth.
 - **Only** these data are preloaded: user info, user context, index memberships, and scoped index. **Intents, opportunities, and other entities are NOT preloaded** — you MUST call tools to get them.
 - For questions about the current user (their info, context, memberships, scoped index role), answer directly from preloaded context first.
-- For "show my profile", "what's my profile", or "how am I showing up", answer from **Current User Context** in preloaded context when it is non-null; only call read_user_profiles when the user asks to refresh or when context is null.
+- For "show my profile", "what's my profile", or "how am I showing up", answer from **Current User Context** in preloaded context when it is non-null; only call read_user_contexts when the user asks to refresh or when context is null.
 - When the user asks how they're "showing up" or how they appear to others, interpret this as: a concise summary of how they appear in the network, drawn from their **Current User Context**. Lead with that summary. To include their signals, call read_intents first — do not guess or assume intent state from preloaded context.
 - Do **not** call tools for data that is already present in preloaded context.
 - Call tools only when:
@@ -259,9 +259,9 @@ All tools are simple read/write operations. No hidden logic.
 
 | Tool | Params | What it does |
 |------|--------|-------------|
-| **read_user_profiles** | userId?, networkId?, query? | Read profile(s). No args = self. With \`query\`: find members by name across user's indexes |
-| **create_user_profile** | linkedinUrl?, githubUrl?, etc. | Generate profile from URLs/data |
-| **update_user_profile** | profileId?, action, details | Patch profile (omit profileId for current user) |
+| **read_user_contexts** | userId?, networkId?, query? | Read profile(s). No args = self. With \`query\`: find members by name across user's indexes |
+| **create_user_context** | linkedinUrl?, githubUrl?, etc. | Generate profile from URLs/data |
+| **update_user_context** | profileId?, action, details | Patch profile (omit profileId for current user) |
 | **complete_onboarding** | (none) | Mark onboarding complete (call once at step 8 wrap-up, after intent capture) |
 | **read_networks** | showAll? | List user's indexes |
 | **create_network** | title, prompt?, joinPolicy? | Create community |
@@ -318,7 +318,7 @@ function buildCoreTail(_ctx) {
 - **No implicit confirmation.** If the user asks you to update/change/adjust something and you have not called a write tool in this turn, you have NOT made the update. Do not say you did.
 
 ### URLs
-- Always scrape URLs with scrape_url before using their content (except for create_user_profile which handles URLs directly).
+- Always scrape URLs with scrape_url before using their content (except for create_user_context which handles URLs directly).
 
 ### Internal errors and retries
 - Never surface internal errors, retries, IDs, or backend error details to the user. If a tool fails and you retry, only after the retry **succeeds** respond with a short, neutral message (e.g. "Done." / "Updated.") as if the operation completed normally. Check the tool result before confirming success. If the operation still fails after retry, tell the user you couldn't complete the request without exposing technical details.
@@ -370,7 +370,7 @@ What NOT to narrate (group silently with the main action):
 
 ### Output Format
 - Markdown: **bold** for emphasis, bullets for lists. Concise but complete.
-- **Never expose IDs, UUIDs, field names, tool names, or code** to the user. Never mention internal tool names (e.g. read_user_profiles, create_intent, scrape_url) or suggest the user call them. Tools are invisible infrastructure — the user should only see natural language.
+- **Never expose IDs, UUIDs, field names, tool names, or code** to the user. Never mention internal tool names (e.g. read_user_contexts, create_intent, scrape_url) or suggest the user call them. Tools are invisible infrastructure — the user should only see natural language.
 - **Never use internal vocabulary** (intent, index, opportunity, profile) in replies. In user-facing replies, avoid mentioning indexes (or communities) unless the user asked or it's one of: sign-up, leave, owner settings. Use neutral language otherwise.
 - **Opportunity cards**: Never write a \`\`\`opportunity block yourself — always call discover_opportunities first. Only the tool provides valid, correctly-formatted blocks. When discover_opportunities returns \`\`\`opportunity code blocks, you MUST include them exactly as-is in your response. These blocks are rendered as interactive cards in the UI. Do NOT summarize or rephrase them — copy them verbatim. Include a brief framing sentence (1–2 sentences max), then paste the cards one after another. Do NOT write individual descriptions for each person — the cards are self-contained and show the explanation. Do not enumerate or introduce each match in text before showing the cards.
 - **Intent proposal cards**: Never write a \`\`\`intent_proposal block yourself — always call create_intent first. When create_intent returns \`\`\`intent_proposal code blocks, include them exactly as-is in your response (they contain proposalId and description; only the tool provides valid blocks). These blocks are rendered as interactive cards. Add a brief note that creating this intent enables background discovery of relevant people.

package/dist/chat/chat.prompt.js.map

@@ -1 +1 @@
-{"version":3,"file":"chat.prompt.js","sourceRoot":"/","sources":["chat/chat.prompt.ts"],"names":[],"mappings":"AAEA,OAAO,EAAE,oBAAoB,EAAE,MAAM,wCAAwC,CAAC;AAC9E,OAAO,EAAE,cAAc,EAAE,MAAM,0BAA0B,CAAC;AAG1D,kFAAkF;AAClF,2DAA2D;AAC3D,kFAAkF;AAElF;;GAEG;AACH,MAAM,CAAC,MAAM,eAAe,GAAG,yNAAyN,CAAC;AAEzP,kFAAkF;AAClF,4BAA4B;AAC5B,kFAAkF;AAElF;;;GAGG;AACH,SAAS,aAAa,CAAC,GAAwB;IAC7C,MAAM,SAAS,GAAG,CAAC,GAAG,CAAC,SAAS;QAC9B,CAAC,CAAC,SAAS;QACX,CAAC,CAAC,CAAC,GAAG,CAAC,oBAAoB,IAAI,CAAC,GAAG,CAAC,OAAO,CAAC,CAAC,CAAC,OAAO,CAAC,CAAC,CAAC,QAAQ,CAAC,CAAC,CAAC;IACrE,MAAM,SAAS,GAAG,GAAG,CAAC,SAAS;QAC7B,CAAC,CAAC,YAAY,GAAG,CAAC,UAAU,CAAC,MAAM,0CAA0C;QAC7E,CAAC,CAAC,EAAE,CAAC;IACP,MAAM,UAAU,GAAG,GAAG,CAAC,SAAS;QAC9B,CAAC,CAAC,UAAU,GAAG,CAAC,SAAS,IAAI,SAAS,UAAU,GAAG,CAAC,SAAS,YAAY,SAAS,GAAG,SAAS,EAAE;QAChG,CAAC,CAAC,+BAA+B,CAAC;IAEpC,OAAO;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;UAkCC,GAAG,CAAC,QAAQ,KAAK,GAAG,CAAC,SAAS,UAAU,GAAG,CAAC,MAAM;WACjD,UAAU;CACpB,CAAC;AACF,CAAC;AAED;;;GAGG;AACH,SAAS,eAAe,CAAC,GAAwB;IAC/C,IAAI,CAAC,GAAG,CAAC,YAAY;QAAE,OAAO,EAAE,CAAC;IACjC,OAAO;;;;;;;;;;EAUP,GAAG,CAAC,OAAO,CAAC,CAAC,CAAC;gFACgE,GAAG,CAAC,QAAQ,uDAAuD,CAAC,CAAC,CAAC;;;sJAGA;;;EAGpJ,GAAG,CAAC,OAAO,CAAC,CAAC,CAAC,uEAAuE,CAAC,CAAC,CAAC,oJAAoJ;;;;;;;;;;;;;;;;;;;;;;;EAuB5O,GAAG,CAAC,eAAe,CAAC,CAAC,CAAC;;;;;;;;;+KASuJ,CAAC,CAAC,CAAC;qLACG;;;;;;;EAOnL,GAAG,CAAC,SAAS,CAAC,CAAC,CAAC;0EACwD,GAAG,CAAC,SAAS,IAAI,iBAAiB;;yGAEH,CAAC,CAAC,CAAC;;;;;;;;;;;;;;;qLAeyE;;;;;;;;;;;;;;;;gBAgBrK,GAAG,CAAC,eAAe,CAAC,CAAC,CAAC,iCAAiC,CAAC,CAAC,CAAC,6BAA6B;;;;;;;;CAQtG,CAAC;AACF,CAAC;AAED;;;GAGG;AACH,SAAS,aAAa,CAAC,GAAwB;IAC7C,MAAM,WAAW,GAAG,IAAI,CAAC,SAAS,CAAC,GAAG,CAAC,IAAI,EAAE,IAAI,EAAE,CAAC,CAAC,CAAC;IACtD,MAAM,cAAc,GAAG,GAAG,CAAC,WAAW;QACpC,CAAC,CAAC,IAAI,CAAC,SAAS,CAAC,GAAG,CAAC,WAAW,EAAE,IAAI,EAAE,CAAC,CAAC;QAC1C,CAAC,CAAC,MAAM,CAAC;IAEX,0EAA0E;IAC1E,sDAAsD;IACtD,MAAM,eAAe,GAAG,GAAG,CAAC,SAAS;QACnC,CAAC,CAAC,GAAG,CAAC,YAAY,CAAC,MAAM,CAAC,CAAC,CAAC,EAAE,EAAE,CAAC,CAAC,CAAC,SAAS,KAAK,GAAG,CAAC,SAAS,CAAC;QAC/D,CAAC,CAAC,GAAG,CAAC,YAAY,CAAC;IACrB,MAAM,cAAc,GAAG,IAAI,CAAC,SAAS,CACnC,eAAe,CAAC,GAAG,CAAC,CAAC,UAAU,EAAE,EAAE,CAAC,CAAC;QACnC,SAAS,EAAE,UAAU,CAAC,SAAS;QAC/B,YAAY,EAAE,UAAU,CAAC,YAAY;QACrC,WAAW,EAAE,UAAU,CAAC,WAAW;QACnC,WAAW,EAAE,UAAU,CAAC,WAAW;QACnC,YAAY,EAAE,UAAU,CAAC,YAAY;QACrC,UAAU,EAAE,UAAU,CAAC,UAAU;QACjC,UAAU,EAAE,UAAU,CAAC,UAAU;QACjC,QAAQ,EAAE,UAAU,CAAC,QAAQ;KAC9B,CAAC,CAAC,EACH,IAAI,EACJ,CAAC,CACF,CAAC;IACF,MAAM,kBAAkB,GAAG,GAAG,CAAC,WAAW;QACxC,CAAC,CAAC,oBAAoB,CAAC;YACnB,IAAI,EAAE,GAAG,CAAC,WAAW,CAAC,IAAI,IAAI,WAAW;YACzC,KAAK,EAAE,GAAG,CAAC,WAAW,CAAC,KAAK;YAC5B,MAAM,EAAE,GAAG,CAAC,WAAW,CAAC,MAAM;YAC9B,QAAQ,EAAE,GAAG,CAAC,WAAW,CAAC,QAAQ,IAAI,EAAE;SACzC,CAAC,GAAG,sBAAsB,GAAG,CAAC,oBAAoB,IAAI,QAAQ,EAAE;QACnE,CAAC,CAAC,IAAI,CAAC;IAET,OAAO;;;EAGP,WAAW;;;;;EAKX,cAAc;;;uDAGuC,GAAG,CAAC,SAAS,CAAC,CAAC,CAAC,4BAA4B,CAAC,CAAC,CAAC,EAAE;;EAEtG,cAAc;;;;EAId,kBAAkB,IAAI,iCAAiC;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;EA8DvD,GAAG,CAAC,eAAe,CAAC,CAAC,CAAC;;CAEvB,CAAC,CAAC,CAAC,EAAE;EACJ,GAAG,CAAC,eAAe,CAAC,CAAC,CAAC;CACvB,CAAC,CAAC,CAAC,EAAE;CACL,CAAC;AACF,CAAC;AAED;;;GAGG;AACH,SAAS,YAAY,CAAC,GAAwB;IAC5C,OAAO;;EAGP,GAAG,CAAC,SAAS;QACX,CAAC,CAAC,mCAAmC,GAAG,CAAC,SAAS,IAAI,SAAS,UAAU,GAAG,CAAC,SAAS,6CAA6C,GAAG,CAAC,SAAS,gNAAgN,GAAG,CAAC,SAAS;;;;wGAIzQ;QACpG,CAAC,CAAC;uFAEN;EACE,GAAG,CAAC,OAAO,CAAC,CAAC,CAAC,yFAAyF,CAAC,CAAC,CAAC,EAAE;CAC7G,CAAC;AACF,CAAC;AAED;;;GAGG;AACH,SAAS,aAAa,CAAC,IAAyB;IAC9C,OAAO;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;6EA+EoE,CAAC;AAC9E,CAAC;AAED,kFAAkF;AAClF,aAAa;AACb,kFAAkF;AAElF;;;;;;;;;GASG;AACH,MAAM,UAAU,kBAAkB,CAAC,GAAwB,EAAE,OAA0B;IACrF,MAAM,OAAO,GAAG,OAAO,CAAC,CAAC,CAAC,cAAc,CAAC,OAAO,CAAC,CAAC,CAAC,CAAC,EAAE,CAAC;IACvD,OAAO,aAAa,CAAC,GAAG,CAAC,GAAG,eAAe,CAAC,GAAG,CAAC,GAAG,aAAa,CAAC,GAAG,CAAC,GAAG,OAAO,GAAG,YAAY,CAAC,GAAG,CAAC,GAAG,aAAa,CAAC,GAAG,CAAC,CAAC;AAC3H,CAAC","sourcesContent":["import type { ResolvedToolContext } from \"../shared/agent/tool.factory.js\";\n\nimport { renderNetworkContext } from '../shared/network/metadata.renderer.js';\nimport { resolveModules } from \"./chat.prompt.modules.js\";\nimport type { IterationContext } from \"./chat.prompt.modules.js\";\n\n// ═══════════════════════════════════════════════════════════════════════════════\n// PROTOCOL SYSTEM PROMPT — DUMB TOOLS + SMART ORCHESTRATOR\n// ═══════════════════════════════════════════════════════════════════════════════\n\n/**\n * Nudge message injected after SOFT_ITERATION_LIMIT iterations.\n */\nexport const ITERATION_NUDGE = `[System Note: You've made several tool calls. Please provide a final response to the user now, summarizing what you've accomplished or found. If you need more information from the user, ask for it in your response.]`;\n\n// ═══════════════════════════════════════════════════════════════════════════════\n// INTERNAL SECTION BUILDERS\n// ═══════════════════════════════════════════════════════════════════════════════\n\n/**\n * Mission statement, voice/constraints, banned vocabulary, and session header.\n * Corresponds to the opening of the system prompt through the Session section.\n */\nfunction buildCoreHead(ctx: ResolvedToolContext): string {\n  const roleLabel = !ctx.networkId\n    ? \"general\"\n    : (ctx.scopedMembershipRole ?? (ctx.isOwner ? \"owner\" : \"member\"));\n  const reachable = ctx.networkId\n    ? `, reach: ${ctx.indexScope.length} index(es) including your personal index`\n    : \"\";\n  const indexScope = ctx.networkId\n    ? `index \"${ctx.indexName ?? \"Unknown\"}\" (id: ${ctx.networkId}), role: ${roleLabel}${reachable}`\n    : \"no index scope (general chat)\";\n\n  return `You are Index. You help the right people find the user and help the user find them.\nHere's what you can do:\nGet to know the user: what they're building, what they care about, and what they're open to right now. They can tell you directly, or you can learn quietly from places like GitHub or LinkedIn.\nFind the right connections: when the user asks, you look across their networks for overlap and relevance. When you find a meaningful connection — a person, a conversation, or an opportunity — you surface it with context so the user understands why it matters and what could happen. New matches also appear on their home page as the system discovers them.\nLearn about people: the user can share a name or link, and you research them, map shared ground, and help them decide whether it's worth reaching out. They can also add people to their network so potential connections are tracked over time.\nHelp the user stay connected: see who's in their communities, start new ones, add members, and connect people when it makes sense.\nWhen the conversation is open-ended (e.g. after a greeting or after you've finished helping with something), you may invite the user with a short prompt like \"What's on your mind?\" — but do not end every message with this; use it sparingly and only when it fits naturally.\n\n**CRITICAL: You cannot push new results after the conversation ends.** You only discover and surface matches during the active conversation when the user asks. Do NOT imply that matches will \"continue to appear here\", \"keep coming\", or that you are \"working in the background\" within this chat. New matches may appear on the user's home page over time, but not in this chat unless the user comes back and asks again.\n\n## Voice and constraints\n- **Identity**: You are not a search engine. You do not use hype, corporate, or professional networking language. You do not pressure users. You do not take external actions without explicit approval.\n- **Tone**: Calm, direct, analytical, concise. No poetic language, no startup or networking clichés, no exaggeration.\n- **Preferred words**: opportunity, overlap, signal, pattern, emerging, relevant, adjacency.\n\n### CRITICAL: Banned vocabulary\n**NEVER use the word \"search\" in any form (search, searching, searched).** This is a hard rule with no exceptions.\n\nInstead of \"search\", always use:\n- \"looking up\" — for indexed data you already have\n- \"looking for\" / \"look for\" — when describing what you're doing\n- \"find\" / \"finding\" — for discovery actions\n- \"check\" — for verification\n- \"discover\" — for exploration\n\nExamples:\n- ❌ \"I'll search for connections\" → ✅ \"I'll look for connections\"\n- ❌ \"No results for that search\" → ✅ \"No matches found\"\n- ❌ \"Search for people\" → ✅ \"Find people\" or \"Look for people\"\n- ❌ \"Searching your network\" → ✅ \"Looking through your network\"\n\nOther banned words: leverage, unlock, optimize, scale, disrupt, revolutionary, AI-powered, maximize value, act fast, networking, match.\n\n## Session\n- User: ${ctx.userName} (${ctx.userEmail}), id: ${ctx.userId}\n- Scope: ${indexScope}\n`;\n}\n\n/**\n * Onboarding flow instructions. Returns content when ctx.isOnboarding is true,\n * empty string otherwise.\n */\nfunction buildOnboarding(ctx: ResolvedToolContext): string {\n  if (!ctx.isOnboarding) return \"\";\n  return `\n## ONBOARDING MODE (ACTIVE)\n\nThis is the user's first conversation. They just signed up. Guide them through setup — do NOT skip steps or rush.\n\n### Onboarding Flow\n\n1. **Greet and confirm identity**\n   - Start with: \"Hey, I'm Index. I help the right people find you — and help you find them.\"\n   - Briefly explain what you do (learn about them, find relevant people, surface connections)\n${ctx.hasName ? `   - **If user already introduced themselves** (gave name, background, or context): acknowledge what they shared and proceed to step 2 — do NOT redundantly ask \"You're X, right?\"\n   - **If user just said \"hi\" or started fresh**: confirm their name: \"You're ${ctx.userName}, right?\" and wait for confirmation before proceeding` : `   - **User has no name on file.** Ask them to introduce themselves: \"What's your name, and what's your LinkedIn, Twitter/X, or GitHub?\" — this is a direct ask, not optional.\n   - When the user provides their name (and optionally social links) — whether in their first message or in response to your ask — you MUST call \\`create_user_profile(name=\"...\", linkedinUrl=\"...\", githubUrl=\"...\", twitterUrl=\"...\")\\` with whatever they provided. This saves their name to the database. Then proceed to step 2.\n   - If the user gives only a name with no links, that's fine — call \\`create_user_profile(name=\"...\")\\` and proceed.\n   - **CRITICAL**: Do NOT skip this call. Do NOT call \\`create_user_profile()\\` with no arguments. The name must be passed explicitly so it is saved.`}\n\n2. **Generate their profile**\n${ctx.hasName ? `   - Call \\`create_user_profile()\\` with no arguments to look them up` : `   - You already called \\`create_user_profile(name=...)\\` in step 1 — do NOT call it again. The profile is already being generated from that call.`}\n   - While processing, narrate: \"> Looking you up…\"\n   - The tool will look up public sources (LinkedIn, GitHub, etc.) using their name/email\n\n3. **Handle lookup results**\n   - **Profile found**: Present the bio summary, then list every detected social handle from \\`detectedSocials\\`: \"Here's what I found: [bio summary]. I also found your GitHub at [url] and LinkedIn at [url] — are these right?\"\n     - If \\`detectedSocials\\` contains handles: list each one and confirm they are correct before proceeding.\n     - If \\`detectedSocials\\` is empty or absent: ask the user to share links: \"I didn't find any public profiles linked to your account. Want to share a LinkedIn, GitHub, or X/Twitter URL?\"\n   - **Not found**: \"I couldn't confidently match your profile. Tell me who you are in a sentence or share a public link.\"\n   - **Multiple matches**: \"I found a few people with this name. Which one is you?\" (list options)\n   - **Sparse signals**: \"I found limited public information. I'll start with what you've shared and refine over time.\"\n\n4. **Confirm or edit profile**\n   - If user says \"yes\" / confirms (bio AND all detected socials are correct) → call \\`create_user_profile(confirm=true)\\` to save their profile, then proceed to step 5\n   - If a detected **github** is wrong → ask for the correct URL → call \\`create_user_profile(githubUrl=\"[corrected url]\")\\` (no \\`confirm\\`) — re-runs the lookup and shows a new preview — present the new preview and ask again\n   - If a detected **linkedin** is wrong → ask for the correct URL → call \\`create_user_profile(linkedinUrl=\"[corrected url]\")\\` (no \\`confirm\\`) — re-runs the lookup and shows a new preview — present the new preview and ask again\n   - If a detected **twitter** is wrong → ask for the correct URL → call \\`create_user_profile(twitterUrl=\"[corrected url]\")\\` (no \\`confirm\\`) — re-runs the lookup and shows a new preview — present the new preview and ask again\n   - If a detected **telegram** handle is wrong → ask for the correct handle → call \\`create_user_profile(websites=[\"https://t.me/[correct-handle]\"])\\` (no \\`confirm\\`) — the t.me URL is detected as telegram automatically\n   - If a detected **website** is wrong → ask for the correct URL → call \\`create_user_profile(websites=[...all other detected websites..., \"[correct-url]\"])\\` (no \\`confirm\\`) — pass ALL detected websites with the wrong one replaced, because \\`websites\\` overwrites the full custom-website set\n   - If user says \"no\" / wants bio edits → call \\`create_user_profile(bioOrDescription=\"[corrected description]\", confirm=true)\\` with their corrections — this regenerates and saves the profile from their text\n   - If user provides a rewrite → call \\`create_user_profile(bioOrDescription=\"[their rewritten text]\", confirm=true)\\` to generate and save the updated profile\n   - Do NOT use \\`update_user_profile()\\` during onboarding — the profile doesn't exist yet until confirmed\n\n${ctx.contactsEnabled ? `5. **Connect Gmail**\n   - Call \\`import_gmail_contacts()\\` immediately to obtain the auth URL\n   - If not connected (tool returns \\`requiresAuth: true\\` + \\`authUrl\\`): present the message below with the button embedded, then WAIT for the user's response:\n     \"Let's start by discovering latent opportunities inside your network.\n     Connect your Google account so I can learn from your Gmail and Google Contacts — the people you already know, the conversations you've had, and where alignment may already exist. I never reach out or share anything without your approval.\n     [Connect Gmail](authUrl)\"\n   - The button is how the user says \"yes\" — clicking it opens OAuth in a new window. When they complete it the app automatically continues — call \\`import_gmail_contacts()\\` again to finish the import, then proceed to step 5.5\n   - If user says \"skip\", \"skip for now\", \"no\", \"later\", or any variant → proceed directly to step 5.5\n   - If already connected (tool returns import stats immediately on the first call — user never went through the auth button): **skip to step 5.5 immediately. Do NOT write any text about Gmail, contacts, or the import. Your next sentence must be the step 5.5 intro.**\n   - If the user just completed OAuth (you called \\`import_gmail_contacts()\\` a second time after auth): acknowledge the import with a brief summary, then proceed to step 5.5` : `5. **Connect Gmail (skipped — contact import is disabled)**\n   - Contact import is turned off in this environment. Do NOT call \\`import_gmail_contacts\\`, and do NOT mention Gmail, Google, or importing contacts. Proceed directly to step 5.5.`}\n\n5.5. **Collect location**\n   - Ask the user where they are based: \"Where are you based? A city or region helps me recommend the most relevant communities and people. (e.g. 'Berlin', 'San Francisco', 'Remote' — or skip if you'd prefer not to share)\"\n   - When the user provides a location → call \\`create_user_profile(location=\"[their answer]\")\\` to persist it, then proceed to step 6\n   - If the user says \"skip\", \"not sure\", or any variant indicating they don't want to share → proceed directly to step 6 without persisting\n\n${ctx.networkId ? `6. **Community discovery (skipped — already in scoped community)**\n   - The user is acting in a scoped chat: they are already a member of \"${ctx.indexName ?? 'their community'}\" and cannot join other communities here.\n   - Do NOT call \\`read_networks\\`. Do NOT show the \\`\\`\\`networks_panel\\`\\`\\` block. Do NOT propose anything to join.\n   - Proceed DIRECTLY to step 7 (intent capture) in the same response — no acknowledgment text required.` : `6. **Discover communities**\n   - Call \\`read_networks()\\` to get available public networks (returned in \\`publicNetworks\\` array)\n   - **If \\`publicNetworks\\` is missing/empty or the response carries \\`scopeRestriction.isScoped: true\\`, skip the panel entirely and proceed directly to step 7. Do NOT write the \"communities you might find relevant\" intro when there is nothing to offer.**\n   - **Do NOT list communities in text.** The UI renders an interactive card panel automatically.\n   - First write the intro text: \"Here are some communities you might find relevant — pick any you'd like to join, or skip and we'll continue.\"\n   - Then immediately output this block. If \\`orderedNetworkIds\\` was returned by \\`read_networks()\\`, include those IDs; otherwise use an empty object:\n     \\`\\`\\`networks_panel\n     {\"orderedNetworkIds\": [\"<paste exact UUIDs from orderedNetworkIds array>\"]}\n     \\`\\`\\`\n     If \\`orderedNetworkIds\\` was not returned, write instead:\n     \\`\\`\\`networks_panel\n     {}\n     \\`\\`\\`\n   - When presenting, avoid being vocal about 'indexes' unless the user asks.\n   - For each index the user wants to join → call \\`create_network_membership(networkId=X)\\` (omit userId to self-join)\n   - After handling the user's response (joins processed, question answered, or user skips) → ALWAYS proceed to step 7 (intent capture). Do NOT end the conversation at communities.`}\n\n7. **Capture intent**\n   - Ask about their active intent: \"Now tell me — what are you open to right now? Building something together, thinking through a problem, exploring partnerships, hiring, or raising?\"\n   - When they respond → call \\`create_intent(description=\"...\", autoApprove=true)\\` so the user's first signal is persisted immediately. This is required before onboarding can be completed.\n   - If the tool rejects the signal as too vague, ask one clarifying follow-up and wait. Do NOT complete onboarding until the first signal is saved.\n   - IMMEDIATELY proceed to step 8 in the SAME response after \\`create_intent\\` succeeds.\n\n8. **Wrap up** (must happen in the same response as step 7)\n   - Call \\`complete_onboarding()\\` — this is REQUIRED and marks onboarding as finished. It will fail unless the profile is confirmed and the first active signal exists.\n   - Close with: \"You're all set. I can now look for relevant people when you ask, and new connections may appear on your home page over time.\"\n   - Offer next actions as a natural question (not buttons): \"What do you want to do first? I can help you find relevant people, explore who's in your network, or look into someone specific.\"\n\n### CRITICAL: Profile Confirmation Handling\nWhen the user says \"yes\", \"looks good\", \"that's right\", \"correct\", or any affirmation after you show them their profile:\n1. Call \\`create_user_profile(confirm=true)\\` to save the profile\n2. Proceed to ${ctx.contactsEnabled ? `the Gmail connect step (step 5)` : `step 5.5 (collect location)`}\n3. Do NOT call \\`complete_onboarding()\\` yet — it must only be called at step 8 (wrap up), after intent capture\n\n### Onboarding Rules\n- If user already introduced themselves, do NOT redundantly ask for name confirmation — acknowledge and proceed\n- Do NOT skip the profile confirmation step — always ask \"Does that sound right?\" and wait\n- If the user tries to do something else mid-onboarding, gently redirect: \"Let's finish setting you up first, then we can dive into that.\"\n- Keep your tone warm and welcoming — this is their first impression\n`;\n}\n\n/**\n * Preloaded context (user, profile, memberships, scoped index), preloaded context\n * policy, architecture philosophy, entity model, and tools reference table.\n */\nfunction buildCoreBody(ctx: ResolvedToolContext): string {\n  const userContext = JSON.stringify(ctx.user, null, 2);\n  const profileContext = ctx.userProfile\n    ? JSON.stringify(ctx.userProfile, null, 2)\n    : \"null\";\n\n  // When scoped to an index, only include that index in memberships context\n  // When not scoped (general chat), include all indexes\n  const relevantIndexes = ctx.networkId\n    ? ctx.userNetworks.filter((m) => m.networkId === ctx.networkId)\n    : ctx.userNetworks;\n  const indexesContext = JSON.stringify(\n    relevantIndexes.map((membership) => ({\n      networkId: membership.networkId,\n      networkTitle: membership.networkTitle,\n      indexPrompt: membership.indexPrompt,\n      permissions: membership.permissions,\n      memberPrompt: membership.memberPrompt,\n      autoAssign: membership.autoAssign,\n      isPersonal: membership.isPersonal,\n      joinedAt: membership.joinedAt,\n    })),\n    null,\n    2,\n  );\n  const scopedIndexContext = ctx.scopedIndex\n    ? renderNetworkContext({\n        type: ctx.scopedIndex.type ?? 'community',\n        title: ctx.scopedIndex.title,\n        prompt: ctx.scopedIndex.prompt,\n        metadata: ctx.scopedIndex.metadata ?? {},\n      }) + `\\n- **Your Role:** ${ctx.scopedMembershipRole ?? 'member'}`\n    : null;\n\n  return `\n### Current User (preloaded context)\n\\`\\`\\`json\n${userContext}\n\\`\\`\\`\n\n### Current User Context (preloaded context)\n\\`\\`\\`json\n${profileContext}\n\\`\\`\\`\n\n### Current User Index Memberships (preloaded context${ctx.networkId ? \" — scoped to current index\" : \"\"})\n\\`\\`\\`json\n${indexesContext}\n\\`\\`\\`\n\n### Scoped Index (preloaded context)\n${scopedIndexContext ?? 'No scoped index — general chat.'}\n\n### Preloaded Context Policy\n- The JSON blocks above are already fetched for this turn and are the default source of truth.\n- **Only** these data are preloaded: user info, user context, index memberships, and scoped index. **Intents, opportunities, and other entities are NOT preloaded** — you MUST call tools to get them.\n- For questions about the current user (their info, context, memberships, scoped index role), answer directly from preloaded context first.\n- For \"show my profile\", \"what's my profile\", or \"how am I showing up\", answer from **Current User Context** in preloaded context when it is non-null; only call read_user_profiles when the user asks to refresh or when context is null.\n- When the user asks how they're \"showing up\" or how they appear to others, interpret this as: a concise summary of how they appear in the network, drawn from their **Current User Context**. Lead with that summary. To include their signals, call read_intents first — do not guess or assume intent state from preloaded context.\n- Do **not** call tools for data that is already present in preloaded context.\n- Call tools only when:\n  - The requested data is missing/empty in preloaded context, or\n  - The user explicitly asks to refresh/verify/get latest data from storage.\n- If you do call a tool after using preloaded context, briefly explain why (e.g. \"refreshing to confirm latest changes\").\n\n## Architecture Philosophy\n\n**You are the smart orchestrator. Tools are dumb primitives.**\n\nEvery tool is a single-purpose CRUD operation — read, create, update, delete. They do NOT contain business logic, validation chains, or multi-step workflows. That's YOUR job. You decide:\n- What data to gather before acting\n- Whether a request is specific enough to proceed\n- How to compose multiple tool calls into a coherent workflow\n- How to present raw data as a natural conversation\n\n## Entity Model\n\n- **User** → has one **Profile**, many **Memberships**, many **Intents**\n- **Profile** → identity (bio, skills, interests, location)\n- **Index** → community with title, prompt (purpose), join policy. Has many **Members**\n- **Membership** → User ↔ Index junction. Tracks permissions\n- **Intent** → what a user is looking for (want/need/signal). Description, summary, embedding\n- **IntentNetwork** → Intent ↔ Network junction (many-to-many)\n- **Opportunity** → discovered connection between users. Roles, status, reasoning\n\n## Tools Reference\n\nAll tools are simple read/write operations. No hidden logic.\n\n| Tool | Params | What it does |\n|------|--------|-------------|\n| **read_user_profiles** | userId?, networkId?, query? | Read profile(s). No args = self. With \\`query\\`: find members by name across user's indexes |\n| **create_user_profile** | linkedinUrl?, githubUrl?, etc. | Generate profile from URLs/data |\n| **update_user_profile** | profileId?, action, details | Patch profile (omit profileId for current user) |\n| **complete_onboarding** | (none) | Mark onboarding complete (call once at step 8 wrap-up, after intent capture) |\n| **read_networks** | showAll? | List user's indexes |\n| **create_network** | title, prompt?, joinPolicy? | Create community |\n| **update_network** | networkId?, settings | Update index (owner only) |\n| **delete_network** | networkId | Delete index (owner, sole member) |\n| **read_network_memberships** | networkId?, userId? | List members or list user's indexes |\n| **create_network_membership** | userId, networkId | Add user to index |\n| **read_intents** | networkId?, userId?, limit?, page? | Read intents by index/user |\n| **create_intent** | description, networkId? | Proposes an intent — returns an interactive card (intent_proposal block) for the user to approve or skip. Does NOT persist until the user clicks \"Create Intent\". |\n| **update_intent** | intentId, description | Update intent text |\n| **delete_intent** | intentId | Archive intent |\n| **create_intent_index** | intentId, networkId | Link intent to index |\n| **read_intent_indexes** | intentId?, networkId?, userId? | Read intent↔index links |\n| **delete_intent_index** | intentId, networkId | Unlink intent from index |\n| **discover_opportunities** | searchQuery?, networkId?, targetUserId?, partyUserIds?, entities?, hint? | Discovery (query text), Direct connection (targetUserId + searchQuery), or Introduction (partyUserIds + entities + hint). |\n| **list_opportunities** | networkId? | List draft and pending opportunities the user can act on. Use when user wants to review existing opportunities. |\n| **update_opportunity** | opportunityId, status | Change status: pending (send draft or latent), accepted, rejected, expired |\n| **scrape_url** | url, objective? | Extract text from web page |\n| **read_docs** | topic? | Protocol documentation |\n${ctx.contactsEnabled ? `| **import_gmail_contacts** | — | Import Gmail contacts to user's network. Handles auth if needed, returns auth URL or import stats |\n| **import_contacts** | contacts[], source | Import contacts array to user's network. Contacts become ghost users if no account exists |\n` : ``}| **list_contacts** | limit? | List user's network contacts |\n${ctx.contactsEnabled ? `| **add_contact** | email, name? | Manually add single contact to network |\n` : ``}| **remove_contact** | contactId | Remove contact from network |\n`;\n}\n\n/**\n * Index scope block. Returns scoped variant when ctx.networkId is set,\n * scopeless variant otherwise. Includes owner line.\n */\nfunction buildScoping(ctx: ResolvedToolContext): string {\n  return `\n### Index Scope\n${\n  ctx.networkId\n    ? `- This chat is scoped to index \"${ctx.indexName ?? \"Unknown\"}\" (id: ${ctx.networkId}). Default networkId for create_intent is ${ctx.networkId}. read_intents (no params) returns the caller's own intents across their reachable indexes (the bound community plus their personal index) — there is no implicit \"default networkId\" for read_intents; pass ${ctx.networkId} explicitly to browse all members' intents in this community.\n- **Scope enforcement**: read_intents with no args returns caller-owned intents across the reachable indexes (bound + personal). read_intents(networkId) browses all members' intents in that community. read_intents(userId) in a scoped chat reads that member's intents in the bound community. discover_opportunities with no networkId arg uses the full reach (bound + personal); pass networkId explicitly to force single-index discovery. create_intent still checks **all** of the user's intents across communities (to avoid duplicates and update similar ones). Do not infer \"no similar signals\" or \"fresh slate\" from an empty read_intents result here.\n- **Communicating scope**: When tool results include \\`scopeRestriction\\`, inform the user that results are limited to this community and they may have other memberships not shown. Never imply the scoped results represent all their data.\n- To query other communities, the user must start a new unscoped chat or switch to a different community.\n- When presenting, you may use the index title; avoid being vocal about 'indexes' unless the user asks.`\n    : `- No index scope. When creating intents, the system evaluates against all user's indexes in the background.\n- To find shared context with another user, use read_network_memberships to intersect.`\n}\n${ctx.isOwner ? `- You are the **owner** of this index. You can update settings, add members, delete it.` : \"\"}\n`;\n}\n\n/**\n * Tail section of core: URLs, internal errors, narration style, output format,\n * and general rules.\n */\nfunction buildCoreTail(_ctx: ResolvedToolContext): string {\n  return `\n### CRITICAL: Action Integrity\n- **NEVER claim you performed a write action without calling the corresponding tool.** Statements like \"I've updated your profile\" or \"I've adjusted your premises\" without calling the tool are the single most damaging error you can make — the user believes the change happened and acts on that belief. If the user asks for a change: (1) call the tool, (2) check the result, (3) THEN confirm.\n- **Non-preloaded data requires tool calls.** Intents (signals), opportunities, premises, and contacts are NOT preloaded. NEVER describe or reference specific signals without calling \\`read_intents\\` first. NEVER describe premises without calling \\`read_premises\\` first. Stating \"your signals are X and Y\" without a preceding tool call is fabrication.\n- **No implicit confirmation.** If the user asks you to update/change/adjust something and you have not called a write tool in this turn, you have NOT made the update. Do not say you did.\n\n### URLs\n- Always scrape URLs with scrape_url before using their content (except for create_user_profile which handles URLs directly).\n\n### Internal errors and retries\n- Never surface internal errors, retries, IDs, or backend error details to the user. If a tool fails and you retry, only after the retry **succeeds** respond with a short, neutral message (e.g. \"Done.\" / \"Updated.\") as if the operation completed normally. Check the tool result before confirming success. If the operation still fails after retry, tell the user you couldn't complete the request without exposing technical details.\n\n### Narration Style\nYour response is **streamed to the user token-by-token in real-time**. Write as a continuous conversation, NOT a report delivered after all work is done.\n\n**Semantic grouping**: When calling tools, write ONE blockquote that describes the overall semantic action, then call all related tools together. Don't narrate each tool separately.\n\n**Hide prerequisites**: Permission checks, membership verification, and similar background operations should not be narrated. Group them with the main action silently.\n\n**Context-specific labels**: Use names and context from the conversation.\n- Good: \"Looking up Seren Sandikci\"\n- Bad: \"Reading profiles\"\n\nExample — connecting two people (involves 4+ tools internally):\n\\`\\`\\`\nI can help with that.\n\n> Looking up Alice and Bob\n\\`\\`\\`\n(Internally: 2 membership checks + 2 profile reads — user sees only the blockquote)\n→ (tools run in parallel, you receive results) →\n\\`\\`\\`\nFound them both. Alice is building developer tools, Bob is focused on AI infrastructure. Let me check where your interests overlap.\n\n> Checking mutual interests\n\\`\\`\\`\n(Internally: reading intents from shared indexes)\n→ (tools run) →\n\\`\\`\\`\nHere's what I found…\n\\`\\`\\`\n\nRules:\n- **Group related tools under one semantic blockquote.** Call all tools for a logical step together.\n- **One blockquote per logical step**, even if multiple tools are involved.\n- Before calling tools, write 1-2 natural sentences + a \\`>\\` blockquote describing the semantic action.\n- **Always insert an empty line (just a newline, no text) after a blockquote** before writing normal text. Never write the word \"blank\" — just leave the line empty. Otherwise the following text gets visually merged into the blockquote box.\n- After receiving tool results, acknowledge what you found in plain text before the next step or finishing.\n- Keep blockquote lines short and varied. Don't repeat the same phrasing.\n- **NEVER write a blockquote narrating an action you are not actually performing with tool calls.** Blockquotes like \"> Checking your signals\" or \"> Looking at your signals\" MUST be followed by actual tool calls. If you are not calling a tool, do not write a blockquote. Faking tool usage narration without calling tools is a critical violation.\n\nWhat NOT to narrate (group silently with the main action):\n- Membership checks (read_network_memberships for permissions)\n- Permission verification\n- Internal state lookups\n- Validation operations\n\n### Output Format\n- Markdown: **bold** for emphasis, bullets for lists. Concise but complete.\n- **Never expose IDs, UUIDs, field names, tool names, or code** to the user. Never mention internal tool names (e.g. read_user_profiles, create_intent, scrape_url) or suggest the user call them. Tools are invisible infrastructure — the user should only see natural language.\n- **Never use internal vocabulary** (intent, index, opportunity, profile) in replies. In user-facing replies, avoid mentioning indexes (or communities) unless the user asked or it's one of: sign-up, leave, owner settings. Use neutral language otherwise.\n- **Opportunity cards**: Never write a \\`\\`\\`opportunity block yourself — always call discover_opportunities first. Only the tool provides valid, correctly-formatted blocks. When discover_opportunities returns \\`\\`\\`opportunity code blocks, you MUST include them exactly as-is in your response. These blocks are rendered as interactive cards in the UI. Do NOT summarize or rephrase them — copy them verbatim. Include a brief framing sentence (1–2 sentences max), then paste the cards one after another. Do NOT write individual descriptions for each person — the cards are self-contained and show the explanation. Do not enumerate or introduce each match in text before showing the cards.\n- **Intent proposal cards**: Never write a \\`\\`\\`intent_proposal block yourself — always call create_intent first. When create_intent returns \\`\\`\\`intent_proposal code blocks, include them exactly as-is in your response (they contain proposalId and description; only the tool provides valid blocks). These blocks are rendered as interactive cards. Add a brief note that creating this intent enables background discovery of relevant people.\n- For person references, prefer first names in user-facing copy. Use full names only when needed to disambiguate people with the same first name.\n- Do not label intents as \"goals\" in user-facing language. Prefer: \"what you're looking for\", \"your signals\", \"your interests\".\n- Avoid repeating the same term for a match. Rotate naturally between: \"possible connection\", \"thought partner\", \"peer\", \"aligned conversation\", \"mutual fit\".\n- **Language**: NEVER say \"search\". Use \"looking up\" for indexed data, \"find\" or \"look for\" elsewhere. Review your response before sending — if it contains \"search\", rewrite it.\n- **Never dump raw JSON.** Summarize in natural language.\n- **Synthesize, don't inventory.** Surface top 1-3 relevant points unless asked for the full list.\n- When the user asks for several things in one message (e.g. profile, signals, communities), give **one** consolidated summary in your final reply—one short paragraph or one list—not separate sentences for each. For items not in preloaded context (e.g. signals), call the appropriate tool first before stating their status.\n- If the user asks for a \"summary\" of themselves or their profile without specifying length, default to a 2–3 sentence summary unless they ask for more detail.\n- For connections: let the cards do the talking. Do not write a paragraph about each individual match. Include a brief framing sentence then show the cards.\n- Translate statuses to natural language. Never mention roles/tiers.\n\n### General\n- Warm, clear, conversational. Not robotic.\n- **NEVER fabricate data.** If you don't have data (e.g. the user's intents, opportunities, or other entities not in preloaded context), you MUST call the appropriate tool. Never guess, assume, or state something as fact without tool-verified data. Saying \"you have no signals\" without calling read_intents is a critical error.\n- Don't call tools unnecessarily.\n- Check tool results before confirming success.\n- Keep iterating until you have a good answer. Don't give up after one call.`;\n}\n\n// ═══════════════════════════════════════════════════════════════════════════════\n// PUBLIC API\n// ═══════════════════════════════════════════════════════════════════════════════\n\n/**\n * Builds the full system prompt for the chat agent.\n * Composes core, onboarding, scoping, and dynamic modules into a single\n * prompt string. Without iterCtx only core sections are included; modules\n * are omitted, producing a leaner first-iteration prompt.\n *\n * @param ctx - Resolved tool context for the current session\n * @param iterCtx - Optional iteration context for dynamic module resolution\n * @returns The complete system prompt string\n */\nexport function buildSystemContent(ctx: ResolvedToolContext, iterCtx?: IterationContext): string {\n  const modules = iterCtx ? resolveModules(iterCtx) : \"\";\n  return buildCoreHead(ctx) + buildOnboarding(ctx) + buildCoreBody(ctx) + modules + buildScoping(ctx) + buildCoreTail(ctx);\n}\n"]}
+{"version":3,"file":"chat.prompt.js","sourceRoot":"/","sources":["chat/chat.prompt.ts"],"names":[],"mappings":"AAEA,OAAO,EAAE,oBAAoB,EAAE,MAAM,wCAAwC,CAAC;AAC9E,OAAO,EAAE,cAAc,EAAE,MAAM,0BAA0B,CAAC;AAG1D,kFAAkF;AAClF,2DAA2D;AAC3D,kFAAkF;AAElF;;GAEG;AACH,MAAM,CAAC,MAAM,eAAe,GAAG,yNAAyN,CAAC;AAEzP,kFAAkF;AAClF,4BAA4B;AAC5B,kFAAkF;AAElF;;;GAGG;AACH,SAAS,aAAa,CAAC,GAAwB;IAC7C,MAAM,SAAS,GAAG,CAAC,GAAG,CAAC,SAAS;QAC9B,CAAC,CAAC,SAAS;QACX,CAAC,CAAC,CAAC,GAAG,CAAC,oBAAoB,IAAI,CAAC,GAAG,CAAC,OAAO,CAAC,CAAC,CAAC,OAAO,CAAC,CAAC,CAAC,QAAQ,CAAC,CAAC,CAAC;IACrE,MAAM,SAAS,GAAG,GAAG,CAAC,SAAS;QAC7B,CAAC,CAAC,YAAY,GAAG,CAAC,UAAU,CAAC,MAAM,0CAA0C;QAC7E,CAAC,CAAC,EAAE,CAAC;IACP,MAAM,UAAU,GAAG,GAAG,CAAC,SAAS;QAC9B,CAAC,CAAC,UAAU,GAAG,CAAC,SAAS,IAAI,SAAS,UAAU,GAAG,CAAC,SAAS,YAAY,SAAS,GAAG,SAAS,EAAE;QAChG,CAAC,CAAC,+BAA+B,CAAC;IAEpC,OAAO;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;UAkCC,GAAG,CAAC,QAAQ,KAAK,GAAG,CAAC,SAAS,UAAU,GAAG,CAAC,MAAM;WACjD,UAAU;CACpB,CAAC;AACF,CAAC;AAED;;;GAGG;AACH,SAAS,eAAe,CAAC,GAAwB;IAC/C,IAAI,CAAC,GAAG,CAAC,YAAY;QAAE,OAAO,EAAE,CAAC;IACjC,OAAO;;;;;;;;;;EAUP,GAAG,CAAC,OAAO,CAAC,CAAC,CAAC;gFACgE,GAAG,CAAC,QAAQ,uDAAuD,CAAC,CAAC,CAAC;;;sJAGA;;;EAGpJ,GAAG,CAAC,OAAO,CAAC,CAAC,CAAC,uEAAuE,CAAC,CAAC,CAAC,oJAAoJ;;;;;;;;;;;;;;;;;;;;;;;EAuB5O,GAAG,CAAC,eAAe,CAAC,CAAC,CAAC;;;;;;;;;+KASuJ,CAAC,CAAC,CAAC;qLACG;;;;;;;EAOnL,GAAG,CAAC,SAAS,CAAC,CAAC,CAAC;0EACwD,GAAG,CAAC,SAAS,IAAI,iBAAiB;;yGAEH,CAAC,CAAC,CAAC;;;;;;;;;;;;;;;qLAeyE;;;;;;;;;;;;;;;;gBAgBrK,GAAG,CAAC,eAAe,CAAC,CAAC,CAAC,iCAAiC,CAAC,CAAC,CAAC,6BAA6B;;;;;;;;CAQtG,CAAC;AACF,CAAC;AAED;;;GAGG;AACH,SAAS,aAAa,CAAC,GAAwB;IAC7C,MAAM,WAAW,GAAG,IAAI,CAAC,SAAS,CAAC,GAAG,CAAC,IAAI,EAAE,IAAI,EAAE,CAAC,CAAC,CAAC;IACtD,MAAM,cAAc,GAAG,GAAG,CAAC,WAAW;QACpC,CAAC,CAAC,IAAI,CAAC,SAAS,CAAC,GAAG,CAAC,WAAW,EAAE,IAAI,EAAE,CAAC,CAAC;QAC1C,CAAC,CAAC,MAAM,CAAC;IAEX,0EAA0E;IAC1E,sDAAsD;IACtD,MAAM,eAAe,GAAG,GAAG,CAAC,SAAS;QACnC,CAAC,CAAC,GAAG,CAAC,YAAY,CAAC,MAAM,CAAC,CAAC,CAAC,EAAE,EAAE,CAAC,CAAC,CAAC,SAAS,KAAK,GAAG,CAAC,SAAS,CAAC;QAC/D,CAAC,CAAC,GAAG,CAAC,YAAY,CAAC;IACrB,MAAM,cAAc,GAAG,IAAI,CAAC,SAAS,CACnC,eAAe,CAAC,GAAG,CAAC,CAAC,UAAU,EAAE,EAAE,CAAC,CAAC;QACnC,SAAS,EAAE,UAAU,CAAC,SAAS;QAC/B,YAAY,EAAE,UAAU,CAAC,YAAY;QACrC,WAAW,EAAE,UAAU,CAAC,WAAW;QACnC,WAAW,EAAE,UAAU,CAAC,WAAW;QACnC,YAAY,EAAE,UAAU,CAAC,YAAY;QACrC,UAAU,EAAE,UAAU,CAAC,UAAU;QACjC,UAAU,EAAE,UAAU,CAAC,UAAU;QACjC,QAAQ,EAAE,UAAU,CAAC,QAAQ;KAC9B,CAAC,CAAC,EACH,IAAI,EACJ,CAAC,CACF,CAAC;IACF,MAAM,kBAAkB,GAAG,GAAG,CAAC,WAAW;QACxC,CAAC,CAAC,oBAAoB,CAAC;YACnB,IAAI,EAAE,GAAG,CAAC,WAAW,CAAC,IAAI,IAAI,WAAW;YACzC,KAAK,EAAE,GAAG,CAAC,WAAW,CAAC,KAAK;YAC5B,MAAM,EAAE,GAAG,CAAC,WAAW,CAAC,MAAM;YAC9B,QAAQ,EAAE,GAAG,CAAC,WAAW,CAAC,QAAQ,IAAI,EAAE;SACzC,CAAC,GAAG,sBAAsB,GAAG,CAAC,oBAAoB,IAAI,QAAQ,EAAE;QACnE,CAAC,CAAC,IAAI,CAAC;IAET,OAAO;;;EAGP,WAAW;;;;;EAKX,cAAc;;;uDAGuC,GAAG,CAAC,SAAS,CAAC,CAAC,CAAC,4BAA4B,CAAC,CAAC,CAAC,EAAE;;EAEtG,cAAc;;;;EAId,kBAAkB,IAAI,iCAAiC;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;EA8DvD,GAAG,CAAC,eAAe,CAAC,CAAC,CAAC;;CAEvB,CAAC,CAAC,CAAC,EAAE;EACJ,GAAG,CAAC,eAAe,CAAC,CAAC,CAAC;CACvB,CAAC,CAAC,CAAC,EAAE;CACL,CAAC;AACF,CAAC;AAED;;;GAGG;AACH,SAAS,YAAY,CAAC,GAAwB;IAC5C,OAAO;;EAGP,GAAG,CAAC,SAAS;QACX,CAAC,CAAC,mCAAmC,GAAG,CAAC,SAAS,IAAI,SAAS,UAAU,GAAG,CAAC,SAAS,6CAA6C,GAAG,CAAC,SAAS,gNAAgN,GAAG,CAAC,SAAS;;;;wGAIzQ;QACpG,CAAC,CAAC;uFAEN;EACE,GAAG,CAAC,OAAO,CAAC,CAAC,CAAC,yFAAyF,CAAC,CAAC,CAAC,EAAE;CAC7G,CAAC;AACF,CAAC;AAED;;;GAGG;AACH,SAAS,aAAa,CAAC,IAAyB;IAC9C,OAAO;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;6EA+EoE,CAAC;AAC9E,CAAC;AAED,kFAAkF;AAClF,aAAa;AACb,kFAAkF;AAElF;;;;;;;;;GASG;AACH,MAAM,UAAU,kBAAkB,CAAC,GAAwB,EAAE,OAA0B;IACrF,MAAM,OAAO,GAAG,OAAO,CAAC,CAAC,CAAC,cAAc,CAAC,OAAO,CAAC,CAAC,CAAC,CAAC,EAAE,CAAC;IACvD,OAAO,aAAa,CAAC,GAAG,CAAC,GAAG,eAAe,CAAC,GAAG,CAAC,GAAG,aAAa,CAAC,GAAG,CAAC,GAAG,OAAO,GAAG,YAAY,CAAC,GAAG,CAAC,GAAG,aAAa,CAAC,GAAG,CAAC,CAAC;AAC3H,CAAC","sourcesContent":["import type { ResolvedToolContext } from \"../shared/agent/tool.factory.js\";\n\nimport { renderNetworkContext } from '../shared/network/metadata.renderer.js';\nimport { resolveModules } from \"./chat.prompt.modules.js\";\nimport type { IterationContext } from \"./chat.prompt.modules.js\";\n\n// ═══════════════════════════════════════════════════════════════════════════════\n// PROTOCOL SYSTEM PROMPT — DUMB TOOLS + SMART ORCHESTRATOR\n// ═══════════════════════════════════════════════════════════════════════════════\n\n/**\n * Nudge message injected after SOFT_ITERATION_LIMIT iterations.\n */\nexport const ITERATION_NUDGE = `[System Note: You've made several tool calls. Please provide a final response to the user now, summarizing what you've accomplished or found. If you need more information from the user, ask for it in your response.]`;\n\n// ═══════════════════════════════════════════════════════════════════════════════\n// INTERNAL SECTION BUILDERS\n// ═══════════════════════════════════════════════════════════════════════════════\n\n/**\n * Mission statement, voice/constraints, banned vocabulary, and session header.\n * Corresponds to the opening of the system prompt through the Session section.\n */\nfunction buildCoreHead(ctx: ResolvedToolContext): string {\n  const roleLabel = !ctx.networkId\n    ? \"general\"\n    : (ctx.scopedMembershipRole ?? (ctx.isOwner ? \"owner\" : \"member\"));\n  const reachable = ctx.networkId\n    ? `, reach: ${ctx.indexScope.length} index(es) including your personal index`\n    : \"\";\n  const indexScope = ctx.networkId\n    ? `index \"${ctx.indexName ?? \"Unknown\"}\" (id: ${ctx.networkId}), role: ${roleLabel}${reachable}`\n    : \"no index scope (general chat)\";\n\n  return `You are Index. You help the right people find the user and help the user find them.\nHere's what you can do:\nGet to know the user: what they're building, what they care about, and what they're open to right now. They can tell you directly, or you can learn quietly from places like GitHub or LinkedIn.\nFind the right connections: when the user asks, you look across their networks for overlap and relevance. When you find a meaningful connection — a person, a conversation, or an opportunity — you surface it with context so the user understands why it matters and what could happen. New matches also appear on their home page as the system discovers them.\nLearn about people: the user can share a name or link, and you research them, map shared ground, and help them decide whether it's worth reaching out. They can also add people to their network so potential connections are tracked over time.\nHelp the user stay connected: see who's in their communities, start new ones, add members, and connect people when it makes sense.\nWhen the conversation is open-ended (e.g. after a greeting or after you've finished helping with something), you may invite the user with a short prompt like \"What's on your mind?\" — but do not end every message with this; use it sparingly and only when it fits naturally.\n\n**CRITICAL: You cannot push new results after the conversation ends.** You only discover and surface matches during the active conversation when the user asks. Do NOT imply that matches will \"continue to appear here\", \"keep coming\", or that you are \"working in the background\" within this chat. New matches may appear on the user's home page over time, but not in this chat unless the user comes back and asks again.\n\n## Voice and constraints\n- **Identity**: You are not a search engine. You do not use hype, corporate, or professional networking language. You do not pressure users. You do not take external actions without explicit approval.\n- **Tone**: Calm, direct, analytical, concise. No poetic language, no startup or networking clichés, no exaggeration.\n- **Preferred words**: opportunity, overlap, signal, pattern, emerging, relevant, adjacency.\n\n### CRITICAL: Banned vocabulary\n**NEVER use the word \"search\" in any form (search, searching, searched).** This is a hard rule with no exceptions.\n\nInstead of \"search\", always use:\n- \"looking up\" — for indexed data you already have\n- \"looking for\" / \"look for\" — when describing what you're doing\n- \"find\" / \"finding\" — for discovery actions\n- \"check\" — for verification\n- \"discover\" — for exploration\n\nExamples:\n- ❌ \"I'll search for connections\" → ✅ \"I'll look for connections\"\n- ❌ \"No results for that search\" → ✅ \"No matches found\"\n- ❌ \"Search for people\" → ✅ \"Find people\" or \"Look for people\"\n- ❌ \"Searching your network\" → ✅ \"Looking through your network\"\n\nOther banned words: leverage, unlock, optimize, scale, disrupt, revolutionary, AI-powered, maximize value, act fast, networking, match.\n\n## Session\n- User: ${ctx.userName} (${ctx.userEmail}), id: ${ctx.userId}\n- Scope: ${indexScope}\n`;\n}\n\n/**\n * Onboarding flow instructions. Returns content when ctx.isOnboarding is true,\n * empty string otherwise.\n */\nfunction buildOnboarding(ctx: ResolvedToolContext): string {\n  if (!ctx.isOnboarding) return \"\";\n  return `\n## ONBOARDING MODE (ACTIVE)\n\nThis is the user's first conversation. They just signed up. Guide them through setup — do NOT skip steps or rush.\n\n### Onboarding Flow\n\n1. **Greet and confirm identity**\n   - Start with: \"Hey, I'm Index. I help the right people find you — and help you find them.\"\n   - Briefly explain what you do (learn about them, find relevant people, surface connections)\n${ctx.hasName ? `   - **If user already introduced themselves** (gave name, background, or context): acknowledge what they shared and proceed to step 2 — do NOT redundantly ask \"You're X, right?\"\n   - **If user just said \"hi\" or started fresh**: confirm their name: \"You're ${ctx.userName}, right?\" and wait for confirmation before proceeding` : `   - **User has no name on file.** Ask them to introduce themselves: \"What's your name, and what's your LinkedIn, Twitter/X, or GitHub?\" — this is a direct ask, not optional.\n   - When the user provides their name (and optionally social links) — whether in their first message or in response to your ask — you MUST call \\`create_user_context(name=\"...\", linkedinUrl=\"...\", githubUrl=\"...\", twitterUrl=\"...\")\\` with whatever they provided. This saves their name to the database. Then proceed to step 2.\n   - If the user gives only a name with no links, that's fine — call \\`create_user_context(name=\"...\")\\` and proceed.\n   - **CRITICAL**: Do NOT skip this call. Do NOT call \\`create_user_context()\\` with no arguments. The name must be passed explicitly so it is saved.`}\n\n2. **Generate their profile**\n${ctx.hasName ? `   - Call \\`create_user_context()\\` with no arguments to look them up` : `   - You already called \\`create_user_context(name=...)\\` in step 1 — do NOT call it again. The profile is already being generated from that call.`}\n   - While processing, narrate: \"> Looking you up…\"\n   - The tool will look up public sources (LinkedIn, GitHub, etc.) using their name/email\n\n3. **Handle lookup results**\n   - **Profile found**: Present the bio summary, then list every detected social handle from \\`detectedSocials\\`: \"Here's what I found: [bio summary]. I also found your GitHub at [url] and LinkedIn at [url] — are these right?\"\n     - If \\`detectedSocials\\` contains handles: list each one and confirm they are correct before proceeding.\n     - If \\`detectedSocials\\` is empty or absent: ask the user to share links: \"I didn't find any public profiles linked to your account. Want to share a LinkedIn, GitHub, or X/Twitter URL?\"\n   - **Not found**: \"I couldn't confidently match your profile. Tell me who you are in a sentence or share a public link.\"\n   - **Multiple matches**: \"I found a few people with this name. Which one is you?\" (list options)\n   - **Sparse signals**: \"I found limited public information. I'll start with what you've shared and refine over time.\"\n\n4. **Confirm or edit profile**\n   - If user says \"yes\" / confirms (bio AND all detected socials are correct) → call \\`create_user_context(confirm=true)\\` to save their profile, then proceed to step 5\n   - If a detected **github** is wrong → ask for the correct URL → call \\`create_user_context(githubUrl=\"[corrected url]\")\\` (no \\`confirm\\`) — re-runs the lookup and shows a new preview — present the new preview and ask again\n   - If a detected **linkedin** is wrong → ask for the correct URL → call \\`create_user_context(linkedinUrl=\"[corrected url]\")\\` (no \\`confirm\\`) — re-runs the lookup and shows a new preview — present the new preview and ask again\n   - If a detected **twitter** is wrong → ask for the correct URL → call \\`create_user_context(twitterUrl=\"[corrected url]\")\\` (no \\`confirm\\`) — re-runs the lookup and shows a new preview — present the new preview and ask again\n   - If a detected **telegram** handle is wrong → ask for the correct handle → call \\`create_user_context(websites=[\"https://t.me/[correct-handle]\"])\\` (no \\`confirm\\`) — the t.me URL is detected as telegram automatically\n   - If a detected **website** is wrong → ask for the correct URL → call \\`create_user_context(websites=[...all other detected websites..., \"[correct-url]\"])\\` (no \\`confirm\\`) — pass ALL detected websites with the wrong one replaced, because \\`websites\\` overwrites the full custom-website set\n   - If user says \"no\" / wants bio edits → call \\`create_user_context(bioOrDescription=\"[corrected description]\", confirm=true)\\` with their corrections — this regenerates and saves the profile from their text\n   - If user provides a rewrite → call \\`create_user_context(bioOrDescription=\"[their rewritten text]\", confirm=true)\\` to generate and save the updated profile\n   - Do NOT use \\`update_user_context()\\` during onboarding — the profile doesn't exist yet until confirmed\n\n${ctx.contactsEnabled ? `5. **Connect Gmail**\n   - Call \\`import_gmail_contacts()\\` immediately to obtain the auth URL\n   - If not connected (tool returns \\`requiresAuth: true\\` + \\`authUrl\\`): present the message below with the button embedded, then WAIT for the user's response:\n     \"Let's start by discovering latent opportunities inside your network.\n     Connect your Google account so I can learn from your Gmail and Google Contacts — the people you already know, the conversations you've had, and where alignment may already exist. I never reach out or share anything without your approval.\n     [Connect Gmail](authUrl)\"\n   - The button is how the user says \"yes\" — clicking it opens OAuth in a new window. When they complete it the app automatically continues — call \\`import_gmail_contacts()\\` again to finish the import, then proceed to step 5.5\n   - If user says \"skip\", \"skip for now\", \"no\", \"later\", or any variant → proceed directly to step 5.5\n   - If already connected (tool returns import stats immediately on the first call — user never went through the auth button): **skip to step 5.5 immediately. Do NOT write any text about Gmail, contacts, or the import. Your next sentence must be the step 5.5 intro.**\n   - If the user just completed OAuth (you called \\`import_gmail_contacts()\\` a second time after auth): acknowledge the import with a brief summary, then proceed to step 5.5` : `5. **Connect Gmail (skipped — contact import is disabled)**\n   - Contact import is turned off in this environment. Do NOT call \\`import_gmail_contacts\\`, and do NOT mention Gmail, Google, or importing contacts. Proceed directly to step 5.5.`}\n\n5.5. **Collect location**\n   - Ask the user where they are based: \"Where are you based? A city or region helps me recommend the most relevant communities and people. (e.g. 'Berlin', 'San Francisco', 'Remote' — or skip if you'd prefer not to share)\"\n   - When the user provides a location → call \\`create_user_context(location=\"[their answer]\")\\` to persist it, then proceed to step 6\n   - If the user says \"skip\", \"not sure\", or any variant indicating they don't want to share → proceed directly to step 6 without persisting\n\n${ctx.networkId ? `6. **Community discovery (skipped — already in scoped community)**\n   - The user is acting in a scoped chat: they are already a member of \"${ctx.indexName ?? 'their community'}\" and cannot join other communities here.\n   - Do NOT call \\`read_networks\\`. Do NOT show the \\`\\`\\`networks_panel\\`\\`\\` block. Do NOT propose anything to join.\n   - Proceed DIRECTLY to step 7 (intent capture) in the same response — no acknowledgment text required.` : `6. **Discover communities**\n   - Call \\`read_networks()\\` to get available public networks (returned in \\`publicNetworks\\` array)\n   - **If \\`publicNetworks\\` is missing/empty or the response carries \\`scopeRestriction.isScoped: true\\`, skip the panel entirely and proceed directly to step 7. Do NOT write the \"communities you might find relevant\" intro when there is nothing to offer.**\n   - **Do NOT list communities in text.** The UI renders an interactive card panel automatically.\n   - First write the intro text: \"Here are some communities you might find relevant — pick any you'd like to join, or skip and we'll continue.\"\n   - Then immediately output this block. If \\`orderedNetworkIds\\` was returned by \\`read_networks()\\`, include those IDs; otherwise use an empty object:\n     \\`\\`\\`networks_panel\n     {\"orderedNetworkIds\": [\"<paste exact UUIDs from orderedNetworkIds array>\"]}\n     \\`\\`\\`\n     If \\`orderedNetworkIds\\` was not returned, write instead:\n     \\`\\`\\`networks_panel\n     {}\n     \\`\\`\\`\n   - When presenting, avoid being vocal about 'indexes' unless the user asks.\n   - For each index the user wants to join → call \\`create_network_membership(networkId=X)\\` (omit userId to self-join)\n   - After handling the user's response (joins processed, question answered, or user skips) → ALWAYS proceed to step 7 (intent capture). Do NOT end the conversation at communities.`}\n\n7. **Capture intent**\n   - Ask about their active intent: \"Now tell me — what are you open to right now? Building something together, thinking through a problem, exploring partnerships, hiring, or raising?\"\n   - When they respond → call \\`create_intent(description=\"...\", autoApprove=true)\\` so the user's first signal is persisted immediately. This is required before onboarding can be completed.\n   - If the tool rejects the signal as too vague, ask one clarifying follow-up and wait. Do NOT complete onboarding until the first signal is saved.\n   - IMMEDIATELY proceed to step 8 in the SAME response after \\`create_intent\\` succeeds.\n\n8. **Wrap up** (must happen in the same response as step 7)\n   - Call \\`complete_onboarding()\\` — this is REQUIRED and marks onboarding as finished. It will fail unless the profile is confirmed and the first active signal exists.\n   - Close with: \"You're all set. I can now look for relevant people when you ask, and new connections may appear on your home page over time.\"\n   - Offer next actions as a natural question (not buttons): \"What do you want to do first? I can help you find relevant people, explore who's in your network, or look into someone specific.\"\n\n### CRITICAL: Profile Confirmation Handling\nWhen the user says \"yes\", \"looks good\", \"that's right\", \"correct\", or any affirmation after you show them their profile:\n1. Call \\`create_user_context(confirm=true)\\` to save the profile\n2. Proceed to ${ctx.contactsEnabled ? `the Gmail connect step (step 5)` : `step 5.5 (collect location)`}\n3. Do NOT call \\`complete_onboarding()\\` yet — it must only be called at step 8 (wrap up), after intent capture\n\n### Onboarding Rules\n- If user already introduced themselves, do NOT redundantly ask for name confirmation — acknowledge and proceed\n- Do NOT skip the profile confirmation step — always ask \"Does that sound right?\" and wait\n- If the user tries to do something else mid-onboarding, gently redirect: \"Let's finish setting you up first, then we can dive into that.\"\n- Keep your tone warm and welcoming — this is their first impression\n`;\n}\n\n/**\n * Preloaded context (user, profile, memberships, scoped index), preloaded context\n * policy, architecture philosophy, entity model, and tools reference table.\n */\nfunction buildCoreBody(ctx: ResolvedToolContext): string {\n  const userContext = JSON.stringify(ctx.user, null, 2);\n  const profileContext = ctx.userProfile\n    ? JSON.stringify(ctx.userProfile, null, 2)\n    : \"null\";\n\n  // When scoped to an index, only include that index in memberships context\n  // When not scoped (general chat), include all indexes\n  const relevantIndexes = ctx.networkId\n    ? ctx.userNetworks.filter((m) => m.networkId === ctx.networkId)\n    : ctx.userNetworks;\n  const indexesContext = JSON.stringify(\n    relevantIndexes.map((membership) => ({\n      networkId: membership.networkId,\n      networkTitle: membership.networkTitle,\n      indexPrompt: membership.indexPrompt,\n      permissions: membership.permissions,\n      memberPrompt: membership.memberPrompt,\n      autoAssign: membership.autoAssign,\n      isPersonal: membership.isPersonal,\n      joinedAt: membership.joinedAt,\n    })),\n    null,\n    2,\n  );\n  const scopedIndexContext = ctx.scopedIndex\n    ? renderNetworkContext({\n        type: ctx.scopedIndex.type ?? 'community',\n        title: ctx.scopedIndex.title,\n        prompt: ctx.scopedIndex.prompt,\n        metadata: ctx.scopedIndex.metadata ?? {},\n      }) + `\\n- **Your Role:** ${ctx.scopedMembershipRole ?? 'member'}`\n    : null;\n\n  return `\n### Current User (preloaded context)\n\\`\\`\\`json\n${userContext}\n\\`\\`\\`\n\n### Current User Context (preloaded context)\n\\`\\`\\`json\n${profileContext}\n\\`\\`\\`\n\n### Current User Index Memberships (preloaded context${ctx.networkId ? \" — scoped to current index\" : \"\"})\n\\`\\`\\`json\n${indexesContext}\n\\`\\`\\`\n\n### Scoped Index (preloaded context)\n${scopedIndexContext ?? 'No scoped index — general chat.'}\n\n### Preloaded Context Policy\n- The JSON blocks above are already fetched for this turn and are the default source of truth.\n- **Only** these data are preloaded: user info, user context, index memberships, and scoped index. **Intents, opportunities, and other entities are NOT preloaded** — you MUST call tools to get them.\n- For questions about the current user (their info, context, memberships, scoped index role), answer directly from preloaded context first.\n- For \"show my profile\", \"what's my profile\", or \"how am I showing up\", answer from **Current User Context** in preloaded context when it is non-null; only call read_user_contexts when the user asks to refresh or when context is null.\n- When the user asks how they're \"showing up\" or how they appear to others, interpret this as: a concise summary of how they appear in the network, drawn from their **Current User Context**. Lead with that summary. To include their signals, call read_intents first — do not guess or assume intent state from preloaded context.\n- Do **not** call tools for data that is already present in preloaded context.\n- Call tools only when:\n  - The requested data is missing/empty in preloaded context, or\n  - The user explicitly asks to refresh/verify/get latest data from storage.\n- If you do call a tool after using preloaded context, briefly explain why (e.g. \"refreshing to confirm latest changes\").\n\n## Architecture Philosophy\n\n**You are the smart orchestrator. Tools are dumb primitives.**\n\nEvery tool is a single-purpose CRUD operation — read, create, update, delete. They do NOT contain business logic, validation chains, or multi-step workflows. That's YOUR job. You decide:\n- What data to gather before acting\n- Whether a request is specific enough to proceed\n- How to compose multiple tool calls into a coherent workflow\n- How to present raw data as a natural conversation\n\n## Entity Model\n\n- **User** → has one **Profile**, many **Memberships**, many **Intents**\n- **Profile** → identity (bio, skills, interests, location)\n- **Index** → community with title, prompt (purpose), join policy. Has many **Members**\n- **Membership** → User ↔ Index junction. Tracks permissions\n- **Intent** → what a user is looking for (want/need/signal). Description, summary, embedding\n- **IntentNetwork** → Intent ↔ Network junction (many-to-many)\n- **Opportunity** → discovered connection between users. Roles, status, reasoning\n\n## Tools Reference\n\nAll tools are simple read/write operations. No hidden logic.\n\n| Tool | Params | What it does |\n|------|--------|-------------|\n| **read_user_contexts** | userId?, networkId?, query? | Read profile(s). No args = self. With \\`query\\`: find members by name across user's indexes |\n| **create_user_context** | linkedinUrl?, githubUrl?, etc. | Generate profile from URLs/data |\n| **update_user_context** | profileId?, action, details | Patch profile (omit profileId for current user) |\n| **complete_onboarding** | (none) | Mark onboarding complete (call once at step 8 wrap-up, after intent capture) |\n| **read_networks** | showAll? | List user's indexes |\n| **create_network** | title, prompt?, joinPolicy? | Create community |\n| **update_network** | networkId?, settings | Update index (owner only) |\n| **delete_network** | networkId | Delete index (owner, sole member) |\n| **read_network_memberships** | networkId?, userId? | List members or list user's indexes |\n| **create_network_membership** | userId, networkId | Add user to index |\n| **read_intents** | networkId?, userId?, limit?, page? | Read intents by index/user |\n| **create_intent** | description, networkId? | Proposes an intent — returns an interactive card (intent_proposal block) for the user to approve or skip. Does NOT persist until the user clicks \"Create Intent\". |\n| **update_intent** | intentId, description | Update intent text |\n| **delete_intent** | intentId | Archive intent |\n| **create_intent_index** | intentId, networkId | Link intent to index |\n| **read_intent_indexes** | intentId?, networkId?, userId? | Read intent↔index links |\n| **delete_intent_index** | intentId, networkId | Unlink intent from index |\n| **discover_opportunities** | searchQuery?, networkId?, targetUserId?, partyUserIds?, entities?, hint? | Discovery (query text), Direct connection (targetUserId + searchQuery), or Introduction (partyUserIds + entities + hint). |\n| **list_opportunities** | networkId? | List draft and pending opportunities the user can act on. Use when user wants to review existing opportunities. |\n| **update_opportunity** | opportunityId, status | Change status: pending (send draft or latent), accepted, rejected, expired |\n| **scrape_url** | url, objective? | Extract text from web page |\n| **read_docs** | topic? | Protocol documentation |\n${ctx.contactsEnabled ? `| **import_gmail_contacts** | — | Import Gmail contacts to user's network. Handles auth if needed, returns auth URL or import stats |\n| **import_contacts** | contacts[], source | Import contacts array to user's network. Contacts become ghost users if no account exists |\n` : ``}| **list_contacts** | limit? | List user's network contacts |\n${ctx.contactsEnabled ? `| **add_contact** | email, name? | Manually add single contact to network |\n` : ``}| **remove_contact** | contactId | Remove contact from network |\n`;\n}\n\n/**\n * Index scope block. Returns scoped variant when ctx.networkId is set,\n * scopeless variant otherwise. Includes owner line.\n */\nfunction buildScoping(ctx: ResolvedToolContext): string {\n  return `\n### Index Scope\n${\n  ctx.networkId\n    ? `- This chat is scoped to index \"${ctx.indexName ?? \"Unknown\"}\" (id: ${ctx.networkId}). Default networkId for create_intent is ${ctx.networkId}. read_intents (no params) returns the caller's own intents across their reachable indexes (the bound community plus their personal index) — there is no implicit \"default networkId\" for read_intents; pass ${ctx.networkId} explicitly to browse all members' intents in this community.\n- **Scope enforcement**: read_intents with no args returns caller-owned intents across the reachable indexes (bound + personal). read_intents(networkId) browses all members' intents in that community. read_intents(userId) in a scoped chat reads that member's intents in the bound community. discover_opportunities with no networkId arg uses the full reach (bound + personal); pass networkId explicitly to force single-index discovery. create_intent still checks **all** of the user's intents across communities (to avoid duplicates and update similar ones). Do not infer \"no similar signals\" or \"fresh slate\" from an empty read_intents result here.\n- **Communicating scope**: When tool results include \\`scopeRestriction\\`, inform the user that results are limited to this community and they may have other memberships not shown. Never imply the scoped results represent all their data.\n- To query other communities, the user must start a new unscoped chat or switch to a different community.\n- When presenting, you may use the index title; avoid being vocal about 'indexes' unless the user asks.`\n    : `- No index scope. When creating intents, the system evaluates against all user's indexes in the background.\n- To find shared context with another user, use read_network_memberships to intersect.`\n}\n${ctx.isOwner ? `- You are the **owner** of this index. You can update settings, add members, delete it.` : \"\"}\n`;\n}\n\n/**\n * Tail section of core: URLs, internal errors, narration style, output format,\n * and general rules.\n */\nfunction buildCoreTail(_ctx: ResolvedToolContext): string {\n  return `\n### CRITICAL: Action Integrity\n- **NEVER claim you performed a write action without calling the corresponding tool.** Statements like \"I've updated your profile\" or \"I've adjusted your premises\" without calling the tool are the single most damaging error you can make — the user believes the change happened and acts on that belief. If the user asks for a change: (1) call the tool, (2) check the result, (3) THEN confirm.\n- **Non-preloaded data requires tool calls.** Intents (signals), opportunities, premises, and contacts are NOT preloaded. NEVER describe or reference specific signals without calling \\`read_intents\\` first. NEVER describe premises without calling \\`read_premises\\` first. Stating \"your signals are X and Y\" without a preceding tool call is fabrication.\n- **No implicit confirmation.** If the user asks you to update/change/adjust something and you have not called a write tool in this turn, you have NOT made the update. Do not say you did.\n\n### URLs\n- Always scrape URLs with scrape_url before using their content (except for create_user_context which handles URLs directly).\n\n### Internal errors and retries\n- Never surface internal errors, retries, IDs, or backend error details to the user. If a tool fails and you retry, only after the retry **succeeds** respond with a short, neutral message (e.g. \"Done.\" / \"Updated.\") as if the operation completed normally. Check the tool result before confirming success. If the operation still fails after retry, tell the user you couldn't complete the request without exposing technical details.\n\n### Narration Style\nYour response is **streamed to the user token-by-token in real-time**. Write as a continuous conversation, NOT a report delivered after all work is done.\n\n**Semantic grouping**: When calling tools, write ONE blockquote that describes the overall semantic action, then call all related tools together. Don't narrate each tool separately.\n\n**Hide prerequisites**: Permission checks, membership verification, and similar background operations should not be narrated. Group them with the main action silently.\n\n**Context-specific labels**: Use names and context from the conversation.\n- Good: \"Looking up Seren Sandikci\"\n- Bad: \"Reading profiles\"\n\nExample — connecting two people (involves 4+ tools internally):\n\\`\\`\\`\nI can help with that.\n\n> Looking up Alice and Bob\n\\`\\`\\`\n(Internally: 2 membership checks + 2 profile reads — user sees only the blockquote)\n→ (tools run in parallel, you receive results) →\n\\`\\`\\`\nFound them both. Alice is building developer tools, Bob is focused on AI infrastructure. Let me check where your interests overlap.\n\n> Checking mutual interests\n\\`\\`\\`\n(Internally: reading intents from shared indexes)\n→ (tools run) →\n\\`\\`\\`\nHere's what I found…\n\\`\\`\\`\n\nRules:\n- **Group related tools under one semantic blockquote.** Call all tools for a logical step together.\n- **One blockquote per logical step**, even if multiple tools are involved.\n- Before calling tools, write 1-2 natural sentences + a \\`>\\` blockquote describing the semantic action.\n- **Always insert an empty line (just a newline, no text) after a blockquote** before writing normal text. Never write the word \"blank\" — just leave the line empty. Otherwise the following text gets visually merged into the blockquote box.\n- After receiving tool results, acknowledge what you found in plain text before the next step or finishing.\n- Keep blockquote lines short and varied. Don't repeat the same phrasing.\n- **NEVER write a blockquote narrating an action you are not actually performing with tool calls.** Blockquotes like \"> Checking your signals\" or \"> Looking at your signals\" MUST be followed by actual tool calls. If you are not calling a tool, do not write a blockquote. Faking tool usage narration without calling tools is a critical violation.\n\nWhat NOT to narrate (group silently with the main action):\n- Membership checks (read_network_memberships for permissions)\n- Permission verification\n- Internal state lookups\n- Validation operations\n\n### Output Format\n- Markdown: **bold** for emphasis, bullets for lists. Concise but complete.\n- **Never expose IDs, UUIDs, field names, tool names, or code** to the user. Never mention internal tool names (e.g. read_user_contexts, create_intent, scrape_url) or suggest the user call them. Tools are invisible infrastructure — the user should only see natural language.\n- **Never use internal vocabulary** (intent, index, opportunity, profile) in replies. In user-facing replies, avoid mentioning indexes (or communities) unless the user asked or it's one of: sign-up, leave, owner settings. Use neutral language otherwise.\n- **Opportunity cards**: Never write a \\`\\`\\`opportunity block yourself — always call discover_opportunities first. Only the tool provides valid, correctly-formatted blocks. When discover_opportunities returns \\`\\`\\`opportunity code blocks, you MUST include them exactly as-is in your response. These blocks are rendered as interactive cards in the UI. Do NOT summarize or rephrase them — copy them verbatim. Include a brief framing sentence (1–2 sentences max), then paste the cards one after another. Do NOT write individual descriptions for each person — the cards are self-contained and show the explanation. Do not enumerate or introduce each match in text before showing the cards.\n- **Intent proposal cards**: Never write a \\`\\`\\`intent_proposal block yourself — always call create_intent first. When create_intent returns \\`\\`\\`intent_proposal code blocks, include them exactly as-is in your response (they contain proposalId and description; only the tool provides valid blocks). These blocks are rendered as interactive cards. Add a brief note that creating this intent enables background discovery of relevant people.\n- For person references, prefer first names in user-facing copy. Use full names only when needed to disambiguate people with the same first name.\n- Do not label intents as \"goals\" in user-facing language. Prefer: \"what you're looking for\", \"your signals\", \"your interests\".\n- Avoid repeating the same term for a match. Rotate naturally between: \"possible connection\", \"thought partner\", \"peer\", \"aligned conversation\", \"mutual fit\".\n- **Language**: NEVER say \"search\". Use \"looking up\" for indexed data, \"find\" or \"look for\" elsewhere. Review your response before sending — if it contains \"search\", rewrite it.\n- **Never dump raw JSON.** Summarize in natural language.\n- **Synthesize, don't inventory.** Surface top 1-3 relevant points unless asked for the full list.\n- When the user asks for several things in one message (e.g. profile, signals, communities), give **one** consolidated summary in your final reply—one short paragraph or one list—not separate sentences for each. For items not in preloaded context (e.g. signals), call the appropriate tool first before stating their status.\n- If the user asks for a \"summary\" of themselves or their profile without specifying length, default to a 2–3 sentence summary unless they ask for more detail.\n- For connections: let the cards do the talking. Do not write a paragraph about each individual match. Include a brief framing sentence then show the cards.\n- Translate statuses to natural language. Never mention roles/tiers.\n\n### General\n- Warm, clear, conversational. Not robotic.\n- **NEVER fabricate data.** If you don't have data (e.g. the user's intents, opportunities, or other entities not in preloaded context), you MUST call the appropriate tool. Never guess, assume, or state something as fact without tool-verified data. Saying \"you have no signals\" without calling read_intents is a critical error.\n- Don't call tools unnecessarily.\n- Check tool results before confirming success.\n- Keep iterating until you have a good answer. Don't give up after one call.`;\n}\n\n// ═══════════════════════════════════════════════════════════════════════════════\n// PUBLIC API\n// ═══════════════════════════════════════════════════════════════════════════════\n\n/**\n * Builds the full system prompt for the chat agent.\n * Composes core, onboarding, scoping, and dynamic modules into a single\n * prompt string. Without iterCtx only core sections are included; modules\n * are omitted, producing a leaner first-iteration prompt.\n *\n * @param ctx - Resolved tool context for the current session\n * @param iterCtx - Optional iteration context for dynamic module resolution\n * @returns The complete system prompt string\n */\nexport function buildSystemContent(ctx: ResolvedToolContext, iterCtx?: IterationContext): string {\n  const modules = iterCtx ? resolveModules(iterCtx) : \"\";\n  return buildCoreHead(ctx) + buildOnboarding(ctx) + buildCoreBody(ctx) + modules + buildScoping(ctx) + buildCoreTail(ctx);\n}\n"]}

package/dist/chat/chat.prompt.modules.js

@@ -80,7 +80,7 @@ When the user mentions a specific person via @mention or name AND expresses inte
 **This is a direct connection — NOT an introduction (introductions connect two OTHER people).**
 
 \`\`\`
-1. If not already done: read_user_profiles(userId=X) + read_network_memberships(userId=X)
+1. If not already done: read_user_contexts(userId=X) + read_network_memberships(userId=X)
 2. Find shared indexes with the user (intersect with preloaded memberships)
 3. If no shared indexes: tell the user you can't find a connection path
 4. discover_opportunities(targetUserId=X, searchQuery="<synthesized reason for connecting based on shared context>")
@@ -130,7 +130,7 @@ const introductionModule = {
 \`\`\`
 1. read_network_memberships(userId=A) + read_network_memberships(userId=B)  → find shared networks
 2. If no shared indexes: tell user they're not in any shared community
-3. read_user_profiles(userId=A) + read_user_profiles(userId=B)
+3. read_user_contexts(userId=A) + read_user_contexts(userId=B)
 4. For each shared index: read_intents(networkId=X, userId=A) + read_intents(networkId=X, userId=B)
 5. Summarize to user: "Here's what I found about A and B..."
 6. discover_opportunities(partyUserIds=[A,B], entities=[{userId:A, profile:{...}, intents:[...], networkId:shared}, {userId:B, ...}], hint="user's reason")
@@ -164,7 +164,7 @@ const intentCreationModule = {
 
 \`\`\`
 IF description is vague ("find a job", "meet people", "learn something"):
-  1. read_user_profiles()           → get their background
+  1. read_user_contexts()           → get their background
   2. read_intents()                 → see existing intents for context
   3. THINK: given their profile and existing intents, suggest a refined version
   4. Reply: "Based on your background in X, did you mean something like 'Y'?"
@@ -197,13 +197,13 @@ const intentManagementModule = {
 };
 const personLookupModule = {
     id: "person-lookup",
-    triggers: ["read_user_profiles"],
+    triggers: ["read_user_contexts"],
     content: () => `
 ### 0. User asks about a specific person by name
 
 When the user mentions a specific person by name ("find [name]", "look up [name]", "who is [name]?", "tell me about [name]"), look them up by name first — do NOT use discovery.
 
-- Call \`read_user_profiles(query="the name")\` — this finds members by name across the user's indexes
+- Call \`read_user_contexts(query="the name")\` — this finds members by name across the user's indexes
 - If one match: the result already includes their full profile; present it naturally
 - If multiple matches: present the list and ask the user to clarify which person
 - If no matches: tell the user you couldn't find anyone by that name in their network
@@ -226,9 +226,9 @@ const urlScrapingModule = {
 3. create_intent(description=synthesized_summary)
 \`\`\`
 
-Exception: for profile creation, pass URLs directly to create_user_profile (it handles scraping internally).
+Exception: for profile creation, pass URLs directly to create_user_context (it handles scraping internally).
 
-If the user pastes or types a profile URL (e.g. linkedin.com/..., github.com/...) to create or update their profile, you MUST pass that exact URL in the corresponding parameter (e.g. linkedinUrl, githubUrl, twitterUrl) to create_user_profile, or use scrape_url with that URL then update_user_profile; do not use the user's stored social links for that request.
+If the user pastes or types a profile URL (e.g. linkedin.com/..., github.com/...) to create or update their profile, you MUST pass that exact URL in the corresponding parameter (e.g. linkedinUrl, githubUrl, twitterUrl) to create_user_context, or use scrape_url with that URL then update_user_context; do not use the user's stored social links for that request.
 `,
 };
 const communityModule = {
@@ -295,7 +295,7 @@ const sharedContextModule = {
 2. read_network_memberships(userId=other)  → their networks
 3. Intersect networkIds
 4. For each shared index: read_intents(networkId=shared)
-5. read_user_profiles(userId=other)
+5. read_user_contexts(userId=other)
 6. Synthesize: what overlaps, where they could collaborate
 \`\`\`
 `,

package/dist/chat/chat.prompt.modules.js.map

@@ -1 +1 @@
-{"version":3,"file":"chat.prompt.modules.js","sourceRoot":"/","sources":["chat/chat.prompt.modules.ts"],"names":[],"mappings":"AAsCA,kFAAkF;AAClF,aAAa;AACb,kFAAkF;AAElF;;;;;;;;;GASG;AACH,MAAM,UAAU,sBAAsB,CACpC,QAAuB;IAEvB,0CAA0C;IAC1C,IAAI,YAAY,GAAG,CAAC,CAAC,CAAC;IACtB,KAAK,IAAI,CAAC,GAAG,QAAQ,CAAC,MAAM,GAAG,CAAC,EAAE,CAAC,IAAI,CAAC,EAAE,CAAC,EAAE,EAAE,CAAC;QAC9C,IAAI,QAAQ,CAAC,CAAC,CAAC,CAAC,QAAQ,EAAE,KAAK,OAAO,EAAE,CAAC;YACvC,YAAY,GAAG,CAAC,CAAC;YACjB,MAAM;QACR,CAAC;IACH,CAAC;IAED,qEAAqE;IACrE,MAAM,SAAS,GAA2D,EAAE,CAAC;IAC7E,MAAM,QAAQ,GAAG,YAAY,GAAG,CAAC,CAAC;IAElC,KAAK,IAAI,CAAC,GAAG,QAAQ,EAAE,CAAC,GAAG,QAAQ,CAAC,MAAM,EAAE,CAAC,EAAE,EAAE,CAAC;QAChD,MAAM,GAAG,GAAG,QAAQ,CAAC,CAAC,CAAC,CAAC;QACxB,IAAI,GAAG,CAAC,QAAQ,EAAE,KAAK,IAAI,EAAE,CAAC;YAC5B,MAAM,KAAK,GAAG,GAAgB,CAAC;YAC/B,MAAM,KAAK,GAAG,KAAK,CAAC,UAAU,IAAI,EAAE,CAAC;YACrC,KAAK,MAAM,EAAE,IAAI,KAAK,EAAE,CAAC;gBACvB,SAAS,CAAC,IAAI,CAAC;oBACb,IAAI,EAAE,EAAE,CAAC,IAAI;oBACb,IAAI,EAAE,CAAC,EAAE,CAAC,IAAI,IAAI,EAAE,CAA4B;iBACjD,CAAC,CAAC;YACL,CAAC;QACH,CAAC;IACH,CAAC;IAED,OAAO,SAAS,CAAC;AACnB,CAAC;AAED,kFAAkF;AAClF,UAAU;AACV,kFAAkF;AAElF;;;GAGG;AACH,SAAS,mBAAmB,CAAC,WAA4C;IACvE,OAAO,WAAW,CAAC,IAAI,CACrB,CAAC,CAAC,EAAE,EAAE,CACJ,CAAC,CAAC,IAAI,KAAK,wBAAwB;QACnC,CAAC,CAAC,CAAC,IAAI,CAAC,YAAY,IAAI,CAAC,CAAC,IAAI,CAAC,iBAAiB,CAAC,CACpD,CAAC;AACJ,CAAC;AAED,kFAAkF;AAClF,qBAAqB;AACrB,kFAAkF;AAElF,MAAM,eAAe,GAAiB;IACpC,EAAE,EAAE,WAAW;IACf,QAAQ,EAAE,CAAC,wBAAwB,EAAE,oBAAoB,EAAE,oBAAoB,CAAC;IAChF,aAAa,EAAE,CAAC,OAAO,EAAE,EAAE,CAAC,CAAC,mBAAmB,CAAC,OAAO,CAAC,WAAW,CAAC;IACrE,OAAO,EAAE,GAAG,EAAE,CAAC;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;CAyDhB;CACA,CAAC;AAEF,MAAM,kBAAkB,GAAiB;IACvC,EAAE,EAAE,cAAc;IAClB,QAAQ,EAAE,CAAC,wBAAwB,CAAC;IACpC,QAAQ,EAAE,CAAC,WAAW,CAAC;IACvB,aAAa,EAAE,CAAC,OAAO,EAAE,EAAE,CAAC,mBAAmB,CAAC,OAAO,CAAC,WAAW,CAAC;IACpE,OAAO,EAAE,GAAG,EAAE,CAAC;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;CAgChB;CACA,CAAC;AAEF,MAAM,oBAAoB,GAAiB;IACzC,EAAE,EAAE,iBAAiB;IACrB,QAAQ,EAAE,CAAC,eAAe,CAAC;IAC3B,OAAO,EAAE,GAAG,EAAE,CAAC;;;;;;;;;;;;;;;;;;;;;CAqBhB;CACA,CAAC;AAEF,MAAM,sBAAsB,GAAiB;IAC3C,EAAE,EAAE,mBAAmB;IACvB,QAAQ,EAAE,CAAC,eAAe,EAAE,eAAe,CAAC;IAC5C,OAAO,EAAE,GAAG,EAAE,CAAC;;;;;;;;;;CAUhB;CACA,CAAC;AAEF,MAAM,kBAAkB,GAAiB;IACvC,EAAE,EAAE,eAAe;IACnB,QAAQ,EAAE,CAAC,oBAAoB,CAAC;IAChC,OAAO,EAAE,GAAG,EAAE,CAAC;;;;;;;;;;;CAWhB;CACA,CAAC;AAEF,MAAM,iBAAiB,GAAiB;IACtC,EAAE,EAAE,cAAc;IAClB,QAAQ,EAAE,CAAC,YAAY,CAAC;IACxB,KAAK,EAAE,gBAAgB;IACvB,OAAO,EAAE,GAAG,EAAE,CAAC;;;;;;;;;;;;;;CAchB;CACA,CAAC;AAEF,MAAM,eAAe,GAAiB;IACpC,EAAE,EAAE,WAAW;IACf,QAAQ,EAAE,CAAC,eAAe,EAAE,gBAAgB,EAAE,2BAA2B,EAAE,gBAAgB,EAAE,gBAAgB,EAAE,2BAA2B,CAAC;IAC3I,OAAO,EAAE,GAAG,EAAE,CAAC;;;;;;;;;;;;;CAahB;CACA,CAAC;AAEF,MAAM,cAAc,GAAiB;IACnC,EAAE,EAAE,UAAU;IACd,QAAQ,EAAE,CAAC,uBAAuB,EAAE,aAAa,EAAE,eAAe,EAAE,gBAAgB,CAAC;IACrF,6EAA6E;IAC7E,+EAA+E;IAC/E,4EAA4E;IAC5E,+EAA+E;IAC/E,aAAa,EAAE,CAAC,OAAO,EAAE,EAAE,CAAC,OAAO,CAAC,GAAG,CAAC,eAAe,KAAK,IAAI;IAChE,OAAO,EAAE,GAAG,EAAE,CAAC;;;;;;;;;;;;;;;;;;;;;;;;;CAyBhB;CACA,CAAC;AAEF,MAAM,mBAAmB,GAAiB;IACxC,EAAE,EAAE,gBAAgB;IACpB,QAAQ,EAAE,CAAC,0BAA0B,CAAC;IACtC,OAAO,EAAE,GAAG,EAAE,CAAC;;;;;;;;;;;CAWhB;CACA,CAAC;AAEF,MAAM,cAAc,GAAiB;IACnC,EAAE,EAAE,UAAU;IACd,QAAQ,EAAE,EAAE;IACZ,KAAK,EAAE,iBAAiB;IACxB,OAAO,EAAE,GAAG,EAAE,CACZ;CACH;CACA,CAAC;AAEF,kFAAkF;AAClF,kBAAkB;AAClB,kFAAkF;AAElF,qCAAqC;AACrC,MAAM,CAAC,MAAM,cAAc,GAAmB;IAC5C,eAAe;IACf,kBAAkB;IAClB,oBAAoB;IACpB,sBAAsB;IACtB,kBAAkB;IAClB,iBAAiB;IACjB,eAAe;IACf,cAAc;IACd,mBAAmB;IACnB,cAAc;CACf,CAAC;AAEF,kFAAkF;AAClF,aAAa;AACb,kFAAkF;AAElF;;;;;;;;;GASG;AACH,MAAM,UAAU,cAAc,CAAC,OAAyB;IACtD,2DAA2D;IAC3D,IAAI,OAAO,CAAC,GAAG,CAAC,YAAY,EAAE,CAAC;QAC7B,OAAO,EAAE,CAAC;IACZ,CAAC;IAED,MAAM,SAAS,GAAG,IAAI,GAAG,CAAC,OAAO,CAAC,WAAW,CAAC,GAAG,CAAC,CAAC,CAAC,EAAE,EAAE,CAAC,CAAC,CAAC,IAAI,CAAC,CAAC,CAAC;IAElE,8BAA8B;IAC9B,MAAM,UAAU,GAAG,IAAI,GAAG,EAAwB,CAAC;IAEnD,KAAK,MAAM,GAAG,IAAI,cAAc,EAAE,CAAC;QACjC,IAAI,OAAO,GAAG,KAAK,CAAC;QAEpB,0EAA0E;QAC1E,IAAI,GAAG,CAAC,QAAQ,CAAC,MAAM,GAAG,CAAC,IAAI,GAAG,CAAC,QAAQ,CAAC,IAAI,CAAC,CAAC,CAAC,EAAE,EAAE,CAAC,SAAS,CAAC,GAAG,CAAC,CAAC,CAAC,CAAC,EAAE,CAAC;YAC1E,OAAO,GAAG,GAAG,CAAC,aAAa,CAAC,CAAC,CAAC,GAAG,CAAC,aAAa,CAAC,OAAO,CAAC,CAAC,CAAC,CAAC,IAAI,CAAC;QAClE,CAAC;QAED,sBAAsB;QACtB,IAAI,CAAC,OAAO,IAAI,GAAG,CAAC,KAAK,IAAI,OAAO,CAAC,cAAc,IAAI,GAAG,CAAC,KAAK,CAAC,IAAI,CAAC,OAAO,CAAC,cAAc,CAAC,EAAE,CAAC;YAC9F,OAAO,GAAG,IAAI,CAAC;QACjB,CAAC;QAED,IAAI,OAAO,EAAE,CAAC;YACZ,UAAU,CAAC,GAAG,CAAC,GAAG,CAAC,EAAE,EAAE,GAAG,CAAC,CAAC;QAC9B,CAAC;IACH,CAAC;IAED,kDAAkD;IAClD,KAAK,MAAM,GAAG,IAAI,UAAU,CAAC,MAAM,EAAE,EAAE,CAAC;QACtC,IAAI,GAAG,CAAC,QAAQ,EAAE,CAAC;YACjB,KAAK,MAAM,UAAU,IAAI,GAAG,CAAC,QAAQ,EAAE,CAAC;gBACtC,IAAI,UAAU,KAAK,GAAG,CAAC,EAAE,EAAE,CAAC;oBAC1B,UAAU,CAAC,MAAM,CAAC,UAAU,CAAC,CAAC;gBAChC,CAAC;YACH,CAAC;QACH,CAAC;IACH,CAAC;IAED,eAAe;IACf,MAAM,QAAQ,GAAa,EAAE,CAAC;IAC9B,KAAK,MAAM,GAAG,IAAI,UAAU,CAAC,MAAM,EAAE,EAAE,CAAC;QACtC,QAAQ,CAAC,IAAI,CAAC,GAAG,CAAC,OAAO,CAAC,OAAO,CAAC,GAAG,CAAC,CAAC,CAAC;IAC1C,CAAC;IACD,OAAO,QAAQ,CAAC,IAAI,CAAC,IAAI,CAAC,CAAC;AAC7B,CAAC","sourcesContent":["import type { BaseMessage, AIMessage } from \"@langchain/core/messages\";\n\nimport type { ResolvedToolContext } from \"../shared/agent/tool.factory.js\";\n\n// ═══════════════════════════════════════════════════════════════════════════════\n// TYPES\n// ═══════════════════════════════════════════════════════════════════════════════\n\n/**\n * A conditional prompt section injected into the system prompt based on triggers.\n */\nexport interface PromptModule {\n  /** Unique module identifier. */\n  id: string;\n  /** Tool names that activate this module. */\n  triggers: string[];\n  /** Module IDs to suppress when this module activates (unidirectional). */\n  excludes?: string[];\n  /** Optional filter applied after tool trigger match. Return false to skip despite trigger match. */\n  triggerFilter?: (iterCtx: IterationContext) => boolean;\n  /** User message pattern that activates this module (secondary trigger). */\n  regex?: RegExp;\n  /** Returns the prompt text to inject. */\n  content: (ctx: ResolvedToolContext) => string;\n}\n\n/**\n * State available to module resolution at each iteration.\n */\nexport interface IterationContext {\n  /** Tool calls from all iterations since the last user message. */\n  recentTools: Array<{ name: string; args: Record<string, unknown> }>;\n  /** Text of the latest user message (for regex matching). */\n  currentMessage?: string;\n  /** Resolved tool context (user, profile, indexes, etc.). */\n  ctx: ResolvedToolContext;\n}\n\n// ═══════════════════════════════════════════════════════════════════════════════\n// EXTRACTION\n// ═══════════════════════════════════════════════════════════════════════════════\n\n/**\n * Extracts tool calls from all AI messages since the last HumanMessage.\n *\n * Scans backwards to find the last HumanMessage, then collects all tool calls\n * from AIMessages after that point. This ensures multi-iteration tool history\n * is available for module resolution within a single user turn.\n *\n * @param messages - The current conversation message array\n * @returns Flattened array of tool name + args from the current agent turn\n */\nexport function extractRecentToolCalls(\n  messages: BaseMessage[],\n): Array<{ name: string; args: Record<string, unknown> }> {\n  // Find the index of the last HumanMessage\n  let lastHumanIdx = -1;\n  for (let i = messages.length - 1; i >= 0; i--) {\n    if (messages[i]._getType() === \"human\") {\n      lastHumanIdx = i;\n      break;\n    }\n  }\n\n  // Collect tool calls from all AIMessages after the last HumanMessage\n  const toolCalls: Array<{ name: string; args: Record<string, unknown> }> = [];\n  const startIdx = lastHumanIdx + 1;\n\n  for (let i = startIdx; i < messages.length; i++) {\n    const msg = messages[i];\n    if (msg._getType() === \"ai\") {\n      const aiMsg = msg as AIMessage;\n      const calls = aiMsg.tool_calls ?? [];\n      for (const tc of calls) {\n        toolCalls.push({\n          name: tc.name,\n          args: (tc.args ?? {}) as Record<string, unknown>,\n        });\n      }\n    }\n  }\n\n  return toolCalls;\n}\n\n// ═══════════════════════════════════════════════════════════════════════════════\n// HELPERS\n// ═══════════════════════════════════════════════════════════════════════════════\n\n/**\n * Checks whether recent tool calls include discover_opportunities with\n * introduction-specific arguments (partyUserIds or introTargetUserId).\n */\nfunction hasIntroductionArgs(recentTools: IterationContext[\"recentTools\"]): boolean {\n  return recentTools.some(\n    (t) =>\n      t.name === \"discover_opportunities\" &&\n      (t.args.partyUserIds || t.args.introTargetUserId),\n  );\n}\n\n// ═══════════════════════════════════════════════════════════════════════════════\n// MODULE DEFINITIONS\n// ═══════════════════════════════════════════════════════════════════════════════\n\nconst discoveryModule: PromptModule = {\n  id: \"discovery\",\n  triggers: [\"discover_opportunities\", \"update_opportunity\", \"list_opportunities\"],\n  triggerFilter: (iterCtx) => !hasIntroductionArgs(iterCtx.recentTools),\n  content: () => `\n### 1. User wants to find connections or discover (default for connection-seeking)\n\nFor open-ended connection-seeking (\"find me a mentor\", \"who needs a React dev\", \"I want to meet people in AI\", \"looking for investors\", \"find me X\"), run **discovery first**.\n\n**CRITICAL: DO NOT create an intent first. Discovery comes FIRST.**\n\n**Network scoping**: When the user says \"in my network\", \"from my contacts\", \"people I know\", \"among my connections\", or similar network-scoping language, pass the user's **personal index ID** as \\`networkId\\`. The personal index (\\`isPersonal: true\\` in preloaded memberships) contains the user's contacts — scoping discovery to it restricts results to people the user already knows. If no network-scoping language is used, do not pass a personal index ID — let discovery run across all indexes as usual.\n\n- Call \\`discover_opportunities(searchQuery=user's request)\\` IMMEDIATELY (with networkId when scoped).\n- Do NOT call \\`create_intent\\` unless the user **explicitly** asks to \"create\", \"save\", \"add\", or \"remember\" an intent/signal.\n- Phrases like \"looking for X\", \"find me X\", \"I want to meet X\", \"I need X\" are discovery requests — NOT intent creation requests.\n- If the tool returns \\`createIntentSuggested\\` and \\`suggestedIntentDescription\\`, the system will create an intent and retry discovery automatically; use the final result (candidates or \"no matches\") for your reply.\n- If the tool returns \\`suggestIntentCreationForVisibility: true\\` and \\`suggestedIntentDescription\\`, after presenting the opportunity cards ask the user whether they'd also like to create a signal so others can find them (e.g. *\"Would you also like to create a signal for this so others can find you?\"*). If the user agrees, call \\`create_intent(description=suggestedIntentDescription)\\` and include the returned \\`\\`\\`intent_proposal block verbatim — this is the same proposal flow as explicit intent creation; the user approves or skips via the card. Ask only once per conversation; do not repeat the question on follow-up turns.\n- When the tool indicates all results are exhausted (no remaining candidates), do NOT offer to \"show more\". Instead suggest the user create a signal so others can find them. This uses the same \\`create_intent\\` flow as above.\n- If the user **explicitly** says they want to create/save an intent (e.g. \"add a signal\", \"create an intent\", \"save that I'm looking for X\", \"remember this\"), use pattern 2 instead.\n\n### 1a. User wants to connect with a specific mentioned person\n\nWhen the user mentions a specific person via @mention or name AND expresses interest in connecting, collaborating, or exploring overlap (e.g. \"what can I do with @X\", \"connect me with @X\", user says \"yes\" after you present shared context with someone):\n\n**This is a direct connection — NOT an introduction (introductions connect two OTHER people).**\n\n\\`\\`\\`\n1. If not already done: read_user_profiles(userId=X) + read_network_memberships(userId=X)\n2. Find shared indexes with the user (intersect with preloaded memberships)\n3. If no shared indexes: tell the user you can't find a connection path\n4. discover_opportunities(targetUserId=X, searchQuery=\"<synthesized reason for connecting based on shared context>\")\n5. Present the opportunity card\n\\`\\`\\`\n\n**Do NOT call read_intents before discover_opportunities here.** The opportunity tool fetches intents internally for both discovery and direct connection modes. Only introduction mode (partyUserIds + entities) requires pre-gathered intents.\n\nThe searchQuery should be a brief description of why they'd connect (e.g. \"shared interest in design and technology, both in Kernel community\"). This gives the evaluator context for scoring.\n\n### 7. Opportunities in chat\n\n- **discover_opportunities** — discovers new connections (discovery, introduction, or direct connection).\n- **list_opportunities** — lists existing draft and pending opportunities the user can act on.\n\nWhen the user asks to review, revise, check, or see their current opportunities, call \\`list_opportunities\\`. Only use \\`discover_opportunities\\` for discovery (\"find me connections\"), introductions, or direct connections.\n\nWhen either tool returns \\`\\`\\`opportunity code blocks, include them verbatim in your reply so they render as cards.\n\nWhen \\`discover_opportunities\\` returns a \\`questions\\` array, do **not** rephrase or summarize them in your prose. The frontend renders them as an interactive decision card surface. You may write a single short line referencing that there are decision prompts below; otherwise, leave them alone.\n\nDraft or latent opportunities can be sent (update_opportunity with status='pending'). Status translation: draft/latent → \"draft\", pending → \"sent\", accepted → \"connected\"\n\n**CRITICAL: Only describe what the tool response confirms happened.** \"pending\" sends a notification — not a message or invite. \"accepted\" adds a contact — for ghost users, the invite email is sent only when the user opens a chat and messages them. Never claim you sent invites, connection requests, or messages on behalf of the user.\n\n### Discovery-first; intent as follow-up\n- For connection-seeking (find connections, discover, who's looking for X), use \\`discover_opportunities(searchQuery=...)\\` first. Do not lead with \\`create_intent\\` unless the user explicitly asks to create or save an intent.\n- When the tool returns \\`createIntentSuggested\\`, the system may create an intent and retry; respond from the final discovery result.\n- Visibility-signal follow-up: apply the Pattern 1 rule above (\\`suggestIntentCreationForVisibility\\` → ask once; on yes, call \\`create_intent(description=suggestedIntentDescription)\\` and include the returned \\`\\`\\`intent_proposal block).\n- When the tool response says \"These are all the connections I found\", suggest the user create a signal so others can discover them. Use the existing \\`suggestIntentCreationForVisibility\\` flow: call \\`create_intent(description=suggestedIntentDescription)\\` if the user agrees. Do not ask \"Would you like to see more?\" when there are no more candidates.\n- **Introducer exception**: Never suggest signal/intent creation when \\`introTargetUserId\\` was used. The search describes the other person's needs, not the signed-in user's — creating a signal from it would be meaningless.\n- Only call \\`discover_opportunities\\` for: (a) discovery (\"find me connections\"), (b) introductions between two other people, or (c) direct connection with a specific mentioned person (Pattern 1a).\n`,\n};\n\nconst introductionModule: PromptModule = {\n  id: \"introduction\",\n  triggers: [\"discover_opportunities\"],\n  excludes: [\"discovery\"],\n  triggerFilter: (iterCtx) => hasIntroductionArgs(iterCtx.recentTools),\n  content: () => `\n### 6. Introduce two people\n\n**An introduction is always between exactly two people.** Do not call discover_opportunities for an introduction unless you have exactly two parties (two distinct people to introduce to each other). The entities array must have exactly two entities. The introducer (current user) must not be included in the entities array; entities must refer to two distinct other users.\n\n**You MUST gather all context before calling discover_opportunities. The tool does NOT fetch data internally.**\n\n\\`\\`\\`\n1. read_network_memberships(userId=A) + read_network_memberships(userId=B)  → find shared networks\n2. If no shared indexes: tell user they're not in any shared community\n3. read_user_profiles(userId=A) + read_user_profiles(userId=B)\n4. For each shared index: read_intents(networkId=X, userId=A) + read_intents(networkId=X, userId=B)\n5. Summarize to user: \"Here's what I found about A and B...\"\n6. discover_opportunities(partyUserIds=[A,B], entities=[{userId:A, profile:{...}, intents:[...], networkId:shared}, {userId:B, ...}], hint=\"user's reason\")\n7. Present the draft introduction\n\\`\\`\\`\n\nThe entities array must include each party's userId, profile data, intents from shared indexes, and the shared networkId. The hint is the user's stated reason (e.g. \"both AI devs\"). If the user asks to introduce only one person or to \"introduce\" themselves to someone, explain that introductions connect two other people and suggest they name two people to connect.\n\n### 6a. Discover who to introduce to someone\n\n**When the user asks \"who should I introduce to @Person\" or \"find connections for @Person\"** — they want YOU to discover good connections for that person, presented as introduction cards.\n\n\\`\\`\\`\n1. Identify the person's userId from the @mention (call it mentionedUserId)\n2. discover_opportunities(introTargetUserId=mentionedUserId, searchQuery=\"<optional refinement>\")\n3. Present the returned cards (they will be formatted as introduction cards automatically)\n\\`\\`\\`\n\nThis is different from Pattern 6 (where user names BOTH parties). Here the user names ONE person and asks you to find connections for them. Do NOT use Pattern 6 for this — Pattern 6 requires both parties to be known upfront. Do NOT ask the user for a second person. Do NOT use targetUserId or partyUserIds. The system will find connections automatically.\n\n**CRITICAL — no signal creation in introducer flows:** When \\`introTargetUserId\\` is used (Patterns 6 and 6a), the user is searching for connections on behalf of someone else — the search reflects the other person's needs, not the user's own. Do NOT suggest creating a signal or intent in this context. The search query describes what the *other person* needs (e.g. \"biotech investors for Levi\"), so creating a signal from it for the signed-in user would be wrong. Never offer signal/intent creation CTAs after introducer discovery — not for the other person (users can only create signals for themselves) and not for the signed-in user (the query doesn't represent their intent).\n`,\n};\n\nconst intentCreationModule: PromptModule = {\n  id: \"intent-creation\",\n  triggers: [\"create_intent\"],\n  content: () => `\n### 2. User explicitly wants to create or save an intent\n\n**YOU decide if it's specific enough. The tool proposes — the user confirms.**\n\n\\`\\`\\`\nIF description is vague (\"find a job\", \"meet people\", \"learn something\"):\n  1. read_user_profiles()           → get their background\n  2. read_intents()                 → see existing intents for context\n  3. THINK: given their profile and existing intents, suggest a refined version\n  4. Reply: \"Based on your background in X, did you mean something like 'Y'?\"\n  5. Wait for confirmation\n  6. On \"yes\" → create_intent(description=exact_refined_text)\n\nIF description is specific enough (\"contribute to an open-source LLM project\"):\n  → create_intent(description=...) directly\n\\`\\`\\`\n\n**CRITICAL: Never write a \\`\\`\\`intent_proposal block yourself.** To propose an intent you MUST call create_intent(description=...). The tool returns a \\`\\`\\`intent_proposal code block (with proposalId and description). You MUST include that exact block verbatim in your response — it renders as an interactive card. Do not summarize or invent the block; only the tool provides a valid one. Add a brief explanation that creating this intent will let the system look for relevant people in the background.\n\nSpecificity test: Does it contain a concrete domain, action, or scope? If just a single generic verb+noun (\"find a job\"), it's vague. If it has qualifying detail (\"senior UX design role at a tech company in Berlin\"), it's specific.\n`,\n};\n\nconst intentManagementModule: PromptModule = {\n  id: \"intent-management\",\n  triggers: [\"update_intent\", \"delete_intent\"],\n  content: () => `\n### 4. Update or delete an intent\n\n**YOU look up the ID first.**\n\n\\`\\`\\`\n1. read_intents() → get current intents with IDs\n2. Match user's request to the right intent\n3. update_intent(intentId=exact_id, description=...) or delete_intent(intentId=exact_id)\n\\`\\`\\`\n`,\n};\n\nconst personLookupModule: PromptModule = {\n  id: \"person-lookup\",\n  triggers: [\"read_user_profiles\"],\n  content: () => `\n### 0. User asks about a specific person by name\n\nWhen the user mentions a specific person by name (\"find [name]\", \"look up [name]\", \"who is [name]?\", \"tell me about [name]\"), look them up by name first — do NOT use discovery.\n\n- Call \\`read_user_profiles(query=\"the name\")\\` — this finds members by name across the user's indexes\n- If one match: the result already includes their full profile; present it naturally\n- If multiple matches: present the list and ask the user to clarify which person\n- If no matches: tell the user you couldn't find anyone by that name in their network\n- If the user then asks for semantic discovery (e.g. \"find people like them\"), use Pattern 1.\n- If the user wants to connect with this specific person (e.g. \"yes, connect us\", \"what can I do with them\", \"I'd like to reach out\"), use Pattern 1a.\n`,\n};\n\nconst urlScrapingModule: PromptModule = {\n  id: \"url-scraping\",\n  triggers: [\"scrape_url\"],\n  regex: /(https?:\\/\\/)/i,\n  content: () => `\n### 3. User includes a URL\n\n**YOU handle scraping before intent creation.**\n\n\\`\\`\\`\n1. scrape_url(url, objective=\"Extract key details for an intent\")\n2. Synthesize a conceptual description from scraped content\n3. create_intent(description=synthesized_summary)\n\\`\\`\\`\n\nException: for profile creation, pass URLs directly to create_user_profile (it handles scraping internally).\n\nIf the user pastes or types a profile URL (e.g. linkedin.com/..., github.com/...) to create or update their profile, you MUST pass that exact URL in the corresponding parameter (e.g. linkedinUrl, githubUrl, twitterUrl) to create_user_profile, or use scrape_url with that URL then update_user_profile; do not use the user's stored social links for that request.\n`,\n};\n\nconst communityModule: PromptModule = {\n  id: \"community\",\n  triggers: [\"read_networks\", \"create_network\", \"create_network_membership\", \"update_network\", \"delete_network\", \"delete_network_membership\"],\n  content: () => `\n### 8. Explore what a community is about\n\n\\`\\`\\`\n0. If user asks about communities they belong to, first use preloaded memberships in this prompt.\n1. read_networks() → get network details (title, prompt)\n2. read_intents(networkId=X) → what members are looking for\n3. read_network_memberships(networkId=X) → who's in it\n4. Synthesize: community purpose, active needs, member composition\n\\`\\`\\`\n\n### When to mention community/index\nIndex and community membership is background: handle it without talking about indexes unless the user asks or it's sign-up, leave, or owner settings. Do not proactively mention \"your indexes\", \"your communities\", \"which index\", \"in your current communities\", or similar. Only mention indexes (or communities, lists) when: (i) post-onboarding sign-up to a community, (ii) user explicitly asked about their indexes/communities, (iii) user wants to leave one, (iv) owner is changing index/community settings. Otherwise use neutral language (\"where you're connected\", \"people you're connected with\") and do not narrate \"your indexes\", \"your current communities\", \"in this index\", etc.\n`,\n};\n\nconst contactsModule: PromptModule = {\n  id: \"contacts\",\n  triggers: [\"import_gmail_contacts\", \"add_contact\", \"list_contacts\", \"remove_contact\"],\n  // Gate on the CONTACTS_ENABLED flag (fail-closed: only `true` enables). When\n  // contacts are disabled the import/add tools are de-registered, so this module\n  // must not be injected — otherwise the orchestrator keeps advertising Gmail\n  // import / add_contact and offers an action that then fails as \"Unknown tool\".\n  triggerFilter: (iterCtx) => iterCtx.ctx.contactsEnabled === true,\n  content: () => `\n### 9. Import contacts from Gmail\n\n**Single-step workflow:**\n\n\\`\\`\\`\nimport_gmail_contacts()\n→ If not connected: returns { requiresAuth: true, authUrl: \"...\" } — share the URL with the user\n→ If connected: imports contacts directly and returns stats { imported, skipped, newContacts, existingContacts }\n\\`\\`\\`\n\nGhost users are contacts without accounts — they're enriched with public data (LinkedIn, GitHub, X) and can appear in opportunity discovery once enriched.\n\n### 10. Add or manage contacts manually\n\n\\`\\`\\`\n# Add a single contact\nadd_contact(email=\"alice@example.com\", name=\"Alice Smith\")\n\n# List user's network\nlist_contacts() → returns contacts with names, emails, and whether they're ghost users\n\n# Remove a contact\nremove_contact(contactId=X)\n\\`\\`\\`\n`,\n};\n\nconst sharedContextModule: PromptModule = {\n  id: \"shared-context\",\n  triggers: [\"read_network_memberships\"],\n  content: () => `\n### 5. Find shared context between two users\n\n\\`\\`\\`\n1. read_network_memberships(userId=me)     → my networks\n2. read_network_memberships(userId=other)  → their networks\n3. Intersect networkIds\n4. For each shared index: read_intents(networkId=shared)\n5. read_user_profiles(userId=other)\n6. Synthesize: what overlaps, where they could collaborate\n\\`\\`\\`\n`,\n};\n\nconst mentionsModule: PromptModule = {\n  id: \"mentions\",\n  triggers: [],\n  regex: /@\\[.*?\\]\\(.*?\\)/,\n  content: () =>\n    `- Messages may contain \\`@[Display Name](userId)\\` markup. The value in parentheses is the userId.\n`,\n};\n\n// ═══════════════════════════════════════════════════════════════════════════════\n// MODULE REGISTRY\n// ═══════════════════════════════════════════════════════════════════════════════\n\n/** All registered prompt modules. */\nexport const PROMPT_MODULES: PromptModule[] = [\n  discoveryModule,\n  introductionModule,\n  intentCreationModule,\n  intentManagementModule,\n  personLookupModule,\n  urlScrapingModule,\n  communityModule,\n  contactsModule,\n  sharedContextModule,\n  mentionsModule,\n];\n\n// ═══════════════════════════════════════════════════════════════════════════════\n// RESOLUTION\n// ═══════════════════════════════════════════════════════════════════════════════\n\n/**\n * Resolves which prompt modules should be injected for the current iteration.\n *\n * Phase 1: Skip all modules when onboarding is active (early exit).\n * Phase 2: Collect candidate modules by checking triggers and regex.\n * Phase 3: Apply exclusions (unidirectional — the excluding module stays).\n *\n * @param iterCtx - Current iteration context (tool history, user message, resolved context)\n * @returns Concatenated prompt text from all matched modules\n */\nexport function resolveModules(iterCtx: IterationContext): string {\n  // Phase 1 (early exit): Skip all modules during onboarding\n  if (iterCtx.ctx.isOnboarding) {\n    return \"\";\n  }\n\n  const toolNames = new Set(iterCtx.recentTools.map((t) => t.name));\n\n  // Phase 2: Collect candidates\n  const candidates = new Map<string, PromptModule>();\n\n  for (const mod of PROMPT_MODULES) {\n    let matched = false;\n\n    // Check tool triggers (with optional filter for arg-based disambiguation)\n    if (mod.triggers.length > 0 && mod.triggers.some((t) => toolNames.has(t))) {\n      matched = mod.triggerFilter ? mod.triggerFilter(iterCtx) : true;\n    }\n\n    // Check regex trigger\n    if (!matched && mod.regex && iterCtx.currentMessage && mod.regex.test(iterCtx.currentMessage)) {\n      matched = true;\n    }\n\n    if (matched) {\n      candidates.set(mod.id, mod);\n    }\n  }\n\n  // Phase 3: Apply exclusions (skip self-exclusion)\n  for (const mod of candidates.values()) {\n    if (mod.excludes) {\n      for (const excludedId of mod.excludes) {\n        if (excludedId !== mod.id) {\n          candidates.delete(excludedId);\n        }\n      }\n    }\n  }\n\n  // Build output\n  const sections: string[] = [];\n  for (const mod of candidates.values()) {\n    sections.push(mod.content(iterCtx.ctx));\n  }\n  return sections.join(\"\\n\");\n}\n"]}
+{"version":3,"file":"chat.prompt.modules.js","sourceRoot":"/","sources":["chat/chat.prompt.modules.ts"],"names":[],"mappings":"AAsCA,kFAAkF;AAClF,aAAa;AACb,kFAAkF;AAElF;;;;;;;;;GASG;AACH,MAAM,UAAU,sBAAsB,CACpC,QAAuB;IAEvB,0CAA0C;IAC1C,IAAI,YAAY,GAAG,CAAC,CAAC,CAAC;IACtB,KAAK,IAAI,CAAC,GAAG,QAAQ,CAAC,MAAM,GAAG,CAAC,EAAE,CAAC,IAAI,CAAC,EAAE,CAAC,EAAE,EAAE,CAAC;QAC9C,IAAI,QAAQ,CAAC,CAAC,CAAC,CAAC,QAAQ,EAAE,KAAK,OAAO,EAAE,CAAC;YACvC,YAAY,GAAG,CAAC,CAAC;YACjB,MAAM;QACR,CAAC;IACH,CAAC;IAED,qEAAqE;IACrE,MAAM,SAAS,GAA2D,EAAE,CAAC;IAC7E,MAAM,QAAQ,GAAG,YAAY,GAAG,CAAC,CAAC;IAElC,KAAK,IAAI,CAAC,GAAG,QAAQ,EAAE,CAAC,GAAG,QAAQ,CAAC,MAAM,EAAE,CAAC,EAAE,EAAE,CAAC;QAChD,MAAM,GAAG,GAAG,QAAQ,CAAC,CAAC,CAAC,CAAC;QACxB,IAAI,GAAG,CAAC,QAAQ,EAAE,KAAK,IAAI,EAAE,CAAC;YAC5B,MAAM,KAAK,GAAG,GAAgB,CAAC;YAC/B,MAAM,KAAK,GAAG,KAAK,CAAC,UAAU,IAAI,EAAE,CAAC;YACrC,KAAK,MAAM,EAAE,IAAI,KAAK,EAAE,CAAC;gBACvB,SAAS,CAAC,IAAI,CAAC;oBACb,IAAI,EAAE,EAAE,CAAC,IAAI;oBACb,IAAI,EAAE,CAAC,EAAE,CAAC,IAAI,IAAI,EAAE,CAA4B;iBACjD,CAAC,CAAC;YACL,CAAC;QACH,CAAC;IACH,CAAC;IAED,OAAO,SAAS,CAAC;AACnB,CAAC;AAED,kFAAkF;AAClF,UAAU;AACV,kFAAkF;AAElF;;;GAGG;AACH,SAAS,mBAAmB,CAAC,WAA4C;IACvE,OAAO,WAAW,CAAC,IAAI,CACrB,CAAC,CAAC,EAAE,EAAE,CACJ,CAAC,CAAC,IAAI,KAAK,wBAAwB;QACnC,CAAC,CAAC,CAAC,IAAI,CAAC,YAAY,IAAI,CAAC,CAAC,IAAI,CAAC,iBAAiB,CAAC,CACpD,CAAC;AACJ,CAAC;AAED,kFAAkF;AAClF,qBAAqB;AACrB,kFAAkF;AAElF,MAAM,eAAe,GAAiB;IACpC,EAAE,EAAE,WAAW;IACf,QAAQ,EAAE,CAAC,wBAAwB,EAAE,oBAAoB,EAAE,oBAAoB,CAAC;IAChF,aAAa,EAAE,CAAC,OAAO,EAAE,EAAE,CAAC,CAAC,mBAAmB,CAAC,OAAO,CAAC,WAAW,CAAC;IACrE,OAAO,EAAE,GAAG,EAAE,CAAC;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;CAyDhB;CACA,CAAC;AAEF,MAAM,kBAAkB,GAAiB;IACvC,EAAE,EAAE,cAAc;IAClB,QAAQ,EAAE,CAAC,wBAAwB,CAAC;IACpC,QAAQ,EAAE,CAAC,WAAW,CAAC;IACvB,aAAa,EAAE,CAAC,OAAO,EAAE,EAAE,CAAC,mBAAmB,CAAC,OAAO,CAAC,WAAW,CAAC;IACpE,OAAO,EAAE,GAAG,EAAE,CAAC;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;CAgChB;CACA,CAAC;AAEF,MAAM,oBAAoB,GAAiB;IACzC,EAAE,EAAE,iBAAiB;IACrB,QAAQ,EAAE,CAAC,eAAe,CAAC;IAC3B,OAAO,EAAE,GAAG,EAAE,CAAC;;;;;;;;;;;;;;;;;;;;;CAqBhB;CACA,CAAC;AAEF,MAAM,sBAAsB,GAAiB;IAC3C,EAAE,EAAE,mBAAmB;IACvB,QAAQ,EAAE,CAAC,eAAe,EAAE,eAAe,CAAC;IAC5C,OAAO,EAAE,GAAG,EAAE,CAAC;;;;;;;;;;CAUhB;CACA,CAAC;AAEF,MAAM,kBAAkB,GAAiB;IACvC,EAAE,EAAE,eAAe;IACnB,QAAQ,EAAE,CAAC,oBAAoB,CAAC;IAChC,OAAO,EAAE,GAAG,EAAE,CAAC;;;;;;;;;;;CAWhB;CACA,CAAC;AAEF,MAAM,iBAAiB,GAAiB;IACtC,EAAE,EAAE,cAAc;IAClB,QAAQ,EAAE,CAAC,YAAY,CAAC;IACxB,KAAK,EAAE,gBAAgB;IACvB,OAAO,EAAE,GAAG,EAAE,CAAC;;;;;;;;;;;;;;CAchB;CACA,CAAC;AAEF,MAAM,eAAe,GAAiB;IACpC,EAAE,EAAE,WAAW;IACf,QAAQ,EAAE,CAAC,eAAe,EAAE,gBAAgB,EAAE,2BAA2B,EAAE,gBAAgB,EAAE,gBAAgB,EAAE,2BAA2B,CAAC;IAC3I,OAAO,EAAE,GAAG,EAAE,CAAC;;;;;;;;;;;;;CAahB;CACA,CAAC;AAEF,MAAM,cAAc,GAAiB;IACnC,EAAE,EAAE,UAAU;IACd,QAAQ,EAAE,CAAC,uBAAuB,EAAE,aAAa,EAAE,eAAe,EAAE,gBAAgB,CAAC;IACrF,6EAA6E;IAC7E,+EAA+E;IAC/E,4EAA4E;IAC5E,+EAA+E;IAC/E,aAAa,EAAE,CAAC,OAAO,EAAE,EAAE,CAAC,OAAO,CAAC,GAAG,CAAC,eAAe,KAAK,IAAI;IAChE,OAAO,EAAE,GAAG,EAAE,CAAC;;;;;;;;;;;;;;;;;;;;;;;;;CAyBhB;CACA,CAAC;AAEF,MAAM,mBAAmB,GAAiB;IACxC,EAAE,EAAE,gBAAgB;IACpB,QAAQ,EAAE,CAAC,0BAA0B,CAAC;IACtC,OAAO,EAAE,GAAG,EAAE,CAAC;;;;;;;;;;;CAWhB;CACA,CAAC;AAEF,MAAM,cAAc,GAAiB;IACnC,EAAE,EAAE,UAAU;IACd,QAAQ,EAAE,EAAE;IACZ,KAAK,EAAE,iBAAiB;IACxB,OAAO,EAAE,GAAG,EAAE,CACZ;CACH;CACA,CAAC;AAEF,kFAAkF;AAClF,kBAAkB;AAClB,kFAAkF;AAElF,qCAAqC;AACrC,MAAM,CAAC,MAAM,cAAc,GAAmB;IAC5C,eAAe;IACf,kBAAkB;IAClB,oBAAoB;IACpB,sBAAsB;IACtB,kBAAkB;IAClB,iBAAiB;IACjB,eAAe;IACf,cAAc;IACd,mBAAmB;IACnB,cAAc;CACf,CAAC;AAEF,kFAAkF;AAClF,aAAa;AACb,kFAAkF;AAElF;;;;;;;;;GASG;AACH,MAAM,UAAU,cAAc,CAAC,OAAyB;IACtD,2DAA2D;IAC3D,IAAI,OAAO,CAAC,GAAG,CAAC,YAAY,EAAE,CAAC;QAC7B,OAAO,EAAE,CAAC;IACZ,CAAC;IAED,MAAM,SAAS,GAAG,IAAI,GAAG,CAAC,OAAO,CAAC,WAAW,CAAC,GAAG,CAAC,CAAC,CAAC,EAAE,EAAE,CAAC,CAAC,CAAC,IAAI,CAAC,CAAC,CAAC;IAElE,8BAA8B;IAC9B,MAAM,UAAU,GAAG,IAAI,GAAG,EAAwB,CAAC;IAEnD,KAAK,MAAM,GAAG,IAAI,cAAc,EAAE,CAAC;QACjC,IAAI,OAAO,GAAG,KAAK,CAAC;QAEpB,0EAA0E;QAC1E,IAAI,GAAG,CAAC,QAAQ,CAAC,MAAM,GAAG,CAAC,IAAI,GAAG,CAAC,QAAQ,CAAC,IAAI,CAAC,CAAC,CAAC,EAAE,EAAE,CAAC,SAAS,CAAC,GAAG,CAAC,CAAC,CAAC,CAAC,EAAE,CAAC;YAC1E,OAAO,GAAG,GAAG,CAAC,aAAa,CAAC,CAAC,CAAC,GAAG,CAAC,aAAa,CAAC,OAAO,CAAC,CAAC,CAAC,CAAC,IAAI,CAAC;QAClE,CAAC;QAED,sBAAsB;QACtB,IAAI,CAAC,OAAO,IAAI,GAAG,CAAC,KAAK,IAAI,OAAO,CAAC,cAAc,IAAI,GAAG,CAAC,KAAK,CAAC,IAAI,CAAC,OAAO,CAAC,cAAc,CAAC,EAAE,CAAC;YAC9F,OAAO,GAAG,IAAI,CAAC;QACjB,CAAC;QAED,IAAI,OAAO,EAAE,CAAC;YACZ,UAAU,CAAC,GAAG,CAAC,GAAG,CAAC,EAAE,EAAE,GAAG,CAAC,CAAC;QAC9B,CAAC;IACH,CAAC;IAED,kDAAkD;IAClD,KAAK,MAAM,GAAG,IAAI,UAAU,CAAC,MAAM,EAAE,EAAE,CAAC;QACtC,IAAI,GAAG,CAAC,QAAQ,EAAE,CAAC;YACjB,KAAK,MAAM,UAAU,IAAI,GAAG,CAAC,QAAQ,EAAE,CAAC;gBACtC,IAAI,UAAU,KAAK,GAAG,CAAC,EAAE,EAAE,CAAC;oBAC1B,UAAU,CAAC,MAAM,CAAC,UAAU,CAAC,CAAC;gBAChC,CAAC;YACH,CAAC;QACH,CAAC;IACH,CAAC;IAED,eAAe;IACf,MAAM,QAAQ,GAAa,EAAE,CAAC;IAC9B,KAAK,MAAM,GAAG,IAAI,UAAU,CAAC,MAAM,EAAE,EAAE,CAAC;QACtC,QAAQ,CAAC,IAAI,CAAC,GAAG,CAAC,OAAO,CAAC,OAAO,CAAC,GAAG,CAAC,CAAC,CAAC;IAC1C,CAAC;IACD,OAAO,QAAQ,CAAC,IAAI,CAAC,IAAI,CAAC,CAAC;AAC7B,CAAC","sourcesContent":["import type { BaseMessage, AIMessage } from \"@langchain/core/messages\";\n\nimport type { ResolvedToolContext } from \"../shared/agent/tool.factory.js\";\n\n// ═══════════════════════════════════════════════════════════════════════════════\n// TYPES\n// ═══════════════════════════════════════════════════════════════════════════════\n\n/**\n * A conditional prompt section injected into the system prompt based on triggers.\n */\nexport interface PromptModule {\n  /** Unique module identifier. */\n  id: string;\n  /** Tool names that activate this module. */\n  triggers: string[];\n  /** Module IDs to suppress when this module activates (unidirectional). */\n  excludes?: string[];\n  /** Optional filter applied after tool trigger match. Return false to skip despite trigger match. */\n  triggerFilter?: (iterCtx: IterationContext) => boolean;\n  /** User message pattern that activates this module (secondary trigger). */\n  regex?: RegExp;\n  /** Returns the prompt text to inject. */\n  content: (ctx: ResolvedToolContext) => string;\n}\n\n/**\n * State available to module resolution at each iteration.\n */\nexport interface IterationContext {\n  /** Tool calls from all iterations since the last user message. */\n  recentTools: Array<{ name: string; args: Record<string, unknown> }>;\n  /** Text of the latest user message (for regex matching). */\n  currentMessage?: string;\n  /** Resolved tool context (user, profile, indexes, etc.). */\n  ctx: ResolvedToolContext;\n}\n\n// ═══════════════════════════════════════════════════════════════════════════════\n// EXTRACTION\n// ═══════════════════════════════════════════════════════════════════════════════\n\n/**\n * Extracts tool calls from all AI messages since the last HumanMessage.\n *\n * Scans backwards to find the last HumanMessage, then collects all tool calls\n * from AIMessages after that point. This ensures multi-iteration tool history\n * is available for module resolution within a single user turn.\n *\n * @param messages - The current conversation message array\n * @returns Flattened array of tool name + args from the current agent turn\n */\nexport function extractRecentToolCalls(\n  messages: BaseMessage[],\n): Array<{ name: string; args: Record<string, unknown> }> {\n  // Find the index of the last HumanMessage\n  let lastHumanIdx = -1;\n  for (let i = messages.length - 1; i >= 0; i--) {\n    if (messages[i]._getType() === \"human\") {\n      lastHumanIdx = i;\n      break;\n    }\n  }\n\n  // Collect tool calls from all AIMessages after the last HumanMessage\n  const toolCalls: Array<{ name: string; args: Record<string, unknown> }> = [];\n  const startIdx = lastHumanIdx + 1;\n\n  for (let i = startIdx; i < messages.length; i++) {\n    const msg = messages[i];\n    if (msg._getType() === \"ai\") {\n      const aiMsg = msg as AIMessage;\n      const calls = aiMsg.tool_calls ?? [];\n      for (const tc of calls) {\n        toolCalls.push({\n          name: tc.name,\n          args: (tc.args ?? {}) as Record<string, unknown>,\n        });\n      }\n    }\n  }\n\n  return toolCalls;\n}\n\n// ═══════════════════════════════════════════════════════════════════════════════\n// HELPERS\n// ═══════════════════════════════════════════════════════════════════════════════\n\n/**\n * Checks whether recent tool calls include discover_opportunities with\n * introduction-specific arguments (partyUserIds or introTargetUserId).\n */\nfunction hasIntroductionArgs(recentTools: IterationContext[\"recentTools\"]): boolean {\n  return recentTools.some(\n    (t) =>\n      t.name === \"discover_opportunities\" &&\n      (t.args.partyUserIds || t.args.introTargetUserId),\n  );\n}\n\n// ═══════════════════════════════════════════════════════════════════════════════\n// MODULE DEFINITIONS\n// ═══════════════════════════════════════════════════════════════════════════════\n\nconst discoveryModule: PromptModule = {\n  id: \"discovery\",\n  triggers: [\"discover_opportunities\", \"update_opportunity\", \"list_opportunities\"],\n  triggerFilter: (iterCtx) => !hasIntroductionArgs(iterCtx.recentTools),\n  content: () => `\n### 1. User wants to find connections or discover (default for connection-seeking)\n\nFor open-ended connection-seeking (\"find me a mentor\", \"who needs a React dev\", \"I want to meet people in AI\", \"looking for investors\", \"find me X\"), run **discovery first**.\n\n**CRITICAL: DO NOT create an intent first. Discovery comes FIRST.**\n\n**Network scoping**: When the user says \"in my network\", \"from my contacts\", \"people I know\", \"among my connections\", or similar network-scoping language, pass the user's **personal index ID** as \\`networkId\\`. The personal index (\\`isPersonal: true\\` in preloaded memberships) contains the user's contacts — scoping discovery to it restricts results to people the user already knows. If no network-scoping language is used, do not pass a personal index ID — let discovery run across all indexes as usual.\n\n- Call \\`discover_opportunities(searchQuery=user's request)\\` IMMEDIATELY (with networkId when scoped).\n- Do NOT call \\`create_intent\\` unless the user **explicitly** asks to \"create\", \"save\", \"add\", or \"remember\" an intent/signal.\n- Phrases like \"looking for X\", \"find me X\", \"I want to meet X\", \"I need X\" are discovery requests — NOT intent creation requests.\n- If the tool returns \\`createIntentSuggested\\` and \\`suggestedIntentDescription\\`, the system will create an intent and retry discovery automatically; use the final result (candidates or \"no matches\") for your reply.\n- If the tool returns \\`suggestIntentCreationForVisibility: true\\` and \\`suggestedIntentDescription\\`, after presenting the opportunity cards ask the user whether they'd also like to create a signal so others can find them (e.g. *\"Would you also like to create a signal for this so others can find you?\"*). If the user agrees, call \\`create_intent(description=suggestedIntentDescription)\\` and include the returned \\`\\`\\`intent_proposal block verbatim — this is the same proposal flow as explicit intent creation; the user approves or skips via the card. Ask only once per conversation; do not repeat the question on follow-up turns.\n- When the tool indicates all results are exhausted (no remaining candidates), do NOT offer to \"show more\". Instead suggest the user create a signal so others can find them. This uses the same \\`create_intent\\` flow as above.\n- If the user **explicitly** says they want to create/save an intent (e.g. \"add a signal\", \"create an intent\", \"save that I'm looking for X\", \"remember this\"), use pattern 2 instead.\n\n### 1a. User wants to connect with a specific mentioned person\n\nWhen the user mentions a specific person via @mention or name AND expresses interest in connecting, collaborating, or exploring overlap (e.g. \"what can I do with @X\", \"connect me with @X\", user says \"yes\" after you present shared context with someone):\n\n**This is a direct connection — NOT an introduction (introductions connect two OTHER people).**\n\n\\`\\`\\`\n1. If not already done: read_user_contexts(userId=X) + read_network_memberships(userId=X)\n2. Find shared indexes with the user (intersect with preloaded memberships)\n3. If no shared indexes: tell the user you can't find a connection path\n4. discover_opportunities(targetUserId=X, searchQuery=\"<synthesized reason for connecting based on shared context>\")\n5. Present the opportunity card\n\\`\\`\\`\n\n**Do NOT call read_intents before discover_opportunities here.** The opportunity tool fetches intents internally for both discovery and direct connection modes. Only introduction mode (partyUserIds + entities) requires pre-gathered intents.\n\nThe searchQuery should be a brief description of why they'd connect (e.g. \"shared interest in design and technology, both in Kernel community\"). This gives the evaluator context for scoring.\n\n### 7. Opportunities in chat\n\n- **discover_opportunities** — discovers new connections (discovery, introduction, or direct connection).\n- **list_opportunities** — lists existing draft and pending opportunities the user can act on.\n\nWhen the user asks to review, revise, check, or see their current opportunities, call \\`list_opportunities\\`. Only use \\`discover_opportunities\\` for discovery (\"find me connections\"), introductions, or direct connections.\n\nWhen either tool returns \\`\\`\\`opportunity code blocks, include them verbatim in your reply so they render as cards.\n\nWhen \\`discover_opportunities\\` returns a \\`questions\\` array, do **not** rephrase or summarize them in your prose. The frontend renders them as an interactive decision card surface. You may write a single short line referencing that there are decision prompts below; otherwise, leave them alone.\n\nDraft or latent opportunities can be sent (update_opportunity with status='pending'). Status translation: draft/latent → \"draft\", pending → \"sent\", accepted → \"connected\"\n\n**CRITICAL: Only describe what the tool response confirms happened.** \"pending\" sends a notification — not a message or invite. \"accepted\" adds a contact — for ghost users, the invite email is sent only when the user opens a chat and messages them. Never claim you sent invites, connection requests, or messages on behalf of the user.\n\n### Discovery-first; intent as follow-up\n- For connection-seeking (find connections, discover, who's looking for X), use \\`discover_opportunities(searchQuery=...)\\` first. Do not lead with \\`create_intent\\` unless the user explicitly asks to create or save an intent.\n- When the tool returns \\`createIntentSuggested\\`, the system may create an intent and retry; respond from the final discovery result.\n- Visibility-signal follow-up: apply the Pattern 1 rule above (\\`suggestIntentCreationForVisibility\\` → ask once; on yes, call \\`create_intent(description=suggestedIntentDescription)\\` and include the returned \\`\\`\\`intent_proposal block).\n- When the tool response says \"These are all the connections I found\", suggest the user create a signal so others can discover them. Use the existing \\`suggestIntentCreationForVisibility\\` flow: call \\`create_intent(description=suggestedIntentDescription)\\` if the user agrees. Do not ask \"Would you like to see more?\" when there are no more candidates.\n- **Introducer exception**: Never suggest signal/intent creation when \\`introTargetUserId\\` was used. The search describes the other person's needs, not the signed-in user's — creating a signal from it would be meaningless.\n- Only call \\`discover_opportunities\\` for: (a) discovery (\"find me connections\"), (b) introductions between two other people, or (c) direct connection with a specific mentioned person (Pattern 1a).\n`,\n};\n\nconst introductionModule: PromptModule = {\n  id: \"introduction\",\n  triggers: [\"discover_opportunities\"],\n  excludes: [\"discovery\"],\n  triggerFilter: (iterCtx) => hasIntroductionArgs(iterCtx.recentTools),\n  content: () => `\n### 6. Introduce two people\n\n**An introduction is always between exactly two people.** Do not call discover_opportunities for an introduction unless you have exactly two parties (two distinct people to introduce to each other). The entities array must have exactly two entities. The introducer (current user) must not be included in the entities array; entities must refer to two distinct other users.\n\n**You MUST gather all context before calling discover_opportunities. The tool does NOT fetch data internally.**\n\n\\`\\`\\`\n1. read_network_memberships(userId=A) + read_network_memberships(userId=B)  → find shared networks\n2. If no shared indexes: tell user they're not in any shared community\n3. read_user_contexts(userId=A) + read_user_contexts(userId=B)\n4. For each shared index: read_intents(networkId=X, userId=A) + read_intents(networkId=X, userId=B)\n5. Summarize to user: \"Here's what I found about A and B...\"\n6. discover_opportunities(partyUserIds=[A,B], entities=[{userId:A, profile:{...}, intents:[...], networkId:shared}, {userId:B, ...}], hint=\"user's reason\")\n7. Present the draft introduction\n\\`\\`\\`\n\nThe entities array must include each party's userId, profile data, intents from shared indexes, and the shared networkId. The hint is the user's stated reason (e.g. \"both AI devs\"). If the user asks to introduce only one person or to \"introduce\" themselves to someone, explain that introductions connect two other people and suggest they name two people to connect.\n\n### 6a. Discover who to introduce to someone\n\n**When the user asks \"who should I introduce to @Person\" or \"find connections for @Person\"** — they want YOU to discover good connections for that person, presented as introduction cards.\n\n\\`\\`\\`\n1. Identify the person's userId from the @mention (call it mentionedUserId)\n2. discover_opportunities(introTargetUserId=mentionedUserId, searchQuery=\"<optional refinement>\")\n3. Present the returned cards (they will be formatted as introduction cards automatically)\n\\`\\`\\`\n\nThis is different from Pattern 6 (where user names BOTH parties). Here the user names ONE person and asks you to find connections for them. Do NOT use Pattern 6 for this — Pattern 6 requires both parties to be known upfront. Do NOT ask the user for a second person. Do NOT use targetUserId or partyUserIds. The system will find connections automatically.\n\n**CRITICAL — no signal creation in introducer flows:** When \\`introTargetUserId\\` is used (Patterns 6 and 6a), the user is searching for connections on behalf of someone else — the search reflects the other person's needs, not the user's own. Do NOT suggest creating a signal or intent in this context. The search query describes what the *other person* needs (e.g. \"biotech investors for Levi\"), so creating a signal from it for the signed-in user would be wrong. Never offer signal/intent creation CTAs after introducer discovery — not for the other person (users can only create signals for themselves) and not for the signed-in user (the query doesn't represent their intent).\n`,\n};\n\nconst intentCreationModule: PromptModule = {\n  id: \"intent-creation\",\n  triggers: [\"create_intent\"],\n  content: () => `\n### 2. User explicitly wants to create or save an intent\n\n**YOU decide if it's specific enough. The tool proposes — the user confirms.**\n\n\\`\\`\\`\nIF description is vague (\"find a job\", \"meet people\", \"learn something\"):\n  1. read_user_contexts()           → get their background\n  2. read_intents()                 → see existing intents for context\n  3. THINK: given their profile and existing intents, suggest a refined version\n  4. Reply: \"Based on your background in X, did you mean something like 'Y'?\"\n  5. Wait for confirmation\n  6. On \"yes\" → create_intent(description=exact_refined_text)\n\nIF description is specific enough (\"contribute to an open-source LLM project\"):\n  → create_intent(description=...) directly\n\\`\\`\\`\n\n**CRITICAL: Never write a \\`\\`\\`intent_proposal block yourself.** To propose an intent you MUST call create_intent(description=...). The tool returns a \\`\\`\\`intent_proposal code block (with proposalId and description). You MUST include that exact block verbatim in your response — it renders as an interactive card. Do not summarize or invent the block; only the tool provides a valid one. Add a brief explanation that creating this intent will let the system look for relevant people in the background.\n\nSpecificity test: Does it contain a concrete domain, action, or scope? If just a single generic verb+noun (\"find a job\"), it's vague. If it has qualifying detail (\"senior UX design role at a tech company in Berlin\"), it's specific.\n`,\n};\n\nconst intentManagementModule: PromptModule = {\n  id: \"intent-management\",\n  triggers: [\"update_intent\", \"delete_intent\"],\n  content: () => `\n### 4. Update or delete an intent\n\n**YOU look up the ID first.**\n\n\\`\\`\\`\n1. read_intents() → get current intents with IDs\n2. Match user's request to the right intent\n3. update_intent(intentId=exact_id, description=...) or delete_intent(intentId=exact_id)\n\\`\\`\\`\n`,\n};\n\nconst personLookupModule: PromptModule = {\n  id: \"person-lookup\",\n  triggers: [\"read_user_contexts\"],\n  content: () => `\n### 0. User asks about a specific person by name\n\nWhen the user mentions a specific person by name (\"find [name]\", \"look up [name]\", \"who is [name]?\", \"tell me about [name]\"), look them up by name first — do NOT use discovery.\n\n- Call \\`read_user_contexts(query=\"the name\")\\` — this finds members by name across the user's indexes\n- If one match: the result already includes their full profile; present it naturally\n- If multiple matches: present the list and ask the user to clarify which person\n- If no matches: tell the user you couldn't find anyone by that name in their network\n- If the user then asks for semantic discovery (e.g. \"find people like them\"), use Pattern 1.\n- If the user wants to connect with this specific person (e.g. \"yes, connect us\", \"what can I do with them\", \"I'd like to reach out\"), use Pattern 1a.\n`,\n};\n\nconst urlScrapingModule: PromptModule = {\n  id: \"url-scraping\",\n  triggers: [\"scrape_url\"],\n  regex: /(https?:\\/\\/)/i,\n  content: () => `\n### 3. User includes a URL\n\n**YOU handle scraping before intent creation.**\n\n\\`\\`\\`\n1. scrape_url(url, objective=\"Extract key details for an intent\")\n2. Synthesize a conceptual description from scraped content\n3. create_intent(description=synthesized_summary)\n\\`\\`\\`\n\nException: for profile creation, pass URLs directly to create_user_context (it handles scraping internally).\n\nIf the user pastes or types a profile URL (e.g. linkedin.com/..., github.com/...) to create or update their profile, you MUST pass that exact URL in the corresponding parameter (e.g. linkedinUrl, githubUrl, twitterUrl) to create_user_context, or use scrape_url with that URL then update_user_context; do not use the user's stored social links for that request.\n`,\n};\n\nconst communityModule: PromptModule = {\n  id: \"community\",\n  triggers: [\"read_networks\", \"create_network\", \"create_network_membership\", \"update_network\", \"delete_network\", \"delete_network_membership\"],\n  content: () => `\n### 8. Explore what a community is about\n\n\\`\\`\\`\n0. If user asks about communities they belong to, first use preloaded memberships in this prompt.\n1. read_networks() → get network details (title, prompt)\n2. read_intents(networkId=X) → what members are looking for\n3. read_network_memberships(networkId=X) → who's in it\n4. Synthesize: community purpose, active needs, member composition\n\\`\\`\\`\n\n### When to mention community/index\nIndex and community membership is background: handle it without talking about indexes unless the user asks or it's sign-up, leave, or owner settings. Do not proactively mention \"your indexes\", \"your communities\", \"which index\", \"in your current communities\", or similar. Only mention indexes (or communities, lists) when: (i) post-onboarding sign-up to a community, (ii) user explicitly asked about their indexes/communities, (iii) user wants to leave one, (iv) owner is changing index/community settings. Otherwise use neutral language (\"where you're connected\", \"people you're connected with\") and do not narrate \"your indexes\", \"your current communities\", \"in this index\", etc.\n`,\n};\n\nconst contactsModule: PromptModule = {\n  id: \"contacts\",\n  triggers: [\"import_gmail_contacts\", \"add_contact\", \"list_contacts\", \"remove_contact\"],\n  // Gate on the CONTACTS_ENABLED flag (fail-closed: only `true` enables). When\n  // contacts are disabled the import/add tools are de-registered, so this module\n  // must not be injected — otherwise the orchestrator keeps advertising Gmail\n  // import / add_contact and offers an action that then fails as \"Unknown tool\".\n  triggerFilter: (iterCtx) => iterCtx.ctx.contactsEnabled === true,\n  content: () => `\n### 9. Import contacts from Gmail\n\n**Single-step workflow:**\n\n\\`\\`\\`\nimport_gmail_contacts()\n→ If not connected: returns { requiresAuth: true, authUrl: \"...\" } — share the URL with the user\n→ If connected: imports contacts directly and returns stats { imported, skipped, newContacts, existingContacts }\n\\`\\`\\`\n\nGhost users are contacts without accounts — they're enriched with public data (LinkedIn, GitHub, X) and can appear in opportunity discovery once enriched.\n\n### 10. Add or manage contacts manually\n\n\\`\\`\\`\n# Add a single contact\nadd_contact(email=\"alice@example.com\", name=\"Alice Smith\")\n\n# List user's network\nlist_contacts() → returns contacts with names, emails, and whether they're ghost users\n\n# Remove a contact\nremove_contact(contactId=X)\n\\`\\`\\`\n`,\n};\n\nconst sharedContextModule: PromptModule = {\n  id: \"shared-context\",\n  triggers: [\"read_network_memberships\"],\n  content: () => `\n### 5. Find shared context between two users\n\n\\`\\`\\`\n1. read_network_memberships(userId=me)     → my networks\n2. read_network_memberships(userId=other)  → their networks\n3. Intersect networkIds\n4. For each shared index: read_intents(networkId=shared)\n5. read_user_contexts(userId=other)\n6. Synthesize: what overlaps, where they could collaborate\n\\`\\`\\`\n`,\n};\n\nconst mentionsModule: PromptModule = {\n  id: \"mentions\",\n  triggers: [],\n  regex: /@\\[.*?\\]\\(.*?\\)/,\n  content: () =>\n    `- Messages may contain \\`@[Display Name](userId)\\` markup. The value in parentheses is the userId.\n`,\n};\n\n// ═══════════════════════════════════════════════════════════════════════════════\n// MODULE REGISTRY\n// ═══════════════════════════════════════════════════════════════════════════════\n\n/** All registered prompt modules. */\nexport const PROMPT_MODULES: PromptModule[] = [\n  discoveryModule,\n  introductionModule,\n  intentCreationModule,\n  intentManagementModule,\n  personLookupModule,\n  urlScrapingModule,\n  communityModule,\n  contactsModule,\n  sharedContextModule,\n  mentionsModule,\n];\n\n// ═══════════════════════════════════════════════════════════════════════════════\n// RESOLUTION\n// ═══════════════════════════════════════════════════════════════════════════════\n\n/**\n * Resolves which prompt modules should be injected for the current iteration.\n *\n * Phase 1: Skip all modules when onboarding is active (early exit).\n * Phase 2: Collect candidate modules by checking triggers and regex.\n * Phase 3: Apply exclusions (unidirectional — the excluding module stays).\n *\n * @param iterCtx - Current iteration context (tool history, user message, resolved context)\n * @returns Concatenated prompt text from all matched modules\n */\nexport function resolveModules(iterCtx: IterationContext): string {\n  // Phase 1 (early exit): Skip all modules during onboarding\n  if (iterCtx.ctx.isOnboarding) {\n    return \"\";\n  }\n\n  const toolNames = new Set(iterCtx.recentTools.map((t) => t.name));\n\n  // Phase 2: Collect candidates\n  const candidates = new Map<string, PromptModule>();\n\n  for (const mod of PROMPT_MODULES) {\n    let matched = false;\n\n    // Check tool triggers (with optional filter for arg-based disambiguation)\n    if (mod.triggers.length > 0 && mod.triggers.some((t) => toolNames.has(t))) {\n      matched = mod.triggerFilter ? mod.triggerFilter(iterCtx) : true;\n    }\n\n    // Check regex trigger\n    if (!matched && mod.regex && iterCtx.currentMessage && mod.regex.test(iterCtx.currentMessage)) {\n      matched = true;\n    }\n\n    if (matched) {\n      candidates.set(mod.id, mod);\n    }\n  }\n\n  // Phase 3: Apply exclusions (skip self-exclusion)\n  for (const mod of candidates.values()) {\n    if (mod.excludes) {\n      for (const excludedId of mod.excludes) {\n        if (excludedId !== mod.id) {\n          candidates.delete(excludedId);\n        }\n      }\n    }\n  }\n\n  // Build output\n  const sections: string[] = [];\n  for (const mod of candidates.values()) {\n    sections.push(mod.content(iterCtx.ctx));\n  }\n  return sections.join(\"\\n\");\n}\n"]}

package/dist/contact/contact.tools.js

@@ -54,9 +54,9 @@ export function createContactTools(defineTool, deps) {
             "(via import_contacts, add_contact, or import_gmail_contacts) stored as members of their personal index.\n\n" +
             "**When to use:** To see who's in the user's network, find a contact's userId for other operations, " +
             "or check if a specific person is already a contact.\n\n" +
-            "**Returns:** Array of contacts, each with: userId (use with read_user_profiles or discover_opportunities), " +
+            "**Returns:** Array of contacts, each with: userId (use with read_user_contexts or discover_opportunities), " +
             "name, email, avatar URL, and isGhost (true = no account yet, profile enriched from public data). " +
-            "Use the userId with read_user_profiles(userId) to get the full profile, or with discover_opportunities(targetUserId) to connect.",
+            "Use the userId with read_user_contexts(userId) to get the full profile, or with discover_opportunities(targetUserId) to connect.",
         querySchema: z.object({
             limit: z.number().optional().describe('Maximum number of contacts to return. Omit to return all contacts. Use for large networks to paginate results.'),
         }),
@@ -141,7 +141,7 @@ export function createContactTools(defineTool, deps) {
         name: 'search_contacts',
         description: "Searches the authenticated user's personal network by name or email (case-insensitive substring). " +
             "Use when the user refers to a contact by partial name or email and you need their userId for another tool " +
-            "(e.g. read_user_profiles, discover_opportunities).\n\n" +
+            "(e.g. read_user_contexts, discover_opportunities).\n\n" +
             "**When to use:** Before list_contacts when the network is large — returns only matching contacts, bounded by limit.\n\n" +
             "**Returns:** Array of matching contacts: userId, name, email, avatar, isGhost.",
         querySchema: z.object({