@indexnetwork/protocol 12.1.0-rc.463.1 → 13.0.0-rc.464.1

package/dist/questions/public/index.d.ts

@@ -40,8 +40,8 @@
 export * from "../domain/index.js";
 export { QuestionerAgent } from "../application/index.js";
 export type { QuestionerAgentConfig } from "../application/index.js";
-export { isQuestionerEnabled, isDiscoveryQuestionsEnabled, isUptakeGuardEnabled, uptakeAuthorityThreshold, discoveryQuestionsInputMode, discoveryQuestionsTimeoutMs, DISCOVERY_QUESTIONS_TIMEOUT_MS_DEFAULT, UPTAKE_AUTHORITY_THRESHOLD_DEFAULT, } from "../application/index.js";
+export { isQuestionerEnabled, isUptakeGuardEnabled, uptakeAuthorityThreshold, UPTAKE_AUTHORITY_THRESHOLD_DEFAULT, } from "../application/index.js";
 export { isValidQuestionerInputContract, } from "../application/index.js";
 export type { QuestionerInput, QuestionerEnqueuePayload, QuestionerEnqueueFn, PoolDiscoveryContext, RecoveryQuestionerInput, UptakeQuestionerInput, PostStallQuestionerInput, InflightQuestionerInput, } from "../application/index.js";
 export { createQuestionerTools, createAskUserQuestionTools } from "../application/index.js";
-export type { AskUserQuestionToolDeps, ChatQuestionAnswerOutcome, ChatQuestionsHost, PersistableQuestion, PersistedQuestion, QuestionFilters, QuestionGeneratorReader, QuestionerDatabase, QuestionerToolDeps, } from "../ports/index.js";
+export type { AskUserQuestionToolDeps, ChatQuestionAnswerOutcome, ChatQuestionsHost, PersistableQuestion, PersistedQuestion, QuestionFilters, QuestionerDatabase, QuestionerToolDeps, } from "../ports/index.js";

package/dist/questions/public/index.js

@@ -42,7 +42,7 @@ export * from "../domain/index.js";
 // ── Application: agent ────────────────────────────────────────────────────────
 export { QuestionerAgent } from "../application/index.js";
 // ── Application: env accessors ────────────────────────────────────────────────
-export { isQuestionerEnabled, isDiscoveryQuestionsEnabled, isUptakeGuardEnabled, uptakeAuthorityThreshold, discoveryQuestionsInputMode, discoveryQuestionsTimeoutMs, DISCOVERY_QUESTIONS_TIMEOUT_MS_DEFAULT, UPTAKE_AUTHORITY_THRESHOLD_DEFAULT, } from "../application/index.js";
+export { isQuestionerEnabled, isUptakeGuardEnabled, uptakeAuthorityThreshold, UPTAKE_AUTHORITY_THRESHOLD_DEFAULT, } from "../application/index.js";
 // ── Application: input types and validation ───────────────────────────────────
 export { isValidQuestionerInputContract, } from "../application/index.js";
 // ── Application: foreground adapter tools ─────────────────────────────────────

package/dist/runtime/foreground/composition/tool.factory.js

