Two different objects. Do not model a personal digest as a space report.
Personal digest (opt-in)
Each person who wants one enables a private weekday digest from Overview › Needs attention › Customize. It is not a repository chain, not on the Reports page, and not something an admin can turn on for someone else. It requires the member’s Warestack session; a GitHub PAT cannot authorize it.
| Fact | Behavior |
|---|---|
| Object | One personal_digest chain per person per space, hidden from the Chains list |
| Source of truth | Overview › Needs attention › For me (review requests, changes requested, failing checks, deployment approvals, rule violations on my PRs) |
| Message | Dated snapshot of those rows; Overview stays live |
| Schedule | Weekdays · daily or Mon/Wed/Fri · HH:MM in the person’s timezone |
| Surface | Slack Messages (default) or account email — one surface |
| Enable | Immediate confirmation (“You’re set”); first populated scheduled morning is the real digest |
| Empty | No message (skipped). Silence is the signal |
| Cap | 5 lines per source, 12 total, then “+N more in Today →” (opens Overview) |
| Header | Your Thursday · 3 things need you plus new · still waiting · cleared since the last posted digest |
| Actions | Open Today (Overview) · Change schedule · Turn off |
| History | Last 7 final runs in Customize: sent, skipped, failed, or confirmation, with up to 2 delivery attempts |
| Failure | Never sends a half-list; one retry about 10 minutes later, then a visible failed outcome |
Weekly space digest
A saved report plus a scheduled_report chain.
- When: the calendar you set (typical: Monday, local time).
- What: in-scope repos — merged PRs, still-open findings, reviews waiting, PRs missing a linked Linear issue, SLA breaches — whatever SQL the saved report holds.
- Where: the Slack channel you name, plus CSV on the report page.
Run now on the report rebuilds SQL. posted stays empty. Slack announce is the chain’s calendar step, not Run now.
The personal digest is optional in the recommended first enablement; it is useful so owners and reviewers see the same attention list the live card already uses. See Overview and attention.
Propose this when
| Need | Object |
|---|---|
| Weekly sample for Vanta or eng ops | Chain scheduled_report + a report intent from /catalog.json |
| Reviewers already in Slack who miss GitHub noise | personal_digest candidates only — they enable Overview › Needs attention › Customize |
Do not
- Model a personal digest as a report or pin it on the Reports page.
- Have an admin “enable digest for the team.”
- Treat Run now as the Slack announce.
Last updated on