Stale decisions due for revisit
stale_decisionsFlags decisions that need revisiting when their revisit date passes or a stale condition matches later activity, providing reasons for follow-up.
Instructions
Decisions due for a revisit — past their date, or with a triggered stale condition.
Two deterministic rules. Date-based (flag="revisit_due"): events whose
revisit_after has passed AND the entity is still live (queried via
blame/diff/prior_attempts after the decision, or its changeset saw
later activity) — pure age alone never surfaces. Condition-based
(flag="review_suggested"): events whose stale_when text shares
keywords with a LATER change event — the named invalidation evidence may
have happened. Surfacing only: nothing is un-retired automatically;
follow up with a supersede if the condition really was triggered.
Each result is the change event plus flag, revisit_due,
days_overdue, active_use_signals, matched_terms,
matched_event_id, and a one-line stale_reason. Date-due rows first,
most-overdue leading; filter by entity_path, project, or agent.
Templated and deterministic; no LLM call.
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| agent | No | Optional filter to the agent that logged the decision. | |
| limit | No | Maximum number of results. | |
| project | No | Optional filter to a specific project/repository. | |
| entity_path | No | Optional filter to a single entity or path prefix — 'users' also covers 'users.email'. Empty = every entity. |
Output Schema
| Name | Required | Description | Default |
|---|---|---|---|
| result | Yes |