@indexnetwork/protocol 6.12.1-rc.404.1 → 6.14.0-rc.406.1

package/dist/questioner/questioner.discovery.prompt.js

@@ -1,182 +1,5 @@
-/** 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.
+ * @deprecated Canonical location: questions/application/question.discovery.prompt — retained
+ * for backward compatibility (IND-547).
  */
-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)";
-}
-//# sourceMappingURL=questioner.discovery.prompt.js.map
+export { DISCOVERY_SYSTEM_PROMPT, buildDiscoveryQuestionPrompt, } from "../questions/application/question.discovery.prompt.js";

package/dist/questioner/questioner.env.d.ts

@@ -1,59 +1,5 @@
 /**
- * Centralized accessors for all question-generation environment variables.
- *
- * Naming scheme (one prefix, hierarchical):
- *
- *   QUESTIONER_ENABLED                  master switch — QuestionerQueue worker +
- *                                       enqueue closures at every composition site.
- *   QUESTIONER_UPTAKE_ENABLED           per-surface switch — advisory pre-accept uptake
- *                                       interlock. Requires the master switch.
- *   QUESTIONER_UPTAKE_AUTHORITY_THRESHOLD
- *                                       authority threshold (0-100, default 70).
- *   QUESTIONER_DISCOVERY_ENABLED        per-surface switch — decision questions during
- *                                       chat/MCP opportunity discovery. Only effective
- *                                       when the master switch is on (the discovery
- *                                       question step adds inline summarizer latency,
- *                                       so operators can turn it off independently).
- *   QUESTIONER_DISCOVERY_INPUT_MODE     'transcripts' | 'insights' generator input.
- *   QUESTIONER_DISCOVERY_TIMEOUT_MS     per-call deadline for the discovery-questions
- *                                       LLM step (default 12s).
- *   QUESTIONER_CHAT_WAIT_TIMEOUT_MS     how long the blocking ask_user_question chat
- *                                       tool waits for an inline answer (default 4 min).
- *
- * All reads go through this module — do not read these variables via
- * `process.env` elsewhere. Values are read on every call (no caching) so tests
- * and long-lived processes observe changes.
+ * @deprecated Canonical location: questions/application/question.env — retained
+ * for backward compatibility (IND-547).
  */
-/**
- * Question-generator budget. Sized against Railway's ~60 s edge timeout:
- * the discovery + evaluation + negotiate phases consume ~50 s on the slow
- * path, leaving ~10 s of headroom for the tail. 12 s is the larger end of
- * "fits"; the question step usually completes in 4-8 s, so most legitimate
- * calls finish well inside. Aborted calls return `null` (no questions);
- * the rest of the discovery payload still ships.
- */
-export declare const DISCOVERY_QUESTIONS_TIMEOUT_MS_DEFAULT = 12000;
-export declare const CHAT_QUESTION_WAIT_TIMEOUT_MS_DEFAULT = 240000;
-export declare const UPTAKE_AUTHORITY_THRESHOLD_DEFAULT = 70;
-/** Master switch: is any background question generation enabled? */
-export declare function isQuestionerEnabled(): boolean;
-/**
- * Per-surface switch: should chat/MCP opportunity discovery produce decision
- * questions? Hierarchical — always false when the master switch is off.
- */
-export declare function isDiscoveryQuestionsEnabled(): boolean;
-/** Advisory uptake interlock. Flag-off by default and subordinate to the master switch. */
-export declare function isUptakeGuardEnabled(): boolean;
-/** Authority threshold below which hosts may generate uptake questions. */
-export declare function uptakeAuthorityThreshold(): number;
-/**
- * Input mode for the discovery question generator. Only `transcripts` is
- * implemented; any other value falls back to `transcripts` (startup.env.ts
- * warns on invalid values).
- */
-export declare function discoveryQuestionsInputMode(): "transcripts" | "insights";
-/** Per-call deadline for the discovery-questions LLM step. */
-export declare function discoveryQuestionsTimeoutMs(): number;
-/** Wait budget for the blocking ask_user_question chat tool. */
-export declare function chatQuestionWaitTimeoutMs(): number;
-//# sourceMappingURL=questioner.env.d.ts.map
+export { isQuestionerEnabled, isDiscoveryQuestionsEnabled, isUptakeGuardEnabled, uptakeAuthorityThreshold, discoveryQuestionsInputMode, discoveryQuestionsTimeoutMs, chatQuestionWaitTimeoutMs, DISCOVERY_QUESTIONS_TIMEOUT_MS_DEFAULT, CHAT_QUESTION_WAIT_TIMEOUT_MS_DEFAULT, UPTAKE_AUTHORITY_THRESHOLD_DEFAULT, } from "../questions/application/question.env.js";

