# Telegram post-view evidence recipe

Use this recipe to attach a public view counter to the right post and retain enough timing information to interpret or compare it responsibly.

## Calculation

- Mode: post_engagement
- Formula: Latest captured views for one resolved SourceItem; reactions and forwards are companion fields from the same snapshot, not part of the view count.

## Query

Locate the specific post in [selected channels] about [topic/date]. Return its latest captured views, reactions, and forwards, the publication timestamp, snapshot age, observation time, and original permalink. Say unmeasured when no captured snapshot exists and explain if several posts could match.

## Inputs

- **Channels:** The selected ready sources allowed to contain the target message.
- **Post clues:** Distinctive subject, wording, channel, date, or prior citation.
- **Comparison need:** Whether this is a standalone observation or will be compared at a shared horizon.
- **Review time:** The date of analysis, kept separate from snapshot collection time.

## Expected output

- Resolved message and direct link
- Captured view count without audience relabeling
- Companion reactions and forwards
- Publication, horizon, and observation timestamps
- Coverage and ambiguity notes

## Coverage checks

- [ ] Never identify viewers from an aggregate counter
- [ ] Never present an absent snapshot as zero views
- [ ] Do not compare differently aged posts without a warning
- [ ] Keep the same snapshot for every companion metric
- [ ] Verify that the resolved post matches the requested topic