@sonnechasser/ntrp 1.4.7 → 1.4.8

package/dist/index.js

@@ -1637,6 +1637,7 @@ function buildSessionContextDoc(file, opts = {}) {
   lines.push(`- Exchanges: ${exchanges}`);
   if (file.summary) lines.push(`- Summary: ${file.summary}`);
   if (file.resumed_from) lines.push(`- Resumed from: ${file.resumed_from}`);
+  lines.push("- Packaging: answer-first; recommendations filtered (silent idea-gate on deep/think/strategy)");
   lines.push("");
   lines.push("## Dataset");
   lines.push("");
@@ -8706,6 +8707,8 @@ KINDS:
 - "preference": how the user wants analysis done or framed.
 - "calibration": a judgment update \u2014 an adjustment to HOW this business should be analyzed. Write it as an applicable rule, e.g. "Enterprise freshness reds here trace to rep coverage gaps, not data hygiene \u2014 cut by owner first" or "This team treats 45 quiet days as normal cadence; don't flag staleness before that." Capture corrections the user made to your reasoning as calibrations, not preferences.
 
+AFTER-ACTION LENS (silent \u2014 never name AAR to anyone): prefer items that capture BELIEF that changed, EVIDENCE that forced the change, or the NEXT BET the team should re-check. Calibrations that supersede contradictions are the highest-value distillates.
+
 SUPERSEDING (calibrations only): the current calibrations are provided with ids. If the session contradicts or refines one, return the replacement with "supersedes" set to the old id. Never emit a calibration that duplicates an existing one.
 
 EXCLUDE:
@@ -21425,6 +21428,21 @@ var init_tool_schemas = __esm({
           required: ["play_id"]
         }
       },
+      {
+        name: "get_framework_detail",
+        description: "Read a consulting/operating framework pack by id: when to use, vital links, board vs operator cut, kill rules, and full body. The system prompt lists only the catalog \u2014 call this when you need depth before recommending. Never name brand labels (Heilmeier, Minto, TOC, MEDDPICC, \u2026) to the user.",
+        parameters: {
+          type: "object",
+          properties: {
+            framework_id: {
+              type: "string",
+              maxLength: 40,
+              description: "Exact id from the framework catalog, e.g. 'bottleneck', 'packaging', 'aar', 'meddpicc'."
+            }
+          },
+          required: ["framework_id"]
+        }
+      },
       {
         name: "get_session_brief",
         description: "Read the 1-page context brief of a PRIOR session by id or 4-char suffix: status, dataset, scope, computed scores with dollar values, headline metrics, deliverables, and conversation log. Use when the user references earlier work \u2014 'last week we found\u2026', 'compare with the previous analysis', 'what did session 9297 conclude?'. Read-only.",
@@ -21526,6 +21544,251 @@ var init_tool_arg_validate = __esm({
   }
 });
 
+// src/data/frameworks.ts
+var frameworks_exports = {};
+__export(frameworks_exports, {
+  FRAMEWORK_PACKS: () => FRAMEWORK_PACKS,
+  PLAY_FRAMEWORK_HOOKS: () => PLAY_FRAMEWORK_HOOKS,
+  buildFrameworkCatalogBlock: () => buildFrameworkCatalogBlock,
+  frameworkIdsForPlay: () => frameworkIdsForPlay,
+  getFrameworkById: () => getFrameworkById,
+  listFrameworkIds: () => listFrameworkIds
+});
+function listFrameworkIds() {
+  return FRAMEWORK_PACKS.map((p) => p.id);
+}
+function getFrameworkById(id) {
+  return FRAMEWORK_PACKS.find((p) => p.id === id);
+}
+function buildFrameworkCatalogBlock() {
+  const lines = FRAMEWORK_PACKS.filter((p) => p.always_on_catalog).map((p) => p.catalog_line);
+  return `FRAMEWORK TOOLKIT (silent brands \u2014 call get_framework_detail for full body; never name brands to the user):
+${lines.join("\n")}
+Optional packs via get_framework_detail: meddpicc, challenger, jtbd, porter, mckinsey_7s, ooda.`;
+}
+function frameworkIdsForPlay(playId) {
+  return PLAY_FRAMEWORK_HOOKS[playId] ?? [];
+}
+var PLAY_FRAMEWORK_HOOKS, SILENT, FRAMEWORK_PACKS;
+var init_frameworks = __esm({
+  "src/data/frameworks.ts"() {
+    "use strict";
+    PLAY_FRAMEWORK_HOOKS = {
+      "clean-dead-pipeline": ["bottleneck", "heilmeier", "aar"],
+      "unstick-pipeline": ["bottleneck", "okr_measurability", "owner_shape"],
+      "fix-handoff-gap": ["bottleneck", "owner_shape", "aar"],
+      "retarget-effort": ["bottleneck", "gtm_engineering"],
+      "multi-thread-deals": ["owner_shape", "heilmeier"]
+    };
+    SILENT = "Never name this framework (or DARPA, McKinsey, Goldratt, etc.) in customer-visible text. Apply the moves; keep the brand silent.";
+    FRAMEWORK_PACKS = [
+      {
+        id: "bottleneck",
+        catalog_line: "- bottleneck \u2014 name the constraint vital/stage before prescribing; do not fix non-constraints",
+        internal_name: "Theory of Constraints / bottleneck",
+        always_on_catalog: true,
+        vital_links: ["freshness", "flow_rate", "drop_rate", "signal_to_noise", "thread_depth"],
+        board_cut: "One constraint is gating the dollar outcome. Fixing anything else is theater.",
+        operator_cut: "Locate the gating vital (layer order) or the stage where deals die; put the first play there.",
+        when_to_use: "Before recommending a play or sequencing workstreams.",
+        kill_rules: [
+          "If the recommendation does not move the constraint, demote or drop it.",
+          "Do not prescribe parallel fixes that starve the constraint of capacity."
+        ],
+        silent_brand_rule: SILENT,
+        body: `BOTTLENECK (constraint first):
+- Respect layer gating: freshness trust \u2192 flow/drop movement \u2192 signal efficiency \u2192 thread resilience.
+- Name the single constraint vital or pipeline stage with its score and dollar label.
+- Prescribe against the constraint first. Non-constraint work is optional polish.
+- If two problems compete, pick the one that unblocks the other (dependency), not the louder scorecard row.`
+      },
+      {
+        id: "packaging",
+        catalog_line: "- packaging \u2014 answer first, then situation/complication that make it true, then so-what",
+        internal_name: "Minto pyramid + SCQA sibling",
+        always_on_catalog: true,
+        vital_links: [],
+        board_cut: "Open with the call and the dollar. Context is support, not the lead.",
+        operator_cut: "Headline \u226420 words \u2192 2\u20133 non-overlapping drivers \u2192 owner-shaped so-what.",
+        when_to_use: "Every executive-facing answer, finding, recap Story, summary_30k.",
+        kill_rules: ["Never open with methodology or a full scorecard.", "Merge overlapping drivers."],
+        silent_brand_rule: SILENT,
+        body: `PACKAGING (answer-first):
+- Governing thought first (verdict + dollars).
+- Then the situation and complication that make the call true (support, not opener).
+- Then drivers (distinct, non-overlapping) and so-what / ask.
+- Brief: one headline + \u22642 drivers + one so-what.`
+      },
+      {
+        id: "aar",
+        catalog_line: "- after-action \u2014 what we believed, what changed, next bet",
+        internal_name: "After Action Review",
+        always_on_catalog: true,
+        vital_links: [],
+        board_cut: "What we thought would move, what the instruments showed, what we bet next.",
+        operator_cut: "Belief \u2192 evidence from vitals/metrics \u2192 keep, kill, or re-sequence the play.",
+        when_to_use: "Strategy review, session distill calibrations, win/miss logging.",
+        kill_rules: ["Do not log vanity narrative without a measured instrument.", "Calibrations supersede; do not pile contradictions."],
+        silent_brand_rule: SILENT,
+        body: `AFTER-ACTION:
+- BELIEF: what we expected to move (metric + range + check date).
+- EVIDENCE: what the instruments actually showed (baseline \u2192 reading).
+- LEARNING: keep, kill, or re-sequence \u2014 write as a calibration when judgment changed.
+- NEXT BET: the single next exam, not a new multi-week program.`
+      },
+      {
+        id: "owner_shape",
+        catalog_line: "- owner-shape \u2014 function-shaped owner and decision rights; not named people",
+        internal_name: "RACI-lite",
+        always_on_catalog: true,
+        vital_links: [],
+        board_cut: "Every ask names who decides and who executes by function.",
+        operator_cut: "RevOps / AE lead / CS lead / Marketing ops \u2014 R does, A decides; avoid named individuals in plans.",
+        when_to_use: "Workstream titles, handoff plans, play prescriptions.",
+        kill_rules: ["No orphan actions without an accountable function.", "Do not invent headcount or reorgs."],
+        silent_brand_rule: SILENT,
+        body: `OWNER-SHAPE:
+- Name the function (RevOps, sales manager, CS lead, marketing ops) \u2014 not a person's name from the CRM.
+- Accountable decides; Responsible executes. Consulted optional; Inform via existing channels.
+- First action must be startable by that function within 48 hours with no new tooling.`
+      },
+      {
+        id: "okr_measurability",
+        catalog_line: "- exams \u2014 mid-term and final checks as dated key results with instruments",
+        internal_name: "OKR / measurability dialect",
+        always_on_catalog: true,
+        vital_links: ["freshness", "flow_rate", "drop_rate", "signal_to_noise", "thread_depth"],
+        board_cut: "Objective + dated key results the board can re-read next quarter.",
+        operator_cut: "Baseline, target range, check date, measured_by instrument \u2014 or demote to assumption.",
+        when_to_use: "Strategist outcomes, Heilmeier exams, milestones.",
+        kill_rules: ["No 'improve' without a number.", "No exam faster than sales-cycle physics."],
+        silent_brand_rule: SILENT,
+        body: `EXAMS (objective + key results):
+- Objective = precise end state in one line.
+- Key results = mid-term check + final exam: metric, baseline, target RANGE, check date, instrument.
+- If unmeasurable with current data, exclude from targets and record as an assumption.`
+      },
+      {
+        id: "heilmeier",
+        catalog_line: "- idea-gate \u2014 newness, stake, and exams must pass before a recommendation ships",
+        internal_name: "Heilmeier catechism",
+        always_on_catalog: true,
+        vital_links: [],
+        board_cut: "Only recommendations with stake and exams reach the room.",
+        operator_cut: "Kill restatements; demote unmeasurable ideas.",
+        when_to_use: "Deep recommend, think before draft_strategy, strategist Stage C.",
+        kill_rules: ["Fail newness, stake, or exams \u2192 do not recommend."],
+        silent_brand_rule: SILENT,
+        body: `IDEA GATE: end state, status quo + limit, newness, stake + cost of inaction, risks/payoffs, effort, time physics, mid+final exams. Kill on newness/stake/exams failure.`
+      },
+      {
+        id: "minto",
+        catalog_line: "- pyramid \u2014 headline, drivers, so-what for recall",
+        internal_name: "Minto Pyramid Principle",
+        always_on_catalog: true,
+        vital_links: [],
+        board_cut: "Repeatable headline + one number an hour later.",
+        operator_cut: "Same shape for findings and deep answers.",
+        when_to_use: "All packaged analyst prose.",
+        kill_rules: ["Methodology-first openers die."],
+        silent_brand_rule: SILENT,
+        body: `PYRAMID: HEADLINE FIRST \u2192 DRIVERS (non-overlapping) \u2192 SO-WHAT. Recall test. Altitude control.`
+      },
+      {
+        id: "gtm_engineering",
+        catalog_line: "- systems \u2014 data foundation \u2192 modeling \u2192 activation; mechanism per fix",
+        internal_name: "GTM engineering",
+        always_on_catalog: true,
+        vital_links: ["signal_to_noise", "drop_rate", "freshness"],
+        board_cut: "Durable systems, not heroics.",
+        operator_cut: "Pair every cleanup with a mechanism and an instrument.",
+        when_to_use: "When recommending action on tool-capable surfaces.",
+        kill_rules: ["Skipping the rung below will not hold."],
+        silent_brand_rule: SILENT,
+        body: `GTM SYSTEMS: three rungs (foundation \u2192 modeling \u2192 activation); signals over lists; CRM is cheapest pipeline; every fix gets a mechanism; instrument what you change.`
+      },
+      {
+        id: "meddpicc",
+        catalog_line: "- deal-qualification pack (optional) \u2014 use when threading or late-stage risk needs a qualification lens",
+        internal_name: "MEDDPICC",
+        always_on_catalog: false,
+        vital_links: ["thread_depth", "flow_rate"],
+        board_cut: "Late-stage risk is usually missing economic buyer or decision process \u2014 not more activity.",
+        operator_cut: "Map Metrics, Economic buyer, Decision criteria/process, Paper process, Identify pain, Champion, Competition \u2014 as observation, not CRM surgery.",
+        when_to_use: "Thread-depth or stuck late-stage deals when the user asks how to qualify.",
+        kill_rules: ["Do not rewrite the CRM; observe and recommend contacts/process gaps."],
+        silent_brand_rule: SILENT,
+        body: `DEAL QUALIFICATION LENS: use when single-threaded or stuck late-stage deals need a checklist. Prefer introducing a second contact and clarifying decision process over more outbound volume.`
+      },
+      {
+        id: "challenger",
+        catalog_line: "- teach-tailor-take pack (optional) \u2014 pressure-test weak narratives in think",
+        internal_name: "Challenger Sale",
+        always_on_catalog: false,
+        vital_links: ["signal_to_noise"],
+        board_cut: "Insight that reframes the problem beats more activity.",
+        operator_cut: "In think: teach with evidence, tailor to this pipeline, take control of next step \u2014 still stethoscope.",
+        when_to_use: "Think channel when the user is soft on a weak story.",
+        kill_rules: ["Do not turn into a pitch script or CRM sequence builder."],
+        silent_brand_rule: SILENT,
+        body: `TEACH-TAILOR-TAKE: reframe with verified numbers; tailor to segment/motion; land one owner-shaped next step.`
+      },
+      {
+        id: "jtbd",
+        catalog_line: "- job-of-the-metric pack (optional) \u2014 what job this number does for this board",
+        internal_name: "Jobs to be Done",
+        always_on_catalog: false,
+        vital_links: [],
+        board_cut: "Each metric has a job in a decision \u2014 name the job or drop the chart.",
+        operator_cut: "When explaining ARR/NRR/vitals: what decision does this number unlock?",
+        when_to_use: "Metric definitions / board deck framing.",
+        kill_rules: ["Ornamental metrics without a decision job die."],
+        silent_brand_rule: SILENT,
+        body: `JOB OF THE METRIC: for each number, name the decision it serves. If none, cut it from the board package.`
+      },
+      {
+        id: "porter",
+        catalog_line: "- industry-structure pack (optional, weak vital fit) \u2014 only if the user asks competitive structure",
+        internal_name: "Porter Five Forces",
+        always_on_catalog: false,
+        vital_links: [],
+        board_cut: "Industry structure is context, not a substitute for pipeline dollars.",
+        operator_cut: "Do not let industry essays displace vital-sign evidence.",
+        when_to_use: "Only when the user explicitly asks for competitive structure.",
+        kill_rules: ["Never use as a substitute for gating vital diagnosis."],
+        silent_brand_rule: SILENT,
+        body: `INDUSTRY STRUCTURE: optional context. Prefer vital signs and dollars for recommendations.`
+      },
+      {
+        id: "mckinsey_7s",
+        catalog_line: "- org-alignment pack (optional, weak vital fit) \u2014 only if the user asks org design",
+        internal_name: "McKinsey 7S",
+        always_on_catalog: false,
+        vital_links: [],
+        board_cut: "Org redesign is out of stethoscope scope.",
+        operator_cut: "Refuse surgery; observe handoff/ownership symptoms via vitals.",
+        when_to_use: "Only if asked; redirect to owner-shape + bottleneck.",
+        kill_rules: ["No reorg prescriptions."],
+        silent_brand_rule: SILENT,
+        body: `ORG ALIGNMENT: out of scope for CRM surgery. Point to function-shaped owners and the constraint vital instead.`
+      },
+      {
+        id: "ooda",
+        catalog_line: "- observe-orient loop pack (optional) \u2014 overlaps gating; use sparingly",
+        internal_name: "OODA",
+        always_on_catalog: false,
+        vital_links: [],
+        board_cut: "Prefer layer gating and hypothesis-first grounding.",
+        operator_cut: "Already covered by Stage A + bottleneck \u2014 do not duplicate jargon.",
+        when_to_use: "Rarely; prefer existing grounding.",
+        kill_rules: ["Do not invent a parallel loop vocabulary for the user."],
+        silent_brand_rule: SILENT,
+        body: `OBSERVE-ORIENT: prefer NTRP layer gating and Stage A hypothesis-first over a separate combat loop.`
+      }
+    ];
+  }
+});
+
 // src/conversation/agent-context.ts
 var agent_context_exports = {};
 __export(agent_context_exports, {
@@ -21939,10 +22202,10 @@ function wrapForTarget(target, analysisBlock, conversationBlock, openQuestions,
   const contextLabel = handoffInstructionPrefix(ctx.analysis.primary);
   const forWhom = audiencePhrase(ctx.scope?.audience);
   const instructions = {
-    deck: `produce an executive review deck outline for ${company}, framed for ${forWhom}. Pyramid structure: (1) HEADLINE \u2014 the governing number and verdict in one line; (2) DRIVERS \u2014 2\u20133 distinct, non-overlapping risks or causes with dollar impact (not a full scorecard); (3) SO-WHAT \u2014 recommended plays; (4) ASKS / decisions the room must make. Optionally one pipeline-health slide after the headline if it supports the call. Use the Metric definitions appendix so every slide can briefly remind the room what the number means for this audience.`,
-    asana: `produce an Asana project plan with sections and tasks tied to findings for ${forWhom}. Prioritize by dollar impact. Reference metric definitions when a task owner needs to know what "good" looks like.`,
+    deck: `produce an executive review deck outline for ${company}, framed for ${forWhom}. Pyramid structure: (1) HEADLINE \u2014 the governing number and verdict in one line; (2) DRIVERS \u2014 2\u20133 distinct, non-overlapping risks or causes with dollar impact (not a full scorecard); (3) SO-WHAT \u2014 recommended plays with function-shaped owners (RevOps / sales manager / CS \u2014 not personal names); (4) ASKS / decisions the room must make. Optionally one pipeline-health slide after the headline if it supports the call. Use the Metric definitions appendix so every slide can briefly remind the room what the number means for this audience.`,
+    asana: `produce an Asana project plan with sections and tasks tied to findings for ${forWhom}. Prioritize by dollar impact. Assign by function (not personal names). Reference metric definitions when a task owner needs to know what "good" looks like.`,
     clay: `produce a Clay table specification to operationalize the highest-impact finding for ${forWhom}.`,
-    plan: `produce a prioritized action plan for ${forWhom}, answer-first: open with the governing call (highest-dollar problem), then items each with problem, play, first 3 steps, owner, and leading indicator. Ground indicators in the Metric definitions appendix. End with the sharpest asks / decisions.`
+    plan: `produce a prioritized action plan for ${forWhom}, answer-first: open with the governing call (highest-dollar problem / constraint), then items each with problem, play, first 3 steps, function-shaped owner, and leading indicator. Ground indicators in the Metric definitions appendix. End with the sharpest asks / decisions.`
   };
   const parts = [
     `# NTRP handoff \u2192 ${target}`,
@@ -22304,6 +22567,7 @@ async function handleGetPlayDetail(input) {
     }
   } catch {
   }
+  const { frameworkIdsForPlay: frameworkIdsForPlay2 } = await Promise.resolve().then(() => (init_frameworks(), frameworks_exports));
   const detail = {
     play_id: play.id,
     play_name: play.name,
@@ -22315,7 +22579,8 @@ async function handleGetPlayDetail(input) {
     tools_that_help: play.tools_that_help,
     expected_outcome: play.expected_outcome,
     source: play.source ?? "seed",
-    local_track_record: trackRecord
+    local_track_record: trackRecord,
+    framework_ids: frameworkIdsForPlay2(play.id)
   };
   if (play.source === "learned") {
     detail.security_notice = UNTRUSTED_CONTENT_NOTICE;
@@ -22326,6 +22591,30 @@ async function handleGetPlayDetail(input) {
   }
   return detail;
 }
+async function handleGetFrameworkDetail(input) {
+  const frameworkId = typeof input.framework_id === "string" ? input.framework_id.trim() : "";
+  const { getFrameworkById: getFrameworkById2, listFrameworkIds: listFrameworkIds2 } = await Promise.resolve().then(() => (init_frameworks(), frameworks_exports));
+  const pack = frameworkId ? getFrameworkById2(frameworkId) : void 0;
+  if (!pack) {
+    return {
+      error: `Unknown framework id '${frameworkId}'.`,
+      valid_framework_ids: listFrameworkIds2()
+    };
+  }
+  return {
+    framework_id: pack.id,
+    catalog_line: pack.catalog_line,
+    always_on_catalog: pack.always_on_catalog,
+    vital_links: pack.vital_links,
+    board_cut: pack.board_cut,
+    operator_cut: pack.operator_cut,
+    when_to_use: pack.when_to_use,
+    kill_rules: pack.kill_rules,
+    silent_brand_rule: pack.silent_brand_rule,
+    body: pack.body,
+    notice: "Apply the moves in body/board_cut/operator_cut. Never name internal brand labels to the user."
+  };
+}
 async function handleGetRevenueMetrics(_input, ctx) {
   if (!ctx.metrics || ctx.metrics.length === 0) {
     const { computeFullMetrics: computeFullMetrics2 } = await Promise.resolve().then(() => (init_compute(), compute_exports));
@@ -22620,6 +22909,7 @@ var init_tool_handlers = __esm({
       query_segment_comparison: handleQuerySegmentComparison,
       query_entity_counts: (input, _) => handleQueryEntityCounts(input),
       get_play_detail: (input, _) => handleGetPlayDetail(input),
+      get_framework_detail: (input, _) => handleGetFrameworkDetail(input),
       get_session_brief: (input, _) => handleGetSessionBrief(input),
       get_revenue_metrics: handleGetRevenueMetrics,
       get_revenue_metrics_timeseries: (input, _) => handleGetRevenueMetricsTimeseries(input),
@@ -22901,6 +23191,12 @@ ${GTM_ENGINEERING_BLOCK}
 IDEA GATE (when recommending a play or before draft_strategy \u2014 silent; probing/imagination turns skip this until you conclude):
 ${HEILMEIER_GATE}
 
+BOTTLENECK (when concluding or recommending \u2014 silent):
+${BOTTLENECK_GATE}
+
+OWNER SHAPE (when recommending \u2014 silent):
+${OWNER_SHAPE_BLOCK}
+
 OUTPUT DOCTRINE (how answers are structured for recall):
 ${PYRAMID_OUTPUT_BLOCK}
 
@@ -22915,6 +23211,8 @@ ${VITAL_SIGNS_BLOCK}
 PLAYBOOK \u2014 name a play when it helps the user act (not a full program):
 ${buildPlaybookBlock()}
 
+${buildFrameworkCatalogBlock()}
+
 ${commandSection}
 ${formattingSection}
 OUTPUT RULES:
@@ -22943,6 +23241,7 @@ var init_think_prompt = __esm({
   "src/ai/think-prompt.ts"() {
     "use strict";
     init_prompt_parts();
+    init_frameworks();
     init_prompt();
   }
 });
@@ -22973,6 +23272,7 @@ var init_ghost_hints = __esm({
       ],
       explore: [
         'try "what is the most expensive problem?"',
+        'try "which constraint is gating the dollars?"',
         'try "how should we fix this?"',
         'try "which segment is weakest?"',
         'try "what is ARR?"',
@@ -23063,9 +23363,28 @@ function buildSituationalAwarenessBlock(ctx, opts = {}) {
   if (examples.length > 0) {
     lines.push(`User may try: ${examples.join(" \xB7 ")}`);
   }
-  lines.push(
-    "Your job in this harness: fill the judgment gap after formula compute \u2014 connect dollars, name the expensive problem, do not restate scorecards the user already saw"
-  );
+  if (channel === "think") {
+    lines.push(
+      "Doctrine: probing leads with the sharpest question (idea-gate off until you conclude); concluding/recommend turns \u2014 silent idea-gate then bottleneck then pyramid packaging; never name frameworks to the user"
+    );
+  } else if (responseMode === "brief") {
+    lines.push(
+      "Doctrine: brief packaging \u2014 headline \u226420 words, \u22642 drivers, one so-what; idea-gate off; never name frameworks to the user; do not restate The Call/scorecard \u2014 advance"
+    );
+  } else {
+    lines.push(
+      "Doctrine: deep/recommend \u2014 silent idea-gate then bottleneck then owner-shape then pyramid packaging; call get_framework_detail for toolkit depth; never name frameworks to the user"
+    );
+  }
+  if (analysisReady) {
+    lines.push(
+      "Your job in this harness: after formula compute, lead with the most expensive or actionable implication \u2014 connect dollars, name the constraint, do not restate scorecards or The Call the user already saw"
+    );
+  } else {
+    lines.push(
+      "Your job in this harness: help the user through the funnel; CLI owns pre-explore gates"
+    );
+  }
   lines.push(
     "Pre-explore funnel gates are handled by the CLI; you speak in explore/think/strategist unless tools explicitly allow a restart"
   );
@@ -23078,10 +23397,12 @@ function buildSituationalRuntimeFacts(ctx, opts = {}) {
   return {
     phase,
     mode: responseMode,
+    channel,
     lens: ctx.scope?.primary_lens,
     stage: ctx.stage,
     can_compute: ctx.gapAudit?.can_compute === void 0 ? void 0 : String(ctx.gapAudit.can_compute),
-    engine: canUseReplAi(ctx) ? "connected" : "none"
+    engine: canUseReplAi(ctx) ? "connected" : "none",
+    idea_gate: channel === "think" || responseMode === "deep" ? "on" : "off"
   };
 }
 function getConversationPhaseBlock(ctx, opts = {}) {
@@ -23301,7 +23622,7 @@ ${commandStyleRule}`;
 - Respond in plain text (not JSON). You do NOT need to emit the findings schema \u2014 only emit structured findings if the user explicitly asks for them.
 - Include specific numbers from tool results, never guess.
 - When you have enough information, answer directly. Don't call tools you don't need.`;
-  const executionBiasSection = responseMode === "brief" ? `OUTPUT DOCTRINE (brief \u2014 one headline + \u22642 drivers + one so-what):
+  const executionBiasSection = responseMode === "brief" ? `OUTPUT DOCTRINE (brief \u2014 one headline + \u22642 drivers + one so-what; situation/complication only as support after the headline):
 ${PYRAMID_OUTPUT_BLOCK}
 
 ` : `EXECUTION BIAS (how you work):
@@ -23313,6 +23634,12 @@ ${GTM_ENGINEERING_BLOCK}
 IDEA GATE (when recommending action \u2014 silent):
 ${HEILMEIER_GATE}
 
+BOTTLENECK (constraint first \u2014 silent):
+${BOTTLENECK_GATE}
+
+OWNER SHAPE (when recommending action \u2014 silent):
+${OWNER_SHAPE_BLOCK}
+
 OUTPUT DOCTRINE (how answers are structured for recall):
 ${PYRAMID_OUTPUT_BLOCK}
 
@@ -23328,6 +23655,8 @@ ${VITAL_SIGNS_BLOCK}
 PLAYBOOK \u2014 recommend these plays when appropriate:
 ${buildPlaybookBlock()}
 
+${buildFrameworkCatalogBlock()}
+
 ${commandSection}`;
   const stable = `You are a world-class GTM operating partner \u2014 the kind of analyst a CEO keeps on speed dial. You are exceptionally well-read, rigorous, and commercially sharp, and you have tools to query a local database of this company's CRM and pipeline data. The user is having an ongoing, free-form conversation with you about their go-to-market health and SaaS metrics.
 
@@ -23576,6 +23905,7 @@ var init_agentic_loop = __esm({
     init_thread();
     init_untrusted();
     init_prompt_parts();
+    init_frameworks();
     init_think_prompt();
     init_prompt();
     init_context2();
@@ -28480,13 +28810,16 @@ ${companyContextSection4()}${operatorSection4()}HOW YOU THINK (the strategist me
 8. RESPECT CAPACITY. Total effort must fit the team that actually exists. A brilliant plan the team cannot staff is a bad plan.
 
 ALTITUDE CONTRACT (the plan must work at every altitude a client reads it at):
-- 30,000 FT: summary_30k is answer-first \u2014 open with the governing thought and what leadership should expect by when, then the situation and complication that make it true. A board member reads only this; it must survive being forwarded unedited.
-- 10,000 FT: each workstream's title + problem line is a delegation unit \u2014 a one-liner an owner could receive in Slack and know what they own, why it's theirs, and what number they move.
+- 30,000 FT: summary_30k is answer-first \u2014 open with the governing thought (the answer) and what leadership should expect by when, then the situation and complication that make it true as support. A board member reads only this; it must survive being forwarded unedited.
+- 10,000 FT: each workstream's title + problem line is a delegation unit \u2014 a one-liner an owner could receive in Slack and know what they own, why it's theirs, and what number they move. Use function-shaped owners (see OWNER SHAPE).
 - GROUND LEVEL: actions are Monday-morning prescriptive. You have built this before \u2014 read the linked play's full detail with get_play_detail and prescribe its known-good sequence adapted to THIS company's numbers and constraints. The first action of every workstream must be startable within 48 hours with no new tooling.
 
 OUTPUT DOCTRINE (narrative fields \u2014 summary_30k and workstream problem lines \u2014 follow pyramid recall):
 ${PYRAMID_OUTPUT_BLOCK}
 
+OWNER SHAPE (workstreams and actions \u2014 silent):
+${OWNER_SHAPE_BLOCK}
+
 ${buildUserVisibleProseBlock()}
 
 GTM ENGINEERING (plans install systems, not heroics):
@@ -28501,7 +28834,10 @@ ${METRICS_BLOCK}
 PLAYBOOK (every workstream must link to at least one play by exact id):
 ${buildPlaybookBlock()}
 
+${buildFrameworkCatalogBlock()}
+
 MEASURABILITY CONTRACT (non-negotiable \u2014 this is what separates you from a slide deck):
+- Treat the objective as the end state; treat expected outcomes and leading indicators as key results (mid-term and final exams).
 - Every expected outcome and leading indicator needs: a metric, the current baseline copied from your verified grounding work, a target RANGE, a check date, and the named instrument that will measure it.
 - Banned words for outcomes: "improve", "better", "significantly", "optimize", "increase" without a number. If you cannot quantify it, it is not an outcome \u2014 demote it to an assumption or replace it with its best measurable proxy.
 - Every workstream needs at least one dated milestone with a verification method that names a number and threshold.
@@ -28520,9 +28856,13 @@ function buildGroundingMessage(input) {
 
 Establish verified reality before any planning. Work hypothesis-first, like an engagement manager on day one: form your top candidate explanations for what stands between today and the objective, then use tools to confirm or kill each one \u2014 don't boil the ocean.
 1. Current state: which vital signs / metrics are worst, what are the exact scores and dollar values, which segments concentrate the problem?
-2. What is already in flight (active strategies below, if any), what has worked before (wins), and what the local play track record says.
-3. What are the binding constraints: data gaps that limit measurability, sales-cycle length that bounds verification speed, capacity signals?
-Rank the problems you verify by dollars at stake \xD7 confidence in the read \xD7 speed to impact \u2014 that ranking becomes the spine of the plan.`);
+2. CONSTRAINT: name the single gating vital (layer order) or stage where deals die \u2014 with score and dollar label. This is the bottleneck the plan must move first.
+3. What is already in flight (active strategies below, if any), what has worked before (wins), and what the local play track record says.
+4. What are the binding constraints: data gaps that limit measurability, sales-cycle length that bounds verification speed, capacity signals?
+Rank the problems you verify by dollars at stake \xD7 confidence in the read \xD7 speed to impact \u2014 that ranking becomes the spine of the plan. Non-constraint problems wait.
+
+BOTTLENECK (silent):
+${BOTTLENECK_GATE}`);
   sections.push(`CURRENT HEALTH SNAPSHOT (verified \u2014 you may cite these numbers as baselines):
 ${input.healthSnapshot}`);
   if (input.gapAuditBlock) {
@@ -28571,6 +28911,8 @@ function buildStressTestMessage() {
 8. ALTITUDE CHECK: does summary_30k survive being forwarded to a board member unedited? Is each workstream title + problem a self-contained delegation one-liner? Is every first action startable within 48 hours?
 9. HEILMEIER GATE (silent \u2014 never name this to the user). Run every workstream through this filter. Failures: cut the workstream, demote it to assumptions, or rewrite until it passes \u2014 then emit final JSON.
 ${HEILMEIER_GATE}
+10. AFTER-ACTION PREP (silent). Ensure each workstream's exams can support a later belief\u2192evidence\u2192next-bet review. Fold gaps into assumptions or contingencies.
+${AAR_BLOCK}
 
 Then respond with the FINAL revised plan as strict JSON in the same schema \u2014 no markdown fences, no prose. Fold what you learned into constraints, assumptions, risks, and confidence. This version is the one that gets saved and reviewed against, so make every number one you are willing to be checked on.`;
 }
@@ -28579,6 +28921,7 @@ var init_strategist_prompt = __esm({
   "src/ai/strategist-prompt.ts"() {
     "use strict";
     init_prompt_parts();
+    init_frameworks();
     init_prompt();
     STRATEGIST_PLAN_SCHEMA_BLOCK = `{
   "title": "Short plan name, e.g. 'Q4 Pipeline Recovery'",
@@ -30286,6 +30629,11 @@ function renderReport(report) {
       `${strategy.slug} \xB7 baseline batch ${shortBatch(report.baseline_batch_id)} \u2192 latest ${shortBatch(report.latest_batch_id)}`
     )
   );
+  console.log(
+    "  " + chalk38.dim(
+      "Read as belief \u2192 evidence \u2192 next bet: what we expected, what instruments showed, what to keep/kill/re-sequence."
+    )
+  );
   if (report.single_batch) {
     console.log(
       "  " + chalk38.yellow("Only one compute batch exists \u2014 ingest fresh data and re-run for a real before/after.")
@@ -36564,7 +36912,8 @@ handler: ../commands/knowledge.ts
 
 Teach the analyst from work done outside the platform.
 Type \`/knowledge add <file>\` to ingest a markdown, text, or PDF case study, framework, or benchmark report.
-NTRP indexes it for retrieval during analysis. Type \`/knowledge list\` to show what is indexed.
+NTRP indexes it for retrieval during analysis (your own consulting packs welcome \u2014 built-in toolkit is silent and lives behind get_framework_detail).
+Type \`/knowledge list\` to show what is indexed.
 Drop files into ~/.ntrp/knowledge to stage them.`
       },
       {
@@ -37100,7 +37449,7 @@ function formatCatalogLine(meta) {
   const note = DESTRUCTIVE_COMMAND_NOTES[meta.name] ? ` (${DESTRUCTIVE_COMMAND_NOTES[meta.name]})` : "";
   return `- /${meta.name}${args} \u2014 ${meta.description}${note}`;
 }
-var ANALYST_FILE_NAME, ANALYST_FILE_MAX_CHARS, EXECUTION_BIAS_BLOCK, ANALYST_INSTINCT_BLOCK, SAFETY_BLOCK, VITAL_SIGNS_BLOCK, PLAYBOOK_BLOCK, DESTRUCTIVE_COMMAND_NOTES, METRICS_BLOCK, GTM_ENGINEERING_BLOCK, HEILMEIER_GATE, PYRAMID_OUTPUT_BLOCK;
+var ANALYST_FILE_NAME, ANALYST_FILE_MAX_CHARS, EXECUTION_BIAS_BLOCK, ANALYST_INSTINCT_BLOCK, SAFETY_BLOCK, VITAL_SIGNS_BLOCK, PLAYBOOK_BLOCK, DESTRUCTIVE_COMMAND_NOTES, METRICS_BLOCK, GTM_ENGINEERING_BLOCK, HEILMEIER_GATE, BOTTLENECK_GATE, OWNER_SHAPE_BLOCK, AAR_BLOCK, PYRAMID_OUTPUT_BLOCK;
 var init_prompt_parts = __esm({
   "src/ai/prompt-parts.ts"() {
     "use strict";
@@ -37180,17 +37529,33 @@ Instrument trust: every metric here carries confidence and reliability_gate fiel
 - INSTRUMENT WHAT YOU CHANGE. A system you can't measure is a system you can't defend at the next QBR. Name the metric each mechanism should move and where it will be read.
 Restraint: you diagnose and prescribe the system; you do not build it here. Name the mechanism class, not a vendor shopping list.`;
     HEILMEIER_GATE = `Before you recommend an action, play, or workstream \u2014 run this gate. Failures are silent: kill, demote to an assumption, or ask one sharper question. Never say Heilmeier, DARPA, or catechism to the user.
-- END STATE. Name the precise outcome in one line. Vague goals die here.
+- END STATE. Name the precise outcome in one line (the objective). Vague goals die here.
 - STATUS QUO. How is it done today, and what is the hard limit of that approach?
 - NEWNESS. What is new in this approach, and why might it work when the status quo fails? If nothing is new, kill it as a restatement.
 - STAKE. Who cares? If it works, what difference does it make \u2014 dollars recovered or a decision unlocked? Name the cost of doing nothing. No stake \u2192 do not recommend.
 - RISKS AND PAYOFFS. State the main downside and the upside in the same breath.
 - EFFORT. Rough cost in team hours or capacity. If it cannot fit the team that exists, cut or re-sequence \u2014 do not soft-pedal.
 - TIME. Bound by sales-cycle and metric-update physics. Dates faster than evidence can appear are invalid.
-- EXAMS. Name a mid-term check and a final exam: dated, measurable, with an instrument that exists. No exams \u2192 demote to assumption or drop.
+- EXAMS (key results). Name a mid-term check and a final exam: dated, measurable, with baseline + target RANGE + an instrument that exists. These are the objective's key results. No exams \u2192 demote to assumption or drop.
 - KILL RULE. If newness, stake, or exams fail: do not recommend. Demote, drop, or ask one sharper question. Surviving ideas then get pyramid packaging.`;
+    BOTTLENECK_GATE = `Before you prescribe a fix \u2014 name the constraint. Never say Theory of Constraints, TOC, or Goldratt to the user.
+- CONSTRAINT FIRST. Identify the single gating vital (layer order: freshness \u2192 flow_rate/drop_rate \u2192 signal_to_noise \u2192 thread_depth) or the pipeline stage where deals die \u2014 with score and dollar label.
+- PRESCRIBE THE CONSTRAINT. The first play or workstream must move that constraint. Non-constraint work is optional polish.
+- DEPENDENCY OVER NOISE. If two problems compete, pick the one that unblocks the other.
+- KILL RULE. If the recommendation does not move the named constraint, demote or drop it.`;
+    OWNER_SHAPE_BLOCK = `When you recommend action \u2014 shape the owner. Never say RACI to the user.
+- FUNCTION NOT PERSON. Name RevOps, sales manager, CS lead, marketing ops, or AE lead \u2014 not a CRM contact's personal name.
+- ACCOUNTABLE DECIDES; RESPONSIBLE EXECUTES. One accountable function per ask.
+- 48-HOUR START. The first action must be startable by that function within 48 hours with no new tooling.
+- NO REORG. Do not invent headcount or redesign the company.`;
+    AAR_BLOCK = `When reviewing outcomes or distilling learning \u2014 run after-action. Never say AAR or after-action review to the user.
+- BELIEF. What we expected to move (metric + range + check date).
+- EVIDENCE. What the instruments showed (baseline \u2192 reading).
+- LEARNING. Keep, kill, or re-sequence. Write judgment changes as calibrations that supersede contradictions.
+- NEXT BET. One next exam \u2014 not a new multi-week program.`;
     PYRAMID_OUTPUT_BLOCK = `Structure everything the way a client remembers it \u2014 pyramid, answer first:
 - HEADLINE FIRST. Open with the verdict and the number in one sentence (\u226420 words): what is true and what it costs. Never open with methodology or context.
+- SITUATION AS SUPPORT. After the headline, the situation and complication that make the call true may follow as support \u2014 never as the opener. Do not name SCQA to the user.
 - THEN THE DRIVERS. Support the headline with 2-3 drivers that are distinct, non-overlapping, and together explain the headline \u2014 each with its own number. If two points share a cause, merge them.
 - THEN THE SO-WHAT. Close with what it means for the decision at hand: the action, the owner-shaped next step, or the sharpest next cut.
 - THE RECALL TEST. A busy executive should be able to repeat your headline and one number to their CEO an hour later. If they couldn't, tighten it.

package/dist/mcp/server.js

@@ -1297,6 +1297,7 @@ function buildSessionContextDoc(file, opts = {}) {
   lines.push(`- Exchanges: ${exchanges}`);
   if (file.summary) lines.push(`- Summary: ${file.summary}`);
   if (file.resumed_from) lines.push(`- Resumed from: ${file.resumed_from}`);
+  lines.push("- Packaging: answer-first; recommendations filtered (silent idea-gate on deep/think/strategy)");
   lines.push("");
   lines.push("## Dataset");
   lines.push("");
@@ -8039,6 +8040,8 @@ KINDS:
 - "preference": how the user wants analysis done or framed.
 - "calibration": a judgment update \u2014 an adjustment to HOW this business should be analyzed. Write it as an applicable rule, e.g. "Enterprise freshness reds here trace to rep coverage gaps, not data hygiene \u2014 cut by owner first" or "This team treats 45 quiet days as normal cadence; don't flag staleness before that." Capture corrections the user made to your reasoning as calibrations, not preferences.
 
+AFTER-ACTION LENS (silent \u2014 never name AAR to anyone): prefer items that capture BELIEF that changed, EVIDENCE that forced the change, or the NEXT BET the team should re-check. Calibrations that supersede contradictions are the highest-value distillates.
+
 SUPERSEDING (calibrations only): the current calibrations are provided with ids. If the session contradicts or refines one, return the replacement with "supersedes" set to the old id. Never emit a calibration that duplicates an existing one.
 
 EXCLUDE:
@@ -10194,7 +10197,8 @@ handler: ../commands/knowledge.ts
 
 Teach the analyst from work done outside the platform.
 Type \`/knowledge add <file>\` to ingest a markdown, text, or PDF case study, framework, or benchmark report.
-NTRP indexes it for retrieval during analysis. Type \`/knowledge list\` to show what is indexed.
+NTRP indexes it for retrieval during analysis (your own consulting packs welcome \u2014 built-in toolkit is silent and lives behind get_framework_detail).
+Type \`/knowledge list\` to show what is indexed.
 Drop files into ~/.ntrp/knowledge to stage them.`
       },
       {
@@ -10730,7 +10734,7 @@ function formatCatalogLine(meta) {
   const note = DESTRUCTIVE_COMMAND_NOTES[meta.name] ? ` (${DESTRUCTIVE_COMMAND_NOTES[meta.name]})` : "";
   return `- /${meta.name}${args} \u2014 ${meta.description}${note}`;
 }
-var ANALYST_FILE_NAME, ANALYST_FILE_MAX_CHARS, EXECUTION_BIAS_BLOCK, ANALYST_INSTINCT_BLOCK, SAFETY_BLOCK, VITAL_SIGNS_BLOCK, PLAYBOOK_BLOCK, DESTRUCTIVE_COMMAND_NOTES, METRICS_BLOCK, GTM_ENGINEERING_BLOCK, HEILMEIER_GATE, PYRAMID_OUTPUT_BLOCK;
+var ANALYST_FILE_NAME, ANALYST_FILE_MAX_CHARS, EXECUTION_BIAS_BLOCK, ANALYST_INSTINCT_BLOCK, SAFETY_BLOCK, VITAL_SIGNS_BLOCK, PLAYBOOK_BLOCK, DESTRUCTIVE_COMMAND_NOTES, METRICS_BLOCK, GTM_ENGINEERING_BLOCK, HEILMEIER_GATE, BOTTLENECK_GATE, OWNER_SHAPE_BLOCK, AAR_BLOCK, PYRAMID_OUTPUT_BLOCK;
 var init_prompt_parts = __esm({
   "src/ai/prompt-parts.ts"() {
     "use strict";
@@ -10810,17 +10814,33 @@ Instrument trust: every metric here carries confidence and reliability_gate fiel
 - INSTRUMENT WHAT YOU CHANGE. A system you can't measure is a system you can't defend at the next QBR. Name the metric each mechanism should move and where it will be read.
 Restraint: you diagnose and prescribe the system; you do not build it here. Name the mechanism class, not a vendor shopping list.`;
     HEILMEIER_GATE = `Before you recommend an action, play, or workstream \u2014 run this gate. Failures are silent: kill, demote to an assumption, or ask one sharper question. Never say Heilmeier, DARPA, or catechism to the user.
-- END STATE. Name the precise outcome in one line. Vague goals die here.
+- END STATE. Name the precise outcome in one line (the objective). Vague goals die here.
 - STATUS QUO. How is it done today, and what is the hard limit of that approach?
 - NEWNESS. What is new in this approach, and why might it work when the status quo fails? If nothing is new, kill it as a restatement.
 - STAKE. Who cares? If it works, what difference does it make \u2014 dollars recovered or a decision unlocked? Name the cost of doing nothing. No stake \u2192 do not recommend.
 - RISKS AND PAYOFFS. State the main downside and the upside in the same breath.
 - EFFORT. Rough cost in team hours or capacity. If it cannot fit the team that exists, cut or re-sequence \u2014 do not soft-pedal.
 - TIME. Bound by sales-cycle and metric-update physics. Dates faster than evidence can appear are invalid.
-- EXAMS. Name a mid-term check and a final exam: dated, measurable, with an instrument that exists. No exams \u2192 demote to assumption or drop.
+- EXAMS (key results). Name a mid-term check and a final exam: dated, measurable, with baseline + target RANGE + an instrument that exists. These are the objective's key results. No exams \u2192 demote to assumption or drop.
 - KILL RULE. If newness, stake, or exams fail: do not recommend. Demote, drop, or ask one sharper question. Surviving ideas then get pyramid packaging.`;
+    BOTTLENECK_GATE = `Before you prescribe a fix \u2014 name the constraint. Never say Theory of Constraints, TOC, or Goldratt to the user.
+- CONSTRAINT FIRST. Identify the single gating vital (layer order: freshness \u2192 flow_rate/drop_rate \u2192 signal_to_noise \u2192 thread_depth) or the pipeline stage where deals die \u2014 with score and dollar label.
+- PRESCRIBE THE CONSTRAINT. The first play or workstream must move that constraint. Non-constraint work is optional polish.
+- DEPENDENCY OVER NOISE. If two problems compete, pick the one that unblocks the other.
+- KILL RULE. If the recommendation does not move the named constraint, demote or drop it.`;
+    OWNER_SHAPE_BLOCK = `When you recommend action \u2014 shape the owner. Never say RACI to the user.
+- FUNCTION NOT PERSON. Name RevOps, sales manager, CS lead, marketing ops, or AE lead \u2014 not a CRM contact's personal name.
+- ACCOUNTABLE DECIDES; RESPONSIBLE EXECUTES. One accountable function per ask.
+- 48-HOUR START. The first action must be startable by that function within 48 hours with no new tooling.
+- NO REORG. Do not invent headcount or redesign the company.`;
+    AAR_BLOCK = `When reviewing outcomes or distilling learning \u2014 run after-action. Never say AAR or after-action review to the user.
+- BELIEF. What we expected to move (metric + range + check date).
+- EVIDENCE. What the instruments showed (baseline \u2192 reading).
+- LEARNING. Keep, kill, or re-sequence. Write judgment changes as calibrations that supersede contradictions.
+- NEXT BET. One next exam \u2014 not a new multi-week program.`;
     PYRAMID_OUTPUT_BLOCK = `Structure everything the way a client remembers it \u2014 pyramid, answer first:
 - HEADLINE FIRST. Open with the verdict and the number in one sentence (\u226420 words): what is true and what it costs. Never open with methodology or context.
+- SITUATION AS SUPPORT. After the headline, the situation and complication that make the call true may follow as support \u2014 never as the opener. Do not name SCQA to the user.
 - THEN THE DRIVERS. Support the headline with 2-3 drivers that are distinct, non-overlapping, and together explain the headline \u2014 each with its own number. If two points share a cause, merge them.
 - THEN THE SO-WHAT. Close with what it means for the decision at hand: the action, the owner-shaped next step, or the sharpest next cut.
 - THE RECALL TEST. A busy executive should be able to repeat your headline and one number to their CEO an hour later. If they couldn't, tighten it.
@@ -11595,6 +11615,21 @@ var init_tool_schemas = __esm({
           required: ["play_id"]
         }
       },
+      {
+        name: "get_framework_detail",
+        description: "Read a consulting/operating framework pack by id: when to use, vital links, board vs operator cut, kill rules, and full body. The system prompt lists only the catalog \u2014 call this when you need depth before recommending. Never name brand labels (Heilmeier, Minto, TOC, MEDDPICC, \u2026) to the user.",
+        parameters: {
+          type: "object",
+          properties: {
+            framework_id: {
+              type: "string",
+              maxLength: 40,
+              description: "Exact id from the framework catalog, e.g. 'bottleneck', 'packaging', 'aar', 'meddpicc'."
+            }
+          },
+          required: ["framework_id"]
+        }
+      },
       {
         name: "get_session_brief",
         description: "Read the 1-page context brief of a PRIOR session by id or 4-char suffix: status, dataset, scope, computed scores with dollar values, headline metrics, deliverables, and conversation log. Use when the user references earlier work \u2014 'last week we found\u2026', 'compare with the previous analysis', 'what did session 9297 conclude?'. Read-only.",
@@ -11696,6 +11731,251 @@ var init_tool_arg_validate = __esm({
   }
 });
 
+// src/data/frameworks.ts
+var frameworks_exports = {};
+__export(frameworks_exports, {
+  FRAMEWORK_PACKS: () => FRAMEWORK_PACKS,
+  PLAY_FRAMEWORK_HOOKS: () => PLAY_FRAMEWORK_HOOKS,
+  buildFrameworkCatalogBlock: () => buildFrameworkCatalogBlock,
+  frameworkIdsForPlay: () => frameworkIdsForPlay,
+  getFrameworkById: () => getFrameworkById,
+  listFrameworkIds: () => listFrameworkIds
+});
+function listFrameworkIds() {
+  return FRAMEWORK_PACKS.map((p) => p.id);
+}
+function getFrameworkById(id) {
+  return FRAMEWORK_PACKS.find((p) => p.id === id);
+}
+function buildFrameworkCatalogBlock() {
+  const lines = FRAMEWORK_PACKS.filter((p) => p.always_on_catalog).map((p) => p.catalog_line);
+  return `FRAMEWORK TOOLKIT (silent brands \u2014 call get_framework_detail for full body; never name brands to the user):
+${lines.join("\n")}
+Optional packs via get_framework_detail: meddpicc, challenger, jtbd, porter, mckinsey_7s, ooda.`;
+}
+function frameworkIdsForPlay(playId) {
+  return PLAY_FRAMEWORK_HOOKS[playId] ?? [];
+}
+var PLAY_FRAMEWORK_HOOKS, SILENT, FRAMEWORK_PACKS;
+var init_frameworks = __esm({
+  "src/data/frameworks.ts"() {
+    "use strict";
+    PLAY_FRAMEWORK_HOOKS = {
+      "clean-dead-pipeline": ["bottleneck", "heilmeier", "aar"],
+      "unstick-pipeline": ["bottleneck", "okr_measurability", "owner_shape"],
+      "fix-handoff-gap": ["bottleneck", "owner_shape", "aar"],
+      "retarget-effort": ["bottleneck", "gtm_engineering"],
+      "multi-thread-deals": ["owner_shape", "heilmeier"]
+    };
+    SILENT = "Never name this framework (or DARPA, McKinsey, Goldratt, etc.) in customer-visible text. Apply the moves; keep the brand silent.";
+    FRAMEWORK_PACKS = [
+      {
+        id: "bottleneck",
+        catalog_line: "- bottleneck \u2014 name the constraint vital/stage before prescribing; do not fix non-constraints",
+        internal_name: "Theory of Constraints / bottleneck",
+        always_on_catalog: true,
+        vital_links: ["freshness", "flow_rate", "drop_rate", "signal_to_noise", "thread_depth"],
+        board_cut: "One constraint is gating the dollar outcome. Fixing anything else is theater.",
+        operator_cut: "Locate the gating vital (layer order) or the stage where deals die; put the first play there.",
+        when_to_use: "Before recommending a play or sequencing workstreams.",
+        kill_rules: [
+          "If the recommendation does not move the constraint, demote or drop it.",
+          "Do not prescribe parallel fixes that starve the constraint of capacity."
+        ],
+        silent_brand_rule: SILENT,
+        body: `BOTTLENECK (constraint first):
+- Respect layer gating: freshness trust \u2192 flow/drop movement \u2192 signal efficiency \u2192 thread resilience.
+- Name the single constraint vital or pipeline stage with its score and dollar label.
+- Prescribe against the constraint first. Non-constraint work is optional polish.
+- If two problems compete, pick the one that unblocks the other (dependency), not the louder scorecard row.`
+      },
+      {
+        id: "packaging",
+        catalog_line: "- packaging \u2014 answer first, then situation/complication that make it true, then so-what",
+        internal_name: "Minto pyramid + SCQA sibling",
+        always_on_catalog: true,
+        vital_links: [],
+        board_cut: "Open with the call and the dollar. Context is support, not the lead.",
+        operator_cut: "Headline \u226420 words \u2192 2\u20133 non-overlapping drivers \u2192 owner-shaped so-what.",
+        when_to_use: "Every executive-facing answer, finding, recap Story, summary_30k.",
+        kill_rules: ["Never open with methodology or a full scorecard.", "Merge overlapping drivers."],
+        silent_brand_rule: SILENT,
+        body: `PACKAGING (answer-first):
+- Governing thought first (verdict + dollars).
+- Then the situation and complication that make the call true (support, not opener).
+- Then drivers (distinct, non-overlapping) and so-what / ask.
+- Brief: one headline + \u22642 drivers + one so-what.`
+      },
+      {
+        id: "aar",
+        catalog_line: "- after-action \u2014 what we believed, what changed, next bet",
+        internal_name: "After Action Review",
+        always_on_catalog: true,
+        vital_links: [],
+        board_cut: "What we thought would move, what the instruments showed, what we bet next.",
+        operator_cut: "Belief \u2192 evidence from vitals/metrics \u2192 keep, kill, or re-sequence the play.",
+        when_to_use: "Strategy review, session distill calibrations, win/miss logging.",
+        kill_rules: ["Do not log vanity narrative without a measured instrument.", "Calibrations supersede; do not pile contradictions."],
+        silent_brand_rule: SILENT,
+        body: `AFTER-ACTION:
+- BELIEF: what we expected to move (metric + range + check date).
+- EVIDENCE: what the instruments actually showed (baseline \u2192 reading).
+- LEARNING: keep, kill, or re-sequence \u2014 write as a calibration when judgment changed.
+- NEXT BET: the single next exam, not a new multi-week program.`
+      },
+      {
+        id: "owner_shape",
+        catalog_line: "- owner-shape \u2014 function-shaped owner and decision rights; not named people",
+        internal_name: "RACI-lite",
+        always_on_catalog: true,
+        vital_links: [],
+        board_cut: "Every ask names who decides and who executes by function.",
+        operator_cut: "RevOps / AE lead / CS lead / Marketing ops \u2014 R does, A decides; avoid named individuals in plans.",
+        when_to_use: "Workstream titles, handoff plans, play prescriptions.",
+        kill_rules: ["No orphan actions without an accountable function.", "Do not invent headcount or reorgs."],
+        silent_brand_rule: SILENT,
+        body: `OWNER-SHAPE:
+- Name the function (RevOps, sales manager, CS lead, marketing ops) \u2014 not a person's name from the CRM.
+- Accountable decides; Responsible executes. Consulted optional; Inform via existing channels.
+- First action must be startable by that function within 48 hours with no new tooling.`
+      },
+      {
+        id: "okr_measurability",
+        catalog_line: "- exams \u2014 mid-term and final checks as dated key results with instruments",
+        internal_name: "OKR / measurability dialect",
+        always_on_catalog: true,
+        vital_links: ["freshness", "flow_rate", "drop_rate", "signal_to_noise", "thread_depth"],
+        board_cut: "Objective + dated key results the board can re-read next quarter.",
+        operator_cut: "Baseline, target range, check date, measured_by instrument \u2014 or demote to assumption.",
+        when_to_use: "Strategist outcomes, Heilmeier exams, milestones.",
+        kill_rules: ["No 'improve' without a number.", "No exam faster than sales-cycle physics."],
+        silent_brand_rule: SILENT,
+        body: `EXAMS (objective + key results):
+- Objective = precise end state in one line.
+- Key results = mid-term check + final exam: metric, baseline, target RANGE, check date, instrument.
+- If unmeasurable with current data, exclude from targets and record as an assumption.`
+      },
+      {
+        id: "heilmeier",
+        catalog_line: "- idea-gate \u2014 newness, stake, and exams must pass before a recommendation ships",
+        internal_name: "Heilmeier catechism",
+        always_on_catalog: true,
+        vital_links: [],
+        board_cut: "Only recommendations with stake and exams reach the room.",
+        operator_cut: "Kill restatements; demote unmeasurable ideas.",
+        when_to_use: "Deep recommend, think before draft_strategy, strategist Stage C.",
+        kill_rules: ["Fail newness, stake, or exams \u2192 do not recommend."],
+        silent_brand_rule: SILENT,
+        body: `IDEA GATE: end state, status quo + limit, newness, stake + cost of inaction, risks/payoffs, effort, time physics, mid+final exams. Kill on newness/stake/exams failure.`
+      },
+      {
+        id: "minto",
+        catalog_line: "- pyramid \u2014 headline, drivers, so-what for recall",
+        internal_name: "Minto Pyramid Principle",
+        always_on_catalog: true,
+        vital_links: [],
+        board_cut: "Repeatable headline + one number an hour later.",
+        operator_cut: "Same shape for findings and deep answers.",
+        when_to_use: "All packaged analyst prose.",
+        kill_rules: ["Methodology-first openers die."],
+        silent_brand_rule: SILENT,
+        body: `PYRAMID: HEADLINE FIRST \u2192 DRIVERS (non-overlapping) \u2192 SO-WHAT. Recall test. Altitude control.`
+      },
+      {
+        id: "gtm_engineering",
+        catalog_line: "- systems \u2014 data foundation \u2192 modeling \u2192 activation; mechanism per fix",
+        internal_name: "GTM engineering",
+        always_on_catalog: true,
+        vital_links: ["signal_to_noise", "drop_rate", "freshness"],
+        board_cut: "Durable systems, not heroics.",
+        operator_cut: "Pair every cleanup with a mechanism and an instrument.",
+        when_to_use: "When recommending action on tool-capable surfaces.",
+        kill_rules: ["Skipping the rung below will not hold."],
+        silent_brand_rule: SILENT,
+        body: `GTM SYSTEMS: three rungs (foundation \u2192 modeling \u2192 activation); signals over lists; CRM is cheapest pipeline; every fix gets a mechanism; instrument what you change.`
+      },
+      {
+        id: "meddpicc",
+        catalog_line: "- deal-qualification pack (optional) \u2014 use when threading or late-stage risk needs a qualification lens",
+        internal_name: "MEDDPICC",
+        always_on_catalog: false,
+        vital_links: ["thread_depth", "flow_rate"],
+        board_cut: "Late-stage risk is usually missing economic buyer or decision process \u2014 not more activity.",
+        operator_cut: "Map Metrics, Economic buyer, Decision criteria/process, Paper process, Identify pain, Champion, Competition \u2014 as observation, not CRM surgery.",
+        when_to_use: "Thread-depth or stuck late-stage deals when the user asks how to qualify.",
+        kill_rules: ["Do not rewrite the CRM; observe and recommend contacts/process gaps."],
+        silent_brand_rule: SILENT,
+        body: `DEAL QUALIFICATION LENS: use when single-threaded or stuck late-stage deals need a checklist. Prefer introducing a second contact and clarifying decision process over more outbound volume.`
+      },
+      {
+        id: "challenger",
+        catalog_line: "- teach-tailor-take pack (optional) \u2014 pressure-test weak narratives in think",
+        internal_name: "Challenger Sale",
+        always_on_catalog: false,
+        vital_links: ["signal_to_noise"],
+        board_cut: "Insight that reframes the problem beats more activity.",
+        operator_cut: "In think: teach with evidence, tailor to this pipeline, take control of next step \u2014 still stethoscope.",
+        when_to_use: "Think channel when the user is soft on a weak story.",
+        kill_rules: ["Do not turn into a pitch script or CRM sequence builder."],
+        silent_brand_rule: SILENT,
+        body: `TEACH-TAILOR-TAKE: reframe with verified numbers; tailor to segment/motion; land one owner-shaped next step.`
+      },
+      {
+        id: "jtbd",
+        catalog_line: "- job-of-the-metric pack (optional) \u2014 what job this number does for this board",
+        internal_name: "Jobs to be Done",
+        always_on_catalog: false,
+        vital_links: [],
+        board_cut: "Each metric has a job in a decision \u2014 name the job or drop the chart.",
+        operator_cut: "When explaining ARR/NRR/vitals: what decision does this number unlock?",
+        when_to_use: "Metric definitions / board deck framing.",
+        kill_rules: ["Ornamental metrics without a decision job die."],
+        silent_brand_rule: SILENT,
+        body: `JOB OF THE METRIC: for each number, name the decision it serves. If none, cut it from the board package.`
+      },
+      {
+        id: "porter",
+        catalog_line: "- industry-structure pack (optional, weak vital fit) \u2014 only if the user asks competitive structure",
+        internal_name: "Porter Five Forces",
+        always_on_catalog: false,
+        vital_links: [],
+        board_cut: "Industry structure is context, not a substitute for pipeline dollars.",
+        operator_cut: "Do not let industry essays displace vital-sign evidence.",
+        when_to_use: "Only when the user explicitly asks for competitive structure.",
+        kill_rules: ["Never use as a substitute for gating vital diagnosis."],
+        silent_brand_rule: SILENT,
+        body: `INDUSTRY STRUCTURE: optional context. Prefer vital signs and dollars for recommendations.`
+      },
+      {
+        id: "mckinsey_7s",
+        catalog_line: "- org-alignment pack (optional, weak vital fit) \u2014 only if the user asks org design",
+        internal_name: "McKinsey 7S",
+        always_on_catalog: false,
+        vital_links: [],
+        board_cut: "Org redesign is out of stethoscope scope.",
+        operator_cut: "Refuse surgery; observe handoff/ownership symptoms via vitals.",
+        when_to_use: "Only if asked; redirect to owner-shape + bottleneck.",
+        kill_rules: ["No reorg prescriptions."],
+        silent_brand_rule: SILENT,
+        body: `ORG ALIGNMENT: out of scope for CRM surgery. Point to function-shaped owners and the constraint vital instead.`
+      },
+      {
+        id: "ooda",
+        catalog_line: "- observe-orient loop pack (optional) \u2014 overlaps gating; use sparingly",
+        internal_name: "OODA",
+        always_on_catalog: false,
+        vital_links: [],
+        board_cut: "Prefer layer gating and hypothesis-first grounding.",
+        operator_cut: "Already covered by Stage A + bottleneck \u2014 do not duplicate jargon.",
+        when_to_use: "Rarely; prefer existing grounding.",
+        kill_rules: ["Do not invent a parallel loop vocabulary for the user."],
+        silent_brand_rule: SILENT,
+        body: `OBSERVE-ORIENT: prefer NTRP layer gating and Stage A hypothesis-first over a separate combat loop.`
+      }
+    ];
+  }
+});
+
 // src/baselines/metrics-benchmarks.ts
 function resolveMetricBenchmarks(motion) {
   return METRICS_BENCHMARKS[motion ?? "mid_market"];
@@ -17012,10 +17292,10 @@ function wrapForTarget(target, analysisBlock, conversationBlock, openQuestions,
   const contextLabel = handoffInstructionPrefix(ctx.analysis.primary);
   const forWhom = audiencePhrase(ctx.scope?.audience);
   const instructions = {
-    deck: `produce an executive review deck outline for ${company}, framed for ${forWhom}. Pyramid structure: (1) HEADLINE \u2014 the governing number and verdict in one line; (2) DRIVERS \u2014 2\u20133 distinct, non-overlapping risks or causes with dollar impact (not a full scorecard); (3) SO-WHAT \u2014 recommended plays; (4) ASKS / decisions the room must make. Optionally one pipeline-health slide after the headline if it supports the call. Use the Metric definitions appendix so every slide can briefly remind the room what the number means for this audience.`,
-    asana: `produce an Asana project plan with sections and tasks tied to findings for ${forWhom}. Prioritize by dollar impact. Reference metric definitions when a task owner needs to know what "good" looks like.`,
+    deck: `produce an executive review deck outline for ${company}, framed for ${forWhom}. Pyramid structure: (1) HEADLINE \u2014 the governing number and verdict in one line; (2) DRIVERS \u2014 2\u20133 distinct, non-overlapping risks or causes with dollar impact (not a full scorecard); (3) SO-WHAT \u2014 recommended plays with function-shaped owners (RevOps / sales manager / CS \u2014 not personal names); (4) ASKS / decisions the room must make. Optionally one pipeline-health slide after the headline if it supports the call. Use the Metric definitions appendix so every slide can briefly remind the room what the number means for this audience.`,
+    asana: `produce an Asana project plan with sections and tasks tied to findings for ${forWhom}. Prioritize by dollar impact. Assign by function (not personal names). Reference metric definitions when a task owner needs to know what "good" looks like.`,
     clay: `produce a Clay table specification to operationalize the highest-impact finding for ${forWhom}.`,
-    plan: `produce a prioritized action plan for ${forWhom}, answer-first: open with the governing call (highest-dollar problem), then items each with problem, play, first 3 steps, owner, and leading indicator. Ground indicators in the Metric definitions appendix. End with the sharpest asks / decisions.`
+    plan: `produce a prioritized action plan for ${forWhom}, answer-first: open with the governing call (highest-dollar problem / constraint), then items each with problem, play, first 3 steps, function-shaped owner, and leading indicator. Ground indicators in the Metric definitions appendix. End with the sharpest asks / decisions.`
   };
   const parts = [
     `# NTRP handoff \u2192 ${target}`,
@@ -17410,13 +17690,16 @@ ${companyContextSection2()}${operatorSection2()}HOW YOU THINK (the strategist me
 8. RESPECT CAPACITY. Total effort must fit the team that actually exists. A brilliant plan the team cannot staff is a bad plan.
 
 ALTITUDE CONTRACT (the plan must work at every altitude a client reads it at):
-- 30,000 FT: summary_30k is answer-first \u2014 open with the governing thought and what leadership should expect by when, then the situation and complication that make it true. A board member reads only this; it must survive being forwarded unedited.
-- 10,000 FT: each workstream's title + problem line is a delegation unit \u2014 a one-liner an owner could receive in Slack and know what they own, why it's theirs, and what number they move.
+- 30,000 FT: summary_30k is answer-first \u2014 open with the governing thought (the answer) and what leadership should expect by when, then the situation and complication that make it true as support. A board member reads only this; it must survive being forwarded unedited.
+- 10,000 FT: each workstream's title + problem line is a delegation unit \u2014 a one-liner an owner could receive in Slack and know what they own, why it's theirs, and what number they move. Use function-shaped owners (see OWNER SHAPE).
 - GROUND LEVEL: actions are Monday-morning prescriptive. You have built this before \u2014 read the linked play's full detail with get_play_detail and prescribe its known-good sequence adapted to THIS company's numbers and constraints. The first action of every workstream must be startable within 48 hours with no new tooling.
 
 OUTPUT DOCTRINE (narrative fields \u2014 summary_30k and workstream problem lines \u2014 follow pyramid recall):
 ${PYRAMID_OUTPUT_BLOCK}
 
+OWNER SHAPE (workstreams and actions \u2014 silent):
+${OWNER_SHAPE_BLOCK}
+
 ${buildUserVisibleProseBlock()}
 
 GTM ENGINEERING (plans install systems, not heroics):
@@ -17431,7 +17714,10 @@ ${METRICS_BLOCK}
 PLAYBOOK (every workstream must link to at least one play by exact id):
 ${buildPlaybookBlock()}
 
+${buildFrameworkCatalogBlock()}
+
 MEASURABILITY CONTRACT (non-negotiable \u2014 this is what separates you from a slide deck):
+- Treat the objective as the end state; treat expected outcomes and leading indicators as key results (mid-term and final exams).
 - Every expected outcome and leading indicator needs: a metric, the current baseline copied from your verified grounding work, a target RANGE, a check date, and the named instrument that will measure it.
 - Banned words for outcomes: "improve", "better", "significantly", "optimize", "increase" without a number. If you cannot quantify it, it is not an outcome \u2014 demote it to an assumption or replace it with its best measurable proxy.
 - Every workstream needs at least one dated milestone with a verification method that names a number and threshold.
@@ -17450,9 +17736,13 @@ function buildGroundingMessage(input) {
 
 Establish verified reality before any planning. Work hypothesis-first, like an engagement manager on day one: form your top candidate explanations for what stands between today and the objective, then use tools to confirm or kill each one \u2014 don't boil the ocean.
 1. Current state: which vital signs / metrics are worst, what are the exact scores and dollar values, which segments concentrate the problem?
-2. What is already in flight (active strategies below, if any), what has worked before (wins), and what the local play track record says.
-3. What are the binding constraints: data gaps that limit measurability, sales-cycle length that bounds verification speed, capacity signals?
-Rank the problems you verify by dollars at stake \xD7 confidence in the read \xD7 speed to impact \u2014 that ranking becomes the spine of the plan.`);
+2. CONSTRAINT: name the single gating vital (layer order) or stage where deals die \u2014 with score and dollar label. This is the bottleneck the plan must move first.
+3. What is already in flight (active strategies below, if any), what has worked before (wins), and what the local play track record says.
+4. What are the binding constraints: data gaps that limit measurability, sales-cycle length that bounds verification speed, capacity signals?
+Rank the problems you verify by dollars at stake \xD7 confidence in the read \xD7 speed to impact \u2014 that ranking becomes the spine of the plan. Non-constraint problems wait.
+
+BOTTLENECK (silent):
+${BOTTLENECK_GATE}`);
   sections.push(`CURRENT HEALTH SNAPSHOT (verified \u2014 you may cite these numbers as baselines):
 ${input.healthSnapshot}`);
   if (input.gapAuditBlock) {
@@ -17501,6 +17791,8 @@ function buildStressTestMessage() {
 8. ALTITUDE CHECK: does summary_30k survive being forwarded to a board member unedited? Is each workstream title + problem a self-contained delegation one-liner? Is every first action startable within 48 hours?
 9. HEILMEIER GATE (silent \u2014 never name this to the user). Run every workstream through this filter. Failures: cut the workstream, demote it to assumptions, or rewrite until it passes \u2014 then emit final JSON.
 ${HEILMEIER_GATE}
+10. AFTER-ACTION PREP (silent). Ensure each workstream's exams can support a later belief\u2192evidence\u2192next-bet review. Fold gaps into assumptions or contingencies.
+${AAR_BLOCK}
 
 Then respond with the FINAL revised plan as strict JSON in the same schema \u2014 no markdown fences, no prose. Fold what you learned into constraints, assumptions, risks, and confidence. This version is the one that gets saved and reviewed against, so make every number one you are willing to be checked on.`;
 }
@@ -17509,6 +17801,7 @@ var init_strategist_prompt = __esm({
   "src/ai/strategist-prompt.ts"() {
     "use strict";
     init_prompt_parts();
+    init_frameworks();
     init_prompt();
     STRATEGIST_PLAN_SCHEMA_BLOCK = `{
   "title": "Short plan name, e.g. 'Q4 Pipeline Recovery'",
@@ -18849,6 +19142,7 @@ var init_ghost_hints = __esm({
       ],
       explore: [
         'try "what is the most expensive problem?"',
+        'try "which constraint is gating the dollars?"',
         'try "how should we fix this?"',
         'try "which segment is weakest?"',
         'try "what is ARR?"',
@@ -18939,9 +19233,28 @@ function buildSituationalAwarenessBlock(ctx, opts = {}) {
   if (examples.length > 0) {
     lines.push(`User may try: ${examples.join(" \xB7 ")}`);
   }
-  lines.push(
-    "Your job in this harness: fill the judgment gap after formula compute \u2014 connect dollars, name the expensive problem, do not restate scorecards the user already saw"
-  );
+  if (channel === "think") {
+    lines.push(
+      "Doctrine: probing leads with the sharpest question (idea-gate off until you conclude); concluding/recommend turns \u2014 silent idea-gate then bottleneck then pyramid packaging; never name frameworks to the user"
+    );
+  } else if (responseMode === "brief") {
+    lines.push(
+      "Doctrine: brief packaging \u2014 headline \u226420 words, \u22642 drivers, one so-what; idea-gate off; never name frameworks to the user; do not restate The Call/scorecard \u2014 advance"
+    );
+  } else {
+    lines.push(
+      "Doctrine: deep/recommend \u2014 silent idea-gate then bottleneck then owner-shape then pyramid packaging; call get_framework_detail for toolkit depth; never name frameworks to the user"
+    );
+  }
+  if (analysisReady) {
+    lines.push(
+      "Your job in this harness: after formula compute, lead with the most expensive or actionable implication \u2014 connect dollars, name the constraint, do not restate scorecards or The Call the user already saw"
+    );
+  } else {
+    lines.push(
+      "Your job in this harness: help the user through the funnel; CLI owns pre-explore gates"
+    );
+  }
   lines.push(
     "Pre-explore funnel gates are handled by the CLI; you speak in explore/think/strategist unless tools explicitly allow a restart"
   );
@@ -18954,10 +19267,12 @@ function buildSituationalRuntimeFacts(ctx, opts = {}) {
   return {
     phase,
     mode: responseMode,
+    channel,
     lens: ctx.scope?.primary_lens,
     stage: ctx.stage,
     can_compute: ctx.gapAudit?.can_compute === void 0 ? void 0 : String(ctx.gapAudit.can_compute),
-    engine: canUseReplAi(ctx) ? "connected" : "none"
+    engine: canUseReplAi(ctx) ? "connected" : "none",
+    idea_gate: channel === "think" || responseMode === "deep" ? "on" : "off"
   };
 }
 function getConversationPhaseBlock(ctx, opts = {}) {
@@ -25280,6 +25595,7 @@ async function handleGetPlayDetail(input) {
     }
   } catch {
   }
+  const { frameworkIdsForPlay: frameworkIdsForPlay2 } = await Promise.resolve().then(() => (init_frameworks(), frameworks_exports));
   const detail = {
     play_id: play.id,
     play_name: play.name,
@@ -25291,7 +25607,8 @@ async function handleGetPlayDetail(input) {
     tools_that_help: play.tools_that_help,
     expected_outcome: play.expected_outcome,
     source: play.source ?? "seed",
-    local_track_record: trackRecord
+    local_track_record: trackRecord,
+    framework_ids: frameworkIdsForPlay2(play.id)
   };
   if (play.source === "learned") {
     detail.security_notice = UNTRUSTED_CONTENT_NOTICE;
@@ -25302,6 +25619,30 @@ async function handleGetPlayDetail(input) {
   }
   return detail;
 }
+async function handleGetFrameworkDetail(input) {
+  const frameworkId = typeof input.framework_id === "string" ? input.framework_id.trim() : "";
+  const { getFrameworkById: getFrameworkById2, listFrameworkIds: listFrameworkIds2 } = await Promise.resolve().then(() => (init_frameworks(), frameworks_exports));
+  const pack = frameworkId ? getFrameworkById2(frameworkId) : void 0;
+  if (!pack) {
+    return {
+      error: `Unknown framework id '${frameworkId}'.`,
+      valid_framework_ids: listFrameworkIds2()
+    };
+  }
+  return {
+    framework_id: pack.id,
+    catalog_line: pack.catalog_line,
+    always_on_catalog: pack.always_on_catalog,
+    vital_links: pack.vital_links,
+    board_cut: pack.board_cut,
+    operator_cut: pack.operator_cut,
+    when_to_use: pack.when_to_use,
+    kill_rules: pack.kill_rules,
+    silent_brand_rule: pack.silent_brand_rule,
+    body: pack.body,
+    notice: "Apply the moves in body/board_cut/operator_cut. Never name internal brand labels to the user."
+  };
+}
 async function handleGetRevenueMetrics(_input, ctx) {
   if (!ctx.metrics || ctx.metrics.length === 0) {
     const { computeFullMetrics: computeFullMetrics2 } = await Promise.resolve().then(() => (init_compute(), compute_exports));
@@ -25596,6 +25937,7 @@ var init_tool_handlers = __esm({
       query_segment_comparison: handleQuerySegmentComparison,
       query_entity_counts: (input, _) => handleQueryEntityCounts(input),
       get_play_detail: (input, _) => handleGetPlayDetail(input),
+      get_framework_detail: (input, _) => handleGetFrameworkDetail(input),
       get_session_brief: (input, _) => handleGetSessionBrief(input),
       get_revenue_metrics: handleGetRevenueMetrics,
       get_revenue_metrics_timeseries: (input, _) => handleGetRevenueMetricsTimeseries(input),
@@ -25733,6 +26075,12 @@ ${GTM_ENGINEERING_BLOCK}
 IDEA GATE (when recommending a play or before draft_strategy \u2014 silent; probing/imagination turns skip this until you conclude):
 ${HEILMEIER_GATE}
 
+BOTTLENECK (when concluding or recommending \u2014 silent):
+${BOTTLENECK_GATE}
+
+OWNER SHAPE (when recommending \u2014 silent):
+${OWNER_SHAPE_BLOCK}
+
 OUTPUT DOCTRINE (how answers are structured for recall):
 ${PYRAMID_OUTPUT_BLOCK}
 
@@ -25747,6 +26095,8 @@ ${VITAL_SIGNS_BLOCK}
 PLAYBOOK \u2014 name a play when it helps the user act (not a full program):
 ${buildPlaybookBlock()}
 
+${buildFrameworkCatalogBlock()}
+
 ${commandSection}
 ${formattingSection}
 OUTPUT RULES:
@@ -25775,6 +26125,7 @@ var init_think_prompt = __esm({
   "src/ai/think-prompt.ts"() {
     "use strict";
     init_prompt_parts();
+    init_frameworks();
     init_prompt();
   }
 });
@@ -25969,7 +26320,7 @@ ${commandStyleRule}`;
 - Respond in plain text (not JSON). You do NOT need to emit the findings schema \u2014 only emit structured findings if the user explicitly asks for them.
 - Include specific numbers from tool results, never guess.
 - When you have enough information, answer directly. Don't call tools you don't need.`;
-  const executionBiasSection = responseMode === "brief" ? `OUTPUT DOCTRINE (brief \u2014 one headline + \u22642 drivers + one so-what):
+  const executionBiasSection = responseMode === "brief" ? `OUTPUT DOCTRINE (brief \u2014 one headline + \u22642 drivers + one so-what; situation/complication only as support after the headline):
 ${PYRAMID_OUTPUT_BLOCK}
 
 ` : `EXECUTION BIAS (how you work):
@@ -25981,6 +26332,12 @@ ${GTM_ENGINEERING_BLOCK}
 IDEA GATE (when recommending action \u2014 silent):
 ${HEILMEIER_GATE}
 
+BOTTLENECK (constraint first \u2014 silent):
+${BOTTLENECK_GATE}
+
+OWNER SHAPE (when recommending action \u2014 silent):
+${OWNER_SHAPE_BLOCK}
+
 OUTPUT DOCTRINE (how answers are structured for recall):
 ${PYRAMID_OUTPUT_BLOCK}
 
@@ -25996,6 +26353,8 @@ ${VITAL_SIGNS_BLOCK}
 PLAYBOOK \u2014 recommend these plays when appropriate:
 ${buildPlaybookBlock()}
 
+${buildFrameworkCatalogBlock()}
+
 ${commandSection}`;
   const stable = `You are a world-class GTM operating partner \u2014 the kind of analyst a CEO keeps on speed dial. You are exceptionally well-read, rigorous, and commercially sharp, and you have tools to query a local database of this company's CRM and pipeline data. The user is having an ongoing, free-form conversation with you about their go-to-market health and SaaS metrics.
 
@@ -26244,6 +26603,7 @@ var init_agentic_loop = __esm({
     init_thread();
     init_untrusted();
     init_prompt_parts();
+    init_frameworks();
     init_think_prompt();
     init_prompt();
     init_context2();

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@sonnechasser/ntrp",
-  "version": "1.4.7",
+  "version": "1.4.8",
   "description": "GTM Health Diagnostic CLI — local pipeline analysis tool",
   "homepage": "https://ntrp.sonnechasser.com",
   "repository": {