Anti-Newsjacking and Ethical Context Use

1. The real problem: visibility is not permission

A public event suddenly trends and a content team proposes a same-day article that attaches a product promotion to it. The topic may be lexically related, but attention alone is not a reason to publish when the reader gains little practical help or the context is sensitive. This lesson builds a gate that checks four independent questions before using live context: Is the event genuinely relevant? Does it create defensible user benefit? Do we have appropriate authority? Are sensitivity, harm, and opportunism controlled?

2. Lesson boundary and owned artifact

The owned artifact is Ethical Context Use & Anti-Newsjacking Gate v1. It produces bounded USE, ADAPT, DEFER, or DO_NOT_USE decisions and preserves UNKNOWN, INSUFFICIENT_DATA, and REVIEW_REQUIRED when evidence is incomplete. PLN-013 owns crisis-envelope detection and PLN-015 owns trend observation and pattern status. This lesson does not determine crisis severity or build durable trend patterns.

3. Record the Context Candidate before judging it

Each candidate should retain context identity, event relevance, user value, audience need, content authority, sensitivity level, harm risk, commercial opportunism, search-manipulation risk, evidence source, context expiry, disclosure need, review owner, and audit reference. Filling these fields after a decision invites rationalization. The correct order is Evidence → Gate → Decision → Audit.

4. People-first is an operational boundary, not a slogan

Current Google Search guidance emphasizes content created primarily to help people rather than content produced mainly to attract search traffic; it also lists writing about things simply because they appear trending as a warning sign that the content approach should be reevaluated [GOOGLE-HELPFUL]. This is not a complete ethical code, but it gives a useful boundary: if the primary reason is attention and the intended audience lacks clear independent value, the gate should become more restrictive.

5. Scaled content abuse clarifies a Search-policy boundary

Google's spam policies describe scaled content abuse as generating many pages primarily to manipulate rankings rather than help users [GOOGLE-SPAM]. That does not prove every opportunistic article is spam. It does mean that turning live context into a high-volume factory for low-value pages should raise explicit search-manipulation risk, and DO_NOT_USE can be a valid outcome.

6. Gate one: genuine relevance is not lexical similarity

event_relevance passes only when the event materially changes a user situation, product workflow, operational constraint, or decision. Sharing a keyword with the brand is not genuine relevance. A useful test is: if the trending name disappears from the headline, would this audience still have a specific reason to need the content? If not, the context is probably decorative or opportunistic.

7. Gate two: user value must stand apart from attention

User value means the reader can do something better, understand a real risk, make a more informed decision, or manage a changed workflow after reading. "It will get traffic," "competitors covered it," and "the topic is hot" are not user value. Direct relevance with unclear benefit is still insufficient for USE; the appropriate outcome may be ADAPT, DEFER, or DO_NOT_USE.

8. Gate three: content authority is different from brand trust

Even when the issue matters to users, the team must have suitable evidence and scope to explain it. Authority includes traceable sources, relevant expertise, fact-check capability, and an identified review owner. High trend velocity cannot repair missing authority. If the event moves quickly but reliable evidence or a competent reviewer is unavailable, DEFER is safer than fast speculation.

9. Gate four: sensitivity and harm risk can change the route

Contexts involving human harm, crisis, death, health, security, or vulnerable groups deserve stricter handling. This lesson does not invent universal legal rules. It requires higher authority, review, and disclosure as sensitivity and harm increase. When exploiting distress or amplifying harm cannot be resolved by adaptation, DO_NOT_USE is a legitimate end state.

10. Opportunism and search manipulation are separate risks

Commercial opportunism asks whether the brand is using the context to push an inappropriate sale or call to action. Search-manipulation risk asks whether the context is selected mainly to capture rankings or produce low-value pages. One can be high while the other is low, so they must remain separate fields. The decision should identify which risk triggered ADAPT, DEFER, or DO_NOT_USE.

11. State machine: USE, ADAPT, DEFER, and DO_NOT_USE

USE requires direct relevance, clear user value, sufficient authority, and controlled sensitivity/risk. ADAPT means the context can be used only after changing angle, CTA, disclosure, scope, or tone. DEFER means evidence, authority, review, or freshness is not closed. DO_NOT_USE applies when attention value exceeds defensible user value, relevance is not genuine, or risk remains unacceptable. Preserve REVIEW_REQUIRED and UNKNOWN for unfinished states rather than forcing a Boolean decision.

12. Expiry, disclosure, and review triggers are part of the decision

Live context expires. context_expiry should identify when evidence must be refreshed. Record disclosure_need when sponsorship, automation, expertise limits, or another material context needs to be visible. review_owner should identify a person or role able to reproduce the decision and own the review. A decision without expiry and review ownership is not auditable.

13. Worked example: public event plus product promotion

Suppose a brand sees a fast-moving public event and proposes an article that mostly attaches the event name to a product while offering little practical help. event_relevance=LEXICAL, user_value=LOW, and commercial_opportunism=HIGH. Even with a strong trend signal and a reliable news source, the gate returns DO_NOT_USE because attention cannot substitute for genuine relevance and user value.

14. Deterministic negative cases

Four shortcuts are intentionally rejected: 1) lexical relevance with no user value → DO_NOT_USE; 2) high trend velocity with insufficient content authority → DEFER; 3) sensitivity rises from LOW to HIGH while the old decision is left unchanged → REVIEW_REQUIRED or DO_NOT_USE depending on harm/opportunism; 4) a live-event headline is copied into unrelated evergreen content → DO_NOT_USE. Stale evidence or incomplete provenance also blocks USE.

15. Transfer: a benign announcement that truly changes the workflow

Now evaluate a benign industry announcement that directly changes a product API or workflow. Here event_relevance=DIRECT, user value is clear, authority is sufficient, and sensitivity is low. The gate should not block it merely because the context is live; complete evidence can support USE or, if framing needs adjustment, ADAPT. The contract remains stable while the decision is recomputed from the new context.