@indexnetwork/protocol 12.1.0-rc.463.1 → 13.1.0-rc.465.1

package/dist/questions/application/question.env.js

@@ -9,14 +9,6 @@
  *                                       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).
  *
@@ -27,15 +19,6 @@
  * IND-547: canonical home — previously questioner/questioner.env.ts.
  * Legacy path is a thin compatibility shim pointing here.
  */
-/**
- * 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;
 /**
@@ -56,13 +39,6 @@ function positiveIntEnv(name, fallback) {
 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";
@@ -77,20 +53,6 @@ export function uptakeAuthorityThreshold() {
     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);

package/dist/questions/application/question.input.d.ts

@@ -1,7 +1,7 @@
 /**
  * questions/application/question.input — QuestionerAgent input envelope.
  *
- * Defines per-mode context types (DiscoveryContext, IntentContext, …),
+ * Defines per-mode context types (IntentContext, NegotiationContext, …),
  * the discriminated QuestionerInput union, and the runtime validation guard
  * `isValidQuestionerInputContract`.
  *
@@ -17,15 +17,9 @@
  * IND-547: canonical home — previously questioner/questioner.types.ts.
  * Legacy path is a thin compatibility shim pointing here.
  */
-import type { DiscoveryQuestionInput } from "../../shared/schemas/discovery-question.schema.js";
 import type { ToolScopeType } from "../../shared/agent/tool.scope.js";
 import type { NegotiationQuestionCandidate, QuestionMode, QuestionPoolDiscriminator } from "../domain/question.schema.js";
 import type { NegotiationConsultationReason } from "../../capabilities/negotiation.questions.facade.js";
