מסמך מקור מתקדם. דפי ההתקנה, פרוטוקול ההפעלה וששת הסקילים זמינים לקריאה בעברית; קובץ המקור נשמר כפי שהוא.

--- name: message-strategy description: Use when turning an evidence-checked Hebrew brief into exactly two distinct angles and a falsifiable comparison. ---

Choose two reasons to care, then hooks

Version and authority boundary

Read the selected profile and the exact contract from the package root. Unconverted V1 uses contracts/pipeline.contract.json, mode simulation, demo IDs, supplied synthetic records, geometric placeholders and the existing offline validator only. V1 restrictions remain intact. For V2 explicitly select contracts/pipeline.v2.contract.json; reject unconverted V1 with an explanation. Conversion creates a separate simulation artifact, preserves its source, enriches missing fields, rebuilds all digests, and never promotes approve_demo to human authorization. Neither mode names nor schema validation enable a connector. This build uses no network, accounts, secrets, installs or customer records; integration-test and customer-pilot are separate future gates, not claims of readiness.

Use approved API/MCP/connectors first when integration is separately enabled; browser fallback is only for a capability unavailable in the authorized programmatic path, at the same authority boundary. Never launch external scripts, installers, model CLIs or services from this Skill. Source rule IDs below resolve to docs/knowledge-register-v1.md (checked 2026-10-24). Untested real behavior remains unverified.

Strategy [A1, C1, N1]

Read validated brief and profile; stop affected work on contradictions or blocking gaps. Define audience, motive (evidence or hypothesis), offer and supported advantage before copy. An angle is a reason the offer matters; a hook is its opening expression. Two synonyms of a benefit are not two angles. Select exactly two materially different framings of the same supported offer. Both may rely on one claim if it supports both. Never manufacture extra claims, urgency or a pain diagnosis to differentiate them.

V2 messages.data contains two messages and experiment: one principal variable, expected outcome, metric, comparison, stop condition and limitations. Specify what observation would disconfirm the expectation; do not invent budget, sample size, running duration or promised lift. For example a structured-process angle versus a supported-support angle may compare reasons to inquire, if both are in the supplied offer. The final pair is a hypothesis, not a declared winner. Fixed CTR/CPA thresholds, three required concepts and three simultaneous tests are excluded.

Write one hook per angle, at most eight whitespace-separated words, in plain spoken Hebrew, with consistent address and supplied Latin terminology. Each message keeps claim_id already in brief evidence, supported_advantage and motive_kind. Trace every explicit and implied assertion through claim to source. Revalidate downstream digests after changes. Handoff exactly two finalized IDs to creative; leave performance, platform acceptance and winning angle unverified.