@sellable/install 0.1.94 → 0.1.95
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.
|
@@ -80,6 +80,9 @@ Quality bar:
|
|
|
80
80
|
|
|
81
81
|
- Do not synthesize a lightweight message from general knowledge. The artifact
|
|
82
82
|
must prove the embedded message-review safety-gate workflow ran.
|
|
83
|
+
- There is no generate-message fast mode in this path. The embedded gate is the
|
|
84
|
+
same campaign-launch quality contract used by the parent-thread compatibility
|
|
85
|
+
path, not a lower-quality shortcut.
|
|
83
86
|
- Message generation can start before `lead-filter.md`, but message review
|
|
84
87
|
cannot start until the parent verifies the selected basis rows still pass the
|
|
85
88
|
final filter.
|
|
@@ -128,6 +131,13 @@ Quality gates:
|
|
|
128
131
|
`[insert]`, or `[generated]`.
|
|
129
132
|
- Optional row-specific personalization must be grounded in a row field or
|
|
130
133
|
omitted entirely.
|
|
134
|
+
- Engagement-source personalization is a special case, not the default opener.
|
|
135
|
+
Do not write `saw you {{engagement_context}} on {{post_context}}`, `saw you
|
|
136
|
+
reacted to`, `saw you engaging with`, or equivalent source-citation copy as a
|
|
137
|
+
default hook. Only refer to the prospect's engagement when the line is
|
|
138
|
+
self-aware and low-certainty, for example `not sure if this is too specific,
|
|
139
|
+
but the [topic] thread felt close enough to send`. Otherwise omit the
|
|
140
|
+
engagement signal and use role/company/problem context.
|
|
131
141
|
- Subjects should be short, buyer-relevant, and specific. Avoid `quick
|
|
132
142
|
question`, `demo`, `founder call`, sender names, and generic `outbound`.
|
|
133
143
|
- If the message is plausible but not ready to send, set `Recommendation:
|
package/bin/sellable-install.mjs
CHANGED
|
@@ -929,6 +929,7 @@ updates.
|
|
|
929
929
|
Do not load the full long-form \`generate-messages\` subskill in this
|
|
930
930
|
create-campaign path; if the safety gate cannot safely approve the draft, route
|
|
931
931
|
to revise messaging with the concrete failure.
|
|
932
|
+
This compatibility path is not a generate-message fast mode.
|
|
932
933
|
Do not synthesize \`message-validation.md\` from the brief, lead review, or
|
|
933
934
|
general knowledge.
|
|
934
935
|
5. Create the campaign shell early with the v1 brief so the user can open the
|
package/package.json
CHANGED
|
@@ -561,6 +561,7 @@ updates.
|
|
|
561
561
|
Do not load the full long-form `generate-messages` subskill in this
|
|
562
562
|
create-campaign path; if the safety gate cannot safely approve the draft,
|
|
563
563
|
route to revise messaging with the concrete failure.
|
|
564
|
+
This compatibility path is not a generate-message fast mode.
|
|
564
565
|
Do not synthesize `message-validation.md` from the brief, lead review, or
|
|
565
566
|
general knowledge.
|
|
566
567
|
5. Create the campaign shell early with the v1 brief so the user can open the
|