Context Radar and Crisis Envelope

1. The real problem: a strong trend is still not a decision

A promotional article is scheduled for today while several external signals indicate a fast-moving public-service disruption in the same audience region. A search surge can draw attention, but by itself it proves neither event severity, relevance to the planned item, nor permission to publish or stop. This lesson builds a Context Radar that records a signal with time, region, freshness, relevance, verification, and uncertainty, then applies a Crisis Envelope to the plan.

2. Lesson boundary and owned artifact

The owned artifact is Context Radar & Crisis Envelope Matrix v1. The radar collects observation and evidence; the envelope issues only bounded CONTINUE, CONSTRAIN, PAUSE, or ESCALATE actions with expiry and resume conditions. When evidence is incomplete, preserve UNKNOWN, INSUFFICIENT_DATA, DEFERRED, REVIEW_REQUIRED, or REJECTED. PLN-012 owns Audience Fit and PLN-014 owns Anti-newsjacking; this lesson does not absorb those outcomes.

3. Separate observation, inference, and action

Each radar row records at least context_signal, signal_source, observed_at, freshness_window, region, topic_cluster, baseline_interest, trend_velocity, relevance_score, verification_state, severity_indicator, and provenance_ref before action. “Search interest surged” is an observation; “this event is a crisis for our plan” is an inference; PAUSE is an action. Collapsing these layers destroys auditability.

4. What Trending Now actually tells you

Current Google Trends guidance says Trending now surfaces searches experiencing recent surges, supports timeframe/status/location filtering, and refreshes fresh trend data on average about every ten minutes [GT-NOW]. That makes it useful as a signal source, but Google does not define the signal as event severity or permission to act. In the matrix, a trend is one timestamped input.

5. Trends is sampled and relative, not an absolute event counter

The official Google Trends FAQ explains that Trends uses a sample of real searches, with anonymized, categorized, aggregated data, and normalizes results to time and location [GT-FAQ]. A value of 100 or a spike is therefore not absolute event severity. Google also warns that Trends is not a perfect mirror of search activity and should be considered one data point among others. trend_velocity must never map directly to severity_indicator or PAUSE.

6. Freshness gate: do not make a stale signal look recent

observed_at and freshness_window must support a reproducible is_fresh check. A signal outside its window is STALE even if visually dramatic. The primary failure probe attempts to make old evidence appear current; the oracle accepts freshness only when provenance and timing agree. Historical data may inform context, but it is not a live trigger.

7. Region gate: the right trend in the wrong place can still be irrelevant

Normalized interest depends on time and location, so region is part of evidence identity. If the same term trends in another region while the underlying event is unrelated to the planned audience, the previous decision must not be copied. region_match=false constrains relevance and may lead to CONTINUE, DEFERRED, or REVIEW_REQUIRED, not automatic PAUSE.

8. Corroboration gate: one fast source is not complete authority

The radar keeps verification_state independent from trend strength. A single signal can remain UNVERIFIED or PARTIAL; corroboration means sufficient independent evidence for the same event, region, and window. If apparent severity remains HIGH while corroboration is removed, the workflow must not preserve a strong action. The deterministic probe sends that state to review rather than pretending certainty.

9. Relevance gate: the event must affect a specific planned item

relevance_score must bind to affected_content and the current plan's audience/region. A crisis envelope is not a global stop button for every piece of content. Ask whether the observed event now changes the risk, appropriateness, or interpretation of this item. If not, the signal can stay in the radar while the envelope remains CONTINUE.

10. Keep severity indicator separate from trend velocity

severity_indicator should come from verified evidence about contextual impact, not simply from search acceleration. Trend velocity may be high for a low-impact or wrong-region event; a meaningful disruption may also have only moderate search volume. This lesson uses a bounded severity field and does not invent a universal crisis scale.

11. Crisis Envelope: four bounded actions

CONTINUE means current evidence does not justify altering the plan. CONSTRAIN means continue with bounded changes to scope, CTA, timing, or distribution. PAUSE temporarily stops the affected item pending recheck. ESCALATE routes evidence or severity beyond this workflow to a human owner. None is permanent; each requires expiry_at and a resume_rule.

12. Expiry and resume rules prevent indefinite holds

An envelope without an exit condition is not governance. expiry_at marks when the decision must be recomputed; resume_rule names the evidence needed to continue, such as sufficient corroboration, region match, and an internally acceptable severity state. If expiry passes without recheck, the old decision is no longer valid and the state moves to REVIEW_REQUIRED or DEFERRED.

13. Worked example: public disruption in the same region

For a scheduled promotion, the signal is fresh, the region matches, two independent sources corroborate the event, relevance to the audience is direct, and fixture severity is HIGH. The matrix produces PAUSE, but only until a declared expiry_at with a finite resume rule. The reason is not “it is trending”; it is Freshness + Region + Corroboration + Relevance + Severity.

14. Deterministic negative cases and failure probes

Four shortcuts are rejected: 1) stale signal disguised as current → REJECTED or DEFERRED; 2) wrong-region trend → do not copy the prior pause; 3) corroboration removed while severity stays high → REVIEW_REQUIRED; 4) envelope expires without rechecking affected content → DEFERRED. Missing provenance or unknown relevance also blocks a strong action.

15. Transfer: same term, different region, unrelated event

Now the same search term surges in another region, but the underlying event is unrelated to the promotion. The contract stays fixed: signal, source, freshness, region, verification, relevance, severity, envelope, expiry, and resume rule are recomputed. This time low relevance can produce CONTINUE. Transfer succeeds when the conclusion is regenerated from new evidence rather than copied from the baseline.