Health updates
Publish human-authored health reports for Features and Initiatives.
Health updates are structured status reports for Spec-Driven Development work. They help a team answer whether a Feature or Initiative is on track, what changed since the last report, and where follow-up conversation belongs.
Each update is authored by a person. Integrity can show changed planning context and due reminders, but it does not rewrite health automatically and agents do not publish updates for you.
An authorized coding agent may read the latest or a bounded recent history of the same visible updates. Agent results use authored plain text and display-safe references; rich editor content, generated context, deleted bodies, and inaccessible child-Feature evidence remain unavailable. Publishing or editing an update still requires an explicit command, and recoverable deletion requires confirmation.
What an update includes
| Part | Meaning |
|---|---|
| Health | The author's current signal: On track, At risk, or Off track. |
| Report body | Rich text for progress, risks, blockers, next steps, or context. |
| Changed context | Display-safe planning rows such as status, priority, Team, lead, owner, dates, Version, relationships, or Feature counts. |
| Discussion | Update-scoped comments, replies, emoji reactions, and edit history using the shared Activity system. |
| Freshness | A schedule-derived state such as current, due soon, overdue, missing, or not expected. |
Health is authored. Freshness is derived. An overdue update does not silently turn the last report from On track into At risk or Off track.
Where updates appear
- Feature and Initiative Overview pages show the latest authored update when one exists.
- Feature and Initiative Activity pages show health updates in the mixed Activity feed with comments, reactions, and property history rows.
- Feature and Initiative tables show compact Health and Health updated scanning context.
- Inbox can show internal update-due reminders for visible objects.
Visibility and safety
Health updates follow the visibility of the underlying Feature or Initiative. Private Teams, hidden private Issues, restricted references, deleted users, and unavailable objects are omitted or rendered as display-safe references. Notification payloads and Activity rows re-check access instead of treating an old update as permission.