@sonnechasser/ntrp 2.2.1 → 2.2.2

package/dist/index.js

@@ -18345,21 +18345,21 @@ var init_metric_definitions = __esm({
         kind: "vital",
         label: "Freshness",
         group: "Vital Signs",
-        tagline: "Is the CRM still talking about live work \u2014 or a museum of old deals?",
-        how_computed: "NTRP computes a weighted average of people, organizations, and opportunities with recent activity. Open opportunities must also not be past-due. Default windows: people and organizations 90 days, opportunities 30 days. Weights are 35 / 30 / 35.",
+        tagline: "Is the CRM talking about live deals \u2014 or a museum of old ones?",
+        how_computed: "We look at how recently people, companies, and deals got a touch. Deals need a fresher pulse than people or companies, and past-due deals count as stale. The formula lines on this card show the exact mix and windows.",
         formula_lines: [
           "freshness = people%\xD70.35 + orgs%\xD70.30 + opps%\xD70.35",
           "people/orgs fresh if activity within 90d",
           "opps fresh if activity within 30d AND not past-due"
         ],
-        meaning: 'We treat Freshness as a truth check on the pipeline number. Quiet days mean different things by motion: in enterprise, 30 quiet days can be normal cadence; in a velocity book, that same silence often means the deal is already dead. Stale open amount is why we show "pipeline at risk."',
-        expert_read: `A useful first cut is by owner and by stage \u2014 reds tend to clump on people or process, not sprinkle evenly. A sudden cliff is usually a broken integration or a departed rep, not gradual decay. Watch for the false positive too: bulk-imported records nobody has touched yet can look "stale" when they're just new.`,
+        meaning: `Freshness asks whether the pipeline number is still true. Quiet deals pad the forecast. Like milk dates on a shelf \u2014 past the date, don't trust the carton. Stale open dollars show as "pipeline at risk."`,
+        expert_read: "Cut by owner and stage first \u2014 reds usually clump, they don't sprinkle. A sudden cliff is often a broken sync or a departed rep, not slow decay. New bulk imports can look stale when they're just new.",
         deepdive: [
-          "Status bands: green 80 or more, yellow 60 or more, red below 60. Motion presets can change the windows.",
-          'Dollar translation: sum of amount on stale open opportunities \u2192 "pipeline at risk".',
-          "Layer 1 of the gating stack. A red score here limits trust in later layers.",
-          "Trigger play: Clean Dead Pipeline (clean-dead-pipeline) when the score is below 60.",
-          "Levers: stale-deal alert at N quiet days. Weekly hygiene scrub. Enrichment refresh on quiet records. Signal-triggered reactivation for paid dormant accounts."
+          "Green 80+, yellow 60+, red below 60. Motion presets can change the windows.",
+          'Dollars: sum of amount on stale open deals \u2192 "pipeline at risk".',
+          "Read this first. If Freshness is red, later vitals are harder to trust.",
+          "Weak score \u2192 play Clean Dead Pipeline.",
+          "Useful moves: stale-deal alert, weekly hygiene scrub, enrichment on quiet records."
         ],
         visual: {
           kind: "bars",
@@ -18383,21 +18383,21 @@ var init_metric_definitions = __esm({
         kind: "vital",
         label: "Flow Rate",
         group: "Vital Signs",
-        tagline: "Where does deal motion slow \u2014 and what's stuck behind that bottleneck?",
-        how_computed: "NTRP sets a base score from average open-deal age versus max_days. It then applies a penalty of up to 20 for the share of stuck deals. A deal is stuck when it has no update beyond stuck_days, or a past-due close. Status uses average open age, not the score alone.",
+        tagline: "Where do deals stop moving \u2014 and what's piled up behind that stage?",
+        how_computed: "We start from how old open deals are versus a max window, then shave points for the share that look stuck. A deal is stuck when it goes quiet too long or its close date is already past. The formula lines show the base, the penalty, and the stuck rules.",
         formula_lines: [
           "base = 100 \xD7 (1 \u2212 avgOpenAge / max_days)",
           "score = base \u2212 stuckSharePenalty (\u226420)",
           "stuck = no update > stuck_days OR past-due close"
         ],
-        meaning: 'We think of Flow Rate as velocity risk with a dollar tag. When deals stop advancing \u2014 and especially when close dates slip past due \u2014 next quarter starts to feel optimistic on paper. The dollar line is the amount still "stuck in pipeline."',
-        expert_read: "We prefer stage age over deal age alone: find the stage where advancement collapses \u2014 it's usually one stage, not everywhere. Compare stuck age to this company's own median cycle rather than a generic norm. Stuck deals plus past-due closes are often a forecast-credibility problem before they're a revenue miss.",
+        meaning: 'Flow Rate asks whether deals are still advancing or sitting still. Stuck deals pad next quarter on paper. Like traffic behind a closed lane \u2014 the jam is one stage, not the whole highway. Dollars on stuck deals show as "stuck in pipeline."',
+        expert_read: "Find the stage where advancement collapses first \u2014 it's usually one stage, not everywhere. Compare stuck age to this company's own median cycle rather than a generic norm. Stuck deals plus past-due closes are often a forecast-credibility problem before they're a revenue miss.",
         deepdive: [
-          "Status uses average open age. Green is 45 days or less. Yellow is 90 days or less. Else red. Defaults: max_days 120, stuck_days 60.",
-          'Dollar translation: sum of amount on stuck deals \u2192 "stuck in pipeline".',
-          "Layer 2 of the gating stack, with Drop Rate.",
-          "Trigger play: Unstick the Pipeline (unstick-pipeline) when the score is weak.",
-          "Levers: stage-age report. Past-due close cleanup. Progression plans on stuck deals. Forecast hygiene on optimistic close dates."
+          "Status uses average open age. Green \u226445 days, yellow \u226490, else red. Defaults: max_days 120, stuck_days 60.",
+          'Dollars: sum of amount on stuck deals \u2192 "stuck in pipeline".',
+          "Read with Drop Rate \u2014 stuck deals and handoff leaks often show up together.",
+          "Weak score \u2192 play Unstick the Pipeline.",
+          "Useful moves: stage-age report, past-due close cleanup, progression plans on stuck deals, forecast hygiene on optimistic close dates."
         ],
         visual: {
           kind: "funnel",
@@ -18423,21 +18423,21 @@ var init_metric_definitions = __esm({
         kind: "vital",
         label: "Drop Rate",
         group: "Vital Signs",
-        tagline: "Where does paid demand fall between systems before anyone works it?",
-        how_computed: "NTRP blends cross-system retention and opportunity retention. Cross-system retention is marketing people also present in sales. Opportunity retention is open opportunities that are not abandoned. Default weights: cross-system 60 percent, opportunity retention 40 percent. Abandoned means open opportunities with no activity in 30 days.",
+        tagline: "Where does paid demand fall between systems before a rep works it?",
+        how_computed: "We blend two checks: do marketing people also show up in sales CRM, and are open deals still being worked (not abandoned). The formula lines show the weights and the 30-day abandon window.",
         formula_lines: [
           "score = crossSystemRetention\xD70.6 + oppRetention\xD70.4",
           "cross-system = marketing people also in sales CRM",
           "abandoned = open opps with no activity in 30d"
         ],
-        meaning: 'We read Drop Rate as the price of the handoff leak \u2014 budget already spent on leads that never reach a working rep. The dollar estimate is droppedCount \xD7 conversion \xD7 avg deal size: "est. lost at handoff."',
-        expert_read: 'In practice this usually looks like a systems story: routing rules, unassigned territories, dead rep queues, or a sync gap between marketing and CRM \u2014 more often than "lazy reps." A useful first cut is by lead source; the leak tends to concentrate in one or two sources. The cheapest pipeline a business can buy is often the leads it already paid for.',
+        meaning: 'Drop Rate prices the handoff leak \u2014 money you already spent on leads that never reach a working rep. Like buying groceries and leaving half the bags in the parking lot. The dollar line is "est. lost at handoff."',
+        expert_read: "A useful first cut is by lead source \u2014 the leak usually concentrates in one or two, not everywhere. Routing rules, unassigned territories, dead queues, or a sync gap between marketing and CRM show up more often than lazy reps. The cheapest pipeline you can buy is often the leads you already paid for.",
         deepdive: [
-          "Status bands: green 80 or more, yellow 60 or more, red below 60.",
-          'Dollar translation: dropped \xD7 conversion \xD7 avg deal (fallback: drop% \xD7 open pipeline) \u2192 "est. lost at handoff".',
-          "Layer 2 of the gating stack, with Flow Rate.",
-          "Trigger play: Fix the Handoff Gap (fix-handoff-gap) when drop is high.",
-          "Levers: source-level handoff audit. Routing and sync repair. Time-to-first-touch SLA. Weekly marketing-only-leads report."
+          "Green 80+, yellow 60+, red below 60.",
+          'Dollars: dropped \xD7 conversion \xD7 avg deal (fallback: drop% \xD7 open pipeline) \u2192 "est. lost at handoff".',
+          "Read with Flow Rate \u2014 handoff leaks and stuck deals often show up together.",
+          "Weak score \u2192 play Fix the Handoff Gap.",
+          "Useful moves: source-level handoff audit, routing and sync repair, time-to-first-touch SLA, weekly marketing-only-leads report."
         ],
         visual: {
           kind: "funnel",
@@ -18462,21 +18462,21 @@ var init_metric_definitions = __esm({
         kind: "vital",
         label: "Signal:Noise",
         group: "Vital Signs",
-        tagline: "How much of the team's effort still aims at deals that can close?",
-        how_computed: "Over a 90-day lookback, NTRP computes (signal activities / all activities) \xD7 100. Signal is activity linked to an open opportunity, a pipeline person, or a pipeline organization.",
+        tagline: "How much effort still aims at accounts that can close \u2014 versus dead ends?",
+        how_computed: "We look at the last 90 days of activity and ask what share is signal \u2014 linked to an open deal, a pipeline person, or a pipeline company. The formula lines show the ratio and what counts as signal.",
         formula_lines: [
           "score = (signalCount / activityCount) \xD7 100",
           "signal = linked to open opp / pipeline person / pipeline org",
           "lookback = trailing 90 days"
         ],
-        meaning: `We treat Signal:Noise as activity efficiency with a capacity price. Noise hours \xD7 hours_per_activity \xD7 rep_hourly_cost becomes "misdirected effort" \u2014 energy aimed at accounts that can't still close.`,
+        meaning: 'Signal:Noise asks whether activity still points at deals that can close. Noise hours are capacity spent on dead ends. Like a radio stuck between stations \u2014 lots of static, little signal. Those hours show as "misdirected effort."',
         expert_read: "A useful cut is by rep and by account status. Persistent noise often means reps keep working dead accounts they already know \u2014 stale targeting or coverage models more than a coaching gap. Also check whether activity is logged against closed or unlinked records; that can be a hygiene artifact pretending to be effort.",
         deepdive: [
-          "Status bands: green 65 or more, yellow 40 or more, red below 40.",
-          "Dollar defaults: 0.25 hours/activity \xD7 $75/hr (config: hours_per_activity, rep_hourly_cost).",
-          "Layer 3 of the gating stack. Trust Freshness, Flow Rate, and Drop Rate before you read activity efficiency.",
-          "Trigger play: Retarget Misdirected Effort (retarget-effort) when the score is low.",
-          "Levers: refresh account lists. Signal-based targeting. Stop logging against closed or unlinked records. Coverage-model redesign."
+          "Green 65+, yellow 40+, red below 40.",
+          'Dollar defaults: 0.25 hours/activity \xD7 $75/hr (config: hours_per_activity, rep_hourly_cost) \u2192 "misdirected effort".',
+          "Read Freshness, Flow Rate, and Drop Rate before you trust this score.",
+          "Weak score \u2192 play Retarget Misdirected Effort.",
+          "Useful moves: refresh account lists, signal-based targeting, stop logging against closed or unlinked records, coverage-model redesign."
         ],
         visual: {
           kind: "split",
@@ -18499,21 +18499,21 @@ var init_metric_definitions = __esm({
         kind: "vital",
         label: "Thread Depth",
         group: "Vital Signs",
-        tagline: "How fragile is revenue if one champion changes jobs?",
-        how_computed: "Percent of open deals with at least multi_thread_threshold distinct people active in the last 90 days. The default threshold is 2. People include opportunity-direct contacts and same-organization activity.",
+        tagline: "How fragile is a deal if one champion changes jobs?",
+        how_computed: "We ask what share of open deals have at least two people active in the last 90 days. Contacts on the deal and activity at the same company both count. The formula lines show the threshold.",
         formula_lines: [
           "score = % open deals with \u22652 active people (90d)",
           "people counted via opp contacts + same-org activity",
           "threshold configurable (default 2)"
         ],
-        meaning: "We read Thread Depth as resilience risk. One single-threaded mega-deal can outweigh ten small ones \u2014 and late-cycle single-threading is especially scary because champions change jobs. The dollar line sums amount on single-threaded deals.",
-        expert_read: "Weight by deal size when you triage. Single-threading late in the cycle tends to matter more than early. In enterprise motions, thin threads are often a leading indicator of slipped quarters: the champion leaves and there's no second contact warm enough to carry the deal.",
+        meaning: 'Thread Depth asks how many people keep each deal warm. One contact is a single point of failure \u2014 if they leave, the deal often dies with them. Like a bridge with one cable. Dollars on thin deals show as "single-threaded."',
+        expert_read: "Weight by deal size when you triage \u2014 one thin mega-deal can outweigh ten small ones. Late-cycle single-threading tends to matter more than early. In enterprise motions, thin threads often lead to slipped quarters: the champion leaves and nobody else is warm enough to carry the deal.",
         deepdive: [
-          "Status bands: green 65 or more, yellow 40 or more, red below 40.",
-          'Dollar translation: sum of amount on single-threaded deals \u2192 "single-threaded".',
-          "Layer 4 of the gating stack. Read this last, after the upstream vital signs.",
-          "Trigger play: Multi-Thread Your Deals (multi-thread-deals) when depth is low.",
-          "Levers: buying-committee map. Warm internal referral first. CRM contact roles. Mid-stage single-thread alerts. Champion job-change signals."
+          "Green 65+, yellow 40+, red below 40.",
+          'Dollars: sum of amount on single-threaded deals \u2192 "single-threaded".',
+          "Read this last, after Freshness, Flow Rate, Drop Rate, and Signal:Noise.",
+          "Weak score \u2192 play Multi-Thread Your Deals.",
+          "Useful moves: buying-committee map, warm internal referral first, CRM contact roles, mid-stage single-thread alerts, champion job-change signals."
         ],
         visual: {
           kind: "bars",

package/dist/mcp/server.js

@@ -12989,21 +12989,21 @@ var init_metric_definitions = __esm({
         kind: "vital",
         label: "Freshness",
         group: "Vital Signs",
-        tagline: "Is the CRM still talking about live work \u2014 or a museum of old deals?",
-        how_computed: "NTRP computes a weighted average of people, organizations, and opportunities with recent activity. Open opportunities must also not be past-due. Default windows: people and organizations 90 days, opportunities 30 days. Weights are 35 / 30 / 35.",
+        tagline: "Is the CRM talking about live deals \u2014 or a museum of old ones?",
+        how_computed: "We look at how recently people, companies, and deals got a touch. Deals need a fresher pulse than people or companies, and past-due deals count as stale. The formula lines on this card show the exact mix and windows.",
         formula_lines: [
           "freshness = people%\xD70.35 + orgs%\xD70.30 + opps%\xD70.35",
           "people/orgs fresh if activity within 90d",
           "opps fresh if activity within 30d AND not past-due"
         ],
-        meaning: 'We treat Freshness as a truth check on the pipeline number. Quiet days mean different things by motion: in enterprise, 30 quiet days can be normal cadence; in a velocity book, that same silence often means the deal is already dead. Stale open amount is why we show "pipeline at risk."',
-        expert_read: `A useful first cut is by owner and by stage \u2014 reds tend to clump on people or process, not sprinkle evenly. A sudden cliff is usually a broken integration or a departed rep, not gradual decay. Watch for the false positive too: bulk-imported records nobody has touched yet can look "stale" when they're just new.`,
+        meaning: `Freshness asks whether the pipeline number is still true. Quiet deals pad the forecast. Like milk dates on a shelf \u2014 past the date, don't trust the carton. Stale open dollars show as "pipeline at risk."`,
+        expert_read: "Cut by owner and stage first \u2014 reds usually clump, they don't sprinkle. A sudden cliff is often a broken sync or a departed rep, not slow decay. New bulk imports can look stale when they're just new.",
         deepdive: [
-          "Status bands: green 80 or more, yellow 60 or more, red below 60. Motion presets can change the windows.",
-          'Dollar translation: sum of amount on stale open opportunities \u2192 "pipeline at risk".',
-          "Layer 1 of the gating stack. A red score here limits trust in later layers.",
-          "Trigger play: Clean Dead Pipeline (clean-dead-pipeline) when the score is below 60.",
-          "Levers: stale-deal alert at N quiet days. Weekly hygiene scrub. Enrichment refresh on quiet records. Signal-triggered reactivation for paid dormant accounts."
+          "Green 80+, yellow 60+, red below 60. Motion presets can change the windows.",
+          'Dollars: sum of amount on stale open deals \u2192 "pipeline at risk".',
+          "Read this first. If Freshness is red, later vitals are harder to trust.",
+          "Weak score \u2192 play Clean Dead Pipeline.",
+          "Useful moves: stale-deal alert, weekly hygiene scrub, enrichment on quiet records."
         ],
         visual: {
           kind: "bars",
@@ -13027,21 +13027,21 @@ var init_metric_definitions = __esm({
         kind: "vital",
         label: "Flow Rate",
         group: "Vital Signs",
-        tagline: "Where does deal motion slow \u2014 and what's stuck behind that bottleneck?",
-        how_computed: "NTRP sets a base score from average open-deal age versus max_days. It then applies a penalty of up to 20 for the share of stuck deals. A deal is stuck when it has no update beyond stuck_days, or a past-due close. Status uses average open age, not the score alone.",
+        tagline: "Where do deals stop moving \u2014 and what's piled up behind that stage?",
+        how_computed: "We start from how old open deals are versus a max window, then shave points for the share that look stuck. A deal is stuck when it goes quiet too long or its close date is already past. The formula lines show the base, the penalty, and the stuck rules.",
         formula_lines: [
           "base = 100 \xD7 (1 \u2212 avgOpenAge / max_days)",
           "score = base \u2212 stuckSharePenalty (\u226420)",
           "stuck = no update > stuck_days OR past-due close"
         ],
-        meaning: 'We think of Flow Rate as velocity risk with a dollar tag. When deals stop advancing \u2014 and especially when close dates slip past due \u2014 next quarter starts to feel optimistic on paper. The dollar line is the amount still "stuck in pipeline."',
-        expert_read: "We prefer stage age over deal age alone: find the stage where advancement collapses \u2014 it's usually one stage, not everywhere. Compare stuck age to this company's own median cycle rather than a generic norm. Stuck deals plus past-due closes are often a forecast-credibility problem before they're a revenue miss.",
+        meaning: 'Flow Rate asks whether deals are still advancing or sitting still. Stuck deals pad next quarter on paper. Like traffic behind a closed lane \u2014 the jam is one stage, not the whole highway. Dollars on stuck deals show as "stuck in pipeline."',
+        expert_read: "Find the stage where advancement collapses first \u2014 it's usually one stage, not everywhere. Compare stuck age to this company's own median cycle rather than a generic norm. Stuck deals plus past-due closes are often a forecast-credibility problem before they're a revenue miss.",
         deepdive: [
-          "Status uses average open age. Green is 45 days or less. Yellow is 90 days or less. Else red. Defaults: max_days 120, stuck_days 60.",
-          'Dollar translation: sum of amount on stuck deals \u2192 "stuck in pipeline".',
-          "Layer 2 of the gating stack, with Drop Rate.",
-          "Trigger play: Unstick the Pipeline (unstick-pipeline) when the score is weak.",
-          "Levers: stage-age report. Past-due close cleanup. Progression plans on stuck deals. Forecast hygiene on optimistic close dates."
+          "Status uses average open age. Green \u226445 days, yellow \u226490, else red. Defaults: max_days 120, stuck_days 60.",
+          'Dollars: sum of amount on stuck deals \u2192 "stuck in pipeline".',
+          "Read with Drop Rate \u2014 stuck deals and handoff leaks often show up together.",
+          "Weak score \u2192 play Unstick the Pipeline.",
+          "Useful moves: stage-age report, past-due close cleanup, progression plans on stuck deals, forecast hygiene on optimistic close dates."
         ],
         visual: {
           kind: "funnel",
@@ -13067,21 +13067,21 @@ var init_metric_definitions = __esm({
         kind: "vital",
         label: "Drop Rate",
         group: "Vital Signs",
-        tagline: "Where does paid demand fall between systems before anyone works it?",
-        how_computed: "NTRP blends cross-system retention and opportunity retention. Cross-system retention is marketing people also present in sales. Opportunity retention is open opportunities that are not abandoned. Default weights: cross-system 60 percent, opportunity retention 40 percent. Abandoned means open opportunities with no activity in 30 days.",
+        tagline: "Where does paid demand fall between systems before a rep works it?",
+        how_computed: "We blend two checks: do marketing people also show up in sales CRM, and are open deals still being worked (not abandoned). The formula lines show the weights and the 30-day abandon window.",
         formula_lines: [
           "score = crossSystemRetention\xD70.6 + oppRetention\xD70.4",
           "cross-system = marketing people also in sales CRM",
           "abandoned = open opps with no activity in 30d"
         ],
-        meaning: 'We read Drop Rate as the price of the handoff leak \u2014 budget already spent on leads that never reach a working rep. The dollar estimate is droppedCount \xD7 conversion \xD7 avg deal size: "est. lost at handoff."',
-        expert_read: 'In practice this usually looks like a systems story: routing rules, unassigned territories, dead rep queues, or a sync gap between marketing and CRM \u2014 more often than "lazy reps." A useful first cut is by lead source; the leak tends to concentrate in one or two sources. The cheapest pipeline a business can buy is often the leads it already paid for.',
+        meaning: 'Drop Rate prices the handoff leak \u2014 money you already spent on leads that never reach a working rep. Like buying groceries and leaving half the bags in the parking lot. The dollar line is "est. lost at handoff."',
+        expert_read: "A useful first cut is by lead source \u2014 the leak usually concentrates in one or two, not everywhere. Routing rules, unassigned territories, dead queues, or a sync gap between marketing and CRM show up more often than lazy reps. The cheapest pipeline you can buy is often the leads you already paid for.",
         deepdive: [
-          "Status bands: green 80 or more, yellow 60 or more, red below 60.",
-          'Dollar translation: dropped \xD7 conversion \xD7 avg deal (fallback: drop% \xD7 open pipeline) \u2192 "est. lost at handoff".',
-          "Layer 2 of the gating stack, with Flow Rate.",
-          "Trigger play: Fix the Handoff Gap (fix-handoff-gap) when drop is high.",
-          "Levers: source-level handoff audit. Routing and sync repair. Time-to-first-touch SLA. Weekly marketing-only-leads report."
+          "Green 80+, yellow 60+, red below 60.",
+          'Dollars: dropped \xD7 conversion \xD7 avg deal (fallback: drop% \xD7 open pipeline) \u2192 "est. lost at handoff".',
+          "Read with Flow Rate \u2014 handoff leaks and stuck deals often show up together.",
+          "Weak score \u2192 play Fix the Handoff Gap.",
+          "Useful moves: source-level handoff audit, routing and sync repair, time-to-first-touch SLA, weekly marketing-only-leads report."
         ],
         visual: {
           kind: "funnel",
@@ -13106,21 +13106,21 @@ var init_metric_definitions = __esm({
         kind: "vital",
         label: "Signal:Noise",
         group: "Vital Signs",
-        tagline: "How much of the team's effort still aims at deals that can close?",
-        how_computed: "Over a 90-day lookback, NTRP computes (signal activities / all activities) \xD7 100. Signal is activity linked to an open opportunity, a pipeline person, or a pipeline organization.",
+        tagline: "How much effort still aims at accounts that can close \u2014 versus dead ends?",
+        how_computed: "We look at the last 90 days of activity and ask what share is signal \u2014 linked to an open deal, a pipeline person, or a pipeline company. The formula lines show the ratio and what counts as signal.",
         formula_lines: [
           "score = (signalCount / activityCount) \xD7 100",
           "signal = linked to open opp / pipeline person / pipeline org",
           "lookback = trailing 90 days"
         ],
-        meaning: `We treat Signal:Noise as activity efficiency with a capacity price. Noise hours \xD7 hours_per_activity \xD7 rep_hourly_cost becomes "misdirected effort" \u2014 energy aimed at accounts that can't still close.`,
+        meaning: 'Signal:Noise asks whether activity still points at deals that can close. Noise hours are capacity spent on dead ends. Like a radio stuck between stations \u2014 lots of static, little signal. Those hours show as "misdirected effort."',
         expert_read: "A useful cut is by rep and by account status. Persistent noise often means reps keep working dead accounts they already know \u2014 stale targeting or coverage models more than a coaching gap. Also check whether activity is logged against closed or unlinked records; that can be a hygiene artifact pretending to be effort.",
         deepdive: [
-          "Status bands: green 65 or more, yellow 40 or more, red below 40.",
-          "Dollar defaults: 0.25 hours/activity \xD7 $75/hr (config: hours_per_activity, rep_hourly_cost).",
-          "Layer 3 of the gating stack. Trust Freshness, Flow Rate, and Drop Rate before you read activity efficiency.",
-          "Trigger play: Retarget Misdirected Effort (retarget-effort) when the score is low.",
-          "Levers: refresh account lists. Signal-based targeting. Stop logging against closed or unlinked records. Coverage-model redesign."
+          "Green 65+, yellow 40+, red below 40.",
+          'Dollar defaults: 0.25 hours/activity \xD7 $75/hr (config: hours_per_activity, rep_hourly_cost) \u2192 "misdirected effort".',
+          "Read Freshness, Flow Rate, and Drop Rate before you trust this score.",
+          "Weak score \u2192 play Retarget Misdirected Effort.",
+          "Useful moves: refresh account lists, signal-based targeting, stop logging against closed or unlinked records, coverage-model redesign."
         ],
         visual: {
           kind: "split",
@@ -13143,21 +13143,21 @@ var init_metric_definitions = __esm({
         kind: "vital",
         label: "Thread Depth",
         group: "Vital Signs",
-        tagline: "How fragile is revenue if one champion changes jobs?",
-        how_computed: "Percent of open deals with at least multi_thread_threshold distinct people active in the last 90 days. The default threshold is 2. People include opportunity-direct contacts and same-organization activity.",
+        tagline: "How fragile is a deal if one champion changes jobs?",
+        how_computed: "We ask what share of open deals have at least two people active in the last 90 days. Contacts on the deal and activity at the same company both count. The formula lines show the threshold.",
         formula_lines: [
           "score = % open deals with \u22652 active people (90d)",
           "people counted via opp contacts + same-org activity",
           "threshold configurable (default 2)"
         ],
-        meaning: "We read Thread Depth as resilience risk. One single-threaded mega-deal can outweigh ten small ones \u2014 and late-cycle single-threading is especially scary because champions change jobs. The dollar line sums amount on single-threaded deals.",
-        expert_read: "Weight by deal size when you triage. Single-threading late in the cycle tends to matter more than early. In enterprise motions, thin threads are often a leading indicator of slipped quarters: the champion leaves and there's no second contact warm enough to carry the deal.",
+        meaning: 'Thread Depth asks how many people keep each deal warm. One contact is a single point of failure \u2014 if they leave, the deal often dies with them. Like a bridge with one cable. Dollars on thin deals show as "single-threaded."',
+        expert_read: "Weight by deal size when you triage \u2014 one thin mega-deal can outweigh ten small ones. Late-cycle single-threading tends to matter more than early. In enterprise motions, thin threads often lead to slipped quarters: the champion leaves and nobody else is warm enough to carry the deal.",
         deepdive: [
-          "Status bands: green 65 or more, yellow 40 or more, red below 40.",
-          'Dollar translation: sum of amount on single-threaded deals \u2192 "single-threaded".',
-          "Layer 4 of the gating stack. Read this last, after the upstream vital signs.",
-          "Trigger play: Multi-Thread Your Deals (multi-thread-deals) when depth is low.",
-          "Levers: buying-committee map. Warm internal referral first. CRM contact roles. Mid-stage single-thread alerts. Champion job-change signals."
+          "Green 65+, yellow 40+, red below 40.",
+          'Dollars: sum of amount on single-threaded deals \u2192 "single-threaded".',
+          "Read this last, after Freshness, Flow Rate, Drop Rate, and Signal:Noise.",
+          "Weak score \u2192 play Multi-Thread Your Deals.",
+          "Useful moves: buying-committee map, warm internal referral first, CRM contact roles, mid-stage single-thread alerts, champion job-change signals."
         ],
         visual: {
           kind: "bars",

package/package.json

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