Stale alerts
/authoring/scribe/stale-alerts
PreviewScribe previewscribe
When a version is re-imported, Spire's stale detection compares every documented target's source digest with what the documentation was written against and raises an alert where they differ. The Stale Documentation Alerts page is the review queue. Without a scope: "Choose a project and version to review the documentation Scribe flagged as out of date."
The page
- Tiles: Flagged today, Pending review, Dismissed (7 days), Auto-resolved.
- A toolbar — "N items · K selected" — with Dismiss selected and type chips All, path, schema, property; Dismiss all in the header.
- A table: checkbox, Project / Type, Field, Change summary, Flagged, Actions. Expanding a row shows the Current description beside the Suggested update; with none, "No suggested rewrite yet — open the target in the workspace to regenerate it."
Empty: "No stale alerts — every description is up to date with the spec." or "No alerts match this filter."
Update or dismiss
| Action | Does |
|---|---|
| Update — "Apply the suggested rewrite and resolve" | Writes the suggested rewrite as the target's description in Spire, marked as AI-provenance, and resolves the alert |
| Dismiss | Marks the alert dismissed; the documentation is unchanged |
The rewrite goes to Spire's documentation content. To see and keep it in the Designer catalog as well, open the target in the content workspace.
The dashboard's Stale Alerts card counts something different — catalog paths not reviewed in 90 days — while this page lists the alerts detection raised.