package/dist/questioner/questioner.env.js

@@ -1,95 +1,5 @@
 /**
- * Centralized accessors for all question-generation environment variables.
- *
- * Naming scheme (one prefix, hierarchical):
- *
- *   QUESTIONER_ENABLED                  master switch — QuestionerQueue worker +
- *                                       enqueue closures at every composition site.
- *   QUESTIONER_UPTAKE_ENABLED           per-surface switch — advisory pre-accept uptake
- *                                       interlock. Requires the master switch.
- *   QUESTIONER_UPTAKE_AUTHORITY_THRESHOLD
- *                                       authority threshold (0-100, default 70).
- *   QUESTIONER_DISCOVERY_ENABLED        per-surface switch — decision questions during
- *                                       chat/MCP opportunity discovery. Only effective
- *                                       when the master switch is on (the discovery
- *                                       question step adds inline summarizer latency,
- *                                       so operators can turn it off independently).
- *   QUESTIONER_DISCOVERY_INPUT_MODE     'transcripts' | 'insights' generator input.
- *   QUESTIONER_DISCOVERY_TIMEOUT_MS     per-call deadline for the discovery-questions
- *                                       LLM step (default 12s).
- *   QUESTIONER_CHAT_WAIT_TIMEOUT_MS     how long the blocking ask_user_question chat
- *                                       tool waits for an inline answer (default 4 min).
- *
- * All reads go through this module — do not read these variables via
- * `process.env` elsewhere. Values are read on every call (no caching) so tests
- * and long-lived processes observe changes.
+ * @deprecated Canonical location: questions/application/question.env — retained
+ * for backward compatibility (IND-547).
  */
