A report is a saved query with a run history (natural-language ask → review the SQL → preview rows → save). A chain is the only thing that decides when it runs and where the result goes.
The personal digest is not a report. Do not pin it on the Reports page.
Build and inspect
- Describe the population in natural language.
- Review the generated SQL rather than treating it as hidden agent reasoning.
- Preview rows.
- Save the report.
- Use Run now for a fresh result and run history.
- Add a
scheduled_reportchain when the result should be delivered.
Optional AI analysis can help interpret a report, but the saved SQL, rows, timestamps, and delivery history are the evidence.
Weekly space digest
The weekly operating picture — and a sampleable change population: the set an auditor would sample, not a handful of screenshots.
See Digests. Run now completes SQL; Slack announce is the Monday (or your calendar) chain step.
You can add or rewrite reports after you see the first runs. The chain is how they get to Slack.
Propose these intent IDs
Use the IDs from /catalog.json. Do not invent SQL in a first draft.
| ID | Title |
|---|---|
report.failed_workflow_runs_7d | Failed workflow runs from the past 7 days |
report.merged_prs_open_findings | Merged PRs still showing unresolved high findings |
report.prs_missing_linear | Open or merged PRs missing a Linear association |
report.reviews_waiting | Requested reviews with no human review |
report.sla_breaches | Review SLA breaches in the window |
report.repos_missing_owner | Governed repos missing an individual owner |
report.failed_production_deploys | Failed production deployments |
First delivery: one scheduled_report chain (typical Monday local time) to the named Slack channel. Prefer report.merged_prs_open_findings as the sampling population unless another intent matches the last 14 days better.
Do not
- Pin
personal_digeston this page. - Treat Run now as Slack announce.
CSV
Scheduled-report notify can attach a summary link, CSV, or both. The Slack card is provenance + title + run time + rows + Open report — not an inline row dump.
See Automation activity for the delivery execution and Events for the underlying change timeline.