@sellable/install 0.1.55 → 0.1.57
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/package.json
CHANGED
|
@@ -92,8 +92,16 @@ clear business decisions, tradeoffs, and approval gates. Use product language:
|
|
|
92
92
|
When explaining lead-source decisions, show the concrete counts behind the
|
|
93
93
|
logic: lanes searched, timeframe, raw result counts, finalist posts or preview
|
|
94
94
|
rows, sampled people, sampled fits as n/N (%), estimated usable people, and the
|
|
95
|
-
confidence basis.
|
|
96
|
-
|
|
95
|
+
confidence basis. Break estimates out by provider/source angle in bullet form
|
|
96
|
+
instead of showing only one raw total. Each angle should show raw pool, sampled
|
|
97
|
+
fits as n/N, estimated good-fit range after cleanup, expected reply-rate range,
|
|
98
|
+
and confidence basis. Never show a percent like "73% match" without the
|
|
99
|
+
numerator, denominator, and sample basis.
|
|
100
|
+
|
|
101
|
+
Use rendered Markdown for campaign brief and lead-source chat, not fenced code
|
|
102
|
+
blocks. Keep lines short, use indexed section labels, and translate internal
|
|
103
|
+
sourcing terms into plain language. For example, explain "signal discovery" as
|
|
104
|
+
"looking for LinkedIn activity from people already talking about this problem."
|
|
97
105
|
|
|
98
106
|
Every approval gate must include artifact access after the readable inline
|
|
99
107
|
content. Show an `Open artifact:` line with the one key clickable markdown link
|