Update reminders
Configure expected update schedules and understand stale or missing health.
Update reminders define when a Feature or Initiative is expected to receive a fresh health update. They are internal Integrity reminders, not Slack, email, browser push, mobile push, webhook, or external delivery.
Schedules
Workspace Project updates settings define the default expectation. A Feature or Initiative can follow that default, use a custom weekly schedule, or set updates to Never.
Supported expectation intervals include No expectation for updates, Every week, and Every 2 weeks through Every 8 weeks. Custom schedules use a weekday and one-hour time window.
Freshness states
| State | Meaning |
|---|---|
| Current | The latest authored update satisfies the schedule. |
| Due soon | The next expected update window is approaching. |
| Overdue | An update is expected and the window has passed. |
| Missing | The object has no qualifying update where one is expected. |
| Not expected | Updates are disabled or the object is inactive/closed. |
Freshness is an overlay. It does not edit the last update body, health value, author, or timestamp.
Inbox reminders
Due reminders appear in Integrity Inbox only for visible objects and display-safe recipients. Reminder payloads route back to the Feature or Initiative Activity surface when the object reference is accessible.
For Feature reminders, the first recipient is the accessible Feature lead. If no accessible lead exists, Integrity falls back to visible workspace owners/admins. Reminder rows are deduplicated per user, object, and due window.
Agent boundary
Agents may help draft update text or summarize changed context when a UI exposes that path, but they cannot publish updates, edit/delete updates, reply, react, change schedules, subscribe users, or send notifications without explicit user action.