# Explainable post-review queue recipe

A triage structure that combines implemented Radar signals without pretending to calculate universal importance.

## Calculation

- Mode: radar_activity_spike
- Formula: Queue eligible Radar signals and recent evidence; order by an explicit operational rule while preserving signal type, reason, confidence, and coverage as separate fields.

## Query

Create a review queue for [selected sources] in the [24-hour, 3-day, or 7-day window]. For every item show signal type, reason, baseline, confidence, coverage, excerpt, timestamp, and permalink. Use [explicit operational priority rule], label unavailable detectors, and leave final importance to the reviewer.

## Inputs

- **Monitoring scope:** Selected channels and the current Radar evaluation window.
- **Signal set:** Implemented activity, engagement, return, and recent-post items allowed in the queue.
- **Priority rule:** An explicit team rule such as newest first or highest-confidence first.
- **Review labels:** Relevant, expected, noise, and unresolved feedback categories.

## Expected output

- Ordered review queue
- Signal reason and detector type
- Confidence and coverage
- Cited evidence post
- Reviewer outcome field

## Coverage checks

- [ ] Do not call the queue objectively important
- [ ] Do not hide unavailable signals
- [ ] Keep unlike metrics in separate fields
- [ ] Require a citation for every escalated item
- [ ] Record reviewer feedback instead of deleting inconvenient alerts