# Comparable engagement-spike recipe

A reviewable specification for identifying unusually strong recent post metrics without mixing measurement ages.

## Calculation

- Mode: radar_engagement_spike
- Formula: Compare one recent captured metric at horizon H with the same source's eligible historical values at H; emit only when readiness, sample, and anomaly thresholds pass.

## Query

For [selected sources] in the [24-hour, 3-day, or 7-day window], report engagement-spike signals. For each, name the metric, shared post-age horizon, observed value, source baseline, historical sample, confidence, coverage states, publication time, and evidence link. Do not describe a signal as viral or causal.

## Inputs

- **Source set:** Public indexed Telegram channels selected for Radar.
- **Radar window:** The recent 24-hour, 3-day, or 7-day evaluation period.
- **Metric readiness:** Comparable captured horizons and coverage states for recent and historical posts.
- **Review threshold:** The anomaly and confidence rule used to create a triage item.

## Expected output

- Trigger metric and observed value
- Comparable horizon and source baseline
- Historical sample and confidence
- Coverage and readiness state
- Cited triggering post

## Coverage checks

- [ ] Never compare unequal post ages silently
- [ ] Never treat missing metrics as zero
- [ ] Keep baselines source-specific
- [ ] Treat signals as review leads, not causal findings
- [ ] Open the cited post before escalation