-/**
- * Discovery context — wraps the existing DiscoveryQuestionInput wholesale.
- * The discovery preset's buildPrompt delegates to `question.discovery.prompt.ts`.
- */
-export type DiscoveryContext = DiscoveryQuestionInput;
 /** Intent context — data needed to generate questions about an intent. */
 export interface IntentContext {
     intentId: string;
@@ -40,14 +34,6 @@ export interface RecoveryIntentContext extends IntentContext {
     /** Privacy-safe aggregate signal; raw negotiation evidence is never provided. */
     rejectedNegotiationCount?: number;
 }
-/** Profile context — data needed to generate questions to fill profile gaps. */
-export interface ProfileContext {
-    /** The user's global user_context paragraph (profile-replacing identity text). */
-    userContext?: string;
-    gaps: string[];
-    /** Existing premise texts the user has already stated (e.g. "I live in Berlin"). */
-    existingPremises?: string[];
-}
 /** Shared context fields for negotiation-mode questions. */
 interface NegotiationContextBase {
     negotiationId: string;
@@ -134,7 +120,7 @@ export interface PoolDiscoveryContext {
     minedAt: string;
 }
 /** Discriminated union: mode selects the context shape. */
-export type QuestionerContext = DiscoveryContext | IntentContext | RecoveryIntentContext | ProfileContext | NegotiationContext | NegotiationInflightContext | ChatContext | PoolDiscoveryContext;
+export type QuestionerContext = IntentContext | RecoveryIntentContext | NegotiationContext | NegotiationInflightContext | ChatContext | PoolDiscoveryContext;
 /**
  * Payload shape accepted by the questionerEnqueue callback. Covers all
  * question modes — the composition root bridges this to the concrete

package/dist/questions/application/question.presets.js

@@ -1,4 +1,3 @@
-import { DISCOVERY_SYSTEM_PROMPT, buildDiscoveryQuestionPrompt } from "./question.discovery.prompt.js";
 import { QUD_UNDERSPECIFICATION_RULES } from "./question.qud.js";
 import { consultationPromptFor } from "../../capabilities/negotiation.questions.facade.js";
 /**
@@ -121,63 +120,6 @@ function buildRecoveryIntentPrompt(ctx) {
         "Return an empty `questions` array when no safe useful axis is missing.",
     ].join("\n");
 }
-// ─── Profile preset ─────────────────────────────────────────────────────────
-const PROFILE_SYSTEM_PROMPT = `You sit between a human and a discovery protocol. The user has a profile that is incomplete. Your job: surface the minimum set of structured questions that fill the identified gaps — asking about location, skills, interests, current work, or goals — so the protocol can run better discovery on their behalf.
-
-The user may already have premises — atomic self-descriptions they have stated. These cover specific profile domains. Do not ask about domains already addressed by existing premises. Focus only on gaps not covered by any premise.
-
-You may pick from two strategies. Choose contextually; mix only when each question is genuinely distinct.
-- surface_missing_detail: ask for one concrete missing piece of profile data (location, current role, skills, interests, goals, availability, …).
-- refine_intent: ask the user to clarify or sharpen an existing profile signal so candidates can be ranked more accurately.
-
-Ask a question only when ALL of these hold:
-1. The answer is not already visible in the profile data shown.
-2. The answer is not already covered by an existing premise listed below the profile.
-3. The answer would meaningfully change which opportunities surface for this user.
-4. The question targets a different profile domain from any other question in this batch.
-
-Standalone prompt rule. Every generated \`prompt\` must be understandable outside the conversation where it was created. Naturally include the profile signal or gap being clarified in the question text itself, using concise plain language from the current profile, existing premises, or identified gaps. Do not rely on \`title\`, UI labels, hidden metadata, or surrounding digest/chat text to explain what the question is about.
-- Bad: "What kind of role are you looking for?"
-- Good: "To improve matches from your founder/operator profile, what kind of role are you looking for?"
-
-${REFERENTIAL_CLOSURE_RULES}
-
-Cardinality. Default one question. Add a second only when a DIFFERENT strategy genuinely complements the first and unblocks a clearly distinct decision. Never ask two questions of the same strategy unless their decision domains differ.
-
-Option construction. Each option must represent a meaningfully different outcome. Suffix the safest or most common 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.
-
-Title rules. ≤12 chars. Noun of the profile domain. Examples: "Location", "Role", "Skills", "Goals", "Interests", "Availability", "Stage".
-
-Anti-patterns — never do these.
-- Don't ask about fields already filled in the profile.
-- Don't ask about information already captured in an existing premise.
-- Don't ask procedural confirmations ("Should I update your profile?").
-- Don't ask vague introspective questions ("Who are you really?").
-- Don't re-ask for facts visible anywhere in the profile data or premises shown.
-
-Output. Return at most 2 entries in the "questions" array. Each entry must include a "strategy" field (one of the two values above). If the profile is already complete enough for discovery, return "questions": [].`;
-function buildProfilePrompt(ctx) {
-    const profileBlock = buildUserContextBlock(ctx.userContext);
-    const premisesBlock = ctx.existingPremises && ctx.existingPremises.length > 0
-        ? ctx.existingPremises.map((p, i) => `${i + 1}. ${p}`).join("\n")
-        : "(none)";
-    const gapsBlock = ctx.gaps.length > 0 ? ctx.gaps.join(", ") : "(none identified)";
-    return [
-        "## Current profile",
-        profileBlock,
-        "",
-        "## Existing premises",
-        premisesBlock,
-        "",
-        "## Identified gaps",
-        gapsBlock,
-        "",
-        "## Your task",
-        "Generate the minimum set of questions needed to fill the identified gaps.",
-        "Apply every rule from your system prompt before outputting.",
-        "Return an empty `questions` array if the profile is already complete enough.",
-    ].join("\n");
-}
 // ─── Negotiation preset ──────────────────────────────────────────────────────
 const NEGOTIATION_SYSTEM_PROMPT = `You sit between a human and a discovery protocol. You generate negotiation-mode questions for one of two purposes described in the user message.
 
@@ -397,18 +339,10 @@ function withQudMetadataRules(systemPrompt) {
     return `${systemPrompt}\n\n${QUD_UNDERSPECIFICATION_RULES}`;
 }
 const presets = {
-    discovery: {
-        systemPrompt: withQudMetadataRules(DISCOVERY_SYSTEM_PROMPT),
-        buildPrompt: (context) => buildDiscoveryQuestionPrompt(context),
-    },
     intent: {
         systemPrompt: withQudMetadataRules(INTENT_SYSTEM_PROMPT),
         buildPrompt: (context) => buildIntentPrompt(context),
     },
-    enrichment: {
-        systemPrompt: withQudMetadataRules(PROFILE_SYSTEM_PROMPT),
-        buildPrompt: (context) => buildProfilePrompt(context),
-    },
     negotiation: {
         systemPrompt: withQudMetadataRules(NEGOTIATION_SYSTEM_PROMPT),
         buildPrompt: (context) => buildNegotiationPrompt(context),

package/dist/questions/application/question.tools.js

@@ -24,7 +24,7 @@ import { callerMayAccessQuestionMode } from "../../shared/agent/activity-project
  * from opportunity metadata that can reference out-of-scope networks and
  * other users' content (same leak class as the getOpportunitiesForUser fix).
  */
-const SELF_OWNED_MODES = ["enrichment", "intent", "discovery"];
+const SELF_OWNED_MODES = ["intent"];
 function isVisibleInScopedNetwork(question, userId, networkId) {
     return question.actors?.some((actor) => actor.userId === userId && actor.networkId === networkId) === true;
 }
@@ -65,11 +65,11 @@ export function createQuestionerTools(defineTool, deps) {
     const readPendingQuestions = defineTool({
         name: "read_pending_questions",
         description: "Returns pending questions generated for the authenticated user across all modes " +
-            "(profile, intent, negotiation, discovery). These are questions generated by the " +
+            "(intent, negotiation, chat, pool_discovery). These are questions generated by the " +
             "system to help surface missing signals, refine intents, or capture engagement context.\n\n" +
             "**Returns:** List of pending questions, each with `id`, `title`, `prompt`, `options`, " +
             "`multiSelect`, `mode`, `sourceType`, `sourceId`, `createdAt`, and optional `expiresAt`. " +
-            "Network-scoped agents receive only profile/intent/discovery questions for the scoped network plus a " +
+            "Network-scoped agents receive only intent questions for the scoped network plus a " +
             "`scopeRestriction` note.\n\n" +
             "**Use:** Call with no arguments to get all pending questions, or pass `limit` to cap the " +
             "count. For the daily brief the script calls with a small `limit` and renders the first " +