buzzword-hijack

# Buzzword hijack ## Contract | Field | Bound contract | |---|---| | Trigger | User wants to choose and execute a bounded positioning move that rides a jargon wave without confusing trend with truth. | | Authority | Write only the named local positioning artifact (copy, landing, or messaging). Rollback: delete or revert the written artifact; no external channel is touched. | | Side effect | A bounded positioning move/artifact is written to a local file. No publish, deploy, or remote mutation. | | Done | A bounded positioning move is executed and the artifact is written without confusing trend with truth. | ## Inputs - The product, project, or message to position. Required. - The target surface for the positioning move: copy, landing page, or messaging. Required; state it before writing. - The jargon wave to ride: the trending term or terms the user wants to use. Required; name the specific term(s). - The output file path. Required. ## Procedure 1. Name the jargon wave: identify the specific trending term(s) the user wants to ride and the space they belong to. **Done when:** the jargon wave and its space are named. 2. Separate trend from truth: list every factual claim about the product. Mark each claim that holds independently of the jargon. Any claim that only holds because of the jargon is a truth-substitution and must be removed or re-grounded. **Done when:** every factual claim is marked as holding independently or flagged as truth-substitution. 3. Choose the bounde...