# Return-after-silence detection recipe

A source-specific timing method for flagging an unusual publication gap and preserving both boundary posts.

## Calculation

- Mode: radar_return_after_silence
- Formula: current_gap = returning_post_time - previous_indexed_post_time; compare current_gap with eligible historical gaps for the same source.

## Query

In [selected sources] during the [Radar window], identify returns after unusually long publication gaps. Show current gap, source-specific historical baseline, sample size, confidence, the prior post, the returning post, timestamps, permalinks, and known history gaps. Do not infer motive or activity outside indexed Telegram history.

## Inputs

- **Selected sources:** Channels for which inactivity and return are meaningful.
- **Recent window:** The 24-hour, 3-day, or 7-day period searched for returning posts.
- **Historical intervals:** Eligible same-source publication gaps used as the baseline.
- **Coverage status:** Known history start, missed ingestion, and availability limitations.

## Expected output

- Source and measured gap
- Historical interval baseline
- Previous and returning timestamps
- Two direct evidence links
- Confidence and coverage caveat

## Coverage checks

- [ ] Never use one silence threshold for every source
- [ ] Treat missed history as a confidence limit
- [ ] Do not infer off-platform inactivity
- [ ] Cite both posts that define the gap
- [ ] Describe the signal as source-specific