@@ -117,7 +117,7 @@ export async function createChatTools(deps, preResolvedContext) {
         : undefined;
     const intentGraph = new IntentGraphFactory(database, embedder, deps.intentQueue, sessionAwareEnqueue).createGraph();
     const premiseGraph = new PremiseGraphFactory(database, embedder).createGraph();
-    const profileGraph = new EnrichmentGraphFactory(database, scraper, deps.enricher, sessionAwareEnqueue, premiseGraph).createGraph();
+    const profileGraph = new EnrichmentGraphFactory(database, scraper, deps.enricher, premiseGraph).createGraph();
     const hydeCache = deps.hydeCache;
     const lensInferrer = new LensInferrer();
     const hydeGenerator = new HydeGenerator();
@@ -169,7 +169,6 @@ export async function createChatTools(deps, preResolvedContext) {
         frontendUrl: deps.frontendUrl,
         apiBaseUrl: deps.apiBaseUrl,
         ...(deps.chatSummary && { chatSummary: deps.chatSummary }),
-        ...(deps.questionGenerator && { questionGenerator: deps.questionGenerator }),
         ...(sessionAwareEnqueue && { questionerEnqueue: sessionAwareEnqueue }),
         ...(deps.findPendingQuestions && { findPendingQuestions: deps.findPendingQuestions }),
         ...(deps.answerPendingQuestion && { answerPendingQuestion: deps.answerPendingQuestion }),

package/dist/shared/agent/activity-projection.d.ts

@@ -136,13 +136,13 @@ export declare const ActivitySummaryResponseSchema: z.ZodObject<{
         title: z.ZodString;
         count: z.ZodNumber;
     }, "strict", z.ZodTypeAny, {
+        count: number;
         title: string;
         intentId: string;
-        count: number;
     }, {
+        count: number;
         title: string;
         intentId: string;
-        count: number;
     }>, "many">>;
     /** questions domain (meta-network) — counts grouped by affected domain. */
     pendingQuestionsByDomain: z.ZodOptional<z.ZodObject<{
@@ -199,9 +199,9 @@ export declare const ActivitySummaryResponseSchema: z.ZodObject<{
     liveSignalsWatched?: number | undefined;
     opportunitiesSurfaced?: number | undefined;
     opportunitiesBySignal?: {
+        count: number;
         title: string;
         intentId: string;
-        count: number;
     }[] | undefined;
     pendingQuestionsByDomain?: {
         chat?: number | undefined;
@@ -226,9 +226,9 @@ export declare const ActivitySummaryResponseSchema: z.ZodObject<{
     liveSignalsWatched?: number | undefined;
     opportunitiesSurfaced?: number | undefined;
     opportunitiesBySignal?: {
+        count: number;
         title: string;
         intentId: string;
-        count: number;
     }[] | undefined;
     pendingQuestionsByDomain?: {
         chat?: number | undefined;

package/dist/shared/agent/activity-projection.js

@@ -53,6 +53,12 @@ export const ActivityQuestionDomainSchema = z.enum([
  * bucket so a future protocol mode can never leak to an agent caller.
  */
 export const QUESTION_MODE_TO_DOMAIN = {
+    // `enrichment` and `discovery` are retired generators — no new question is
+    // ever produced in either mode. Their rows predate the removal and remain
+    // answerable, so both keep their original affected-domain mapping: dropping
+    // them here would silently fall back to the "chat" domain and change which
+    // permission an agent needs to answer a pre-existing row.
+    //
     // Enrichment answers run the PremiseGraph lifecycle (createPremiseFromAnswer →
     // PremiseEvents.onCreated), so enrichment questions affect the premises domain.
     enrichment: "premises",

package/dist/shared/agent/tool.helpers.d.ts

@@ -12,7 +12,6 @@ import type { IntentGraphQueue } from "../interfaces/queue.interface.js";
 import type { ChatSessionReader } from "../interfaces/chat-session.interface.js";
 import type { ChatSummaryReader } from "../interfaces/chat-summary.interface.js";
 import type { ChatMessageWriter } from "../interfaces/chat-message-writer.interface.js";
-import type { QuestionGeneratorReader } from "../../questions/ports/question.generator.port.js";
 import type { NegotiationSummaryReader } from "../interfaces/negotiation-summary.interface.js";
 import type { Embedder } from "../interfaces/embedder.interface.js";
 import type { AgentDatabase } from "../../participant-agents/ports/index.js";
@@ -161,8 +160,6 @@ interface ToolContextBindings {
     chatSummary?: ChatSummaryReader;
     /** Writes user messages into the user's most-recent chat session (Slice 5 MCP elicitation). */
     chatMessageWriter?: ChatMessageWriter;
-    /** Decision-question generator. Optional; consumers fall back to no `questions`. */
-    questionGenerator?: QuestionGeneratorReader;
     /**
      * Optional async question enqueue callback. When provided, question generation
      * is dispatched asynchronously to the QuestionerQueue instead of running inline.
@@ -413,13 +410,10 @@ interface ToolDepsBindings {
     };
     /** Writes user messages into the user's most-recent chat session (Slice 5 MCP elicitation). */
     chatMessageWriter?: ChatMessageWriter;
-    /** Decision-question generator. Optional; consumers fall back to no `questions`. */
-    questionGenerator?: QuestionGeneratorReader;
     /**
      * Optional async question enqueue callback. When provided, question generation
-     * is dispatched asynchronously to the QuestionerQueue instead of running inline
-     * via the `questionGenerator`. Injected by the composition root when
-     * QUESTIONER_ENABLED=true.
+     * is dispatched asynchronously to the QuestionerQueue. Injected by the
+     * composition root when QUESTIONER_ENABLED=true.
      */
     questionerEnqueue?: QuestionerEnqueueFn;
     /**

package/dist/shared/schemas/discovery-question.schema.d.ts

@@ -1,12 +1,8 @@
 /**
- * DiscoveryQuestionInput and nested types.
- * Leaf types have full Zod schemas. The composite DiscoveryQuestionInput is
- * a pure interface referencing cross-schema types (DiscoveryNegotiationDigest,
- * ChatContextDigest) to avoid Zod cross-schema runtime coupling.
+ * Discovery negotiation summary types shared by the opportunity graph and its
+ * negotiation-summary builder. Leaf types carry full Zod schemas.
  */
 import { z } from "zod";
-import type { DiscoveryNegotiationDigest } from "./negotiation-digest.schema.js";
-import type { ChatContextDigest } from "./chat-context.schema.js";
 export declare const NegotiationRoleSchema: z.ZodEnum<["agent", "patient", "peer"]>;
 export type NegotiationRole = z.infer<typeof NegotiationRoleSchema>;
 export declare const DiscoveryTurnSchema: z.ZodObject<{
@@ -24,18 +20,18 @@ export declare const DiscoveryTurnSchema: z.ZodObject<{
     }>;
 }, "strip", z.ZodTypeAny, {
     reasoning: string;
+    action: "propose" | "accept" | "reject" | "counter" | "question" | "outreach" | "withdraw" | "decline" | "ask_user";
     suggestedRoles: {
         ownUser: "agent" | "patient" | "peer";
         otherUser: "agent" | "patient" | "peer";
     };
-    action: "propose" | "accept" | "reject" | "counter" | "question" | "outreach" | "withdraw" | "decline" | "ask_user";
 }, {
     reasoning: string;
+    action: "propose" | "accept" | "reject" | "counter" | "question" | "outreach" | "withdraw" | "decline" | "ask_user";
     suggestedRoles: {
         ownUser: "agent" | "patient" | "peer";
         otherUser: "agent" | "patient" | "peer";
     };
-    action: "propose" | "accept" | "reject" | "counter" | "question" | "outreach" | "withdraw" | "decline" | "ask_user";
 }>;
 export type DiscoveryTurn = z.infer<typeof DiscoveryTurnSchema>;
 export declare const DiscoveryOutcomeSchema: z.ZodObject<{
@@ -89,18 +85,18 @@ export declare const DiscoveryNegotiationSchema: z.ZodObject<{
         }>;
     }, "strip", z.ZodTypeAny, {
         reasoning: string;
+        action: "propose" | "accept" | "reject" | "counter" | "question" | "outreach" | "withdraw" | "decline" | "ask_user";
         suggestedRoles: {
             ownUser: "agent" | "patient" | "peer";
             otherUser: "agent" | "patient" | "peer";
         };
-        action: "propose" | "accept" | "reject" | "counter" | "question" | "outreach" | "withdraw" | "decline" | "ask_user";
     }, {
         reasoning: string;
+        action: "propose" | "accept" | "reject" | "counter" | "question" | "outreach" | "withdraw" | "decline" | "ask_user";
         suggestedRoles: {
             ownUser: "agent" | "patient" | "peer";
             otherUser: "agent" | "patient" | "peer";
         };
-        action: "propose" | "accept" | "reject" | "counter" | "question" | "outreach" | "withdraw" | "decline" | "ask_user";
     }>, "many">;
     outcome: z.ZodObject<{
         hasOpportunity: z.ZodBoolean;
@@ -135,16 +131,16 @@ export declare const DiscoveryNegotiationSchema: z.ZodObject<{
     }>;
     seedAssessmentScore: z.ZodOptional<z.ZodNumber>;
 }, "strip", z.ZodTypeAny, {
+    counterpartyId: string;
     counterpartyHint: string;
     indexContext: string;
-    counterpartyId: string;
     turns: {
         reasoning: string;
+        action: "propose" | "accept" | "reject" | "counter" | "question" | "outreach" | "withdraw" | "decline" | "ask_user";
         suggestedRoles: {
             ownUser: "agent" | "patient" | "peer";
             otherUser: "agent" | "patient" | "peer";
         };
-        action: "propose" | "accept" | "reject" | "counter" | "question" | "outreach" | "withdraw" | "decline" | "ask_user";
     }[];
     outcome: {
         reasoning: string;
@@ -157,16 +153,16 @@ export declare const DiscoveryNegotiationSchema: z.ZodObject<{
     };
     seedAssessmentScore?: number | undefined;
 }, {
+    counterpartyId: string;
     counterpartyHint: string;
     indexContext: string;
-    counterpartyId: string;
     turns: {
         reasoning: string;
+        action: "propose" | "accept" | "reject" | "counter" | "question" | "outreach" | "withdraw" | "decline" | "ask_user";
         suggestedRoles: {
             ownUser: "agent" | "patient" | "peer";
             otherUser: "agent" | "patient" | "peer";
         };
-        action: "propose" | "accept" | "reject" | "counter" | "question" | "outreach" | "withdraw" | "decline" | "ask_user";
     }[];
     outcome: {
         reasoning: string;
@@ -226,17 +222,3 @@ export declare const DiscoverySourceProfileSchema: z.ZodObject<{
     interests?: string[] | undefined;
 }>;
 export type DiscoverySourceProfile = z.infer<typeof DiscoverySourceProfileSchema>;
-/**
- * Full input to the question generator.
- * Defined as a pure interface so it can reference DiscoveryNegotiationDigest
- * and ChatContextDigest from sibling schemas without Zod runtime coupling.
- */
-export interface DiscoveryQuestionInput {
-    query: string;
-    /** The seeker's global user_context paragraph (profile-replacing identity text). */
-    userContext: string;
-    negotiationDigests: DiscoveryNegotiationDigest[];
-    summary: DiscoverySummary;
-    chatContext?: ChatContextDigest;
-    now: string;
-}

package/dist/shared/schemas/discovery-question.schema.js

@@ -1,8 +1,6 @@
 /**
- * DiscoveryQuestionInput and nested types.
- * Leaf types have full Zod schemas. The composite DiscoveryQuestionInput is
- * a pure interface referencing cross-schema types (DiscoveryNegotiationDigest,
- * ChatContextDigest) to avoid Zod cross-schema runtime coupling.
+ * Discovery negotiation summary types shared by the opportunity graph and its
+ * negotiation-summary builder. Leaf types carry full Zod schemas.
  */
 import { z } from "zod";
 // ─── Primitives ───────────────────────────────────────────────────────────────

package/dist/shared/schemas/negotiation-digest.schema.d.ts

@@ -35,22 +35,22 @@ export declare const DiscoveryNegotiationDigestSchema: z.ZodObject<{
         otherUser: "agent" | "patient" | "peer";
     }>>;
 }, "strip", z.ZodTypeAny, {
+    suggestedRoles: {
+        ownUser: "agent" | "patient" | "peer";
+        otherUser: "agent" | "patient" | "peer";
+    } | null;
     counterpartyHint: string;
     indexContext: string;
     outcomeRole: "opportunity" | "no-opportunity";
     outcomeReason: "timeout" | "stalled" | "rejected" | "turn_cap" | "screened_out" | null;
     keyTake: string;
+}, {
     suggestedRoles: {
         ownUser: "agent" | "patient" | "peer";
         otherUser: "agent" | "patient" | "peer";
     } | null;
-}, {
     outcomeRole: "opportunity" | "no-opportunity";
     outcomeReason: "timeout" | "stalled" | "rejected" | "turn_cap" | "screened_out" | null;
-    suggestedRoles: {
-        ownUser: "agent" | "patient" | "peer";
-        otherUser: "agent" | "patient" | "peer";
-    } | null;
     counterpartyHint?: unknown;
     indexContext?: unknown;
     keyTake?: unknown;

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@indexnetwork/protocol",
-  "version": "12.1.0-rc.463.1",
+  "version": "13.0.0-rc.464.1",
   "type": "module",
   "main": "./dist/index.js",
   "types": "./dist/index.d.ts",

package/dist/questions/application/question.discovery.prompt.d.ts

@@ -1,8 +0,0 @@
-import type { DiscoveryQuestionInput } from "../../shared/schemas/discovery-question.schema.js";
-/** System prompt for the QuestionerAgent's `discovery` mode. */
-export declare const DISCOVERY_SYSTEM_PROMPT = "You help write user-facing follow-up questions after Index has reviewed potential connections for a human. Your job: surface the minimum set of structured decision questions the human must answer to make the next discovery turn sharper, or improve their outlook on the intent.\n\nYou may pick from five strategies. Choose contextually; mix when multiple questions genuinely complement.\n- refine_intent: ask the user to sharpen or pivot their original signal.\n- surface_missing_detail: ask for one concrete missing input (stage, location, timing, scope, \u2026).\n- open_adjacent_thread: offer a pivot suggested by recurring connection signals.\n- reflective_summary: mirror what the connection review revealed and ask the user to decide.\n- surface_emergent_knowledge: cite a fact you learned from the connection review and ask the user to decide in light of it.\n\nAsk a question only when ALL of these hold:\n1. Index cannot resolve the decision autonomously from the evidence shown.\n2. The answer would materially change which people surface next.\n3. The same fact is NOT already in chatContext.statedFacts, NOT already asked in chatContext.openQuestions, and NOT already shared in chatContext.surfacedFindings.\n\nStandalone prompt rule. Every generated `prompt` must be understandable outside the conversation where it was created. Naturally include the original query, discovery pattern, connection pattern, or concrete learned fact in the question text itself. Do not rely on `title`, UI labels, hidden metadata, or surrounding digest/chat text to explain what the question is about. For example, prefer \"For your AI crypto decentralized deep-tech search, which area is most critical right now?\" over \"Which area is most critical right now?\"\n\nReferential closure. The prompt must resolve entirely on its own, with no dangling references. The reader sees ONLY the question text \u2014 never the people you reviewed, the events on their calendar, or this conversation. Do not use demonstratives or definite anaphora that point at things the reader cannot see: \"these builders\", \"those founders\", \"these researchers\", \"these conversations\", \"this lunch\", \"the speaker\". If you reference a person, name them. If you reference a group, restate the concrete shared attribute inside the question itself (\"founders working on decentralized identity\"), never \"these founders\". Never imply a list, set, or prior exchange the reader is not currently looking at.\n- Bad: \"What kind of collaboration are you looking for with these builders?\"\n- Good: \"You're meeting people building agent infrastructure \u2014 what kind of collaboration are you looking for?\"\n\nNo process narration. Never describe Index's own activity or internal state. Forbidden: \"the previous negotiation\", \"the negotiation stalled\", \"opportunities found so far\", \"my search\", \"the counterparty\", \"candidates reviewed\", restating why a match did or did not happen, or quoting words a counterparty did or did not use. Ask about the user's goal or intent directly, never about the matching pipeline.\n- Bad: \"All opportunities found so far are related to 'Edge Esmeralda'. Would you like to broaden the search?\"\n- Good: \"Do you want to focus on people at Edge Esmeralda, or also connect beyond it?\"\n\nCardinality. Default one question. Add a second only when a DIFFERENT strategy genuinely complements the first (e.g. one surface_emergent_knowledge + one refine_intent). Add a third only when there are \u22653 substantive people reviewed and three distinct strategies each unblock a real decision. Two questions of the same strategy are acceptable only if their decision domains differ (different titles). Avoid stacking three pulls (info-from-user); balance with pushes (info-to-user via reflective_summary / surface_emergent_knowledge).\n\nOrdering. Questions whose answer unblocks the most connection reviews come first; then highest-impact; then ambiguity-clarifying. Reviews that needed more detail or ran out of time signal under-specification \u2014 prioritize.\n\nUser-facing language. Every title, prompt, option label, and option description is shown directly to the user. Never mention raw protocol mechanics or internal labels such as \"agent\", \"patient\", \"peer\", \"suggestedRoles\", \"role distribution\", \"counterparty\", \"negotiation\", \"turn_cap\", \"timeout\", or \"candidate\". Use natural language instead: people, matches, connections, mutual collaboration, someone who can help, or someone seeking help.\n\nOption construction. Each option must represent a meaningfully different outcome. Suffix the safest path with \" (Recommended)\" and list it first. The description states the CONSEQUENCE of choosing the option, not its definition. 2\u20134 options. Never add an \"Other\" option \u2014 clients provide a free-text fallback automatically. For surface_emergent_knowledge questions, anchor the prompt in the concrete cited fact (\"Multiple people flagged that\u2026\") and let the options represent decisions in light of that fact, not different versions of the fact.\n\nTitle rules. \u226412 chars. Noun of the decision domain. Discovery examples: \"Stage\", \"Timing\", \"Role\", \"Location\", \"Stack\", \"Budget\", \"Scope\", \"Format\".\n\nAnti-patterns \u2014 never do these.\n- Don't ask procedural confirmations (\"Should I look again?\").\n- Don't ask about hypothetical edge cases that didn't occur.\n- Don't ask about specific person identities; treat the provided person summary as the only allowed reference.\n- Don't repeat anything in chatContext.openQuestions.\n- Don't re-surface anything in chatContext.surfacedFindings.\n- Don't ask for facts in chatContext.statedFacts.\n\nOutput. Return at most 3 entries in the \"questions\" array. Each entry must include a \"strategy\" field (one of the five values). If nothing is worth asking, return \"questions\": [].";
-/**
- * Pure builder: assembles the discovery-mode user message string from a
- * structured input.
- */
-export declare function buildDiscoveryQuestionPrompt(input: DiscoveryQuestionInput): string;

package/dist/questions/application/question.discovery.prompt.js

@@ -1,181 +0,0 @@
-/** System prompt for the QuestionerAgent's `discovery` mode. */
-export const DISCOVERY_SYSTEM_PROMPT = `You help write user-facing follow-up questions after Index has reviewed potential connections for a human. Your job: surface the minimum set of structured decision questions the human must answer to make the next discovery turn sharper, or improve their outlook on the intent.
-
-You may pick from five strategies. Choose contextually; mix when multiple questions genuinely complement.
-- refine_intent: ask the user to sharpen or pivot their original signal.
-- surface_missing_detail: ask for one concrete missing input (stage, location, timing, scope, …).
-- open_adjacent_thread: offer a pivot suggested by recurring connection signals.
-- reflective_summary: mirror what the connection review revealed and ask the user to decide.
-- surface_emergent_knowledge: cite a fact you learned from the connection review and ask the user to decide in light of it.
-
-Ask a question only when ALL of these hold:
-1. Index cannot resolve the decision autonomously from the evidence shown.
-2. The answer would materially change which people surface next.
-3. The same fact is NOT already in chatContext.statedFacts, NOT already asked in chatContext.openQuestions, and NOT already shared in chatContext.surfacedFindings.
-
-Standalone prompt rule. Every generated \`prompt\` must be understandable outside the conversation where it was created. Naturally include the original query, discovery pattern, connection pattern, or concrete learned fact in the question text itself. Do not rely on \`title\`, UI labels, hidden metadata, or surrounding digest/chat text to explain what the question is about. For example, prefer "For your AI crypto decentralized deep-tech search, which area is most critical right now?" over "Which area is most critical right now?"
-
-Referential closure. The prompt must resolve entirely on its own, with no dangling references. The reader sees ONLY the question text — never the people you reviewed, the events on their calendar, or this conversation. Do not use demonstratives or definite anaphora that point at things the reader cannot see: "these builders", "those founders", "these researchers", "these conversations", "this lunch", "the speaker". If you reference a person, name them. If you reference a group, restate the concrete shared attribute inside the question itself ("founders working on decentralized identity"), never "these founders". Never imply a list, set, or prior exchange the reader is not currently looking at.
-- Bad: "What kind of collaboration are you looking for with these builders?"
-- Good: "You're meeting people building agent infrastructure — what kind of collaboration are you looking for?"
-
-No process narration. Never describe Index's own activity or internal state. Forbidden: "the previous negotiation", "the negotiation stalled", "opportunities found so far", "my search", "the counterparty", "candidates reviewed", restating why a match did or did not happen, or quoting words a counterparty did or did not use. Ask about the user's goal or intent directly, never about the matching pipeline.
-- Bad: "All opportunities found so far are related to 'Edge Esmeralda'. Would you like to broaden the search?"
-- Good: "Do you want to focus on people at Edge Esmeralda, or also connect beyond it?"
-
-Cardinality. Default one question. Add a second only when a DIFFERENT strategy genuinely complements the first (e.g. one surface_emergent_knowledge + one refine_intent). Add a third only when there are ≥3 substantive people reviewed and three distinct strategies each unblock a real decision. Two questions of the same strategy are acceptable only if their decision domains differ (different titles). Avoid stacking three pulls (info-from-user); balance with pushes (info-to-user via reflective_summary / surface_emergent_knowledge).
-
-Ordering. Questions whose answer unblocks the most connection reviews come first; then highest-impact; then ambiguity-clarifying. Reviews that needed more detail or ran out of time signal under-specification — prioritize.
-
-User-facing language. Every title, prompt, option label, and option description is shown directly to the user. Never mention raw protocol mechanics or internal labels such as "agent", "patient", "peer", "suggestedRoles", "role distribution", "counterparty", "negotiation", "turn_cap", "timeout", or "candidate". Use natural language instead: people, matches, connections, mutual collaboration, someone who can help, or someone seeking help.
-
-Option construction. Each option must represent a meaningfully different outcome. Suffix the safest path with " (Recommended)" and list it first. The description states the CONSEQUENCE of choosing the option, not its definition. 2–4 options. Never add an "Other" option — clients provide a free-text fallback automatically. For surface_emergent_knowledge questions, anchor the prompt in the concrete cited fact ("Multiple people flagged that…") and let the options represent decisions in light of that fact, not different versions of the fact.
-
-Title rules. ≤12 chars. Noun of the decision domain. Discovery examples: "Stage", "Timing", "Role", "Location", "Stack", "Budget", "Scope", "Format".
-
-Anti-patterns — never do these.
-- Don't ask procedural confirmations ("Should I look again?").
-- Don't ask about hypothetical edge cases that didn't occur.
-- Don't ask about specific person identities; treat the provided person summary as the only allowed reference.
-- Don't repeat anything in chatContext.openQuestions.
-- Don't re-surface anything in chatContext.surfacedFindings.
-- Don't ask for facts in chatContext.statedFacts.
-
-Output. Return at most 3 entries in the "questions" array. Each entry must include a "strategy" field (one of the five values). If nothing is worth asking, return "questions": [].`;
-/**
- * Pure builder: assembles the discovery-mode user message string from a
- * structured input.
- */
-export function buildDiscoveryQuestionPrompt(input) {
-    const profileSummary = input.userContext?.trim() || "(no profile data)";
-    const connectionReviewBlocks = renderConnectionReviewDigests(input.negotiationDigests);
-    const chatContextBlock = input.chatContext
-        ? renderDigest(input.chatContext)
-        : "(no chat context available)";
-    const engagementPattern = renderEngagementPattern(input.summary.roleDistribution);
-    return [
-        "## Seeker's query",
-        input.query,
-        "",
-        "## Seeker profile",
-        profileSummary,
-        "",
-        "## This discovery turn",
-        `- ${input.summary.totalCandidates} people reviewed`,
-        `- ${input.summary.opportunitiesFound} promising connections found`,
-        `- ${input.summary.noOpportunityCount} reviews did not find enough fit (${input.summary.timeoutCount} needed more detail or time)`,
-        `- Engagement pattern: ${engagementPattern}`,
-        "",
-        "## Connection review evidence (compact digests)",
-        connectionReviewBlocks,
-        "",
-        "## What the user has already said in this session",
-        chatContextBlock,
-        "",
-        "## Now",
-        input.now,
-        "",
-        "## Your task",
-        "Identify the minimum set of decision questions the seeker must answer to make",
-        "the next discovery turn sharper. Apply every rule from your system prompt",
-        "before outputting. Return an empty `questions` array if nothing is worth asking.",
-    ].join("\n");
-}
-/**
- * Render the negotiation-digest collection into compact one-liners. Each digest
- * is fixed-size (≤ ~400 chars after rendering), so the rendered block scales
- * linearly with candidate count: 10 candidates ≈ 4 KB, well within budget.
- */
-function renderConnectionReviewDigests(digests) {
-    if (digests.length === 0)
-        return "(no connection reviews)";
-    return digests
-        .map((d) => {
-        const relationshipSignal = d.suggestedRoles
-            ? [`  Relationship signal: ${renderRelationshipSignal(d.suggestedRoles)}`]
-            : [];
-        return [
-            `- Person: ${d.counterpartyHint}`,
-            `  Community context: ${d.indexContext}`,
-            `  Outcome: ${renderOutcome(d)}`,
-            ...relationshipSignal,
-            `  Take: ${d.keyTake}`,
-        ].join("\n");
-    })
-        .join("\n\n");
-}
-function renderEngagementPattern(dist) {
-    const parts = [];
-    if ((dist.peer ?? 0) > 0) {
-        parts.push(`${dist.peer} mutual collaboration${dist.peer === 1 ? "" : "s"}`);
-    }
-    if ((dist.agent ?? 0) > 0) {
-        parts.push(`${dist.agent} where the user could offer help or expertise`);
-    }
-    if ((dist.patient ?? 0) > 0) {
-        parts.push(`${dist.patient} where the user seemed to be seeking help or expertise`);
-    }
-    return parts.length > 0 ? parts.join(", ") : "(no engagement pattern available)";
-}
-function renderOutcome(digest) {
-    const outcome = digest.outcomeRole === "opportunity"
-        ? "promising connection"
-        : "not enough fit";
-    const reason = renderOutcomeReason(digest.outcomeReason);
-    return reason ? `${outcome} (${reason})` : outcome;
-}
-function renderOutcomeReason(reason) {
-    switch (reason) {
-        case "turn_cap":
-            return "needed more detail";
-        case "timeout":
-            return "ran out of time";
-        case "rejected":
-            return "not enough mutual interest";
-        case "stalled":
-            return "stalled";
-        case "screened_out":
-            return "didn't look like a strong enough fit to pursue";
-        case null:
-            return "";
-    }
-}
-function renderRelationshipSignal(roles) {
-    if (roles.ownUser === "peer" && roles.otherUser === "peer")
-        return "mutual collaboration";
-    if (roles.ownUser === "agent" && roles.otherUser === "patient") {
-        return "the user could offer help or expertise";
-    }
-    if (roles.ownUser === "patient" && roles.otherUser === "agent") {
-        return "the user seemed to be seeking help or expertise";
-    }
-    if (roles.ownUser === "agent")
-        return "the user could offer help or expertise";
-    if (roles.ownUser === "patient")
-        return "the user seemed to be seeking help or expertise";
-    return "collaboration fit";
-}
-function renderDigest(d) {
-    const lines = [];
-    if (d.statedFacts.length > 0) {
-        lines.push("Stated facts:");
-        for (const f of d.statedFacts)
-            lines.push(`  - ${f}`);
-    }
-    if (d.openQuestions.length > 0) {
-        lines.push("Open questions (assistant already asked):");
-        for (const q of d.openQuestions)
-            lines.push(`  - ${q}`);
-    }
-    if (d.rejectionReasons.length > 0) {
-        lines.push("User pushback / rejections:");
-        for (const r of d.rejectionReasons)
-            lines.push(`  - ${r}`);
-    }
-    if (d.surfacedFindings.length > 0) {
-        lines.push("Findings already surfaced to user:");
-        for (const f of d.surfacedFindings)
-            lines.push(`  - ${f}`);
-    }
-    return lines.length > 0 ? lines.join("\n") : "(digest is empty)";
-}

package/dist/questions/ports/question.generator.port.d.ts

@@ -1,33 +0,0 @@
-/**
- * questions/ports/question.generator.port — inline question generator port.
- *
- * @deprecated Inline question generation is superseded by the async
- * QuestionerQueue path (`questionerEnqueue`). Will be removed once the inline
- * fallback in `opportunity.discover.ts` is retired.
- *
- * Protocol-level read contract for decision-question generation. Implementations
- * live in the backend (see `QuestionGeneratorService`, which delegates to the
- * QuestionerAgent's `discovery` mode) and are injected into the protocol via
- * `ProtocolDeps`/`ToolContext`. The protocol module never constructs its own
- * LLM-bound generator — callers inject one (or `undefined` to opt out).
- *
- * IND-547: canonical question generator port.
- */
-import type { DiscoveryQuestionInput } from "../../shared/schemas/discovery-question.schema.js";
-import type { QuestionGenerationResult } from "../domain/question.schema.js";
-export interface QuestionGeneratorReader {
-    /**
-     * Run the question generator over a single discovery turn.
-     *
-     * @param input  Discovery turn payload (query + negotiation digests + chat context).
-     * @param options.signal  Optional AbortSignal. When aborted (deadline reached or
-     *   upstream cancel) the in-flight LLM call is cancelled and `null` is returned —
-     *   discovery still emits its response, just without questions.
-     * @returns The structured result, or `null` when generation failed,
-     *   guardrails dropped all candidates, the underlying LLM threw, or
-     *   the call was aborted.
-     */
-    generate(input: DiscoveryQuestionInput, options?: {
-        signal?: AbortSignal;
-    }): Promise<QuestionGenerationResult | null>;
-}

package/dist/questions/ports/question.generator.port.js

@@ -1 +0,0 @@
-export {};