@sellable/install 0.1.160 → 0.1.161
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.
|
@@ -26,11 +26,14 @@ Sellable MCP/product reads:
|
|
|
26
26
|
- optional `campaignName`
|
|
27
27
|
- optional workspace id when known
|
|
28
28
|
- selected source decision and source-use rule
|
|
29
|
+
- source ownership classification: `sender-owned-single`,
|
|
30
|
+
`sender-owned-ambiguous`, or `third-party`
|
|
31
|
+
- source post author/sender match when known
|
|
29
32
|
- `selectedLeadListId` or selected source list context
|
|
30
33
|
- filter choice at branch start
|
|
31
34
|
- concise brief summary: offer, buyer, safe proof, blocked claims
|
|
32
35
|
- 3-5 sample workflow-table rows with `rowId`, name, title, company when
|
|
33
|
-
available, and
|
|
36
|
+
available, signal, engagement type, and whether comment text exists
|
|
34
37
|
|
|
35
38
|
Do not require campaign revision, brief hash, copied row count, review-batch
|
|
36
39
|
count, row hash, or a long review-batch row-id list in the handoff. Use live
|
|
@@ -222,13 +225,27 @@ own revision. The parent renders the revised template and waits for
|
|
|
222
225
|
low-certainty, such as `found you in a thread about [topic], so may be off,
|
|
223
226
|
but this seemed relevant`.
|
|
224
227
|
- Sender-owned post sources are different: if the source post was authored by
|
|
225
|
-
the sender/client and the row proves a reaction/comment,
|
|
226
|
-
|
|
228
|
+
the sender/client and the row proves a reaction/comment, classify it as
|
|
229
|
+
`sender-owned-single` only when the final sender/source-owner match is known.
|
|
230
|
+
A light first-person acknowledgment is allowed for `sender-owned-single`, but
|
|
231
|
+
it must be followed by a soft
|
|
227
232
|
relevance bridge before broad problem or product copy. Use a bridge like
|
|
228
233
|
`figured this might be relevant if LinkedIn is becoming more of a GTM
|
|
229
234
|
channel for [company]` before any broader `a lot of B2B teams...` claim. Do
|
|
230
235
|
not jump straight from `appreciate you showing some love...` to
|
|
231
236
|
`a lot of B2B teams...` or `most teams...`.
|
|
237
|
+
- For sender-owned sources, `found you in a thread`, `saw you in a thread`, and
|
|
238
|
+
`saw you in conversations` are blocked unless the source is truly third-party.
|
|
239
|
+
The branch-level template must either use the first-person acknowledgment plus
|
|
240
|
+
bridge, or omit the source line.
|
|
241
|
+
- If multiple senders may send the campaign, or the final sender/source-owner
|
|
242
|
+
match is ambiguous, do not assume `my post`, `Grace's post`, or any specific
|
|
243
|
+
first-person post voice. Omit the sender-owned source line until row-level
|
|
244
|
+
sender ownership is proven. Neutral low-certainty thread/source language is
|
|
245
|
+
only for truly third-party sources.
|
|
246
|
+
- Do not say `you commented` or name/comment on a comment unless comment text is
|
|
247
|
+
present in row data. If only reaction/support is known, use `showing some
|
|
248
|
+
love` or `showing support`.
|
|
232
249
|
- Every line must make the next
|
|
233
250
|
line feel earned: source/post signal -> relevance bridge -> product/problem
|
|
234
251
|
-> next step. If adjacent lines could be swapped, deleted, or joined with
|