Stale decisions due for revisit
stale_decisionsIdentify decisions with past revisit dates that remain actively used. Returns overdue items with reasons and active-use signals to prioritize review.
Instructions
Decisions whose revisit_after has passed AND that are still in active use.
The date-based half of active memory (v0.3.8). Returns events with a
revisit_after now in the past — but ONLY when the entity is still live, so
an old-but-correct decision nobody touches never nags. The required
active-use signal is one of: the entity was queried (blame / diff /
prior_attempts) at or after the decision, or its changeset_id saw later
activity. Pure age alone does NOT surface.
Each result is the change event plus four fields: revisit_due (UTC ISO),
days_overdue (int, 0 on the due day), active_use_signals (list), and
stale_reason (a one-line summary). Most-overdue first; filter by
entity_path, project, or agent. Date-based only — expires_when
evaluation lands in v0.3.11. Templated and deterministic; no LLM call.
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| entity_path | No | Optional filter to a single entity or path prefix — 'users' also covers 'users.email'. Empty = every entity. | |
| project | No | Optional filter to a specific project/repository. | |
| agent | No | Optional filter to the agent that logged the decision. | |
| limit | No | Maximum number of results. |
Output Schema
| Name | Required | Description | Default |
|---|---|---|---|
| result | Yes |