-/**
- * Question-generator budget. Sized against Railway's ~60 s edge timeout:
- * the discovery + evaluation + negotiate phases consume ~50 s on the slow
- * path, leaving ~10 s of headroom for the tail. 12 s is the larger end of
- * "fits"; the question step usually completes in 4-8 s, so most legitimate
- * calls finish well inside. Aborted calls return `null` (no questions);
- * the rest of the discovery payload still ships.
- */
-export const DISCOVERY_QUESTIONS_TIMEOUT_MS_DEFAULT = 12000;
-export const CHAT_QUESTION_WAIT_TIMEOUT_MS_DEFAULT = 240000;
-export const UPTAKE_AUTHORITY_THRESHOLD_DEFAULT = 70;
-/**
- * Parse a positive integer env var, clamped to the safe-integer range so a
- * malformed env value cannot crash `AbortSignal.timeout` (which throws on
- * values outside `[0, MAX_SAFE_INTEGER]`).
- */
-function positiveIntEnv(name, fallback) {
-    const raw = process.env[name];
-    if (!raw)
-        return fallback;
-    const parsed = Number.parseInt(raw, 10);
-    if (!Number.isFinite(parsed) || parsed <= 0 || parsed > Number.MAX_SAFE_INTEGER)
-        return fallback;
-    return parsed;
-}
-/** Master switch: is any background question generation enabled? */
-export function isQuestionerEnabled() {
-    return process.env.QUESTIONER_ENABLED === "true";
-}
-/**
- * Per-surface switch: should chat/MCP opportunity discovery produce decision
- * questions? Hierarchical — always false when the master switch is off.
- */
-export function isDiscoveryQuestionsEnabled() {
-    return isQuestionerEnabled() && process.env.QUESTIONER_DISCOVERY_ENABLED === "true";
-}
-/** Advisory uptake interlock. Flag-off by default and subordinate to the master switch. */
-export function isUptakeGuardEnabled() {
-    return isQuestionerEnabled() && process.env.QUESTIONER_UPTAKE_ENABLED === "true";
-}
-/** Authority threshold below which hosts may generate uptake questions. */
-export function uptakeAuthorityThreshold() {
-    const raw = process.env.QUESTIONER_UPTAKE_AUTHORITY_THRESHOLD;
-    if (!raw?.trim())
-        return UPTAKE_AUTHORITY_THRESHOLD_DEFAULT;
-    if (!/^-?\d+$/.test(raw.trim()))
-        return UPTAKE_AUTHORITY_THRESHOLD_DEFAULT;
-    const parsed = Number.parseInt(raw, 10);
-    return Math.min(100, Math.max(0, parsed));
-}
-/**
- * Input mode for the discovery question generator. Only `transcripts` is
- * implemented; any other value falls back to `transcripts` (startup.env.ts
- * warns on invalid values).
- */
-export function discoveryQuestionsInputMode() {
-    return process.env.QUESTIONER_DISCOVERY_INPUT_MODE?.trim() === "insights"
-        ? "insights"
-        : "transcripts";
-}
-/** Per-call deadline for the discovery-questions LLM step. */
-export function discoveryQuestionsTimeoutMs() {
-    return positiveIntEnv("QUESTIONER_DISCOVERY_TIMEOUT_MS", DISCOVERY_QUESTIONS_TIMEOUT_MS_DEFAULT);
-}
-/** Wait budget for the blocking ask_user_question chat tool. */
-export function chatQuestionWaitTimeoutMs() {
-    return positiveIntEnv("QUESTIONER_CHAT_WAIT_TIMEOUT_MS", CHAT_QUESTION_WAIT_TIMEOUT_MS_DEFAULT);
-}
-//# sourceMappingURL=questioner.env.js.map
+export { isQuestionerEnabled, isDiscoveryQuestionsEnabled, isUptakeGuardEnabled, uptakeAuthorityThreshold, discoveryQuestionsInputMode, discoveryQuestionsTimeoutMs, chatQuestionWaitTimeoutMs, DISCOVERY_QUESTIONS_TIMEOUT_MS_DEFAULT, CHAT_QUESTION_WAIT_TIMEOUT_MS_DEFAULT, UPTAKE_AUTHORITY_THRESHOLD_DEFAULT, } from "../questions/application/question.env.js";

package/dist/questioner/questioner.presets.d.ts

@@ -1,21 +1,6 @@
 /**
- * Mode presets for the QuestionerAgent. Each preset provides a system prompt
- * and a buildPrompt function that assembles the user message from a typed
- * context object. Only the `discovery` preset ships in Slice 1; others throw
- * until their implementation slices land.
+ * @deprecated Canonical location: questions/application/question.presets — retained
+ * for backward compatibility (IND-547).
  */
-import type { QuestionMode, QuestionPurpose } from "../shared/schemas/question.schema.js";
-export interface QuestionerPreset {
-    /** The LLM system prompt for this mode. */
-    systemPrompt: string;
-    /** Builds the user-message string from the mode-specific context. */
-    buildPrompt: (context: unknown) => string;
-}
-/**
- * Retrieve the preset for the given mode.
- * @param mode - The question mode to look up.
- * @returns The matching preset with systemPrompt and buildPrompt.
- * @throws Error if the mode's preset is not yet implemented.
- */
-export declare function getPreset(mode: QuestionMode, purpose?: QuestionPurpose): QuestionerPreset;
-//# sourceMappingURL=questioner.presets.d.ts.map
+export { getPreset } from "../questions/application/question.presets.js";
+export type { QuestionerPreset } from "../questions/application/question.presets.js";